Sorry, I forgot to tell you why PS1 will not export: You need to be able
to test it in shell scripts to see if you are in an interactive shell. If
it was exported, that mechanism would not work.
--
-Time flies like the wind. Fruit flies like a banana. Stranger things have -
-happened but none st
PS1 is a 'special' variable. If you export it it will not be inherited by
child processes. Just set it in your .bashrc and all will be well.
--
-Time flies like the wind. Fruit flies like a banana. Stranger things have -
-happened but none stranger than this. Does your driver's license say Organ
On Tue, 21 Nov 2000, Stan Isaacs wrote:
> > The full comment in /etc/bashrc on my machine (RH6.0) is:
> >
> > # For some unknown reason bash refuses to inherit
> > # PS1 in some circumstances that I can't figure out.B
> > # Putting PS1 here ensures that it gets loaded every time.
> > PS1="[\u@\h
> On Mon, 20 Nov 2000, Stan Isaacs wrote:
>
> >A beginner simply takes the "|" to work like a ";", and their limited
> > testing seems to show that to be correct. They are likely never to get
> > processes that take enough time to show the mistake, in simple testing.
> > Perhaps you are cor
On Mon, 20 Nov 2000, Stan Isaacs wrote:
>A beginner simply takes the "|" to work like a ";", and their limited
> testing seems to show that to be correct. They are likely never to get
> processes that take enough time to show the mistake, in simple testing.
> Perhaps you are correct, that we
If you want bash to share current history across multiple logins, you can
use the following:
export PROMPT_COMMAND='history -a; history -n'
which will run a history file read and write append every time a prompt is
issued. That said, you'll always be a prompt or two behind, and your
hist
> > 1. Bash re-starts history each time it goes into a subshell.
> > I think it would be much more reasonable to keep a uniform history
> > for a given login session, even if, for instance, you started the
> > "script" command to keep track of what you are doing. Or at least a flag
> > that
On Fri, 17 Nov 2000, Stan Isaacs wrote:
> 1. Bash re-starts history each time it goes into a subshell. I think it
>would be much more reasonable to keep a uniform history for a given
>login session, even if, for instance, you started the "script" command
>to keep track of what you a
> 1. Bash re-starts history each time it goes into a subshell.
> I think it would be much more reasonable to keep a uniform history
> for a given login session, even if, for instance, you started the
> "script" command to keep track of what you are doing. Or at least a flag
> that allowed a
At 01:50 PM 11/17/00 , Stan Isaacs wrote:
>I have several qustions about the Bash shell, some of which are probably
>true also of ksh and maybe other shells. Is there a good, detailed
>description/explaination for bash and why certain decisions have been made?
Stan, this is a poor excuse for a
L.G.:
Thanks for the reply - I'll look up the documents. I'm certain the class
does NOT want to see these gritty details, and what I'm trying to do is
to avoid having to mention them. But I do like to mention human readable
forms of output - which means mention of tabs (unless there is a bet
Stan,
I checked out www.gnu.org for the following link, but I think
that 'man bash' would give you the same thing.
http://www.gnu.org/manual/bash-2.02/html_chapter/bashref_4.es.html
http://mirrors.ccs.neu.edu/UNIXhelp/shell/bash_hist.html
Getting into the nitty gritty of bash syntax, and what s
I have several qustions about the Bash shell, some of which are probably
true also of ksh and maybe other shells. Is there a good, detailed
description/explaination for bash and why certain decisions have been made?
In particular:
1. Bash re-starts history each time it goes into a subshell. I
13 matches
Mail list logo
