Re: tcsh and chere-0.3-1

2004-10-15 Thread Igor Pechtchanski
On Thu, 14 Oct 2004, Dave wrote: --- Andrew Grimm [EMAIL PROTECTED] wrote: http://cygwin.com/acronyms/#PCYMTNQREAIYR. Thanks. Igor Pechtchanski said: Does anyone know of a way to get a `-` at the start of $0? I believe this will force all the shells to start as login shells and is

Re: tcsh and chere-0.3-1 (fwd)

2004-10-14 Thread Dave
From: Andrew Grimm On Wed, Oct 13, 2004 at 07:02:13PM -0400, Christopher Faylor wrote: Actually, All shells which support -l seem to cd to the home directory. I'm not sure what the -l adds to the above since the above code just calls the shell again after cd'ing to the directory. I think

Re: tcsh and chere-0.3-1 (fwd)

2004-10-14 Thread Igor Pechtchanski
On Thu, 14 Oct 2004, Dave wrote: [snip] If that is the case then maybe we could get some coordination going and set a CYGWIN_CD_HERE environment variable or something and just have the login shell cd to the right directory automatically with the help of the /etc/* scripts. This would

Re: tcsh and chere-0.3-1

2004-10-14 Thread Andrew Grimm
Igor Pechtchanski said: Does anyone know of a way to get a `-` at the start of $0? I believe this will force all the shells to start as login shells and is the most generic solution. Sure. 'bash -c exec -l $PROG $ARGS'. :-) Ya beat me to it :) Although, in the current design, this would

Re: tcsh and chere-0.3-1

2004-10-14 Thread Dave
--- Andrew Grimm [EMAIL PROTECTED] wrote: Igor Pechtchanski said: Does anyone know of a way to get a `-` at the start of $0? I believe this will force all the shells to start as login shells and is the most generic solution. Sure. 'bash -c exec -l $PROG $ARGS'. :-) Ya beat me to

tcsh and chere-0.3-1

2004-10-13 Thread Andrew Grimm
The new (very cool!) chere package doesn't work with tcsh, at least on my system. The problem is that tcsh -l doesn't work with any additional arguments. There is even a comment to that effect in the script: tcsh ) # Apparently -l only applies if it is the only argument # so

Re: tcsh and chere-0.3-1

2004-10-13 Thread Andrew Grimm
Actually I made a minor goof, the order should be: /etc/csh.cshrc /etc/csh.login ~/.tcshrc ~/.login There is also the possibility that ~/.tcshrc does not exist, if that is the case ~/.cshrc should be read (but not both). I didn't bother with that as I use

Re: tcsh and chere-0.3-1

2004-10-13 Thread Christopher Faylor
On Wed, Oct 13, 2004 at 03:58:02PM -0600, Andrew Grimm wrote: The new (very cool!) chere package doesn't work with tcsh, at least on my system. The problem is that tcsh -l doesn't work with any additional arguments. There is even a comment to that effect in the script: tcsh ) #

Re: tcsh and chere-0.3-1

2004-10-13 Thread Christopher Faylor
On Wed, Oct 13, 2004 at 07:02:13PM -0400, Christopher Faylor wrote: It almost seems like you could just use to invoke the real shell in all ash cases. That would be faster. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports:

Re: tcsh and chere-0.3-1

2004-10-13 Thread Andrew Grimm
On Wed, Oct 13, 2004 at 07:02:13PM -0400, Christopher Faylor wrote: Actually, All shells which support -l seem to cd to the home directory. I'm not sure what the -l adds to the above since the above code just calls the shell again after cd'ing to the directory. I think the purpose of that is to

Re: tcsh and chere-0.3-1

2004-10-13 Thread Christopher Faylor
On Wed, Oct 13, 2004 at 06:20:55PM -0600, Andrew Grimm wrote: I think with most login shells the cd $HOME behavior is due to the way the scripts are written in /etc (for example Cygwin's /etc/csh.login). That is probably a good thing to have in the script, but it presents a difficulty for this