|
From: | martin rudalics |
Subject: | bug#53910: [External] : bug#53910: 29.0.50; context-menu-mode breaks help in read-only buffers |
Date: | Mon, 21 Feb 2022 10:07:39 +0100 |
> Then 'bury-buffer' could have a new optional argument WINDOW, > thus changing this line: > > (not (eq buffer (window-buffer))) > > to: > > (not (eq buffer (window-buffer window))) > > and using WINDOW in other places in 'bury-buffer' too. Even without such an argument 'bury-buffer' is complex enough so I doubt that many people will understand what it does in all its consequences. Can you tell how burying a buffer affects the next C-x <left> sequence you type? martin
[Prev in Thread] | Current Thread | [Next in Thread] |