GNU bug report logs -
#64022
Subject: 28.2; minibuffer-beginning-of-buffer fails to set mark
Previous Next
Reported by: Al Petrofsky <al <at> petrofsky.org>
Date: Mon, 12 Jun 2023 15:17:02 UTC
Severity: normal
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 64022 in the body.
You can then email your comments to 64022 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#64022
; Package
emacs
.
(Mon, 12 Jun 2023 15:17:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Al Petrofsky <al <at> petrofsky.org>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Mon, 12 Jun 2023 15:17:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
emacs -Q
M-: foo M-< C-x C-x
In emacs 26, point returns to the end of the minibuffer, but in 27 and
28.2 a bogus "No mark set in this buffer" error is reported.
I think the first 'when' in minibuffer-beginning-of-buffer is supposed
to be 'unless'.
Another issue is that this:
emacs -Q
M-: C-x C-x
correctly reports "No mark set in this buffer", but this:
emacs -Q
M-: t C-@ RET
M-: C-x C-x
does not. This does no harm, but logically the mark should probably
be unset when a new minibuffer is created.
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#64022
; Package
emacs
.
(Mon, 12 Jun 2023 15:50:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 64022 <at> debbugs.gnu.org (full text, mbox):
> From: Al Petrofsky <al <at> petrofsky.org>
> Date: Mon, 12 Jun 2023 11:15:43 -0400
>
> emacs -Q
> M-: foo M-< C-x C-x
>
> In emacs 26, point returns to the end of the minibuffer, but in 27 and
> 28.2 a bogus "No mark set in this buffer" error is reported.
>
> I think the first 'when' in minibuffer-beginning-of-buffer is supposed
> to be 'unless'.
You are right. I've now fixed this on the emacs-29 branch.
> Another issue is that this:
>
> emacs -Q
> M-: C-x C-x
>
> correctly reports "No mark set in this buffer", but this:
>
> emacs -Q
> M-: t C-@ RET
> M-: C-x C-x
>
> does not. This does no harm, but logically the mark should probably
> be unset when a new minibuffer is created.
It's not a new minibuffer, it's the same "*Minibuf-1*" minibuffer used
the first time. So I think Emacs behaves correctly here.
Reply sent
to
Eli Zaretskii <eliz <at> gnu.org>
:
You have taken responsibility.
(Sat, 17 Jun 2023 07:46:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Al Petrofsky <al <at> petrofsky.org>
:
bug acknowledged by developer.
(Sat, 17 Jun 2023 07:46:02 GMT)
Full text and
rfc822 format available.
Message #13 received at 64022-done <at> debbugs.gnu.org (full text, mbox):
> Cc: 64022 <at> debbugs.gnu.org
> Date: Mon, 12 Jun 2023 18:49:30 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
>
> > From: Al Petrofsky <al <at> petrofsky.org>
> > Date: Mon, 12 Jun 2023 11:15:43 -0400
> >
> > emacs -Q
> > M-: foo M-< C-x C-x
> >
> > In emacs 26, point returns to the end of the minibuffer, but in 27 and
> > 28.2 a bogus "No mark set in this buffer" error is reported.
> >
> > I think the first 'when' in minibuffer-beginning-of-buffer is supposed
> > to be 'unless'.
>
> You are right. I've now fixed this on the emacs-29 branch.
No further comments, so I'm now closing this bug.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sat, 15 Jul 2023 11:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 2 years and 26 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.