From: Juri Linkov <juri@linkov.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: Michael Perry <amperry@provide.net>,
Stefan Kangas <stefan@marxist.se>,
Arthur Miller <arthur.miller@live.com>,
"52384@debbugs.gnu.org" <52384@debbugs.gnu.org>
Subject: bug#52384: [External] : bug#52384: 26.3; dired buffer navigation tweak
Date: Sun, 12 Dec 2021 10:41:32 +0200 [thread overview]
Message-ID: <86zgp68c8j.fsf@mail.linkov.net> (raw)
In-Reply-To: <SJ0PR10MB54882817D69D580141F63D3DF3729@SJ0PR10MB5488.namprd10.prod.outlook.com> (Drew Adams's message of "Sat, 11 Dec 2021 22:06:31 +0000")
>> > (The Dired+ versions of these commands wrap
>> > around, if option `diredp-wrap-around-flag'
>> > has its default value of `t'.)
>>
>> Yet another feature I had already implemented
>> since Emacs 21.1 and sent to you for review in 2007.
>
> Interesting. Or is that tongue in cheek?
>
> I just searched all messages I've received from
> you, including those in 2007, from mailing lists
> and direct mails, and I don't find any such
> suggestion or review request. Could you point
> to it - I'm curious. I expect that if that were
> the case I would most likely have added it to
> Dired+ long before I did (which was not until
> July 12, 2013).
I don't remember exactly, but the closest is in the
thread "TAB for non-editing modes" on emacs-devel
with the discussion about using TAB in dired
to move between directories. When TAB/S-TAB will go
to the next/previous directory, then `<' and `>'
will be free to use for going to the first/last file.
>> But I don't use it too much because it's not
>> so useful with --group-directories-first
>> that really should be the default.
>
> I have that as default for my own use. But I
> often change sort orders, especially for date.
When you change sort orders, directories still
remain at the top? So first are directories
sorted by date, then below files sorted by date?
next prev parent reply other threads:[~2021-12-12 8:41 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 [this message]
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=86zgp68c8j.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=52384@debbugs.gnu.org \
--cc=amperry@provide.net \
--cc=arthur.miller@live.com \
--cc=drew.adams@oracle.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).