unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Perry <amperry@provide.net>
Cc: 52384@debbugs.gnu.org
Subject: bug#52384: 26.3; dired buffer navigation tweak
Date: Fri, 10 Dec 2021 13:00:12 +0100	[thread overview]
Message-ID: <87ee6kzn3n.fsf@gnus.org> (raw)
In-Reply-To: <69e7c202-8ad6-46c7-800a-f54f0b314d61@provide.net> (Michael Perry's message of "Thu, 9 Dec 2021 00:39:39 +0000 (UTC)")

Michael Perry <amperry@provide.net> writes:

> When visiting a directory in dired-mode, you get not only a list of contents, 
> but also a two-line header ('/path/to/directory' and 'total used ...') 

(The second line has been removed in Emacs 29, and the first line has
been made useful in Emacs 28 (you can now click on the segments).)

> and a trailing blank line. Those are a nuisance when navigating using 
> `M-<` and `M->'. 
>
> Can I suggest the following become standard? 
>
> (with-eval-after-load "dired" 
>   (define-key dired-mode-map (kbd "M-<") 
>     (lambda () (interactive) (beginning-of-buffer) (next-line 2))) 
>   (define-key dired-mode-map (kbd "M->") 
>     (lambda () (interactive) (end-of-buffer) (previous-line 1)))) 
>
> It's truly a small issue, but it's an irritation that multiplies over time. 

I don't think we should do something like this in Dired buffers (or
anywhere else, for that matter).  I want commands like `M-<' to be
predictable across modes, and I certainly don't want `M->' to take me to
the start of the last line.  (What if I want to copy the region to the
clipboard, for instance?)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      parent reply	other threads:[~2021-12-10 12:00 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09  0:39 bug#52384: 26.3; dired buffer navigation tweak Michael Perry
2021-12-10  1:36 ` Stefan Kangas
2021-12-10  7:13   ` Arthur Miller
2021-12-10 17:11     ` bug#52384: [External] : " Drew Adams
2021-12-10 22:26       ` Arthur Miller
2021-12-10 22:52         ` Drew Adams
2021-12-11 14:08           ` Arthur Miller
2021-12-11 16:41             ` Drew Adams
2021-12-11 19:40       ` Juri Linkov
2021-12-11 22:06         ` Drew Adams
2021-12-12  8:41           ` Juri Linkov
2021-12-12 18:35             ` Drew Adams
2021-12-12 18:52               ` Juri Linkov
2021-12-12 19:15                 ` Arthur Miller
2021-12-12 19:28                   ` Juri Linkov
2021-12-12 19:37                   ` Eli Zaretskii
2021-12-13 10:14                     ` Arthur Miller
2021-12-13 12:24                       ` Stefan Kangas
2021-12-13 16:29                         ` Arthur Miller
2021-12-13 13:07                       ` Eli Zaretskii
2021-12-13 16:21                         ` Arthur Miller
2021-12-13 16:59                           ` Eli Zaretskii
2021-12-13 17:11                             ` Arthur Miller
2021-12-12 19:45                 ` Drew Adams
2021-12-12 20:10                   ` Juri Linkov
2021-12-10 12:00 ` Lars Ingebrigtsen [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=87ee6kzn3n.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=52384@debbugs.gnu.org \
    --cc=amperry@provide.net \
    /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).