zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: PGP; stdin/heredoc
Date: Tue, 01 May 2007 08:26:36 -0700	[thread overview]
Message-ID: <070501082636.ZM22388@torch.brasslantern.com> (raw)
In-Reply-To: <20070501005603.GB95730@redoubt.spodhuis.org>

On Apr 30,  5:56pm, Phil Pennock wrote:
} 
} Anyone have any preferences yay-nay about PGP-signing submitted patches?

No particular preference.  Many readers of this mailing list (at least
in the past) have preferred that there be no MIME attachments or other
MIME-multipart messages; unless the patch is really large, keep it in
plain text in the message body, use text/plain not text/x-patch or some
other weird type if you must attach it, and don't sign with S/MIME.

} For builtin/module commands, is there a real facility for
} being able to get at the virtual stdin provided which supports
} heredoc/herestring/etc?

I'm not sure what you mean, or why you care.  Unless you're adding a
syntactic construct rather than just a builtin command, the virtual
stdin is indistinguishable from real stdin by the time control has
transferred from the parser to your module.  The here-document is
copied to a temporary file and the descriptor for that file is dup'd
to stdin, THEN zrb is called.

So presumably you could get at the virtual stdin by doing fstat() or
some such on fd 0, or isatty(0) or (in a function) [[ -t 0 ]] may give
you enough information to decide to change behavior.


      reply	other threads:[~2007-05-01 15:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01  0:56 Phil Pennock
2007-05-01 15:26 ` Bart Schaefer [this message]

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=070501082636.ZM22388@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@sunsite.dk \
    /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).