Path: csiph.com!xmission!news.glorb.com!usenet.stanford.edu!not-for-mail From: Linda Walsh Newsgroups: gnu.bash.bug Subject: Re: ! in PS1 in posix mode Date: Mon, 12 Oct 2015 22:46:52 -0700 Lines: 36 Approved: bug-bash@gnu.org Message-ID: References: <561A6877.4010709@case.edu> <561BDFBA.4020304@tlinx.org> <561C029E.8060703@case.edu> <561C3C22.3010900@tlinx.org> <561C4F2D.10505@case.edu> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: usenet.stanford.edu 1444715244 8633 208.118.235.17 (13 Oct 2015 05:47:24 GMT) X-Complaints-To: action@cs.stanford.edu Cc: isabella parakiss , bug-bash To: chet.ramey@case.edu Envelope-to: bug-bash@gnu.org User-Agent: Thunderbird In-Reply-To: <561C4F2D.10505@case.edu> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x (no timestamps) [generic] X-Received-From: 173.164.175.65 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: csiph.com gnu.bash.bug:11642 Chet Ramey wrote: > On 10/12/15 7:02 PM, Linda Walsh wrote: > >>> It happens in posix mode. >> --- >> How lame! It's a '!' in a quoted string. Another example >> of posix braindeath -- how long before people realize that the >> thing branded 'posix' now isn't the real posix that was started >> to *describe* behaviors, not prescribe or proscribe behaviors. > > Do you realize that this prompt expansion was in ksh since at least > ksh-86? ksh-88 was one of the Posix base documents, and that > expansion was estabished behavior by the time Posix started its work. --- Haven't used ksh for some time....I thought the '!' stuff came from csh? It seemed so pointless, since having to look up things by command number I thought, was way too much work... searching via a string in the line seemed so much faster... For stuff I typed last week or earlier, I'd use grep on the hist files. I thought to have all my hist files merged and deduped... but the resulting master hist file -- .. I used it for a while (somewhat accidently as it was renamed to a normal hist file @ around 2-3M in length). command response was quite slow (took a while to figure out it was the history updating every command that caused a delay of about 2-3 seconds/command). I don't think I have all the kinks in the combining routines worked out yet either... but certainly wouldn't want to switch to the newest master @ 6.4M until history updating is sped up a bit... (I'm not holding my break... at least I can still browse/grep it by tty#)...