unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Kangas <stefankangas@gmail.com>, 59280@debbugs.gnu.org
Subject: bug#59280: 29.0.50; Buffer-menu-view-other-window lack of keybinding makes help look off
Date: Tue, 15 Nov 2022 15:18:24 +0100	[thread overview]
Message-ID: <87sfikcndb.fsf@gmail.com> (raw)
In-Reply-To: <83edu4iatp.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 15 Nov 2022 15:52:50 +0200")

>>>>> On Tue, 15 Nov 2022 15:52:50 +0200, Eli Zaretskii <eliz@gnu.org> said:

    >> From: Stefan Kangas <stefankangas@gmail.com>
    >> Date: Mon, 14 Nov 2022 23:47:14 -0800
    >> 
    >> q    Remove the Buffer Menu from the display.
    >> RET  Select current line’s buffer in place of the buffer menu.
    >> o    Select that buffer in another window,
    >> so the Buffer Menu remains visible in its window.
    >> V    Select current line’s buffer, in View mode.
    >> M-x Buffer-menu-view-other-window  Select that buffer in
    >> another window, in ‘view-mode’.
    >> 
    >> The last entry there looks a bit off (see it in context).  I see two
    >> solutions:
    >> 
    >> 1. Add some keybinding for `Buffer-menu-view-other-window'.
    >> 2. Move `Buffer-menu-view-other-window' last.
    >> 
    >> I have no preferences here, but it would be good to do one of them.

    Eli> How about removing it from the list?  Isn't 'o' enough?

'o' doesnʼt put the buffer in `view-mode'. We could bind it to 'O'

(and while weʼre at it we should reorder things so that eg 'v' and 'V'
are next to each other. And use either "View mode" or `view-mode'
consistently)

Robert
-- 





  reply	other threads:[~2022-11-15 14:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15  7:47 bug#59280: 29.0.50; Buffer-menu-view-other-window lack of keybinding makes help look off Stefan Kangas
2022-11-15 13:52 ` Eli Zaretskii
2022-11-15 14:18   ` Robert Pluim [this message]
2022-11-25  0:44     ` Stefan Kangas

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=87sfikcndb.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=59280@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=stefankangas@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).