all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Shynur Xie <one.last.kiss@outlook.com>
To: Stefan Kangas <stefankangas@gmail.com>,
	Drew Adams <drew.adams@oracle.com>
Cc: "65621@debbugs.gnu.org" <65621@debbugs.gnu.org>
Subject: bug#65621: [PATCH] `dired-next-line' go to meaningful line
Date: Fri, 1 Sep 2023 17:29:11 +0000	[thread overview]
Message-ID: <PH0PR11MB7470E78B7F2F0950B81D3C43D7E4A@PH0PR11MB7470.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CADwFkmkiOsMnE1M0h8qT37=7V9BnWUmfQttY_bkFFDo=DXuAKg@mail.gmail.com>

> Stefan:
> I like the option `dired-cursor-goto-meaningful-line', which seems
> to both add wrap-around and make the feature as a whole optional.

Thx!  Yes, to use the `wrap-around' you mentioned, just set the option
to `cycle'.

> Stefan:
> But in Emacs, we say "point" rather than "cursor", so we'd have to
> change that.  I suggest naming it `dired-movement-style'.

OK.

> Drew:
> there's no need for "cursor" in the option name.

I'll try not to mention cursor/point in docstring when possible.

> Drew:
> The doc should say that it affects only commands
> `dired-(next|previous)-line'.

Yeah, docstring should state it.

> Drew:
> FWIW, for vanilla Dired, lines `.' and `..' are generally
> "meaningless".

You can discard them by setting `dired-listing-switches' to an
appropriate value if you don't like them.  The value is passed to the
program `ls'.  On MS-Windows things seem to be a little different, not
sure.

___

To sum up, new patch will provide an option which controls the style
of moving point.

--
Responses may be delayed as I have classes during the day
(UTC+8, not 0, contrary to what my email program indicates).




  parent reply	other threads:[~2023-09-01 17:29 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30 13:02 bug#65621: [PATCH] `dired-next-line' go to meaningful line Shynur Xie
2023-08-30 13:36 ` Eli Zaretskii
2023-08-30 13:50   ` Shynur Xie
2023-08-30 14:20     ` Eli Zaretskii
2023-08-30 19:14       ` Stefan Kangas
2023-08-30 20:58         ` Drew Adams
2023-08-30 21:34           ` Stefan Kangas
2023-08-30 22:36             ` Drew Adams
2023-08-31  5:45         ` Shynur Xie
2023-08-31 15:35           ` Drew Adams
2023-08-31 15:46             ` Shynur Xie
2023-08-31 15:55               ` Drew Adams
2023-08-31 18:15                 ` Shynur Xie
2023-08-31 19:10                   ` Drew Adams
2023-08-31 19:17                     ` Drew Adams
2023-08-31 19:44                     ` Shynur Xie
2023-08-31 21:51                       ` Drew Adams
2023-08-31 21:35                   ` Stefan Kangas
2023-08-31 21:37                     ` Stefan Kangas
2023-09-01 17:29                     ` Shynur Xie [this message]
2023-09-01 18:46                       ` Drew Adams
2023-09-01 20:51                         ` Shynur Xie
2023-09-01 21:06                           ` Drew Adams
2023-09-02 12:05                             ` Shynur Xie
2023-09-02 12:13                               ` Eli Zaretskii
2023-09-02 12:18                                 ` Shynur Xie
2023-09-02 12:39                                   ` Eli Zaretskii
2023-09-02 14:40                                     ` Shynur Xie
2023-09-10  7:45                                       ` Eli Zaretskii
2023-09-03 21:47                               ` Drew Adams
2023-09-07 15:04                                 ` Shynur Xie
2023-08-30 14:54 ` Drew Adams
2023-08-30 15:39   ` Shynur Xie
2023-08-30 15:55     ` Drew Adams

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=PH0PR11MB7470E78B7F2F0950B81D3C43D7E4A@PH0PR11MB7470.namprd11.prod.outlook.com \
    --to=one.last.kiss@outlook.com \
    --cc=65621@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=stefankangas@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.