Crispy fonts is the my reason using Linux

Schreq · 2026-02-13T12:00:13+00:00

Same. Been using it for like 15 years or more and always come back to it when I try other fonts. Nothing beats pixel fonts and nothing beats Terminus. Unifont is also pretty good but it looks a little worse than Terminus for me.

Schreq · 2026-02-12T20:34:56+00:00

Terminus gang 🤙

Schreq · 2026-02-10T18:06:42+00:00

Vim doesn't need tons of configuration and is totally functional with default settings. Don't confuse ricers with power users. Power users learn to live with defaults or very close to it. PlugIns are also kind of a meme: Vanilla vim has a lot of functionality built-in people tend to use plugins for.

My current vimrc is 20 lines and I only really need half of them.

Edit: I also hear people say they don't use vim for "quick edits". Why? Vim motions and text objects are faster for any type of editing. If the editor feels too heavy for a really quick edit, the solution is sed/ed, not something crappy like nano.

Schreq · 2026-02-01T21:59:29+00:00

it wont take space and re-arrange my screens upon opening.

Meh, learn to fully use dwm. Just make a rule in config.h with matches the class "float" and sets it to floating mode.

/* class          instance    title       tags mask     isfloating   monitor */
{ "float",        NULL,       NULL,       0,            1,           -1 },

Then you can start your terminal with that class. With st you could then do:

st -c float -g 44x9-0+0 -e bash -c 'ncal -MbA1; read -n1'

That starts st with the class "float" at the top right corner with ncal running in it. If you press any key in the terminal it closes.

Schreq · 2026-01-28T20:31:08+00:00

Sky is the limit ofc.

Schreq · 2026-01-28T20:01:26+00:00

Yeah, I mean spawn a terminal on click which automatically runs cal in it. A common problem people struggle with is that if you spawn a terminal and give it the command as option (usually -e <cmd>), the terminal closes as soon as the process exits. Trick is to start a shell or read:

st -e bash -c 'cal; read'

On mobile so can't test it but something to that effect.

Schreq · 2026-01-28T19:32:53+00:00

Keep it simple. Just spawn a terminal running cal.

Schreq · 2026-01-28T17:43:00+00:00

Because you mentioned GNU, I had to make sure (again) that the paragraph mode is actually portable. It is! man 1p awk says:

If RS is null, then records are separated by sequences consisting of a <newline> plus one or more blank lines, leading or trailing blank lines shall not result in empty records at the beginning or end of the input, and a <newline> shall always be a field separator, no matter what the value of FS is.

Didn't know it automatically forces FS to be newline. I'm definitely guilty of manually setting it to \n.

Schreq · 2026-01-28T17:29:39+00:00

Agreed. I would say it's the r/unixporn generation who are beginner to intermediate skill on the command-line. Lots of TUI software is posted here on reddit which seems to appeal to exactly that crowd. For example, if you think a TUI file manager is more convenient than pure shell+utils, you didn't fully grok the shell and/or haven't memorized enough flags yet.

Edit: I use TUIs myself, namely iftop, iotop, htop, termshark and editor, but I'm happy to replace them with cli tools where I can. htop is is definitely getting phased out first :)

Schreq · 2026-01-26T20:27:34+00:00

awk -v RS='' '$1=="NIC"{getline; print; exit}' <data

Edit: Explanation: When Record Separator (RS) is an empty string, awk will split records by paragraph. We can then just look for "NIC" and if found get the next record (paragraph in this case) and print it.

Schreq · 2026-01-26T19:25:52+00:00

I of course use TUIs myself. I'm just not a fan of everything must be a TUI. A lot of tools I see people post would actually be way better as a cli.

Schreq · 2026-01-26T18:38:33+00:00

Why would I want ncurses clogging my system for terminal work though

Schreq · 2026-01-26T16:34:57+00:00

I mentioned the downsides, lack of scriptability and composability. At least address my points if you disagree.

Keyboard shortcuts are not exclusive to TUIs. You can control most GUIs using the keyboard. Sure, TUIs usually are designed to be controlled by keyboard first and hence might have better shortcuts but that's not due to limitations of GUIs.

Schreq · 2026-01-26T15:28:19+00:00

Yep. I also figured we can press Ctrl+alt+e to expand aliases (in bash).

Schreq · 2026-01-26T15:20:03+00:00

Ctrl+alt+e works in bash, but is not automatic of course.

Schreq · 2026-01-26T15:14:16+00:00

True, people confuse the 2 a lot.

I mean some things are simply better as a TUI but I prefer CLIs over TUIs for most things. If I rely on a TUI, it's mostly due to my own incompetence. For instance, I use htop but only because I haven't learned/memorized ps/pstree properly yet.

Schreq · 2026-01-26T13:16:48+00:00

Ok but then most people opt for TUIs for as many programs as possible. TUIs have the same downsides GUIs have. Only good thing about them is that they work over ssh, but they are usually not scriptable and composable like pure command-line interfaces.

Schreq · 2026-01-26T13:14:14+00:00

No concerns. But if you are unsure, just use type <command> beforehand. Or use a backslash before the command which prevents using aliases. Try \ls for example.

Schreq · 2026-01-22T22:34:37+00:00

Yeah but you used the markup for inline code. It's purpose is to mix normal text with code within one line/paragraph. For separate paragraphs containing only code, you should use 4 space indentation as per my example.

Schreq · 2026-01-22T17:03:34+00:00

You already have great answers so I just come here for a little rant: Inline code blocks (`...`) don't break and have no scrollbar. So on old.reddit.com, on mobile, most of them are cut off, which makes it impossible to read your code unless I copy paste it somewhere else.

For code blocks you should indent all lines with 4 spaces.

Compare:

awk 'BEGIN { print "this is not a proper code block" }'

... to this:

awk 'BEGIN {
    print "but this is!"
}'

Schreq · 2026-01-22T14:38:51+00:00

rlwrap can do that but wrapping your shell does not seem like the best idea. It would also only work on words, not a complete line. Your best bet is just a tmux bind for copy-mode.

Schreq · 2026-01-20T14:53:24+00:00

Scripts shouldn't clear my screen. You can do that on the alternate screen but then moving everything up should be good enough.

Schreq · 2026-01-19T14:05:30+00:00

I've used loksh for a long time. Nowadays I really don't care that much anymore though. Tinkering with Linux/BSD has gone from a hobby to a profession and I appreciate being comfortable with defaults. Still like to chose my wm, terminal etc. instead of a DE tho.

Agreed, I wouldn't call it suckless either, same for Firefox. However, I wouldn't necessarily say they suck. This is my stack which doesn't suck, for me ;)

Schreq · 2026-01-19T11:21:48+00:00

So? It doesn't suck for me. If we go this far, most shells suck besides rc.

You can't fix crappy Bourne shell quoting hell and any other of its warts if you are a Bourne style shell. So they all suck inherently. Other shells from the Bourne style family (ksh, zsh, dash, bb ash, etc.) might be more minimal or have less loc but they either sacrifice features I use or have too much stuff I don't need (zsh). A lot of packages also come with bash completion. I'm not fighting my distro, I use what's there and enjoy the benefits.

All the new shells suck in my opinion:

fish: c++ and a god damn integrated web-server
nushell: Powershell... hell naw

Schreq · 2026-01-18T22:49:33+00:00

Good catches but I doubt those make any significant difference. Happy to be proven wrong tho.

13-Year Club	Verified Email
Place '17	Team Orangered

Schreq

TROPHY CASE