nano-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 4/4] docs: remove all mentions of --markmatch and 'set markma


From: Benno Schulenberg
Subject: Re: [PATCH 4/4] docs: remove all mentions of --markmatch and 'set markmatch'
Date: Thu, 4 Feb 2021 16:36:42 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0

Op 03-02-2021 om 12:03 schreef pepa65:
> I would not have markmatch turned on all the time, just like I don't
> have search backwards or search regex always on, but I have a shortcut
> to toggle it on when useful. I was hoping markmatch could be the same
> way.

Now you're asking not only for an option but also for a toggle and a
bindable function.

> And perhaps some people (like Obel) would want to have it turned on
> all the time. It's not a costly feature in terms of code length, you've
> done all the work already, also documenting, it would not really be a
> win discarding it now I would think.

Discarding it is a win, because it gets rid of an option whose usefulness
is questionable and unobvious.  Case-sensitivity, clear.  Backward search,
clear.  Regex... one has to know what regexes are, but then: it allows
finding variations of things.  Mark-the-match... hmmm... how is that
useful?  I can't think anything I would want to use it for.

The purpose of --markmatch was to highlight the match.  That the match was
selected too was an implementation thing -- it sounded like a good idea,
but in practice it is a nuisance.  And just like --nonewlines by default
for version 4.0 looked like a good idea, but wasn't, and was quickly undone,
so I will undo this mark-the-match mistake.

Benno

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]