zsh-workers
 help / color / mirror / code / Atom feed
From: Martijn Dekker <martijn@inlv.org>
To: Bart Schaefer <schaefer@brasslantern.com>,
	Zsh hackers list <zsh-workers@zsh.org>
Subject: interactive comments [was: exported unset variables]
Date: Sat, 29 Oct 2016 21:20:51 +0100	[thread overview]
Message-ID: <474aa7c9-4dd8-7d88-1cbd-df58a03e7e13@inlv.org> (raw)
In-Reply-To: <161029120555.ZM17132@torch.brasslantern.com>

Op 29-10-16 om 20:05 schreef Bart Schaefer:
> The only other thing might be to also give it the OPT_EMULATE flag, but
> I'm uncertain about that.  In what circumstances are you encountering
> difficulty with this?

None really, it was just a difference that slipped under my radar until now.

Yes, zsh invoked as sh or ksh already parses comments on the interactive
command line. It would seem logical to me for 'emulate sh' and 'emulate
ksh' to enable that behaviour as well.

Thanks,

- M.


  reply	other threads:[~2016-10-29 20:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-22  3:02 'export -p' lacks POSIX output Martijn Dekker
2016-10-22 18:24 ` Bart Schaefer
2016-10-23 12:00   ` Martijn Dekker
2016-10-23 16:47     ` Bart Schaefer
2016-10-24  8:33   ` Peter Stephenson
2016-10-28 21:00 ` exported unset variables [was: 'export -p' lacks POSIX output] Martijn Dekker
2016-10-28 21:31   ` Bart Schaefer
2016-10-28 21:48     ` Martijn Dekker
2016-10-29  0:18       ` Bart Schaefer
2016-10-29  8:11         ` Martijn Dekker
2016-10-29 18:09           ` Bart Schaefer
2016-10-29 18:43             ` Peter Stephenson
2016-10-29 19:05           ` Bart Schaefer
2016-10-29 20:20             ` Martijn Dekker [this message]
2016-10-30  1:25               ` interactive comments [was: exported unset variables] 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=474aa7c9-4dd8-7d88-1cbd-df58a03e7e13@inlv.org \
    --to=martijn@inlv.org \
    --cc=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).