zsh-workers
 help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Marlon Richert <marlon.richert@gmail.com>,
	Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [BUG] zle_highlight fails to highlight suffix added with compadd -R
Date: Wed, 8 Sep 2021 04:13:36 +0200	[thread overview]
Message-ID: <CAHYJk3RJA+=owtdOkf85gO2nchgq2VkzXvHYAFJUU-QrkMQk+g@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7Y0yT7d+HBuZ37dWGfSf_CQJfHp5Z9h9d9WTuCgRL_Kow@mail.gmail.com>

On 9/8/21, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Tue, Sep 7, 2021 at 3:07 AM Marlon Richert <marlon.richert@gmail.com>
> wrote:
>>
>> _tst() { compadd -S '<SUFFIX>' -q -- '' }
>> _tst() { compadd -S '<SUFFIX>' -r '' -- '' }
>> _tst() { compadd -S '<SUFFIX>' -R '' -- '' }
>>
>> With the first two functions, <SUFFIX> correctly gets highlighted as
>> autoremovable. However, with the third function, <SUFFIX> does not get
>> highlighted, even though it is autoremovable.
>
> -R is supposed to be followed by the name of a function.  You gave it
> the empty string.  That should probably have been an error right off
> the bat, but it does mean the suffix can't possibly be autoremoved.
>
> However, the same highlight behavior occurs even if you do supply a
> working subroutine.  Does anyone remember why suffixfunclen needed to
> be stored separately?

I didn't make any attempt to understand the code, but can you usefully
specify both -r and -R? (it doesn't appear to be an error).

-- 
Mikael Magnusson


  reply	other threads:[~2021-09-08  2:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07 10:05 Marlon Richert
2021-09-07 22:19 ` Bart Schaefer
2021-09-08  2:13   ` Mikael Magnusson [this message]
2021-09-08  2:43     ` 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='CAHYJk3RJA+=owtdOkf85gO2nchgq2VkzXvHYAFJUU-QrkMQk+g@mail.gmail.com' \
    --to=mikachu@gmail.com \
    --cc=marlon.richert@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).