trying rox-filer. it's nice, much more lightweight than other graphical file managers, but it uses its own launcher instead of xdg-open (i'm sure there's a way to configure it for xdg, though maybe not a clean one).
now it wants me to install this thing (it's like flatpak/snap, but simpler and with no containers i think?): https://0install.net . which is an interesting idea, but also sounds like a security nightmare.
> In the mid-1990s while porting the sc spreadsheet to the S-Lang library, Davis developed the library's screen management facility. This component was designed to optimize screen output (by minimizing the number of characters sent to the terminal), and provide a simple way to support a variety of terminals through an extra layer of abstraction between the application code and the terminal.
virtual dom for terminals!
is there any reason to use terminfo in 2020 other than to find out how many colors the terminal supports? i don't think anyone would run my software on a tektronix 4014 or a dec vt52, let alone ibm model 37 teletype..
(also thinking about hardcoding things like `if $TERM contains 256`, though that's probably not a good idea)
"Web Design Museum exhibits over 1,600 carefully selected and sorted web sites that show web design trends between the years 1991 and 2006."
on an unrelated note, "os/2" is such a hashtag-hostile product name. i wonder if companies think about hashtag-friendliness when naming their products in 2010's/2020's.
read a comment about how spatial file managers are useful (under an article about haiku). the only time i used one was when i tried os/2, it was confusing (and i still don't get the concept of their "object-oriented desktop"). now i wanna try it again, but i don't know if there're any spatial file managers for linux..
it's weird how such a popular concept from back then can't be found anywhere anymore
in nano, you can select more than 223 characters using mouse! and i checked it, it receives mouse input in a different format: ^[[<0;1;1M for click, ^[[<0;1;1m for release. can't find the code it uses to enable that mode though!
(i love how easy it is to check this stuff. in my program, i copy input from stdin into a pty, so i modified that function to instead copy it into a MultiWriter which writes to pty and stderr simultaneously. then `go run . 2> out` and `tail -f out | cat -A`.)
i should probably switch to gvim, i don't think it has any of these limitations.. but console vim is so convenient, and usable in ssh!
you can check it out yourself. run this command: `printf '\033[?1000h' && cat`, then click and hold somewhere inside the terminal window.
you'll see something like `^[[M AH`. here, `^[[M` stands for mouse input, space means mouse button 0 (left), `A` and `H` are the coordinates (33 and 40 in my case). release the button and you'll see another code, this time with `#` for mouse button. 3 stands for "release".
finally, mystery solved. i didn't understand why i could only select 223 characters with my mouse in #vim. the number seemed pretty arbitrary. turns out, xterm-style mouse-tracking codes encode numbers in one character, 32 + number. so space is 0, ! is 1, " is 2 and so on. coordinates are one-indexed, so no zero. aaand there can only be 256 values of a byte. 256 - 32 - 1 = 223.
hmm there're tango and oxygen icons (which were used in gnome 2 and kde 4 respectively)
but PTYs are fun!
i'll be banished from the church of software development for this, but i don't know how to make it better
a strange girl interested in infosec and coding. loves her girlfriend. interact with my posts please!
A Mastodon instance for info/cyber security-minded people.