Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #225768 > unrolled thread

Re: Bash question hard to formulate

Started bysongbird <songbird@anthive.com>
First post2020-08-03 06:50 +0200
Last post2020-08-03 18:10 +0200
Articles 4 — 3 participants

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Bash question hard to formulate songbird <songbird@anthive.com> - 2020-08-03 06:50 +0200
    Re: Bash question hard to formulate <tomas@tuxteam.de> - 2020-08-03 10:20 +0200
      Re: Bash question hard to formulate songbird <songbird@anthive.com> - 2020-08-03 14:20 +0200
      Re: Bash question hard to formulate David Wright <deblis@lionunicorn.co.uk> - 2020-08-03 18:10 +0200

#225768 — Re: Bash question hard to formulate

Fromsongbird <songbird@anthive.com>
Date2020-08-03 06:50 +0200
SubjectRe: Bash question hard to formulate
Message-ID<AzAA9-6P1-1@gated-at.bofh.it>
...

  i'm not familiar with that problem but another tip
which is helpful when dealing with a terminal that
gets into a strange state is to press return then
type in reset and press return again.


  songbird

[toc] | [next] | [standalone]


#225772

From<tomas@tuxteam.de>
Date2020-08-03 10:20 +0200
Message-ID<AzDRs-yN-63@gated-at.bofh.it>
In reply to#225768

[Multipart message — attachments visible in raw view] — view raw

On Mon, Aug 03, 2020 at 12:47:32AM -0400, songbird wrote:
> ...
> 
>   i'm not familiar with that problem but another tip
> which is helpful when dealing with a terminal that
> gets into a strange state is to press return then
> type in reset and press return again.

Typing return when you have already half-a-command line
(and are not sure what it is) is somewhat dangerous.

That's OK, it can be a life style. Be sure to keep some
backups around, then :-)

Cheers
-- t

[toc] | [prev] | [next] | [standalone]


#225774

Fromsongbird <songbird@anthive.com>
Date2020-08-03 14:20 +0200
Message-ID<AzHBD-2Ve-3@gated-at.bofh.it>
In reply to#225772
<tomas@tuxteam.de> wrote:
> On Mon, Aug 03, 2020 at 12:47:32AM -0400, songbird wrote:
>> ...
>>=20
>>   i'm not familiar with that problem but another tip
>> which is helpful when dealing with a terminal that
>> gets into a strange state is to press return then
>> type in reset and press return again.
>
> Typing return when you have already half-a-command line
> (and are not sure what it is) is somewhat dangerous.
>
> That's OK, it can be a life style. Be sure to keep some
> backups around, then :-)

  haha, yeah...  with github these days my more recent
projects are being backed up "off site" so i'm not too
worried about the most recent changes not being 
available to me in case of a severe crash.  but i do
also keep backups.

  Ctrl-C can also be used to cancel a command in progress.
:)  i'm not often typing dangerous commands into the 
terminal, especially one which is in an odd state.


  songbird

[toc] | [prev] | [next] | [standalone]


#225778

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2020-08-03 18:10 +0200
Message-ID<AzLce-599-15@gated-at.bofh.it>
In reply to#225772
On Mon 03 Aug 2020 at 11:30:42 (+0200), Esteban L wrote:

> I am not typing return. I am typing in a sentence...As I receive new
> output to the terminal window, and I continue typing, my text stream
> just goes down a line. Which is fine, UNLESS I otherwise want to correct
> something, and backspacing doesn't word wrap back to the previously
> typed line.

If characters are typed by a process while you're typing a command
line, then naively trying to backspace over a newline will not work
because bash has a different idea of where the cursor is from reality.

If you just ignore said characters, the command line you typed will
be unaffected, and will execute correctly when you press Return.

> the main thing I want is, if I backspace into a sentence (as I am
> receiving output to the terminal window and that i have not CR'ed), that
> the incomplete sentence will re-show up on the active line, when I reach
> the beginning of the that line.

That's not going to work. When you "backspace into a sentence", you're
rubbing out characters that *you* typed, even though the characters
that are actually disappearing from the display are the ones that were
displayed last, ie those output by the other process.

If you want the characters that *you* typed to be re-shown, clean, on
the command line, then pressing Ctrl-L is the correct way to do it.
*Then* apply your corrections, using Backspace or the arrow keys as
appropriate.

Cheers,
David.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web