note
Crackers2
<blockquote>The backspace/back-arrow/run-out) key should delete the presceding character and delete the character under the cursor, but we could never get both to function correctly. </blockquote>
<p>That's what it's doing by default for me in bash on linux. Of course things like this are really related to the terminal, not the shell; cmd doesn't have the separate concepts.</p>
<blockquote>When line-editing, ctrl + left-arrow/right-arrow move back/forward 1 "word" at a time -- these are amongst my most used keys but I never did find a way to make them work the same in a *nix shell. </blockquote>
<p>Ah yes. I do remember these now from the Borland IDE days. That same functionality is alt-b/alt-f in bash</p>
<blockquote>escape clears the command line. Never got that to work. </blockquote>
<p>Didn't know that one. I've always just used Ctrl-C in both windows and linux to get a new empty prompt</p>
<blockquote>Go into the command window properties->defaults->options tab and select the "quick-edit mode" and you can do exactly that in every command window thence forth. (I've had it that way for so long I'd forgotten it wasn't then default. :) </blockquote>
<p>Ah that does improve things some. Though the rectangular select (as opposed to the default stream-like select in bash) makes it still mostly useless to me except in a few specific situations. Got any way to get the other kind of select? </p>
<blockquote>The main problem with c&p under nix shells was that they don't (or I never worked out how to make them) inter-operate with other programs. Ie. I couldn't easily copy from a shell and paste into an editor or browser; or vice versa. </blockquote>
<p>That seems to be mostly an X problem. I think that's gotten better over the years but can't vouch for it. I personally run PuTTY on windows to log into a linux box, so cut and paste between everything works just fine.</p>
<blockquote>Many people have never discovered the following functions: </blockquote>
<p>Indeed. In bash they're not function keys. "history" to display command history, Ctrl-R for incremental search in the history, "history -c" to clear</p>
<blockquote>Another factor that many people miss is that cmd.exe uses multiple histories. So text entered to program prompts doesn't get mixed in with commands typed into the shell itself.</blockquote>
<p>Heh that's different. In linux the shell never even sees the stuff typed once a program starts, so it can't keep a history. It'd indeed be up to the separate program to provide it. For me in practice that's not an issue since 99% of everything i run in the shell is either non-interactive or curses-like (e.g. vi), but yes it sounds like it could be convenient for interacive stuff.</p>
<p>Oh, one more thing that frustrates me about the command prompt: Can't resize it by simply dragging the window corner. If you make it smaller you get scroll bars instead of a resized buffer, and trying to make it bigger than the screen buffer size simply doesn't do anything.</p>
1038453
1038600