unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Jakub Ječmínek" <kuba@kubajecminek.cz>
Cc: 64497@debbugs.gnu.org, hugo@heagren.com
Subject: bug#64497: 30.0.50; `other-buffer' returns current buffer
Date: Mon, 03 Jun 2024 14:27:40 +0300	[thread overview]
Message-ID: <865xuqmfkj.fsf@gnu.org> (raw)
In-Reply-To: <87frtvxd7a.fsf@kubajecminek.cz> (message from Jakub Ječmínek on Sun, 02 Jun 2024 21:11:08 +0000)

tags 64497 moreinfo unreproducible
close 64497
thanks

> Date: Sun, 02 Jun 2024 21:11:08 +0000
> From: Jakub Ječmínek <kuba@kubajecminek.cz>
> Cc: hugo@heagren.com, 64497@debbugs.gnu.org
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> Date: Thu, 06 Jul 2023 17:16:21 +0100
> >> From: hugo@heagren.com
> >> 
> >> I've just built Emacs from master. My binding to
> >> `mode-line-other-buffer' wasn't doing what it should, so I investigated.
> >> On my machine, the form `(other-buffer)' returns the current buffer.
> >> 
> >> I notice that a recent change to `other-buffer' relates to scratch
> >> buffers (though my C isn't good enough to know what it really does). I
> >> have tested this in a scratch buffer, and there too `(other-buffer)'
> >> returns the current buffer (i.e. *scratch*).
> >> 
> >> `(other-buffer (current-buffer))' behaves as it -- i.e. returns a buffer
> >> other than the current buffer.
> >
> > I cannot reproduce this with the current master branch, FWIW.
> 
> Should we close this?  No response in almost a year.

Closing.





      reply	other threads:[~2024-06-03 11:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06 16:16 bug#64497: 30.0.50; `other-buffer' returns current buffer hugo
2023-07-06 17:40 ` Eli Zaretskii
2024-06-02 21:11 ` Jakub Ječmínek via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-03 11:27   ` Eli Zaretskii [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=865xuqmfkj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=64497@debbugs.gnu.org \
    --cc=hugo@heagren.com \
    --cc=kuba@kubajecminek.cz \
    /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).