bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "Variation" in Command Substitution Behaviour


From: Reuti
Subject: Re: "Variation" in Command Substitution Behaviour
Date: Wed, 1 Mar 2017 11:38:20 +0100

Hi,

> Am 01.03.2017 um 07:04 schrieb Geoff Hull <gbhull@gmail.com>:
> 
> Hi Reuti, Andreas,
> 
> Yes, forgot to mention the bash versions I have tried: 4.3.46 on Arch Linux 
> and 4.1.2 on CentOS 6.8.
> 
> This is getting weirder: I've found I can replicate the behaviour you are 
> getting Reuti, if I first do this command:
> 
> unset COMMAND_PROMPT
> 
> If I want to go back to the behaviour I first experienced (i.e. 
> Rubbles=barney after running assemble_fam1 then assemble_fam2), then I put 
> the default COMMAND_PROMPT back:
> 
> PROMPT_COMMAND='printf "\033]0;%s@%s:%s\007" "${USER}" "${HOSTNAME%%.*}" 
> "${PWD/#$HOME/~}"'
> 
> Does this work the same for you?

No, it doesn't change anything setting, unsetting and/or exporting it. Is it a 
Bash environment variable? I set PS1 on openSUSE for the prompt.

BTW: On a Mac with Bash 4.3.30(1) it works fine all the time, whatever order of 
executed aliases I use.

-- Reuti

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail


reply via email to

[Prev in Thread] Current Thread [Next in Thread]