In this context the ! outputs the current line number in the shell history file.
The ">" is just a character and plays no active part.
Type "history" to see the correlation of the line numbers.
Notice that the line number is one higher than expected because executing the "PS1" statement counts as a command.
Hello there !
I am new in this Unix world and just start learning Unix. I have very simple question about changing PS1 variable (Shell Prompt)
i have local.profile file in my working directory, i open in vi edit mode and add this line PS1="Hello:>" and i save that file.
I disconnected from... (2 Replies)
I want to set my prompt to something more descriptive than a plain old $, so I set the PS1 variable as such:
PS1=""
Which changes the prompt correctly, but when I change directories, it does not update the prompt. So I tried this:
PS1="`pwd`>"
I get the same results when changing... (2 Replies)
I would like to "BOLD" print the hostname in the following statement:
export PS1=$USER"@"$(hostname -s):'$PWD>'
Is there a special character I can put before and after the variable to make it bold or blinking?
Thanks. (4 Replies)
Any help developing a command to find all files on the system named ".bashrc" that modify the PS1 variable. I wanna list the full file name, including the full path, and protection. Nothing else. (2 Replies)
Is there a command for finding all files on the system named ".bashrc" that modify the PS1 variable? I'd like to list the full file name(s) and the protection (including the full path). (5 Replies)
Hi
I have set PS1 in my profile as -
PS1='${LOGNAME}@${PWD}>' ; export PS1
it works fine if I am in bash/ksh shell, but as soon as i switch to bourn shell (sh) then it shows "${LOGNAME}@${PWD}>" as prompt.
It is also not working in csh.
Please help. (3 Replies)
I have set PSI for my prompt using the following command:
PS1="${debian_chroot:+($debian_chroot)}\\u@\h:\\\w\a]\ "which produces
chrisd@pguk:~]I want to include [ in the beginning but cannot understand the way to do this.
Also I want to show only the current directory, not the whole... (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)
Hi i'm new to unix, can anyone assist in me setting the PS1 variable in unix (3 Replies)
Discussion started by: user@123
3 Replies
LEARN ABOUT OPENDARWIN
unix
UNIX(4) BSD Kernel Interfaces Manual UNIX(4)NAME
unix -- UNIX-domain protocol family
SYNOPSIS
#include <sys/types.h>
#include <sys/un.h>
DESCRIPTION
The UNIX-domain protocol family is a collection of protocols that provides local (on-machine) interprocess communication through the normal
socket(2) mechanisms. The UNIX-domain family supports the SOCK_STREAM and SOCK_DGRAM socket types and uses filesystem pathnames for address-
ing.
ADDRESSING
UNIX-domain addresses are variable-length filesystem pathnames of at most 104 characters. The include file <sys/un.h> defines this address:
struct sockaddr_un {
u_char sun_len;
u_char sun_family;
char sun_path[104];
};
Binding a name to a UNIX-domain socket with bind(2) causes a socket file to be created in the filesystem. This file is not removed when the
socket is closed--unlink(2) must be used to remove the file.
The UNIX-domain protocol family does not support broadcast addressing or any form of ``wildcard'' matching on incoming messages. All
addresses are absolute- or relative-pathnames of other UNIX-domain sockets. Normal filesystem access-control mechanisms are also applied
when referencing pathnames; e.g., the destination of a connect(2) or sendto(2) must be writable.
PROTOCOLS
The UNIX-domain protocol family is comprised of simple transport protocols that support the SOCK_STREAM and SOCK_DGRAM abstractions.
SOCK_STREAM sockets also support the communication of UNIX file descriptors through the use of the msg_control field in the msg argument to
sendmsg(2) and recvmsg(2).
Any valid descriptor may be sent in a message. The file descriptor(s) to be passed are described using a struct cmsghdr that is defined in
the include file <sys/socket.h>. The type of the message is SCM_RIGHTS, and the data portion of the messages is an array of integers repre-
senting the file descriptors to be passed. The number of descriptors being passed is defined by the length field of the message; the length
field is the sum of the size of the header plus the size of the array of file descriptors.
The received descriptor is a duplicate of the sender's descriptor, as if it were created with a call to dup(2). Per-process descriptor
flags, set with fcntl(2), are not passed to a receiver. Descriptors that are awaiting delivery, or that are purposely not received, are
automatically closed by the system when the destination socket is closed.
SEE ALSO socket(2), intro(4)
"An Introductory 4.3 BSD Interprocess Communication Tutorial", PS1, 7.
"An Advanced 4.3 BSD Interprocess Communication Tutorial", PS1, 8.
BSD June 9, 1993 BSD