From: Eli Zaretskii <eliz@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 64733@debbugs.gnu.org
Subject: bug#64733: [PATCH] ; Handle string-at-point at end of buffer gracefully
Date: Thu, 20 Jul 2023 13:21:07 +0300 [thread overview]
Message-ID: <83sf9i3muk.fsf@gnu.org> (raw)
In-Reply-To: <87o7k7ynx4.fsf@posteo.net> (message from Philip Kaludercic on Thu, 20 Jul 2023 08:42:15 +0000)
> From: Philip Kaludercic <philipk@posteo.net>
> Cc: 64733@debbugs.gnu.org
> Date: Thu, 20 Jul 2023 08:42:15 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Philip Kaludercic <philipk@posteo.net>
> >> Cc: 64733@debbugs.gnu.org
> >> Date: Thu, 20 Jul 2023 06:57:17 +0000
> >>
> >> Eli Zaretskii <eliz@gnu.org> writes:
> >>
> >> > This is for master, right?
> >>
> >> I actually had indented for this and bug#64664 to be applied onto
> >> emacs-29.
> >
> > Why are these important enough to install on the release branch? Did
> > the behavior change in Emacs 29?
>
> I assumed so, but on checking both of these issues exist since Emacs 28.
> That being said, the fact that (thing-at-point 'string) raises an
> (avoidable) error seems to be something that shouldn't be the case, but
> I don't know if that warrants applying this patch at this late stage.
Let's install these on master, and maybe consider backporting then
after Emacs 29.1 is released.
Thanks.
next prev parent reply other threads:[~2023-07-20 10:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 18:51 bug#64733: [PATCH] ; Handle string-at-point at end of buffer gracefully Philip Kaludercic
2023-07-19 19:06 ` Eli Zaretskii
2023-07-19 19:17 ` Philip Kaludercic
2023-07-20 4:40 ` Eli Zaretskii
2023-07-20 6:57 ` Philip Kaludercic
2023-07-20 7:38 ` Eli Zaretskii
2023-07-20 8:42 ` Philip Kaludercic
2023-07-20 10:21 ` Eli Zaretskii [this message]
2023-07-21 14:53 ` Philip Kaludercic
2023-07-21 15:13 ` Eli Zaretskii
2023-07-22 7:21 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83sf9i3muk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64733@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 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.