Bug 620435 - Please use printf instead of echo.
Please use printf instead of echo.
Product: Fedora
Classification: Fedora
Component: setup (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ondrej Vasik
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-08-02 10:09 EDT by Roman Rakus
Modified: 2010-08-18 04:45 EDT (History)
4 users (show)

See Also:
Fixed In Version: setup-2.8.25-1.fc15
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 620408
Last Closed: 2010-08-13 08:37:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Roman Rakus 2010-08-02 10:09:17 EDT
+++ This bug was initially created as a clone of Bug #620408 +++

Description of problem:
Due to the fix of bug #142125 the default PROMPT_COMMAND has been set to a list of two commands.  This causes strange behaviour when the output of a background process might get flushed after the output of the first PROMPT_COMMAND echo and hence appear between the escape sequences which mark the X terminal title.  It also means the text doesn't appear in the terminal itself.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. In xterm/gnome-terminal/Terminal run: yes &
2. while 'yes' is running: cat /var/log/yum.log (or whatever application which prints out something on the terminal and takes some time)
3. Look at the terminal title -- it would read something like "tsmetana@localhost:~/bash_testy y y y y y"
4. if not GOTO 2.
Actual results:
The text printed in the terminal title was not printed in the terminal window (this can be verified by running something else than 'yes' -- e.g. a simple c-program which outputs a number sequence)

Expected results:
The output of PROMPT_COMMAND shouldn't get mixed with the other text that goes to the terminal.

Additional info:
There is a simple way to check the more commands in PROMPT_COMMAND can have unusual consequence -- try to add sleep between the two commands:

export PROMPT_COMMAND='echo -ne "\033]0;${USER}@${HOSTNAME%%.*}:${PWD/#$HOME/~}"; sleep 1; echo -ne "\007"'

Now just press enter and some random keys on the keyboard, then look at the xterm title -- it would contain the keys you pressed.  Note that the sleep only increases the chance for this to happen.

I'm not actually sure how to solve the problem properly: maybe the bug #142125 has to be fixed some other way and PROMPT_COMMAND should be reverted to the old value with just one echo command.

--- Additional comment from rrakus@redhat.com on 2010-08-02 09:42:28 EDT ---

I guess we should use `printf' instead of `echo'.

--- Additional comment from rrakus@redhat.com on 2010-08-02 10:08:23 EDT ---

PROMPT_COMMAND='printf "\033]0;%s@%s:%s\007" "${USER}" "${HOSTNAME%%.*}" "${PWD/#HOME/~}"'

works for me. Reassigning to setup.
Comment 1 Ondrej Vasik 2010-08-13 08:37:26 EDT
Built as setup-2.8.25-1.fc15, closing RAWHIDE.
Comment 2 Pete Zaitcev 2010-08-17 22:56:33 EDT
See possible regression in bug 624900.
Comment 3 Tomas Smetana 2010-08-18 04:20:26 EDT
I'm sorry. I should have noticed before: there's yet another problem with the change: There is a missing '$' before HOME... The PROMPT_COMMAND should look like this:

PROMPT_COMMAND='printf "\033]0;%s@%s:%s\007" "${USER}" "${HOSTNAME%%.*}" "${PWD/#$HOME/~}"'

As for Pete's problem with screen: I don't think it's this change that caused it (tested on F-13 -- I put the new PROMPT_COMMAND definition in my ~/.bashrc using the Xfce terminal):

[tsmetana@zaphod ~]$ echo $TERM
[tsmetana@zaphod ~]$ echo $PROMPT_COMMAND 
printf "\033]0;%s@%s:%s\007" "${USER}" "${HOSTNAME%%.*}" "${PWD/#$HOME/~}"
[tsmetana@zaphod ~]$ pstree | grep screen
     |      `-sshd---sshd---bash---screen---screen---bash-+-grep

Comment 4 Ondrej Vasik 2010-08-18 04:45:07 EDT
Tomas - it was really problem caused by the change to printf - I did a typo there... this should be fixed in setup-2.8.26-1.fc15 ... 
You are right about the missing $ ... will fix that in next setup build ...

Note You need to log in before you can comment on or make changes to this bug.