On Thu, 20 Jun 2013 10:36:44 -0400 David Korn wrote:
> > ~{fd}/.. doesn't work. It returns the /proc/pid/fd directory and not
> > the parent of the directory opened via openat().
> This is a bug which I will fix.
> >
> > The bash and dash camps have already rejected ~{fd}/rel_path as "not
> > in the spirit of POSIX", and that implementing relative paths via
> > ~{fd} creates too much code bloat.
I don't understand the code bloat argument because I bet cd isn't the last thing
that people will want to add -f fd to
besides, shell already handles ~ (per posix) and ~{fd} would be one more
addition to that centralized code
> Since ksh93 already supports exec {fd}< file, supporting ~{fd} fits
> in naturally. I will consider adding -f fd, if bash and dash add it,
> but it will be equivalent to ~{fd}/rel_path.
> >
> > Wendy
> >
> David Korn
> [email protected]
> _______________________________________________
> ast-developers mailing list
> [email protected]
> http://lists.research.att.com/mailman/listinfo/ast-developers
_______________________________________________
ast-developers mailing list
[email protected]
http://lists.research.att.com/mailman/listinfo/ast-developers
