From: tpeplt <tpeplt@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: [External] : Undefined behavior for the function ‘last’ or an error?
Date: Tue, 02 Apr 2024 21:05:31 -0400 [thread overview]
Message-ID: <87plv78dd0.fsf@gmail.com> (raw)
In-Reply-To: <8734s4alnv.fsf@gmail.com> (tpeplt@gmail.com's message of "Mon, 01 Apr 2024 16:11:00 -0400")
Drew Adams <drew.adams@oracle.com> writes:
>
>>
>> I suggest you do: `M-x report-emacs-bug'.
>> Thanks for uncovering this.
>
> Thanks for the response. I will wait a day to see if anyone can point
> to something I have missed. If no one does, then I will report the
> problem.
>
> --
There have been no additional responses to this. This issue has been
now been reported. It has been assigned bug #70155
(70155@debbugs.gnu.org).
--
prev parent reply other threads:[~2024-04-03 1:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 16:53 Undefined behavior for the function ‘last’ or an error? tpeplt
2024-04-01 17:12 ` tpeplt
2024-04-01 17:28 ` [External] : " Drew Adams
2024-04-01 18:35 ` tpeplt
2024-04-01 19:25 ` Drew Adams
2024-04-01 20:11 ` tpeplt
2024-04-03 1:05 ` tpeplt [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=87plv78dd0.fsf@gmail.com \
--to=tpeplt@gmail.com \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.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.
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).