unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Shynur Xie <one.last.kiss@outlook.com>,
	Stefan Kangas <stefankangas@gmail.com>
Cc: "65621@debbugs.gnu.org" <65621@debbugs.gnu.org>
Subject: bug#65621: [PATCH] `dired-next-line' go to meaningful line
Date: Sun, 3 Sep 2023 21:47:28 +0000	[thread overview]
Message-ID: <SJ0PR10MB54880F95B1D9D596D6F51EA5F3EAA@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <PH0PR11MB7470B92C8D4D88240F8C5935D7EBA@PH0PR11MB7470.namprd11.prod.outlook.com>

> > > Drew wants to skip the current directory
> > > and the parent directory;
> >
> > No, he doesn't.  Not at all.  Definitely not.
> > I think maybe you misread what I wrote.
> 
> You really confused me.  If you don't want it,
> why mentioned it twice?

I mentioned it only because you were defining a
Boolean option `dired-headerline-is-meaningful'.

I wanted to let you know that `.' and `..' are
also lines that you might want to let the
option skip over, because vanilla Emacs doesn't
allow actions on them sometimes.

IOW, IF you're going to have an option for
choosing which lines are "meaningful", THEN you
might want to allow for header lines too, as
another kind of line to skip.

I clearly introduced that FYI with "FWIW", and
added:

  Dunno whether you want to include optionally
  skipping over them with `n'|`p', i.e., via
  `dired-cursor-goto-meaningful-line.

Clearly I wasn't _requesting_ being able to
skip `.' and `..' lines, and a conclusion that
Drew _asked_ for that was unwarranted.  As was
the further conclusion that his supposed ask
for that conflicted with his (repeated) FYIs
that this was _not_ something he requested.

The contradiction and confusion were in your
imagination, I'm afraid.  I think I was clear
from the outset.

If it were I, I'd have done what I did in
Dired+: no option to decide what lines are
"meaningful".

I do think it's fine to skip over blank lines
(which Dired+ hasn't done).  But I saw and I
see no real need for an option such as
`dired-headerline-is-meaningful'.  (I think
Stefan said that too, and I see you've now
removed it.)

What I argued for was having `n' and `p' go
to header lines, as they always have.  To
accommodate _your_ wish to _not_ do that I
suggested you make that optional (but have
skipping such lines be opt-in).

IOW, I suggested an option to accommodate
your new behavior (skip header lines) as
well as to respect Emacs's longstanding
(and more useful) behavior of not skipping
them.

> You proposed this idea:
> 
> > What I said was that for _vanilla_
> > Emacs some actions aren't allowed
> > on `.' and `..'.  And so based on
> > that, you or someone else (NOT I),
> > might want those lines, in addition
> > to blank lines, to be skipped over
> > as "meaningless".
> 
> and then rejected it:
> 
> > I'd say that none of the complications
> > you've offered with this latest
> > suggestion are helpful.

You elided the real point I made there:

  I'd suggest that skipping over blank lines, if
  you want to do that, is enough.  And offering
  cycling is a nice-to-have, but is orthogonal to
  the bug report.

And that matches what you ended up with.

> Inconsistent.
> 
> If you don't want it and you don't want anyone else to use it, then
> do not mention it in the first place.

I mentioned it because you were looking to
have users customize the kinds of lines
they want to consider "meaningless" (and
thus skip over).

I was just trying to help you in your attempt
to do that, by offering an FYI about another
kind of line that vanilla Emacs sometimes
allows no action on.

HTH.





  parent reply	other threads:[~2023-09-03 21:47 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
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 [this message]
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

  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=SJ0PR10MB54880F95B1D9D596D6F51EA5F3EAA@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=65621@debbugs.gnu.org \
    --cc=one.last.kiss@outlook.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 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).