unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Arthur Miller <arthur.miller@live.com>
Cc: Michael Perry <amperry@provide.net>,
	Stefan Kangas <stefan@marxist.se>,
	"52384@debbugs.gnu.org" <52384@debbugs.gnu.org>
Subject: bug#52384: [External] : bug#52384: 26.3; dired buffer navigation tweak
Date: Fri, 10 Dec 2021 22:52:03 +0000	[thread overview]
Message-ID: <SJ0PR10MB548840C9DC82FBD33D04B7B5F3719@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <AM9PR09MB49774A143751E3DB7590564F96719@AM9PR09MB4977.eurprd09.prod.outlook.com>

> > My 2c:
> > Leave `<' and `>' alone, letting them move to
> > the previous/next directory file line.
> 
> If you keep directories sorted before or after files then < and > become
> almost redundant, since 'p' and 'n' will have same effect in practice.

For some meaning of "almost".

> I say almost, because there is instance when one is deep below in files
> and would like to jump do directories (when sorted before). So pressing
> '<' would take you to the last directory before files listing begin, and
> than one can use either p/n or </> to move cursor.

That's far from the only case/difference.

`<' and `>' move only among dir-header lines.

They do that wherever those lines might be.
Including for inserted subdirs.

If you never insert subdir listings, and you
always list dir lines first, then, within that
block of dir headers (only), yes, `<' and `>' act
like `p' and `n'.  That's one case out of many.

> I also think dired should use by default
> --group-directories-first/ls-lisp-dirs-first...

Please file a separate enhancement request for
that, if you like.

> > (The Dired+ versions of these commands wrap
> > around, if option `diredp-wrap-around-flag'
> > has its default value of `t'.)
> 
> I would suggest this option to make it's way into Emacs. Can't you suggest a
> patch? Windmove has similar option for moving left-right windows to wrap
> around.

Giving such behavior to vanilla Emacs is trivial.
And I likely did propose it long ago, and there's
a chance I even provided code for it.  In any case,
the code isn't hard.

> It would be handy if 'p' and 'n' and '<' and '>' would behave
> similarly.

`p' and `n' do behave similarly, based on the same
user option.  And yes, I generally do provide
wraparound navigation etc. in my code.  It usually
makes sense to do so.





  reply	other threads:[~2021-12-10 22:52 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 [this message]
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

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=SJ0PR10MB548840C9DC82FBD33D04B7B5F3719@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=52384@debbugs.gnu.org \
    --cc=amperry@provide.net \
    --cc=arthur.miller@live.com \
    --cc=stefan@marxist.se \
    /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).