From: Mikael Magnusson <mikachu@gmail.com>
To: zsh workers <zsh-workers@zsh.org>
Subject: Re: zsh 4.3.10-test-3
Date: Fri, 17 Dec 2010 18:50:40 +0100 [thread overview]
Message-ID: <AANLkTikmwiUgOd12Wytk6x3fD0puy9i7asLmKZjSj9AR@mail.gmail.com> (raw)
In-Reply-To: <20101217171253.443dc65c@pwslap01u.europe.root.pri>
On 17 December 2010 18:12, Peter Stephenson <Peter.Stephenson@csr.com> wrote:
> On Fri, 17 Dec 2010 08:35:24 -0800
> Wayne Davison <wayned@users.sourceforge.net> wrote:
>> On Fri, Dec 17, 2010 at 5:03 AM, Simon Ruderich <simon@ruderich.org>
>> wrote:
>>
>> > Could the default get changed back to the old behaviour with causes
>> > no highlight (in bold)?
>> >
>>
>> I think the suffix highlighting makes a nice default, since it helps
>> to show people that the character is nebulous, and may disappear.
>> Many people who are new to zsh get surprised by the automatic
>> trimming of a visible slash, and having an easy way for someone to
>> see that that slash is going to disappear (or not disappear) when
>> return is pressed is a good thing, in my opinion.
>
> Yes, the intention that anyone worried by that sort of thing is likely
> to be able to do what Mikael suggested to turn off everything, so the
> fix should be good enough.
+zle_highlight also control highlighting of a removable completion
+suffix, e.g. the "/" automatically appended to directories. This uses
+the keyword "suffix".
"also controls"
- isearch_atr_on_set = 1;
+ isearch_atr_on_set = suffix_atr_on-set = 1;
_set, not -set
--
Mikael Magnusson
prev parent reply other threads:[~2010-12-17 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <27627.1292500716@csr.com>
2010-12-17 16:43 ` Bart Schaefer
[not found] ` <20101217130335.GA12154@ruderich.org>
[not found] ` <AANLkTimBSM77GUg7vJm4Oed1iGSZOKgW5YN3qAcTju9V@mail.gmail.com>
[not found] ` <20101217171253.443dc65c@pwslap01u.europe.root.pri>
2010-12-17 17:50 ` Mikael Magnusson [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=AANLkTikmwiUgOd12Wytk6x3fD0puy9i7asLmKZjSj9AR@mail.gmail.com \
--to=mikachu@gmail.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).