would someone please explain in detail, how does the code below change the color or bash prompt
$ echo $PS1
:\033
are there other tricks like above? (3 Replies)
please advise what's wrong with this command ?
PS1="`hostname`:`who am i | cut -d " " -f1`:>>"
trying to make the PS1 prompt look like :
machine_name:username:>>
thank you (4 Replies)
Hi,
I'm using the ksh shell and I'd like to set my PS1 prompt on an AIX system to include, amongst ther things, the current time.
This was my best effort: export PS1=$(date -u +%R)'${ME}:${PWD}# '
but this only sets the time to the value when PS1 is defined and the time value doesn't... (4 Replies)
Hi,
I'm trying to find out if there is a way to get a timestamp on my Solaris root shell prompt using /sbin/sh?
I'm trying to archive something in line with the following:
12:34:26 root@server #
12:34:28 root@server #
12:34:28 root@server # ls
...
12:34:30 root@server #
I know there... (1 Reply)
Greetings!
I have to work with a NFS user id between two hosts: A running Ksh 93 and B running pdksh 88.
My problem has to do with the custom prompt I created on A: it works like a charm and display colors:
PS1="$'\E
But I switch over to B, it all goes to hell (private info... (4 Replies)
Hi,
I am using git bash terminal window to do git operations. I have set the prompt string variable PS1 in the ~/.bashrc file as follows:
export PS1=" "
This is intended to show me the current git branch's name which is active as part of the prompt string. But, the problem is when I do a git... (2 Replies)
I have coded PS1 as shown, producing the following result when writing on the command line
┌─ cdl
└──╼ make tracepdf2d
If I make an error in the command an ✗ is printed
┌─ ✗ cdl
└──╼ ls-a
ls-a: command not found
My problem is that if I just press enter, I do not want to have the... (3 Replies)
So, this is strange... I created this prompt:
PS1='\n\e
You can see that it's a pretty minor modification of the default Debian prompt. And, if it matters, I'm using Putty to SSH to my server. The following strange symptoms appear when I use that prompt, and disappear when I change and... (2 Replies)
RedHat Linux 5.8/Korn Shell
I have text file name /etc/oracle/config.loc. It has the following text
#Device/file getting replaced by device +OCR
ocrconfig_loc=+DATA
ocrmirrorconfig_loc=+OCRBut , when I open this file using cat , the PS1 character (for prompt) appears as the last character... (8 Replies)
Discussion started by: omega3
8 Replies
LEARN ABOUT DEBIAN
env::ps1
Env::PS1(3pm) User Contributed Perl Documentation Env::PS1(3pm)NAME
Env::PS1 - prompt string formatter
SYNOPSIS
# use the import function
use Env::PS1 qw/$PS1/;
$ENV{PS1} = 'u@h $ ';
print $PS1;
$readline = <STDIN>;
# or tie it yourself
tie $prompt, 'Env::PS1', 'PS1';
# you can also tie a scalar ref
$format = 'u@h$ ';
tie $prompt, 'Env::PS1', $format;
DESCRIPTION
This package supplies variables that are "tied" to environment variables like 'PS1' and 'PS2', if read it takes the contents of the
variable as a format string like the ones bash(1) uses to format the prompt.
It is intended to be used in combination with the various ReadLine packages.
EXPORT
You can request for arbitrary variables to be exported, they will be tied to the environment variables of the same name.
TIE
When you "tie" a variable you can supply one argument which can either be the name of an environement variable or a SCALAR reference. This
argument defaults to 'PS1'.
METHODS
"sprintf($format)"
Returns the formatted string.
Using this method all the time is a lot less efficient then using the tied variable, because the tied variable caches parts of the
format that remain the same anyway.
FORMAT
The format is copied mostly from bash(1) because that's what it is supposed to be compatible with. We made some private extensions which
obviously are not portable.
Note that this is not the prompt format as specified by the posix specification, that would only know "!" for the history number and "!!"
for a literal "!".
Apart from the escape sequences you can also use environment variables in the format string; use $VAR or "${VAR}".
The following escape sequences are recognized:
a The bell character, identical to "