zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: localoptions, emulate -L, and top-level shell
Date: Mon, 05 Dec 2016 09:46:12 +0000	[thread overview]
Message-ID: <20161205094612.2ca609b3@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <20161203082343.GA6789@fujitsu.shahaf.local2>

On Sat, 3 Dec 2016 08:23:43 +0000
Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> Bart Schaefer wrote on Fri, Dec 02, 2016 at 15:50:33 -0800:
> > I'm wondering whether "setopt localoptions", including via "emulate -L",
> > perhaps ought to at least grumble if its state changes from unset to set
> > at the top level of an interactive shell.
> > 
> > Can wait until after 5.3, obviously.  Just thinking "aloud."
> 
> Perhaps some people intentionally setopt localoptions in .zshrc so that
> no plugin can change global options... but then, a plugin doing «setopt
> nolocaloptions foo» would still set 'foo' globally, despite the zshrc
> setting.

I think setting localoptions globally for the benefit of safety with
your own functions is a perfectly reasonable usage --- and it's also
compatible with supplied functions, which will happily leave the glocal
setting alone, so probably best not to do anything to undermine it
centrally.

I'm vaguely aware of having used "nolocaloptions" to pass up option
settings in the past, but I don't think there are standard functions
that do that.

pws


  reply	other threads:[~2016-12-05  9:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-02 23:50 Bart Schaefer
2016-12-03  8:23 ` Daniel Shahaf
2016-12-05  9:46   ` Peter Stephenson [this message]
2016-12-06  0:09     ` Bart Schaefer
2016-12-03  9:01 ` Sebastian Gniazdowski

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=20161205094612.2ca609b3@pwslap01u.europe.root.pri \
    --to=p.stephenson@samsung.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).