From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 22147@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#22147: Obsolete search-forward-lax-whitespace
Date: Fri, 18 Dec 2015 00:55:06 +0000 [thread overview]
Message-ID: <CAAdUY-+RnEfyDQftR-FQKS5PC7_1aPJO7GR8pDDRaUa=b2KCGQ@mail.gmail.com> (raw)
In-Reply-To: <9ec649c4-5d95-4192-8a73-cc438ad0e4aa@default>
[out of order quotes below]
2015-12-17 22:16 GMT+00:00 Drew Adams <drew.adams@oracle.com>:
>> This would offer a dead-simple defcustom that covers most cases, while
>> still allowing the versatility of having multiple options for those
>> who need it.
>
> What I proposed is just as "dead-simple", but cleaner (IMO) and open
> to all users. Just as importantly, it lets users (easily) define
> multiple classes that they can (easily) use in different contexts.
And this is the source of our impasse. IMO (and I say this will all
due respect) your proposal is not as simple as the two defcustoms I
suggested, and it is not cleaner than just using hooks/local-vars to
set the value of character-fold-table to whatever is relevant for the
current situation.
Since we're both just stating opinions, it's unlikely this discussion
will go anywhere.
> My point, as I said, is only this:
>
> Users should be able to define their own equivalence classes (groups),
> not just one class. Each class should be the value of a user option.
>
> Anything less than that is not serving users as well as they deserve, IMO.
And my point is that this is too complex for user options.
Most people won't need this much generality, and the amount of time
these people will waste trying to understand this multi-option
configuration will be significant. The few who want this behavior will
be glad that we offered it, but the time it will save them (compared
to if they wrote something in elisp) will be (IMO) small compared to
the total accumulated wasted time for everyone else.
prev parent reply other threads:[~2015-12-18 0:55 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 23:52 bug#22147: Obsolete search-forward-lax-whitespace Juri Linkov
2015-12-12 0:44 ` Artur Malabarba
2015-12-12 23:31 ` Juri Linkov
2015-12-13 0:29 ` Artur Malabarba
2015-12-14 0:23 ` Juri Linkov
2015-12-14 1:11 ` Artur Malabarba
2015-12-14 23:58 ` Juri Linkov
2015-12-15 10:15 ` Artur Malabarba
2015-12-16 0:57 ` Juri Linkov
2015-12-16 1:47 ` Drew Adams
2016-05-14 20:45 ` Juri Linkov
2016-05-14 22:20 ` Artur Malabarba
2016-05-14 22:27 ` Drew Adams
2016-05-15 20:45 ` Juri Linkov
2016-05-14 22:22 ` Drew Adams
2016-05-15 20:56 ` Juri Linkov
2016-05-15 21:51 ` Drew Adams
2016-05-17 20:55 ` Juri Linkov
2016-05-17 21:55 ` Drew Adams
2016-05-18 3:00 ` Artur Malabarba
2016-05-18 19:34 ` Juri Linkov
2016-05-18 20:40 ` Artur Malabarba
2016-05-30 20:57 ` Juri Linkov
2016-06-01 15:03 ` Artur Malabarba
2020-09-05 14:54 ` Lars Ingebrigtsen
2020-09-07 18:34 ` Juri Linkov
2015-12-16 10:59 ` Artur Malabarba
2015-12-17 0:57 ` Juri Linkov
2015-12-17 16:33 ` Artur Malabarba
2015-12-17 17:21 ` Drew Adams
2015-12-17 18:47 ` Artur Malabarba
2015-12-17 22:16 ` Drew Adams
2015-12-18 0:55 ` Artur Malabarba [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAdUY-+RnEfyDQftR-FQKS5PC7_1aPJO7GR8pDDRaUa=b2KCGQ@mail.gmail.com' \
--to=bruce.connor.am@gmail.com \
--cc=22147@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=juri@linkov.net \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).