You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I use Nemo's 'address bar', i.e. the path input field that appears when I press Ctrl+L, I expect it to behave mostly like Bash's tab completion (which I believe may actually be handled by Readline).
In some ways, this is indeed what it does, and for some of the ways it doesn't, there are clear reasons. But there are also use cases where it just behaves confusingly and frustratingly, and in at least one case, a way that most users would consider a bug:
In Bash, if I type a couple of letters and the press Tab, it will either list all the matching path elements, or step through them, depending on Readline's settings (menu-complete in .inputrc, or something—I'm not sure, because I like the former, default setting). But Nemo, in this case, does nothing. It would be lovely if, instead, a dropdown appeared, so I could either see what further characters to type, or arrow through and select one, or click one.
In Bash, if I type a path that contains nothing except one subdirectory, and then press Tab, it will fill in that one subdirectory. Nemo doesn't do this; instead, again, it does nothing. Worse, there seems to be no way to tell whether it's not showing the subdirectory because I made a typo further up the path; the behaviour is exactly the same, either way. I would already consider this a UX bug, but I haven't gotten to the kicker yet:
In Bash, if I make a typo in a path and press Tab, Readline does nothing, which indicates that I made the typo. And in that case, when I press Backspace, it, well, backspaces, one character at a time.* In Nemo, however, if I type an invalid path and press Tab, and then press Backspace once, the whole input field disappears!! The button-based path UI takes its place, and I have to type Ctrl+L and start typing the path all over again. This is surely a bug!
If Bash-like behaviour is beyond Nemo's intended scope, and I'm just more of an old-time shell-based keyboard warrior than its expected userbase, then I'm open to hearing about an alternative. (I'm a Gen-Xer who started with X-Windows around 1990, and still paste the keyboard buffer with my middle mouse button, so I know I'm a minority.) But I don't think adding these functions to Nemo would hinder other users' experiences, and the behaviour I noted in point 3 surely doesn't help anyone!
* I have my editing-mode set to vi, so in Bash, I can actually type EscF/C, if I want to delete back to the previous slash. I certainly don't expect Nemo to honour Vi keys, especially since Ctrl+Backspace already deletes a word at a time. But I don't expect my whole input to disappear so easily, either!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
When I use Nemo's 'address bar', i.e. the path input field that appears when I press Ctrl+L, I expect it to behave mostly like Bash's tab completion (which I believe may actually be handled by Readline).
In some ways, this is indeed what it does, and for some of the ways it doesn't, there are clear reasons. But there are also use cases where it just behaves confusingly and frustratingly, and in at least one case, a way that most users would consider a bug:
menu-complete
in.inputrc
, or something—I'm not sure, because I like the former, default setting). But Nemo, in this case, does nothing. It would be lovely if, instead, a dropdown appeared, so I could either see what further characters to type, or arrow through and select one, or click one.If Bash-like behaviour is beyond Nemo's intended scope, and I'm just more of an old-time shell-based keyboard warrior than its expected userbase, then I'm open to hearing about an alternative. (I'm a Gen-Xer who started with X-Windows around 1990, and still paste the keyboard buffer with my middle mouse button, so I know I'm a minority.) But I don't think adding these functions to Nemo would hinder other users' experiences, and the behaviour I noted in point 3 surely doesn't help anyone!
* I have my
editing-mode
set tovi
, so in Bash, I can actually type EscF/C, if I want to delete back to the previous slash. I certainly don't expect Nemo to honour Vi keys, especially since Ctrl+Backspace already deletes a word at a time. But I don't expect my whole input to disappear so easily, either!Beta Was this translation helpful? Give feedback.
All reactions