zsh-workers
 help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh workers <zsh-workers@zsh.org>
Subject: Re: incorrect setopt completion
Date: Sat, 15 Aug 2015 04:14:57 +0200	[thread overview]
Message-ID: <CAHYJk3QtvBiEVTzu0+vDcp_VYMTwVEAwRwpgPviPShHLGT=f+w@mail.gmail.com> (raw)
In-Reply-To: <150814190936.ZM17069@torch.brasslantern.com>

On Sat, Aug 15, 2015 at 4:09 AM, Bart Schaefer
<schaefer@brasslantern.com> wrote:
> On Aug 15,  2:05am, Vincent Lefevre wrote:
> }
> } zira:~> setopt | grep print
> } printexitvalue
> }
> } "setopt nopri[TAB]" and "unsetopt pri[TAB]" don't give any completion.
> } However "setopt pri[TAB]" has printexitvalue among its completions.
> } This should be the opposite!
>
> Hm.
>
> _main_complete is saving the state of the options as early as it can,
> but XTRACE, PRINTEXITVALUE, LOCALOPTIONS, and LOCALLOOPS are all subject
> to being saved/restored during the execution of shell functions, which
> of course means the entirety of compsys.
>
> There's no way to fix this from shell script code.  The state of the
> options will have to be stashed somewhere at the C code level before
> completion functions are entered, if we want this to work.

I guess I should amend my patch to include all four of these.

-- 
Mikael Magnusson


  reply	other threads:[~2015-08-15  2:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-15  0:05 Vincent Lefevre
2015-08-15  1:02 ` Mikael Magnusson
2015-08-17 22:02   ` Daniel Shahaf
2015-08-15  2:09 ` Bart Schaefer
2015-08-15  2:14   ` Mikael Magnusson [this message]
2015-08-16 22:55     ` Mikael Magnusson

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='CAHYJk3QtvBiEVTzu0+vDcp_VYMTwVEAwRwpgPviPShHLGT=f+w@mail.gmail.com' \
    --to=mikachu@gmail.com \
    --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).