Date: Tue, 3 Nov 1998 13:06:06 +0200 From: Shaun Courtney <shaun@emma.eng.uct.ac.za> To: Geoffrey Robinson <geoffr@globalserve.net> Cc: questions@FreeBSD.ORG Subject: Re: Setting BASH Prompt Message-ID: <19981103130606.A29763@emma.eng.uct.ac.za> In-Reply-To: <363DB3A8.1AACCE3@globalserve.net>; from Geoffrey Robinson on Mon, Nov 02, 1998 at 08:29:12AM -0500 References: <363DB3A8.1AACCE3@globalserve.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi
On Mon Nov 2 08:29:12 1998 Geoffrey Robinson wrote:
> How do you change the BASH prompts? The man page seems to leave a lot to be
> desired on that. :)
Yes it does... that is have a lot be to desired :)
man bash
/^PROMPTING
PROMPTING
When executing interactively, bash displays the primary
prompt PS1 when it is ready to read a command, and the
secondary prompt PS2 when it needs more input to complete
a command. Bash allows these prompt strings to be cus-
tomized by inserting a number of backslash-escaped special
characters that are decoded as follows:
\a an ASCII bell character (07)
\d the date in "Weekday Month Date" format
(e.g., "Tue May 26")
\e an ASCII escape character (033)
\h the hostname up to the first `.'
\H the hostname
\n newline
\s the name of the shell, the basename of $0
(the portion following the final slash)
\t the current time in 24-hour HH:MM:SS format
\T the current time in 12-hour HH:MM:SS format
\@ the current time in 12-hour am/pm format
\u the username of the current user
\v the version of bash (e.g., 2.00)
\V the release of bash, version + patchlevel
(e.g., 2.00.0)
\w the current working directory
\W the basename of the current working direc-
tory
\! the history number of this command
\# the command number of this command
\$ if the effective UID is 0, a #, otherwise a
$
\nnn the character corresponding to the octal
number nnn
\\ a backslash
\[ begin a sequence of non-printing characters,
which could be used to embed a terminal
control sequence into the prompt
\] end a sequence of non-printing characters
The command number and the history number are usually dif-
ferent: the history number of a command is its position in
the history list, which may include commands restored from
the history file (see HISTORY below), while the command
number is the position in the sequence of commands exe-
cuted during the current shell session. After the string
is decoded, it is expanded via parameter expansion, com-
mand substitution, arithmetic expansion, string expansion,
and quote removal, subject to the value of the promptvars
shell option (see the description of the shopt command
under SHELL BUILTIN COMMANDS below).
>
> --
> Geoffrey Robinson
> geoffr@globalserve.net
> Oakville, Ontario, Canada.
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message
--
Department of Electrical Engineering and CERECAM
System Administrator and Unix/NT support
http://www.eng.uct.ac.za
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981103130606.A29763>