zsh-workers
 help / color / mirror / code / Atom feed
From: Zoltan Hidvegi <hzoli@cs.elte.hu>
To: pws@ifh.de (Peter Stephenson)
Cc: zsh-workers@math.gatech.edu
Subject: Re: More Configure problems
Date: Thu, 1 Aug 1996 19:55:32 +0200 (MET DST)	[thread overview]
Message-ID: <199608011755.TAA00850@bolyai.cs.elte.hu> (raw)
In-Reply-To: <199608011740.TAA03299@hydra.ifh.de> from Peter Stephenson at "Aug 1, 96 07:40:59 pm"

Peter wrote:
> > Next problem with Configure... actually with the makedepend script
> > that comes with it:  this assignment is failing:
> > 
> >     defrule=`<$mf sed -n		\
> > ...
> > 
> > That first interestingly positioned <$mf (sometimes I wonder if people
> > do this deliberately) is supposed to be a redirection, but zsh is
> > treating it like $(<...).  ksh behaves like sh here, i.e. only $(<...)
> > has that behaviour.  Perhaps we should follow suit.
> 
> Well, there's only about one possible fix, as follows.  The manual
> page mentions $(<...) and specifically fails to mention `<...`, so I
> think we're in line with that after the patch.  No other Configure
> problems that I've noticed.  (This is actually non-trivial, if you
> want to install perl on Linux without having to have bash around.)

I'd prefer a different fix.  I think it is better to parse each command
substitution lexically and if it consists of a single redirection to stdin
than behave as $(< file) behaves now.  This is really preferrable since $(<
file command) should execute the given command.  That's the ksh behaviour
and that's what required by POSIX.  I'll try to write a patch for that.

Zoltan


  reply	other threads:[~1996-08-01 18:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-07-31 21:11 Announcement draft Zoltan Hidvegi
1996-07-31 22:15 ` Zefram
1996-08-01  6:36 ` Bas V. de Bakker
1996-08-01  8:31   ` Peter Stephenson
1996-08-01  9:04     ` Running zsh as sh (Was: Announcement draft) Bas V. de Bakker
1996-08-01  9:10     ` Announcement draft Andrej Borsenkow
1996-08-01 13:49       ` Here docs Peter Stephenson
1996-08-01 14:07         ` Zoltan Hidvegi
1996-08-01 16:27           ` More Configure problems Peter Stephenson
1996-08-01 17:40             ` Peter Stephenson
1996-08-01 17:55               ` Zoltan Hidvegi [this message]
1996-08-01 21:03                 ` Zoltan Hidvegi
1996-08-01 23:30                   ` Zoltan Hidvegi
1996-08-02  8:32                   ` Peter Stephenson
1996-08-02 10:03                     ` Andrej Borsenkow
1996-08-02 13:29                       ` Zoltan Hidvegi
1996-08-02  1:03             ` Zefram
1996-08-01 14:42   ` Announcement draft Zoltan Hidvegi
1996-08-08 15:13 ` sh compatibility again :-> Andrej Borsenkow
1996-08-12  2:18   ` Zoltan Hidvegi
1996-08-12  4:36     ` Bart Schaefer
1996-08-12  5:00       ` Zefram
1996-08-12  6:01         ` Bart Schaefer
1996-08-12  6:34           ` Bart Schaefer
1996-08-12  6:20       ` Andrej Borsenkow

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199608011755.TAA00850@bolyai.cs.elte.hu \
    --to=hzoli@cs.elte.hu \
    --cc=pws@ifh.de \
    --cc=zsh-workers@math.gatech.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).