&& causing bash to dump core, varia

Thread View: gnu.bash.bug

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Francois Pinard Sun, 09 Jul 1989 12:03

#279

Author: Francois Pinard
Date: Sun, 09 Jul 1989 12:03

24 lines
1414 bytes

   From: lamy@ai.utoronto.ca (Jean-Francois Lamy)
   Newsgroups: gnu.bash.bug
   Date: 29 Jun 89 14:08:59 GMT

Salut, cher confre`re :-)

   c) Can the &#^*%&! insertion of a * at the beginning of the prompt
      when a line is edited be turned off?  it appears as well that
      only the prompt is shifted as well, which is disconcerting if
      not wrong.

What's wrong with this?  bash is telling you: there is now an
undo-list for this command.  This information might be useful,
especially when you move back in the command history.

I'm sure that the author had to seek a way to display this
information.  What would you have choosen instead?  Effectively, I
have been ``disconcerted'' when I saw this * for the first time, but
only disconcerted by a subtle wave of pleasure (:-).

-- 
Franc,ois Pinard                                    pinard@iro.umontreal.ca
(514) 588-4656           ``Vivement GNU!''          ...!uunet!iros1!pinard

Re: && causing bash to dump core, varia

#281

Author: Andrew Thomas
Date: Sun, 09 Jul 1989 19:08

26 lines
1902 bytes

In article <8907091203.AA06418@ouareau.iro.umontreal.CA> mcgill-vision!iros1!pinard@EDDIE.MIT.EDU (Francois Pinard) writes:
   Salut, cher confre`re :-)

      c) Can the &#^*%&! insertion of a * at the beginning of the prompt
	 when a line is edited be turned off?  it appears as well that
	 only the prompt is shifted as well, which is disconcerting if
	 not wrong.

   What's wrong with this?  bash is telling you: there is now an
   undo-list for this command.  This information might be useful,
   especially when you move back in the command history.

I have to agree that the * at the beginning is a BAD THING.  This can
be very annoying at low baud rates, say 1200.  This also is quite
frustrating when you use the universal argument on a command.  In
general, I think that any key sequence that modifies the prompt,
including universal argument, the little *, back and forward search,
should all be optional.  Preferably, they should be removable
independently of one another (I would like to be able to turn off the
* and the arg:, buy keep reverse search sometimes).  Would this be
difficuly to implement?
--

Andrew Thomas
andrewt@watsnew.waterloo.edu	Systems Design Eng.	University of Waterloo
"If a million people do a stupid thing, it's still a stupid thing." - Opus

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads