dharmik
@dharmik@linuxusers.in
mostly computers. student. linux. python. lisp.
dharmik
@dharmik@linuxusers.in
- mail at dharmiik [at] proton [dot] me
- i occasionally post in long-form at: https://dhrm1k.github.io
I concur with options 1 and 2. Reason: would enable vertical masonry layouts with flex or grid so that 3-6 colums of posts can be displayed, depending on screen size, vastly improving the scroll-through experience. See here for the direction I'm hinting at: https://neon.nightbulb.net/firefly?skip=33&show=33 ... and if you scroll a bit you'll see what I mean.
If the block content could be collapsed or truncated to certain length by default with a ... more ... link, one could quickly buzz through a weeks worth of posts.
The nice thing is that flexbox allows using calc to adjust the height of each cell so that vertical height of elements can vary and will get gaps smushed together with that uneven block size vertical masonry look.
Also, it would allow cool horizontal scroll arrangements using anchor tags to swipe. I remember many years ago how some websites were designed to scroll horiontally with buttons and links anchoring to sections. Maybe some expert theme designer would have fun cooking up a new rendition of that method ...
add the option to hide the "block" notification (I feel like it's less hurtful not to know when it happens, mobs use it as taunting strategy and it works so well I can't deny it T_T)Also, knowing about this makes me very sad; I had no idea this was a thing. In fact, being notified about blocks is very recent, just a few versions away. This is another example of how social networks are easily turned into toxic behaviour.
I'll add this option ASAP.
Thank you so much for making #snac look cool.
quitting in the terminal
![panel 1: quitting a terminal program isn't always easy
person (thinking): "I pressed Ctrl-C 17 times and NOTHING HAPPENED"
panel 2: ways to quit
Ctrl-C - the default
Ctrl-D - if you're at a prompt in a REPL >>>
q - if it's a full screen program
Ctrl-\ - sometimes works if Ctrl-C doesn't
kill -9 - the last resort
panel 3: how Ctrl-D works
programs that read input will usually have some code like this:
text = read_line()
if (text == EOF) {
exit()
}
Ctrl-D is how you send an EOF to the program ("I'm done!")
important: Ctrl-D ONLY works if you press it on an empty line
panel 4: how Ctrl-C works *
* unless your program is in "raw mode", we'll talk about that later
person: "ctrl-C"
terminal emulator: "ok, C is the 3rd letter of the alphabet, I'll write 3 to the tty"
OS terminal driver: ah, a 3, that means I should send the SIGINT signal to the current program
program: ooh, a SIGINT, I will [shutdown gracefully, immediately exit, ignore it, stop a subtask, etc]
* unless your program is in "raw mode", we'll talk about that later
panel 5: some programs have weird quitting incantations
for example every text editor (vim, nano, emacs, etc) has its own completely unique way to quit](https://cdn.masto.host/socialjvnsca/media_attachments/files/113/386/622/100/439/265/original/f1a4db8ea7527296.png "panel 1: quitting a terminal program isn't always easy
person (thinking): \"I pressed Ctrl-C 17 times and NOTHING HAPPENED\"
panel 2: ways to quit
Ctrl-C - the default
Ctrl-D - if you're at a prompt in a REPL >>>
q - if it's a full screen program
Ctrl-\ - sometimes works if Ctrl-C doesn't
kill -9 - the last resort
panel 3: how Ctrl-D works
programs that read input will usually have some code like this:
text = read_line()
if (text == EOF) {
exit()
}
Ctrl-D is how you send an EOF to the program (\"I'm done!\")
important: Ctrl-D ONLY works if you press it on an empty line
panel 4: how Ctrl-C works *
* unless your program is in \"raw mode\", we'll talk about that later
person: \"ctrl-C\"
terminal emulator: \"ok, C is the 3rd letter of the alphabet, I'll write 3 to the tty\"
OS terminal driver: ah, a 3, that means I should send the SIGINT signal to the current program
program: ooh, a SIGINT, I will [shutdown gracefully, immediately exit, ignore it, stop a subtask, etc]
* unless your program is in \"raw mode\", we'll talk about that later
panel 5: some programs have weird quitting incantations
for example every text editor (vim, nano, emacs, etc) has its own completely unique way to quit")
Alt...
panel 1: quitting a terminal program isn't always easy
person (thinking): "I pressed Ctrl-C 17 times and NOTHING HAPPENED"
panel 2: ways to quit
Ctrl-C - the default
Ctrl-D - if you're at a prompt in a REPL >>>
q - if it's a full screen program
Ctrl-\ - sometimes works if Ctrl-C doesn't
kill -9 - the last resort
panel 3: how Ctrl-D works
programs that read input will usually have some code like this:
text = read_line()
if (text == EOF) {
exit()
}
Ctrl-D is how you send an EOF to the program ("I'm done!")
important: Ctrl-D ONLY works if you press it on an empty line
panel 4: how Ctrl-C works *
* unless your program is in "raw mode", we'll talk about that later
person: "ctrl-C"
terminal emulator: "ok, C is the 3rd letter of the alphabet, I'll write 3 to the tty"
OS terminal driver: ah, a 3, that means I should send the SIGINT signal to the current program
program: ooh, a SIGINT, I will [shutdown gracefully, immediately exit, ignore it, stop a subtask, etc]
* unless your program is in "raw mode", we'll talk about that later
panel 5: some programs have weird quitting incantations
for example every text editor (vim, nano, emacs, etc) has its own completely unique way to quit
@b0rk and sometimes Ctrl-G helps if you find yourself stuck within Emacs...
@b0rk This obviously means that we need an editor which follows the standard and uses q as the quit key, since its a fullscreen application.
@b0rk TIL about the C→3→SIGINT mapping!
@dngrs @b0rk A tiny technical caveat: control-C sends a byte with value 0x03 on purpose; this is designed into ASCII; the control key maps A through Z to control codes 1 through 26 in alphabetical order; yes, this is why control-[ is another way to type the ESC key.
But the "character code 0x03 means send SIGINT" rule is adjustable (with the `stty` command) and SIGINT itself is usually *not* signal number 3 (there's no official rule for which signals have which numbers, but SIGINT is almost always number 2).
@zwol @dngrs @b0rk I'd like to link this [1] here since it does a great job of explaining the relation between keys and codes, for whomever is curious about this. (It also claims that Ctrl+C has no relation to ETX which would explain why SIGINT isn't signal number 3)
[1] http://www.catb.org/~esr/faqs/things-every-hacker-once-knew/#_ascii
@zwol do you know of any accurate reference? one thing I noticed with that one is that (on my machine) Ctrl+H is not backspace but it wasn't obvious why not, since I think I've been on other machines where Ctrl+H was backspace
@b0rk Unfortunately, not for the stuff covered by that one. I have occasionally been tempted to write my own version but it would be so much tedious fact-checking that I probably won't ever do it unless someone wants to pay me to do it.
The backspace key nowadays almost always sends ^? to the software running in the terminal (ASCII DEL, 0x7F). However, a long time ago (I remember this being a Thing in the 1990s), depending on which terminal (emulator) you had and how it was connected to the computer (actual serial line, ssh, rlogin, telnet, local pseudoterminal pair, etc) there was a good chance backspace would send ^H (ASCII BS, 0x08) instead. I never knew how to predict which I'd get.
(On terminals that used ^H for backspace, the delete key, if there was one, would usually send ^?. Nowadays, with ^? being used for backspace, the delete key sends ESC [ 3 ~ instead (no spaces).)
@zwol i started trying to make my own this morning but it's really a mess and has a million mistakes, and who handles what seems to depend on so many things (raw vs cooked, stty, probably more)
@b0rk I love how simple this is. Perfect explanation.
@b0rk I recently met someone who used Ctrl-q instead of q to quit full screen program. It seemed natural for him, and I can't blame him for this. But he piled up a list of stopped processes in his session. 😞
@dharmik Ahhann, intresting thing😃
https://expressionstatement.com/html-form-validation-is-heavily-underused
@dharmik great buddy. Jogging karo par itna nai ki had pinjar bahar kudke aa jaye lol.But nice decision ✨🤩
@0xZogG Zig because your username is Zog. That is all.
@dharmik @0xZogG People seem to enjoy https://ziglings.org/
And hop on https://ziggit.dev/ for community
But brace yourself, simple things will feel unnecessarily complicated because #Zig doesn't hide implementation details of memory management like most other systems. If you get over that part, you will appreciate what you've learned and can apply it anywhere
the strongest bocchi (evil)
winget is installed by default on windows 11. cool.i'd love to know if it takes this much time usually or there's something wrong with my internet connection or my machine config!
@dharmik I use zig on Debian with wsl no problems, and extract doesn't take that long. My guess is your windows anti-virus is checking every file. You can configure it to ignore your dev directories if you like.
I've been using Linux since I was 13 (I'm 27 now) and I still don't know how to use top(1).
The manual for top starts off by saying:
When operating top, the two most important keys are the help (h or ?) key and quit (
q) key. Alternatively, you could simply use the traditional interrupt key (^C) when you're done.
They are clearly aware that the primary usage of top is accidental (you quit and install htop instead).
@zyd how do you use htop anyway? Since the only thing that made a difference was the bars for mem and CPU usage at the top in htop, I've been using top since they're both inscrutable.
[ The units of mem usage can be changed in top so even less reason to install htop, as o learnt yesterday. ]
Nowadays I mostly use proced since searching for a process isn't a PITA.
@viz I largely use M-x proced as well. On remote servers I use htop. Its much easier than top: press F6 and choose your sorting method. How I primarily use it.
- mail at dharmiik [at] proton [dot] me
- i occasionally post in long-form at: https://dhrm1k.github.io
History
