Re: [Nmh-workers] More than one parameters in .mh_profile

2012-05-29 Thread Ralph Corderoy
Hi Ken, for (s = cmd; *s; s++) { if (*s != ' ' !isALPHA(*s) strchr($*(){}[]'\;\\|?~`\n,*s)) { Seems like that's a pretty good list; if we see one of those characters, it gets sent to /bin/sh -c. Otherwise we split and do it ourselves. No `#'? How about just

Re: [Nmh-workers] More than one parameters in .mh_profile

2012-05-29 Thread valdis . kletnieks
On Tue, 29 May 2012 10:01:22 +0100, Ralph Corderoy said: No `#'? How about just always send to the user's shell from the password entry with a -c, as distinct from /bin/sh. The problem is that some people (at least in the Elder TImes) would have their login shell set to /bin/csh but they'd

Re: [Nmh-workers] More than one parameters in .mh_profile

2012-05-29 Thread Kevin Cosgrove
On 29 May 2012 at 8:00, valdis.kletni...@vt.edu wrote: On Tue, 29 May 2012 10:01:22 +0100, Ralph Corderoy said: No `#'? How about just always send to the user's shell from the password entry with a -c, as distinct from /bin/sh. The problem is that some people (at least in the Elder

Re: [Nmh-workers] More than one parameters in .mh_profile

2012-05-29 Thread Ralph Corderoy
Hi Valdis, No `#'? How about just always send to the user's shell from the password entry with a -c, as distinct from /bin/sh. The problem is that some people (at least in the Elder TImes) would have their login shell set to /bin/csh but they'd want their scripty things done in /bin/sh.

Re: [Nmh-workers] More than one parameters in .mh_profile

2012-05-29 Thread Tethys
valdis.kletni...@vt.edu writes: No `#'? How about just always send to the user's shell from the password entry with a -c, as distinct from /bin/sh. The problem is that some people (at least in the Elder TImes) would have their login shell set to /bin/csh but they'd want their scripty things

Re: [Nmh-workers] More than one parameters in .mh_profile

2012-05-29 Thread Jerrad Pierce
In which case, couldn't they just do sh -c whatever as the thing that would get passed to their login shell (i.e., csh)? It's a bit clumsy, but it should work for the few people that are in that situation. Why do you want to use the user shell exactly? Yes, the user might be more familiar with

Re: [Nmh-workers] More than one parameters in .mh_profile

2012-05-29 Thread Paul Vixie
On 2012-05-29 2:46 PM, Kevin Cosgrove wrote: On 29 May 2012 at 8:00, valdis.kletni...@vt.edu wrote: ... Does anybody still do that? Why yes, my login shell is /bin/tcsh and I program in sh, bash, perl. me too, give or take a conditional exec tcsh in my .cshrc file.

Re: [Nmh-workers] More than one parameters in .mh_profile

2012-05-29 Thread Lyndon Nerenberg
On 2012-05-29, at 7:19 PM, Paul Vixie wrote: for that we have getenv('SHELL'), which is far more closely related to the user's preferred command language than either their login shell or the posix standard are going to be. This conversation is cool. It reminds me of a phone call I had with