Suggestions (bash 1.02)

Thread View: gnu.bash.bug

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by drw Wed, 16 Aug 1989 03:21

#471

Author: drw
Date: Wed, 16 Aug 1989 03:21

7 lines
522 bytes

In the README file, you should make it clear that
'decode_prompt_string' is a C function that the value of PS1/PS2 is
fed through, not a bash command function.

Could you support a $cwd variable?

Dale

Re: Suggestions (bash 1.02)

#476

Author: Chet Ramey
Date: Wed, 16 Aug 1989 16:56

15 lines
880 bytes

In article <8908160321.AA07596@schubert.mit.edu> drw@BOURBAKI.MIT.EDU writes:

>Could you support a $cwd variable?

What's wrong with $PWD?

Chet Ramey




Chet Ramey			"We are preparing to think about contemplating 
Network Services Group, CWRU	 preliminary work on plans to develop a
chet@cwjcc.INS.CWRU.Edu		 schedule for producing the 10th Edition of 
				 the Unix Programmers Manual." -- Andrew Hume

Suggestions (bash 1.02)

#479

Author: Brian Fox
Date: Thu, 17 Aug 1989 19:45

13 lines
776 bytes

   Date: Tue, 15 Aug 89 23:21:17 EDT
   From: drw@bourbaki.mit.edu

   In the README file, you should make it clear that
   'decode_prompt_string' is a C function that the value of PS1/PS2 is
   fed through, not a bash command function.

   Could you support a $cwd variable?

The value of the current working directory is kept in $PWD.

brian

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads