From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: exported unset variables [was: 'export -p' lacks POSIX output]
Date: Sat, 29 Oct 2016 12:05:55 -0700 [thread overview]
Message-ID: <161029120555.ZM17132@torch.brasslantern.com> (raw)
In-Reply-To: <6db9e2a5-8f0b-71a2-95e6-8a8bbf4a281e@inlv.org>
On Oct 29, 9:11am, Martijn Dekker wrote:
}
} > } (Also, is it correct/expected behaviour that zsh doesn't parse comments
} > } on the interactive command line? Blindly copying/pasting the above won't
} > } work for that reason.)
} >
} > Yes, the option INTERACTIVE_COMMENTS has to be set to recognize comments
} > at the command line. Should this be on in POSIX mode?
}
} I think so. All the other shells recognise comments in interactive mode
} by default.
Hmm, it looks like this is already the case; if I invoke zsh as "ksh":
$ setopt | grep comment
nointeractivecomments off
And indeed the source gives interactivecomments the OPT_BOURNE flag.
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?
next prev parent reply other threads:[~2016-10-29 19:11 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 [this message]
2016-10-29 20:20 ` interactive comments [was: exported unset variables] Martijn Dekker
2016-10-30 1:25 ` 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=161029120555.ZM17132@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).