From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: PATCH: vcs_info: Set NO_warn_create_global option
Date: Sun, 21 Feb 2010 13:17:40 -0800 [thread overview]
Message-ID: <100221131740.ZM24810@torch.brasslantern.com> (raw)
In-Reply-To: <87d3zy8ib8.fsf@ft.bewatermyfriend.org>
On Feb 21, 9:06pm, Frank Terbeck wrote:
}
} > d) Suppress warn_create_global for the parameters "reply" and "REPLY"
} > at all times. In fact it probably ought to be suppressed for STTY
} > and a few others in the "Parameters Used By The Shell" section of
} > the manual.
}
} You're probably right that this should always apply to `reply', `REPLY'
} and the like. I don't know how to do that, though. Would you always have
} such parameters be available globally, even after an `unset'?
No, leaving them available would violates some of the other rules of
"non-special" parameters.
} Any ideas where to apply the leverage?
In Src/params.c, assignsparam() and assignaparam(), I suppose, by a
check of v->pm->node.nam against a list (which doesn't exist yet) of
parameters that don't require warnings. I further suppose that list
could itself be controlled by a parameter, but that'd have to be
handled carefully to avoid fetching a value while setting it.
I see PWS has already applied your (a) patch from 27731, so perhaps
this discussion is moot ...
next prev parent reply other threads:[~2010-02-21 21:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-21 14:53 Frank Terbeck
2010-02-21 15:09 ` PATCH: Disable WARN_CREATE_GLOBAL in 'zstyle -e' code Frank Terbeck
2010-02-21 15:18 ` Frank Terbeck
2010-02-21 17:25 ` PATCH: vcs_info: Set NO_warn_create_global option Bart Schaefer
2010-02-21 20:06 ` Frank Terbeck
2010-02-21 21:17 ` Bart Schaefer [this message]
2010-02-21 21:34 ` Frank Terbeck
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=100221131740.ZM24810@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).