unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: David Masterson <dsmasterson92630@outlook.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Patch request - menu modifications
Date: Tue, 02 Feb 2021 15:52:54 -0800	[thread overview]
Message-ID: <SJ0PR03MB5455E19EE67E5F3CB85E85B49BB59@SJ0PR03MB5455.namprd03.prod.outlook.com> (raw)
In-Reply-To: <874kixlfmp.fsf@zoho.eu> (moasenwood's message of "Sun, 31 Jan 2021 08:39:10 +0100")

moasenwood--- via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org> writes:

> David Masterson wrote:
>
>> I'd like to request two simple changes to the basic Emacs
>> menus:
>>
>> 1. Add dired-quit ('q') to the dired menus. It would make it
>> easier to traverse a directory tree using just the mouse
>> (click directory to descend and click dired-quit to return
>> up). To me, it is not obvious which menu to put it in.
>
> Interesting ... I don't even have "dired-quit", q meanwhile is
> `quit-window', which isn't dired specific ... certainly it
> doesn't help you "descend", it buries the buffer!

You're right -- I got it wrong!  (Could've swore it was dired-quit...)

> Maybe you look for `dired-up-directory'?

Didn't know that one, but that might work.

> (Here, it depends how you visualize the file system hierarchy,
> I think ./ is _downmost_, like the basic element [1], but some
> people think it it is the top node in a tree-like
> data structure.)

My goal is to 'f' into a directory and 'q' to exit a directory using
only the menu.  That would make the menu complete for walking the
directory tree. (I'm considering changing <mouse-1> to dired-find-file)

>> 2. Add kill-this-buffer to the "Buffers" menu. The funny
>> thing is that where-is reports it as "<menu-bar> <file>
>> <kill-buffer>", but I don't see it there.
>
> `C-x k' `kill-buffer' ... so the menu has its own functions, now?
>
> kill-this-buffer:
>
>   This command can be reliably invoked only from the menu bar,
>   otherwise it could decide to silently do nothing.
>
> "it could decide"? ??? Okay?

kill-this-buffer seems better so it doesn't take input. This could be
used to clean up buffers from walking the dir tree.

-- 
David Masterson



  reply	other threads:[~2021-02-02 23:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-31  6:34 Patch request - menu modifications David Masterson
2021-01-31  7:39 ` moasenwood--- via Users list for the GNU Emacs text editor
2021-02-02 23:52   ` David Masterson [this message]
2021-01-31 15:09 ` Stefan Monnier
2021-01-31 16:44   ` moasenwood--- via Users list for the GNU Emacs text editor
2021-02-02 23:55   ` David Masterson
2021-02-03  0:28     ` Michael Heerdegen
2021-02-05  5:50       ` David Masterson
2021-02-05  7:54         ` Thibaut Verron
2021-02-07  5:57           ` David Masterson

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=SJ0PR03MB5455E19EE67E5F3CB85E85B49BB59@SJ0PR03MB5455.namprd03.prod.outlook.com \
    --to=dsmasterson92630@outlook.com \
    --cc=help-gnu-emacs@gnu.org \
    /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.
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).