Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 42491 - PROMPT_COMMAND set inappropriately in /etc/bashrc
PROMPT_COMMAND set inappropriately in /etc/bashrc
Product: Red Hat Linux
Classification: Retired
Component: bash (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bernhard Rosenkraenzer
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2001-05-27 16:00 EDT by John M. Adams
Modified: 2007-04-18 12:33 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-05-27 16:00:10 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 John M. Adams 2001-05-27 16:00:06 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.75 [en] (X11; U; Linux 2.2.17 i686)

Description of problem:
It's really a very bad idea to set PROMPT_COMMAND in /etc/bashrc.
In particular, it should not be set to echo an xterm escape.  More,
specifically, it should not be set to diddle with the term window
title.  This defeats standard means for users to set the title in xterm and
rxvt and causes confusion.

In general, I suggest that Red Hat refrain from setting a bunch of
personal preference type variables in the system init files for bash.

How reproducible:

Steps to Reproduce:
1. start bash with xterm -title fubar or rxvt -title fubar

Actual Results:  You don't get the window title you specified.

Expected Results:  The window should have had the title "fubar".

Additional info:

If you want Red Hat to be accepted by casual, non-geek type users,
then don't do unnecessary, fancy, counterintuitive things in the
system startup files.
Comment 1 Bernhard Rosenkraenzer 2001-05-28 02:59:08 EDT
It's a feature.
You can turn it off in the current version (rawhide), though.

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