From: Amin Bandali <bandali@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 38257@debbugs.gnu.org
Subject: bug#38257: Acknowledgement (27.0.50; ERC does not match or highlight nick surrounded by parens)
Date: Thu, 21 Nov 2019 20:06:28 -0500 [thread overview]
Message-ID: <87pnhk90tn.fsf@gnu.org> (raw)
In-Reply-To: <87imndxr6i.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
[...]
>
> I haven't tried this patch, but doesn't this syntax table apply to all
> buttons in erc, including URLs? So an URL like
> http://foo.bar/zot'foo would no longer be recognised properly? (I'm not
> sure that it should, to be honest...)
It does indeed, and it didn't quite occur to me
when writing the patch; whoops.
But like Corwin, I too personally much rather
be notified of my nick getting highlighted in
exchange for losing some convenience with
respect to clickable links.
That said, from a brief chat with Tom Tromey in
#erc on freenode today, I agree with him that
one probably shouldn't make changes to syntax
tables lightly, without first considering all
possible cases. I wonder if you or Tom would
be so kind to do such an audit for this change.
I'd also be open to other ways of doing this if
there's a better way. I guess in general it is
kind of tricky to deal with these characters in
URLs. At least one person I talked to earlier
today said they would expect the apostrophe to
be part of the URL (i.e. not a word boundary).
It may be even more tricky or more subjective
for parens.
Thoughts?
next prev parent reply other threads:[~2019-11-22 1:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 15:40 bug#38257: 27.0.50; ERC does not match or highlight nick surrounded by parens Amin Bandali
[not found] ` <handler.38257.B.15740916515869.ack@debbugs.gnu.org>
2019-11-18 15:49 ` bug#38257: Acknowledgement (27.0.50; ERC does not match or highlight nick surrounded by parens) Amin Bandali
2019-11-20 6:04 ` Amin Bandali
2019-11-21 14:03 ` Lars Ingebrigtsen
2019-11-22 1:06 ` Amin Bandali [this message]
2019-11-22 12:25 ` Lars Ingebrigtsen
2019-11-22 12:31 ` Lars Ingebrigtsen
2019-11-22 13:42 ` Amin Bandali
2019-12-29 4:30 ` Amin Bandali
2019-12-29 17:30 ` Emanuel Berg via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-01-04 9:22 ` Eli Zaretskii
2020-01-09 7:14 ` Amin Bandali
2020-01-09 7:42 ` Emanuel Berg via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-01-09 18:41 ` Amin Bandali
2020-01-11 8:41 ` Eli Zaretskii
2020-01-13 7:19 ` Amin Bandali
2020-01-20 18:55 ` Stefan Kangas
2020-01-21 13:35 ` Amin Bandali
2019-11-21 20:17 ` bug#38257: Missed notif > broken buttons Corwin Brust
2020-01-03 23:39 ` bug#38257: Still working well for me (GNU 26.3 Windows 10) Corwin Brust
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=87pnhk90tn.fsf@gnu.org \
--to=bandali@gnu.org \
--cc=38257@debbugs.gnu.org \
--cc=larsi@gnus.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.