Re: How to use PROMPT_COMMAND(S) without breaking other scripts

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: How to use PROMPT_COMMAND(S) without breaking other scripts
Date	2020-08-24 15:58 -0400
Organization	ITS, Case Western Reserve University
Message-ID	<mailman.1061.1598299124.2469.bug-bash@gnu.org> (permalink)
References	(3 earlier) <0c10b76f-a7f0-1c52-77b7-4b208035956b@case.edu> <c904f5b5-1312-ac4c-26bd-bfb97c1f43e8@inlv.org> <669a0539-fd4f-b4f9-f4c5-06922fb670d0@case.edu> <fa6b2bac-5bcd-1cce-94af-0be4aff02cbf@inlv.org> <e442fa50-38cc-1d1b-a9e0-1de07755b10d@case.edu>

Show all headers | View raw

On 8/24/20 3:53 PM, Martijn Dekker wrote:

>> What I mean is looking for PROMPT_COMMAND as happens now, and reacting a
>> different way if it's an array variable. That would resolve the existing
>> assignment issues, but open up the separate issues you describe.
> 
> 
> But I also suggested a way of avoiding those issues: initialise
> $PROMPT_COMMAND a.k.a. ${PROMPT_COMMAND[0]} as empty.

Sure. The burden to do that is on the user. As long as startup scripts do
that -- which they don't do now -- there's no problem.


-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Re: How to use PROMPT_COMMAND(S) without breaking other scripts Chet Ramey <chet.ramey@case.edu> - 2020-08-24 15:58 -0400

csiph-web