zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: PATCH: refactor memstream for "print -v"
Date: Tue, 5 Jan 2016 08:33:03 -0800	[thread overview]
Message-ID: <160105083303.ZM3620@torch.brasslantern.com> (raw)
In-Reply-To: <20160105114701.5b7d8363@pwslap01u.europe.root.pri>

On Jan 5, 11:47am, Peter Stephenson wrote:
} Subject: Re: PATCH: refactor memstream for "print -v"
}
} On Tue, 5 Jan 2016 09:48:21 +0000
} Peter Stephenson <p.stephenson@samsung.com> wrote:
} > > - I note in passing that "print something >&-" is explicitly not an error,
} > >   but "print -u1 something >&-" IS an error.  Also unchanged here.
} > 
} > In the second case we've explicitly been told to "do something" with the
} > fd, which happens to be dup'ing and fdopen'ing it.  There's no such code
} > in the first place, and there doesn't seem any point in making the
} > second case silent.
} 
} Actually, it appears this is deliberate.

Yeah, I knew it was deliberate, though I'd forgotten about the discussion
with Zefram.

Recent bash do emit an error on "echo >&-", for whatever that's worth, in
case we want to revisit Zefram's argument.


  reply	other threads:[~2016-01-05 16:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-05  7:18 Bart Schaefer
2016-01-05  9:48 ` Peter Stephenson
2016-01-05 11:47   ` Peter Stephenson
2016-01-05 16:33     ` Bart Schaefer [this message]
2016-01-05 16:31 ` Jun T.
2016-01-05 17:58   ` Bart Schaefer
2016-01-06  6:02     ` Jun T.
2016-01-06 21:30       ` Bart Schaefer
2016-01-08 12:32         ` Jun T.
2016-01-09  4:37           ` Bart Schaefer

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=160105083303.ZM3620@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \
    /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).