Idk if you know but you van actually save a post or comment pressing the button "save" under it. It will appear in your profile in a section of saved stuff.
You might already know these but no one else has posted them on this thread yet. I work in both Linux and Mac a lot and this works for them. No idea about Windows I'm no longer forced to use it at work 🙂
Also Ctrl + w to delete one word backwards (which is what OP wants to do).
Edit: Nvm I misread the post, deleting is not what OP wants to do. Still gonna keep this because Ctrl + w is easily the readline shortcut I use the most.
No (although you can easily create such a key mapping if so inclined). To type b character one must first enter the so called Insert mode. Depending on where exactly you wish to type the character, you can enter the Insert mode by typing for example i, a, I, A, o or O.
Because terminal emulators are literally the old terminal emulators (ye oldy screens + keyboard combos that looked like a computer but were just IO) and everything modern they do is just a hack.
Terminals with screens? What's all that newfangled shit?
Nah, whippersnapper, this tech goes all the way back to teletypes. You didn't get a fancy-shmancy "screen;" instead, it printed out the results of your commands. On actual paper!
Seriously though, that's why the device files for terminals in Linux are named tty[$NUM] -- "tty" is shorthand for "TeleTYpe."
I believe it's also why really primitive programs can't scroll up and do things like writing an entire screen worth of content in order to emulate interactivity (as opposed to seeking the cursor backwards and replacing only the parts the program wants to replace): they're using a version of the control protocol so primitive that it didn't have a function to go backwards because teletypes didn't need it due to physical impossibility. (That's my theory, anyway -- I haven't dug deep enough into the guts of TERMCAP etc. to be sure. I'm also not actually old enough to have experienced that stuff, despite my joke above.)
Edit: look at this excerpt from man terminfo(5), for instance:
Basic Capabilities
The number of columns on each line for the terminal is given by
the cols numeric capability. If the terminal is a CRT, then the
number of lines on the screen is given by the lines capability.
If the terminal wraps around to the beginning of the next line
when it reaches the right margin, then it should have the am
capability. If the terminal can clear its screen, leaving the
cursor in the home position, then this is given by the clear
string capability. If the terminal overstrikes (rather than
clearing a position when a character is struck over) then it
should have the os capability. If the terminal is a printing
terminal, with no soft copy unit, give it both hc and os.
To this day, the info database entry for your virtual terminal has to specify that it's capable of deleting a line of text instead of merely striking it out, because some terminals back in the day actually couldn't!
What happens to me is the opposite. I got used to Ctrl+w to delete a word in terminal and accidentally closed browser tabs many times while typing in them.
C-x C-s
Save the current buffer to its file (save-buffer).
C-x s
Save any or all buffers to their files (save-some-buffers).
M-~
Forget that the current buffer has been changed (not-modified). With prefix argument (C-u), mark the current buffer as changed.
C-x C-w
Save the current buffer with a specified file name (write-file).
M-x set-visited-file-name
Change the file name under which the current buffer will be saved.
When you wish to save the file and make your changes permanent, type C-x C-s (save-buffer). After saving is finished, C-x C-s displays a message like this:
Wrote /u/rms/gnu/gnu.tasks
If the current buffer is not modified (no changes have been made in it since the buffer was created or last saved), saving is not really done, because it would have no effect. Instead, C-x C-s displays a message like this in the echo area:
(No changes need to be saved)
With a prefix argument, C-u C-x C-s, Emacs also marks the buffer to be backed up when the next save is done. See Backup Files.
The command C-x s (save-some-buffers) offers to save any or all modified buffers. It asks you what to do with each buffer. The possible responses are analogous to those of query-replace:
y
SPC
Save this buffer and ask about the rest of the buffers.
n
DEL
Don’t save this buffer, but ask about the rest of the buffers.
!
Save this buffer and all the rest with no more questions.
q
RET
Terminate save-some-buffers without any more saving.
.
Save this buffer, then exit save-some-buffers without even asking about other buffers.
C-r
View the buffer that you are currently being asked about. When you exit View mode, you get back to save-some-buffers, which asks the question again.
C-f
Exit save-some-buffers and visit the buffer that you are currently being asked about.
d
Diff the buffer against its corresponding file, so you can see what changes you would be saving. This calls the command diff-buffer-with-file (see Comparing Files).
CTRL-C has been the default key combination to terminate a running process, since forever. Reassigning it to “copy selection” would be very inconvenient.
I like the solution of the ElementaryOS terminal: when you press CTRL-C, it does “the right thing” depending on the context.
What happens to me is the opposite. I got used to Ctrl+w to delete a word in terminal and accidentally closed browser tabs many times while typing in them.