You are correct, sir!
Momentary loss of brain wave activity. It never worked under 1.14
because I just recently got a working X server. Hence I never would have
known whether it worked or not. All my VC logins *were* login
shells...duh!
Thanks to your pointers, the O'Reilly bash book, and my own /etc/profile
which I'd hacked once before I got the prompt to give me what I wanted..,
[EMAIL PROTECTED] on one line and working directory on another line.
For those interested this does what I wanted: PS1='<[EMAIL
PROTECTED]>\n<`pwd`>\$'
Thanks joost (and one other helpful responder-sorry deleted your mail
before engaging my brain).
kfh
On Sun, 15 Jun 1997, joost witteveen wrote:
> > Question 1: since this used to work under bash 1.14, I presume it's
> > related to bash 2.00's posix compliance, but what 2.00 convention have I
> > broke? Where should I put the matching `'' to get the same functionality
> > as before?
>
> Well, I seriously doubt if this worked under bash 1.14: you're messing
> up the quotes. Eighter you want:
>
> PS1="\u\'@'\h\n\w"
>
> or you want
>
> PS1='[EMAIL PROTECTED]'
>
> (I guess the latter). What you've got now is simply a unfished string.
>
> > Question 2: Why doesn't the error occur in the default xterm. After all
> > that isn't a login shell...is it?
>
> Login shells parse ~/.bash_login, non-login shells (in xterm) parse
> ~/.bash_rc.
>
>
>
> --
> joost witteveen, [EMAIL PROTECTED]
> #!/usr/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
> $/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
> lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
> #what's this? see http://www.dcs.ex.ac.uk/~aba/rsa/
>
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
