From: Lars Ingebrigtsen <larsi@gnus.org>
To: dick.r.chiang@gmail.com
Cc: 57081@debbugs.gnu.org
Subject: bug#57081: 29.0.50; [PATCH] Point associated with Window for good reasons
Date: Tue, 09 Aug 2022 19:55:54 +0200 [thread overview]
Message-ID: <87czd9wbbp.fsf@gnus.org> (raw)
In-Reply-To: <87zggdbp6y.fsf@dick> (dick r. chiang's message of "Tue, 09 Aug 2022 08:01:57 -0400")
dick.r.chiang@gmail.com writes:
> When temporarily switching out one window, say to check a definition,
> our flow gets wrecked by C-x b's refusal to flip back to the original
> buffer since it's already displayed in another window, albeit, and
> very importantly, at a different point (which to belabor things, is
> the whole reason we want the same buffer in two windows).
I think adding this might make sense, but with a user option to control
the action.
> * lisp/ido.el (ido-make-buffer-list-1): De-obfuscate.
> (ido-make-buffer-list): Include visible buffer when switching.
> (ido-get-buffers-in-frames): De-obfuscate.
> * lisp/window.el (read-buffer-to-switch): Include visible buffer.
> * test/lisp/ido-tests.el (ert-deftest): Test it.
And as usual, your patch includes a whole bunch of apparently irrelevant
stuff.
next prev parent reply other threads:[~2022-08-09 17:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 12:01 bug#57081: 29.0.50; [PATCH] Point associated with Window for good reasons dick.r.chiang
2022-08-09 16:53 ` Eli Zaretskii
2022-08-09 17:35 ` dick
2022-08-09 17:41 ` Eli Zaretskii
2022-08-09 17:55 ` Lars Ingebrigtsen [this message]
2022-08-09 18:18 ` Eli Zaretskii
2022-08-09 18:25 ` Lars Ingebrigtsen
2022-08-09 18:35 ` Eli Zaretskii
2022-08-09 18:39 ` Eli Zaretskii
2022-08-09 19:10 ` dick
2022-08-09 19:08 ` Lars Ingebrigtsen
2022-08-09 19:22 ` Eli Zaretskii
2022-08-09 19:29 ` Lars Ingebrigtsen
2022-08-09 19:35 ` Eli Zaretskii
2022-08-12 13:06 ` Lars Ingebrigtsen
2022-08-12 13:19 ` Eli Zaretskii
2022-08-12 13:41 ` dick
2022-08-12 13:57 ` Lars Ingebrigtsen
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=87czd9wbbp.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=57081@debbugs.gnu.org \
--cc=dick.r.chiang@gmail.com \
/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).