things humans are bad at: memorising specific sequences of words
-
things humans are bad at: memorising specific sequences of words
things humans are good at: navigating spaces, finding objects within those spaces, interacting with objects in ways suggested by the object’s appearance and reactions
things linux is good at: making people memorise specific sequences of not quite real words, punctuations, and syntaxes
things linux is bad at: providing humans with coherent, consistent and stable spaces to navigate, or objects with appearances or reactions that suggest their function
@bri7 isn't this a command line issue in general?
-
@bri7 isn't this a command line issue in general?
@oblomov it is extremely possible to make a command line system that does not require people to memorise exact sequences of words. the popularity of search engines and chat GPT are two visible examples
-
@oblomov it is extremely possible to make a command line system that does not require people to memorise exact sequences of words. the popularity of search engines and chat GPT are two visible examples
@bri7 I wouldn't define those as command line systems, TBH.
-
@bri7 I wouldn't define those as command line systems, TBH.
@oblomov well, then you’d be wrong
-
things humans are bad at: memorising specific sequences of words
things humans are good at: navigating spaces, finding objects within those spaces, interacting with objects in ways suggested by the object’s appearance and reactions
things linux is good at: making people memorise specific sequences of not quite real words, punctuations, and syntaxes
things linux is bad at: providing humans with coherent, consistent and stable spaces to navigate, or objects with appearances or reactions that suggest their function
@bri7 In other words, Emacs > POSIX. -
@bri7
Ugh. Give me spacial metaphors any day.iirc, some Lisp Machines let you click on directories to switch to them so it's not a new idea.
@bri7
Oh, the last time I played with the Inspector in McClim it also allowed you do to this and more.
May be worth a look for anyone interested in this. -
some nerd somewhere i am sure: “uhh you can hit the tab key to autocomplete the directory”
me: oh wow it would be super neat if that was written anywhere other than a shitty internet comment about how stupid i am for not knowing that
repeat for every single linux feature
@bri7@social.treehouse.systems
oh wow it would be super neat if that was written anywhere other than a shitty internet comment about how stupid i am for not knowing that
In Bash's manpage it's written in the §Readline - Completing.
Completing complete (TAB) Attempt to perform completion on the text before point. Bash at‐ tempts completion treating the text as a variable (if the text begins with $), username (if the text begins with ~), hostname (if the text begins with @), or command (including aliases and functions) in turn. If none of these produces a match, filename completion is attempted.Granted it would've been helpful if there was some built-in tutorial feature.
Part of the issue here is that POSIX & UNIX expect you to have a physical user manual or guidebook/handbook or to already be familiar with UNIX & POSIX.
Because historically it was easier and cheaper to have a paper book available (things have certainly changed).
-
@bri7 A lot of Linux was styled after older, similarly obtuse systems that had to be a little curt with i/o because they ran on mainframes built when 4kb was a lot of memory.
Only nerd nostalgia keeps it that way. While some attempts have been made to improve the situation, like the fish shell, none of them go far enough.
@madengineering @bri7 > Only nerd nostalgia keeps it that way.
Some things are required to be crappy by POSIX.
Shells that do structured pipes are incompatible. -
@bri7 I wouldn't define those as command line systems, TBH.
-
@bri7 In other words, Emacs > POSIX.
@lispi314 i hope you’re talking about some emacs that isn’t the text editor that opens with nothing but a blank screen and some cryptic text along the top and bottom, that expects you to memorise 5000 keyboard shortcuts. that would be a silly thing to say, cos at least you can learn a small number of commands on linux that at least lists the available commands and allow you to type them by name
-
@bri7@social.treehouse.systems
oh wow it would be super neat if that was written anywhere other than a shitty internet comment about how stupid i am for not knowing that
In Bash's manpage it's written in the §Readline - Completing.
Completing complete (TAB) Attempt to perform completion on the text before point. Bash at‐ tempts completion treating the text as a variable (if the text begins with $), username (if the text begins with ~), hostname (if the text begins with @), or command (including aliases and functions) in turn. If none of these produces a match, filename completion is attempted.Granted it would've been helpful if there was some built-in tutorial feature.
Part of the issue here is that POSIX & UNIX expect you to have a physical user manual or guidebook/handbook or to already be familiar with UNIX & POSIX.
Because historically it was easier and cheaper to have a paper book available (things have certainly changed).
“In Bash's manpage it's written in the §Readline - Completing.”
you have got to be joking.
you do not follow me and be that oblivious about how stupid that sentence sounds
-
@lispi314 i hope you’re talking about some emacs that isn’t the text editor that opens with nothing but a blank screen and some cryptic text along the top and bottom, that expects you to memorise 5000 keyboard shortcuts. that would be a silly thing to say, cos at least you can learn a small number of commands on linux that at least lists the available commands and allow you to type them by name
-
“In Bash's manpage it's written in the §Readline - Completing.”
you have got to be joking.
you do not follow me and be that oblivious about how stupid that sentence sounds
@bri7
How long is that manpage!? -
@bri7
How long is that manpage!?@bri7
Oh, and it doesn't show up for "man -k completion" which is yet another "I have to type what for the documentation?" -
“In Bash's manpage it's written in the §Readline - Completing.”
you have got to be joking.
you do not follow me and be that oblivious about how stupid that sentence sounds
@bri7@social.treehouse.systems It was written somewhere else.
Not somewhere particularly user-friendly (I even remarked on that), but it was.
It noteworthy because there are some things that truly aren't documented at all in various other programs (guess you're fucked if you don't have the Internet then?).
-
@bri7@social.treehouse.systems It was written somewhere else.
Not somewhere particularly user-friendly (I even remarked on that), but it was.
It noteworthy because there are some things that truly aren't documented at all in various other programs (guess you're fucked if you don't have the Internet then?).
@lispi314 i beseech you review my list of UI principles to find out why that doesn’t count as being written somewhere
https://notes.yip.pe/Principles%20of%20UI,%20A%20Thread.html
-
@lispi314 i hope you’re talking about some emacs that isn’t the text editor that opens with nothing but a blank screen and some cryptic text along the top and bottom, that expects you to memorise 5000 keyboard shortcuts. that would be a silly thing to say, cos at least you can learn a small number of commands on linux that at least lists the available commands and allow you to type them by name
@bri7@social.treehouse.systems I never had that
Emacs, it sounds a lot likezileormg.The one I have has the third link on the opening page be "tutorial".
The tutorial also talks about
apropos,execute-extended-command(M-x) andcompletionwhich remove most of the need to memorize.Through those, with configuration, one can either lookup something by partly-remembered name or remembered movements (keybinds).
-
@lispi314 i beseech you review my list of UI principles to find out why that doesn’t count as being written somewhere
https://notes.yip.pe/Principles%20of%20UI,%20A%20Thread.html
1. need to know the man command in advance
2. need to know the feature exists already (defeating the point)
3. need to know the NAME of the feature
4. need to know what bash is
5. need to know what readline isyou might as well say it was written on the dark side of the moon, at the end of a rainbow, at the bottom of a leprechauns’s pot of gold
-
@bri7@social.treehouse.systems I never had that
Emacs, it sounds a lot likezileormg.The one I have has the third link on the opening page be "tutorial".
The tutorial also talks about
apropos,execute-extended-command(M-x) andcompletionwhich remove most of the need to memorize.Through those, with configuration, one can either lookup something by partly-remembered name or remembered movements (keybinds).
@lispi314 right so… your emacs is worse than linux, and *is* the one i remember that is worse than linux
-
@lispi314 right so… your emacs is worse than linux, and *is* the one i remember that is worse than linux
@lispi314 RTFM is not a serious response to the issue that humans are still not good at memorising specific sequences of words or command key sequences; it displays a kind of illiteracy that makes me wonder