6 ms·
These are not features of the terminal at all. “>” is a customizable prompt of your shell, and “-“ is a convention used by most (but not all) binaries. It’s als
by Siira 5y ago
These are not features of the terminal at all. “>” is a customizable prompt of your shell, and “-“ is a convention used by most (but not all) binaries. It’s also a very useful convention; How else are you going to tell arguments apart from options?
- slver 5y agoYou'd think the very purpose of calling it a "Graphical Command Line" would be that you're not restricted to a literal line of text. Just because it should be convenient to type and navigate with a keyboard doesn't mean the command line can't have structure beyond just the characters on it. I can fill in a webform just the keyboard. Tab, type, tab, type, tab, type, tab to the submit button, hit enter. Done. So I didn't have to type "--" anywhere. I didn't have to type the field names at all actually. Not saying I want them fixed per se, but "telling them apart" shouldn't be a real question in a graphical terminal UI. Likewise we should never escape strings or quote strings in a Graphical Terminal IMHO. They should just be text fields integrated seamlessly into the line, with visible boundaries. If you copy the line and paste it in a text editor, then sure, maybe show all this ghastly encoding happening underneath. But in the GUI Terminal... nah I don't accept it. EDIT: While we're at it, I don't think we should use monospace fonts in a GUI terminal. Certainly a font with distinct letters like lI1 and 0O, but not monospaced.