multi-digit file descriptors

multi-digit file descriptors

[Vincent Lefevre]

Contrary to bash and mksh, zsh doesn't support file descriptors with
multiple digits. Considered the following file "redir".

----------------------------------------
( echo foo >&9; ) 9>my_file
cat my_file

( echo bar >&10; ) 10>my_file
cat my_file
----------------------------------------

xvii% bash redir
foo
bar
xvii% mksh redir
foo
bar
xvii% zsh redir
foo
redir:4: parse error near `10'

The behavior of dash and ksh93 is similar to zsh. But is there any
reason?

BTW, POSIX doesn't seem to restrict file descriptors to 1 digit.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: multi-digit file descriptors

[Bart Schaefer]

[-- Attachment #1: Type: text/plain, Size: 302 bytes --]

On Feb 11, 2015 8:28 AM, "Vincent Lefevre" <vincent@vinc17.net> wrote:
>
> The behavior of dash and ksh93 is similar to zsh. But is there any
> reason?

Zsh reserves descriptors 10 and up for internal use; for example, 10 is
nearly always a copy of the original input terminal in an interactive shell.

Re: multi-digit file descriptors

[Peter Stephenson]

On Wed, 11 Feb 2015 09:27:51 -0800
Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Feb 11, 2015 8:28 AM, "Vincent Lefevre" <vincent@vinc17.net> wrote:
> >
> > The behavior of dash and ksh93 is similar to zsh. But is there any
> > reason?
> 
> Zsh reserves descriptors 10 and up for internal use; for example, 10 is
> nearly always a copy of the original input terminal in an interactive shell.

You can grab use of one yourself with the recommended syntax (we
actually agreed this with David Korn):

  local foo
  exec {foo}>blah
  echo bleugh >&$foo

and given what Bart mentioned we wouldn't be that keen to open it up
more widely.

Note there's nothing magic about foo, it just contains a number.  So you
can do

  local foo=12
  exec {foo}>&-

etc.

pws

Re: multi-digit file descriptors

[Stephane Chazelas]

2015-02-11 17:26:37 +0100, Vincent Lefevre:
> Contrary to bash and mksh, zsh doesn't support file descriptors with
> multiple digits. Considered the following file "redir".
> 
> ----------------------------------------
> ( echo foo >&9; ) 9>my_file
> cat my_file
> 
> ( echo bar >&10; ) 10>my_file
> cat my_file
> ----------------------------------------
> 
> xvii% bash redir
> foo
> bar
> xvii% mksh redir
> foo
> bar
> xvii% zsh redir
> foo
> redir:4: parse error near `10'
> 
> The behavior of dash and ksh93 is similar to zsh. But is there any
> reason?
> 
> BTW, POSIX doesn't seem to restrict file descriptors to 1 digit.
[...]

Related discussion on the austin-group mailing list:

http://thread.gmane.org/gmane.comp.standards.posix.austin.general/10094

-- 
Stephane

Re: multi-digit file descriptors

[Vincent Lefevre]

On 2015-02-11 09:27:51 -0800, Bart Schaefer wrote:
> On Feb 11, 2015 8:28 AM, "Vincent Lefevre" <vincent@vinc17.net> wrote:
> > The behavior of dash and ksh93 is similar to zsh. But is there any
> > reason?
> 
> Zsh reserves descriptors 10 and up for internal use; for example, 10 is
> nearly always a copy of the original input terminal in an interactive shell.

But this doesn't explain the error message, in particular...

On 2015-02-11 20:47:09 +0000, Stephane Chazelas wrote:
> Related discussion on the austin-group mailing list:
> 
> http://thread.gmane.org/gmane.comp.standards.posix.austin.general/10094

which mentions the use of 09. With zsh:

( echo foo >&09; ) 09>my_file

still gives an error:

redir:4: parse error near `09'

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: multi-digit file descriptors

[Vincent Lefevre]

On 2015-02-11 17:46:05 +0000, Peter Stephenson wrote:
> You can grab use of one yourself with the recommended syntax (we
> actually agreed this with David Korn):
> 
>   local foo
>   exec {foo}>blah
>   echo bleugh >&$foo

However this is not portable (not supported by dash and mksh).

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: multi-digit file descriptors

[Bart Schaefer]

On Feb 12, 11:24am, Vincent Lefevre wrote:
} Subject: Re: multi-digit file descriptors
}
} On 2015-02-11 17:46:05 +0000, Peter Stephenson wrote:
} > You can grab use of one yourself with the recommended syntax (we
} > actually agreed this with David Korn):
} > 
} >   local foo
} >   exec {foo}>blah
} >   echo bleugh >&$foo
} 
} However this is not portable (not supported by dash and mksh).

Well, neither are multi-digit fd redirections (which was actually
sort of the point of that austin-group thread although it came at
the issue from a different direction).

Re: multi-digit file descriptors

[Bart Schaefer]

On Feb 12, 11:16am, Vincent Lefevre wrote:
} Subject: Re: multi-digit file descriptors
}
} On 2015-02-11 09:27:51 -0800, Bart Schaefer wrote:
} > Zsh reserves descriptors 10 and up for internal use; for example, 10 is
} > nearly always a copy of the original input terminal in an interactive shell.
} 
} But this doesn't explain the error message, in particular...
} 
} ( echo foo >&09; ) 09>my_file
} 
} still gives an error:
} 
} redir:4: parse error near `09'

"09>my_file" is parsed as "09" ">" "my_file", because zsh doesn't support
multi-digit descriptors on the left side of a redirect.  So what you have
is the same as

  { ( echo foo >&09 ) 09 } > my_file

Which is a parse error because you can't follow a subshell with an argument
list.

Zsh does support multi-digit descriptors on the right side, so >&09 is all
one token (and is the same as >&9 in this case).