unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Phil Sainty <psainty@orcon.net.nz>
To: ndame <laszlomail@protonmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 52558@debbugs.gnu.org
Subject: bug#52558: Option for easier typing of regexps
Date: Mon, 20 Dec 2021 05:11:32 +1300	[thread overview]
Message-ID: <0857117dcca6f1d8a617ad1fa34a3450@webmail.orcon.net.nz> (raw)
In-Reply-To: <IYJ7YagIfVsTeDCozhGrysAaRXCwZuX8xmHwXAntLmxLD12euxGmJvPmPqge9YQba18sMRpvxGB0eyrWhRoCa29FNrrBA3PaY88jgEWEwKU=@protonmail.com>

On 2021-12-20 03:08, ndame wrote:
> Why would it create confusion if it's an option which the
> user has to enable explicitly?

If the user is (a) well aware of the change they've made (not
blindly copying it from somewhere else), and (b) have a good
understanding of regexp syntax and/or the documentation such
that they won't be asking anyone questions about regexps, then
it shouldn't cause them any confusion.

OTOH for someone who (a) doesn't have a strong understanding of
Emacs regexp syntax; (b) is more familiar with other dialects
with fewer backslashes; (c) enables the hypothetical option to
make things seem more familiar but still doesn't entirely know
what they're doing; and (d) asks questions or searches for pre-
existing Q&As to figure out how to construct their regexp...
I think there's ample opportunity for crossed wires on both
sides of any ensuing interactions, and pre-existing information
will likely not match the syntax that they have chosen.

To me it feels like the kind of option which would be more
likely to be preferred by people who are less familiar with
Emacs regexp syntax, in which case the likelihood of confusion
probably increases.

I'm just speculating, though.


-Phil






  reply	other threads:[~2021-12-19 16:11 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16 17:41 bug#52558: Option for easier typing of regexps ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-17 10:07 ` Phil Sainty
2021-12-18 16:47   ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-18  4:41 ` Richard Stallman
2021-12-19 11:56 ` Lars Ingebrigtsen
2021-12-19 13:03   ` Phil Sainty
2021-12-19 14:08     ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-19 16:11       ` Phil Sainty [this message]
2021-12-19 15:10   ` Michael Heerdegen
2021-12-20  4:43   ` Richard Stallman
2021-12-20 19:46   ` Jim Porter
2021-12-22  4:16     ` Richard Stallman
2021-12-19 17:01 ` Juri Linkov
2021-12-19 17:39   ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-19 17:52     ` Juri Linkov
2021-12-19 17:57       ` Juri Linkov
2021-12-19 18:38     ` Juri Linkov
2021-12-19 18:48       ` Juri Linkov
2021-12-28 19:15         ` Juri Linkov
2021-12-28 20:21           ` Eli Zaretskii
2021-12-28 20:25             ` Juri Linkov
2021-12-28 20:35               ` Eli Zaretskii
2021-12-28 20:51                 ` Juri Linkov
2021-12-29 12:32                   ` Eli Zaretskii
2021-12-29 17:17                     ` Juri Linkov
2021-12-29 18:25                       ` Eli Zaretskii
2022-01-22 14:23         ` Lars Ingebrigtsen
2022-01-22 19:01           ` Juri Linkov
2022-01-23 12:36             ` Lars Ingebrigtsen
2022-01-23 18:09               ` Juri Linkov
2022-01-23 18:29                 ` Lars Ingebrigtsen
2022-01-24 18:46                   ` Juri Linkov

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=0857117dcca6f1d8a617ad1fa34a3450@webmail.orcon.net.nz \
    --to=psainty@orcon.net.nz \
    --cc=52558@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=laszlomail@protonmail.com \
    /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).