On Wednesday, February 27, 2013 01:31:58 PM Thorsten Glaser wrote:
> Why whitespace? $IFS certainly contains none. And the usual
> insertion rules all specify the first character of $IFS and
> specify what to do if $IFS is empty or unset (which it isn’t
> in these examples).
Well, ok then. I'm jus
Chet Ramey wrote:
> On 2/27/13 11:05 PM, Linda Walsh wrote:
>>
>> Greg Wooledge wrote:
How often, when at a terminal, do you type #!/bin/bash before every line?
>>> When I've put the contents into a file? Every. single. time.
>> ---
>> Then when I press 'v' to edit the command line in a tex
On Thu, Feb 28, 2013 at 09:55:01AM -0700, Bob Proulx wrote:
> Who still remembers when if the exec(2) failed then the shell
> examined the first character. If it was a '#' then shell ran the file
> through csh. If ':' then through ksh. If neither then sh. This may
> have been a local hack thou
* On 2013-02-28 at 19:13 GMT, Chet Ramey wrote:
> On 2/28/13 9:24 AM, Jonathan Perkin wrote:
>
> > There is already handling for this chosen behaviour within sh_eaccess(), so
> > it
> > is simply a matter of extending it for the faccessat() case, as implemented
> > in
> > the patch below (agains
On 2/28/13 9:24 AM, Jonathan Perkin wrote:
> The implementation-defined behaviour of access() and faccessat() on Solaris is
> as follows:
>
> If any access permissions are to be checked, each will be
> checked individually, as described in Intro(2). If the
> process has appropria
On Thu, Feb 28, 2013 at 7:09 PM, Andreas Schwab wrote:
> Bob Proulx writes:
>
>> I say that somewhat tongue-in-cheek myself. Because sourcing files
>> removes the abstraction barriers of a stacked child process and
>> actions there can persistently change the current shell. Not good as
>> a gen
Bob Proulx writes:
> I say that somewhat tongue-in-cheek myself. Because sourcing files
> removes the abstraction barriers of a stacked child process and
> actions there can persistently change the current shell. Not good as
> a general interface for random actions. Normal scripts are better.
The implementation-defined behaviour of access() and faccessat() on Solaris is
as follows:
If any access permissions are to be checked, each will be
checked individually, as described in Intro(2). If the
process has appropriate privileges, an implementation may
indicate suc
Chet Ramey wrote:
> Linda Walsh wrote:
> > Greg Wooledge wrote:
> >>> How often, when at a terminal, do you type #!/bin/bash before every line?
> >>
> >> When I've put the contents into a file? Every. single. time.
> > ---
> > Then when I press 'v' to edit the command line in a text editor --
> >
On 2/27/13 11:05 PM, Linda Walsh wrote:
>
>
> Greg Wooledge wrote:
>>> How often, when at a terminal, do you type #!/bin/bash before every line?
>>
>> When I've put the contents into a file? Every. single. time.
> ---
> Then when I press 'v' to edit the command line in a text editor --
> maybe '
10 matches
Mail list logo
