_TwoFinger
Joined 9 years ago
Karma
78
Submissions
36
Member since
Oct 17
Recent submissions
Comment · 3 years ago
Comment · 3 years ago
Your Indonesian is pretty good, sir. Have an upvote.
Comment · 3 years ago
For prose, it probably is the best, but have you tried it for programming?
I find that my keyboard usage is dominated by text-editing shortcuts and punctuation characters. Not sure how well stenography would fit in.
On a similar note, though, I have amassed a "dictionary" of 50+ bash aliases, 1-, 2-, or 3-characters long.
Some "theories" emerged as well - I have groups of aliases whose names follow a pattern and depend on what subcommand (e.g. in git or kubectl) or options are included in the alias. This is good for mnemonics.
For extremely common commands, I ditch mnemonics and just choose a 1- or 2-character name that has no connection to the name of the command. For example r='cd -'. I chose "r" simply because it's on the opposite side of Enter, and I get to alternate my hands. (I guess this is a "brief".)
What got me into the alias hoarding business was the discovery of complete-alias[1] and, later, the progcomp_alias bash option. Turned out, you don't have to choose between aliases and programmable completion, you can have both.
Comment · 3 years ago
Just want to mention sticky keys[1], as it seems often overlooked.
Instead of holding the modifier key(s) when activating a shortcut, you can press and release each modifier sequentially.
It does come with some of the fancy keyboards' firmware, but is also a built-in feature of all major OS-es. You can get it without spending a single dollar.
Comment · 3 years ago
Emphasis on "also".
If you optimize a shell feature for general-purpose programming, interactivity will suffer (increased verboseness, usually), and vice versa.
If we try to bring shells closer to the real PLs, instead of just using those PLs when it matters, we'll lose some of things that made shells attractive in the first place.
Comment · 3 years ago
> So, bash is a programming language, right?
No, it's a shell that lets you interact with the OS. All the "clasical" UNIX shells were created with interactive use in mind and optimized for it, but happen to be good enough at batch processing[1] to be conflated with programming languages (mostly these days, like, 40+ years later).
The focus on interactive use is the reason you don't have to
- surround command argument lists with parentheses
- put commas between command arguments
- put semicolons at EOL
- surround string literals with quotes (unless the content interferes with the syntax, like, sigils or IFS chars, and you want to escape it).
- surround variable names in braces (unless you want to use some advanced substitution)
- call commands to manipulate I/O; it's baked in.
And these are just the things that existed 40 years ago. Bash gives you so much more stuff that makes interactive use a bliss, but I'm not going to dump the man page here.
Comment · 3 years ago
Ah, we are really just one smart kid away from extinction.
Something something boson something neutron, and the Earth goes kaboom.
Children can be very dangerous.
Comment · 3 years ago
> Missing semicolon.
It's not missing. PP is making a point about "single-command variables."
Comment · 3 years ago
> I had to [...] and set my shell to bash/zsh
Most likely a command in your script (or one source-d into it) makes an assumption about your $SHELL or login shell that is true for bash/zsh but not for fish.
Merely adding a shebang won't fix such a script.
Comment · 3 years ago
> having to retype the whole filepath when using mv can lead to errors.
If you use bash, or any readline-based command line (in emacs mode):
mv long.file.name |^W^Y^Y
mv long.file.name long.file.name |
edit: and if your filename has spaces, replace the ^W above with M-C-b C-k
Comment · 3 years ago
> we effectively have infinite vertical space
It's only infinite if you scroll for infinitely long time.
I think the author's point was about how much code you have on the screen at any given instant. Without having to scroll or jump.
Comment · 3 years ago
Comment · 3 years ago
I don't use the tiling at all.
I use the multiple desktops feature a lot, though. Some programs are pinned to a dedicated desktop and run all day. Others I start in (or move to, later) a numbered desktop, and switch to them by changing the desktop. Often, most of the desktops contain only one window.
I once used i3 and sway the right way, of course. I guess I had one too many of those programs that were not designed to work at arbitrary window sizes, added the above rule and called it a day.
Comment · 3 years ago
Just an idea, if you find yourself unable to warm up to tiling:
for_window [all] floating enable
That said, this is probably what any big enough company would do. So your point still stands, maybe car manufacturers are no different.