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: Sat, 11 Dec 2021 16:41:22 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488D5A3F35A935BA9E478E6F3729@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <AM9PR09MB4977D5E1C3574EF4217DC36696729@AM9PR09MB4977.eurprd09.prod.outlook.com>
> > 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.
>
> I don't think it is hard to code; it was just you already made it in
> dired+, so it's your code, your thing, your patch :).
As I said, I likely already did that, long ago.
Patches I submit are generally ignored.
If you think that the slight changes I made in
Dired+ for this are worth proposing in a patch,
feel free to do so. But there's nothing special
about that particular coding.
> >> 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.
>
> Yes, It would be nice if Emacs had consistent "wrap around" for more
> things, as an option of course; like in windmove.el.
Yes, optionally. Sometimes, as in Dired for
different kinds of navigation, a single option
could reasonably control wraparound for different
commands. Other times, it's more appropriate to
have separate options.
next prev parent reply other threads:[~2021-12-11 16: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 [this message]
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=SJ0PR10MB5488D5A3F35A935BA9E478E6F3729@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).