From: Eli Zaretskii <eliz@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 67600@debbugs.gnu.org
Subject: bug#67600: [PATCH] Add dashes to 'thing-at-point-email-regexp'
Date: Sat, 16 Dec 2023 15:38:31 +0200 [thread overview]
Message-ID: <838r5umfmw.fsf@gnu.org> (raw)
In-Reply-To: <87jzpetoo3.fsf@posteo.net> (message from Philip Kaludercic on Sat, 16 Dec 2023 10:41:32 +0000)
> From: Philip Kaludercic <philipk@posteo.net>
> Cc: 67600@debbugs.gnu.org
> Date: Sat, 16 Dec 2023 10:41:32 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Philip Kaludercic <philipk@posteo.net>
> >> Cc: 67600@debbugs.gnu.org
> >> Date: Tue, 12 Dec 2023 07:21:18 +0000
> >>
> >> Eli Zaretskii <eliz@gnu.org> writes:
> >>
> >> >> From: Philip Kaludercic <philipk@posteo.net>
> >> >> Date: Sun, 03 Dec 2023 12:52:04 +0000
> >> >>
> >> >> I noticed this recently when trying to extract a link to an mailing list
> >> >> of mine hosted on SourceHut.
> >> >
> >> > Looks like you are adding slashes, not dashes?
> >>
> >> Of course, my bad:
> >
> > Thanks.
> >
> > My bother here is that this could cause false positives whereby
> > thing-at-point would recognize file names with slashes as email
> > addresses. Because otherwise I don't understand why the slash was
> > omitted in the first place. Can we somehow make sure this won't
> > happen?
>
> One idea might be to just add slashes to the user name part of the
> address, which would suffice to solve the issue I was having.
Can you show a patch, so we could make sure we are on the same page?
Thanks.
next prev parent reply other threads:[~2023-12-16 13:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 12:52 bug#67600: [PATCH] Add dashes to 'thing-at-point-email-regexp' Philip Kaludercic
2023-12-03 13:14 ` Eli Zaretskii
2023-12-12 7:21 ` Philip Kaludercic
2023-12-12 12:06 ` Eli Zaretskii
2023-12-12 12:21 ` Visuwesh
2023-12-12 12:27 ` Eli Zaretskii
2023-12-12 12:41 ` Visuwesh
2023-12-12 13:08 ` Eli Zaretskii
2023-12-12 13:23 ` Visuwesh
2023-12-12 13:35 ` Eli Zaretskii
2023-12-12 14:25 ` Visuwesh
2023-12-16 10:41 ` Philip Kaludercic
2023-12-16 13:38 ` Eli Zaretskii [this message]
2023-12-16 14:50 ` Philip Kaludercic
2023-12-16 14:59 ` Eli Zaretskii
2023-12-17 12:11 ` Philip Kaludercic
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=838r5umfmw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=67600@debbugs.gnu.org \
--cc=philipk@posteo.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).