zsh-users
 help / color / mirror / code / Atom feed
From: "İsmail Dönmez" <ismail@donmez.ws>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: zsh-users@zsh.org
Subject: Re: Silent setopt
Date: Wed, 23 Jan 2013 13:28:34 +0100	[thread overview]
Message-ID: <CAJ1KOAhD8E1YOyLa22MSgPvCjGiZ9ah7NFzceMqWUS3O=ixD-Q@mail.gmail.com> (raw)
In-Reply-To: <20130123121400.5239671d@pwslap01u.europe.root.pri>

[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]

Hi;

On Wed, Jan 23, 2013 at 1:14 PM, Peter Stephenson
<p.stephenson@samsung.com>wrote:

> On Wed, 23 Jan 2013 11:32:54 +0000
> Peter Stephenson <p.stephenson@samsung.com> wrote:
> > On Wed, 23 Jan 2013 11:21:38 +0100
> > İsmail Dönmez <ismail@donmez.ws> wrote:
> > > I am using the same zsh config across a lot of machine which have all
> kinds
> > > of versions of zsh and when I ssh into an old zsh machine I get
> > >
> > > setopt:47: no such option: COMBININGCHARS
> > > setopt:48: no such option: HASH_EXECUTABLESONLY
> > >
> > > Which is expected but gets boring after some time. So I wonder if
> there is
> > > a way to silence setopt for unsupported options?
> >
> > It should be as simple as
> >
> > setopt COMBININGCHARS HASHEXECUTABLESONLY 2>/dev/null
>
> Ooh, I've noted a slightly more sophisticated (but slower) way in my
> .zshrc.
>
>   zmodload -i zsh/parameter
>   for opt in incappendhistory histexpiredupsfirst typesetsilent; do
>     [[ -n ${options[$opt]} ]] && setopt $opt
>   done
>
> This relies on the special options associative array, also used by
> completion.
>

Elegant, thanks!

      reply	other threads:[~2013-01-23 12:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 10:21 İsmail Dönmez
2013-01-23 11:32 ` Peter Stephenson
2013-01-23 12:14   ` Peter Stephenson
2013-01-23 12:28     ` İsmail Dönmez [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='CAJ1KOAhD8E1YOyLa22MSgPvCjGiZ9ah7NFzceMqWUS3O=ixD-Q@mail.gmail.com' \
    --to=ismail@donmez.ws \
    --cc=p.stephenson@samsung.com \
    --cc=zsh-users@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).