all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Jean Louis <bugs@gnu.support>,
	41097@debbugs.gnu.org, tomasn@posteo.net, arthur.miller@live.com
Subject: bug#41097: 28.0.50; (dired-toggle-marks) not working after copy
Date: Sun, 10 May 2020 19:33:39 -0700 (PDT)	[thread overview]
Message-ID: <8552ae27-0c1c-4048-a258-2d2dc030f502@default> (raw)
In-Reply-To: <87eerrtiia.fsf@web.de>

> > > Because t toggles marks, and C is not a mark, it's a flag.
> >
> > This is not true.  Let's please not go there.
> 
> But if you think so (and I somewhat agree), isn't then the first
> sentence in the docstring that Eli didn't touch:
> 
>   "Toggle marks: marked files become unmarked, and vice versa."
> 
> even more confusing?  I guess Eli wanted to avoid a sentence like "and
> files marked with marks other than the * mark don't count as marked."

I already agreed that the doc string could be clearer.
I suggested this:

  Toggle `*' marks: unmark marked files, and vice versa.

But perhaps this would be even better (since "those"
refers to "`*' marks"):

  Toggle `*' marks: unmark those marked, and vice versa.

Or (72 chars):

  Toggle `*' marks: unmark files marked `*'; mark unmarked files with `*'.

IOW, explicitly say that toggling applies to `*' marks.

> But the inconsistency goes much further, we say that commands operate
> on the "marked" files, but we mean only the *-marked files.

See above.  (Are you talking about `t' here still?
Why do you say "commands" (plural)?)

> So I guess the terminology is "marked with" applies to any mark and
> "marked" only to files marked with *, and "unmarked" means "doesn't
> have any mark".  Oh dear, it's like learning English modal verbs.

I don't understand.  Perhaps I'm missing something.
No, there's nothing special about "marked with".

`t' replaces all `*' marks with a space - unmarks them.
`t' replaces all unmarked (space) with a `*' mark.

> I think we can be more specific in the docstring, and I also don't like
> to introduce the second term "flag" here since it is somewhat linked to
> deletion indeed, and it's meaning is as fluent as "mark" - that doesn't
> help.

It's _entirely_ linked to deletion, in Dired.  Or it
was, until Eli's change.

> Ok, would something like this be a compromise?
> 
> - Toggle marks: marked files become unmarked, and vice versa.
> - Files marked with other flags (such as `D') are not affected.
> 
> + Toggle marks: marked files become unmarked, and vice versa.
> + This means that files marked with `*' are unmarked and files that
> don't
> + have any mark are marked with `*'.  Files marked with any
> + characters other than `*' are uneffected.

unaffected, not uneffected.

That text is fine by me, even if a bit verbose
("This means").

I'd still propose mentioning `*' in the first
sentence (the main one) - it's about `*' marks
(only).  But your text is clear enough, to me.

> (the term "marker character" is already used in the manual.)

FWIW I don't understand why you added that part
in parens to your message.





  reply	other threads:[~2020-05-11  2:33 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-05 15:01 bug#41097: 28.0.50; (dired-toggle-marks) not working after copy Jean Louis
2020-05-06 14:05 ` Arthur Miller
2020-05-06 14:44   ` Jean Louis
2020-05-08  9:05     ` Arthur Miller
2020-05-08 13:29       ` Jean Louis
2020-05-09  0:25         ` Michael Heerdegen
2020-05-09  1:50           ` Drew Adams
2020-05-09  5:22             ` Michael Heerdegen
2020-05-09  4:23           ` Jean Louis
2020-05-10  1:11             ` Michael Heerdegen
2020-05-10  5:00               ` Jean Louis
2020-05-10  9:25             ` Tomas Nordin
2020-05-10  9:56               ` Jean Louis
2020-05-10 14:07                 ` Eli Zaretskii
2020-05-10 14:55                   ` Jean Louis
2020-05-10 15:11                     ` Eli Zaretskii
2020-05-10 15:33                       ` Jean Louis
2020-05-10 16:05                         ` Eli Zaretskii
2020-05-10 16:29                           ` Drew Adams
2020-05-10 16:40                             ` Eli Zaretskii
2020-05-10 17:17                           ` Jean Louis
2020-05-10 17:19                             ` Eli Zaretskii
2020-05-10 16:26                       ` Drew Adams
2020-05-10 17:32                         ` Jean Louis
2020-05-11  0:36                         ` Michael Heerdegen
2020-05-11  2:33                           ` Drew Adams [this message]
2020-05-11  5:34                             ` Michael Heerdegen
2020-05-11 16:18                               ` Drew Adams
2020-05-11 13:15                         ` Arthur Miller
2020-05-11 16:41                           ` Drew Adams
     [not found] <<20200506144423.GW24998@protected.rcdrun.com>
     [not found] ` <<VI1PR06MB452640273F3311C283C50B5F96A20@VI1PR06MB4526.eurprd06.prod.outlook.com>
     [not found]   ` <<20200508132924.GI14650@protected.rcdrun.com>
     [not found]     ` <<87r1vukl86.fsf@web.de>
     [not found]       ` <<20200509042353.GA15309@protected.rcdrun.com>
     [not found]         ` <<87h7wonnuh.fsf@fliptop.i-did-not-set--mail-host-address--so-tickle-me>
     [not found]           ` <<20200510095646.GA22962@protected.rcdrun.com>
     [not found]             ` <<83y2pzdgt7.fsf@gnu.org>
     [not found]               ` <<20200510145503.GE28606@protected.rcdrun.com>
     [not found]                 ` <<83sgg7ddtz.fsf@gnu.org>
     [not found]                   ` <<20200510153311.GH28606@protected.rcdrun.com>
     [not found]                     ` <<83r1vrdbc0.fsf@gnu.org>
     [not found]                       ` <<6bc132d3-2d2d-4eb3-86dd-b818c1b856a2@default>
     [not found]                         ` <<83mu6fd9q6.fsf@gnu.org>
2020-05-10 16:46                           ` Drew Adams
2020-05-10 17:10                             ` Eli Zaretskii
     [not found] <<<20200506144423.GW24998@protected.rcdrun.com>
     [not found] ` <<<VI1PR06MB452640273F3311C283C50B5F96A20@VI1PR06MB4526.eurprd06.prod.outlook.com>
     [not found]   ` <<<20200508132924.GI14650@protected.rcdrun.com>
     [not found]     ` <<<87r1vukl86.fsf@web.de>
     [not found]       ` <<<20200509042353.GA15309@protected.rcdrun.com>
     [not found]         ` <<<87h7wonnuh.fsf@fliptop.i-did-not-set--mail-host-address--so-tickle-me>
     [not found]           ` <<<20200510095646.GA22962@protected.rcdrun.com>
     [not found]             ` <<<83y2pzdgt7.fsf@gnu.org>
     [not found]               ` <<<20200510145503.GE28606@protected.rcdrun.com>
     [not found]                 ` <<<83sgg7ddtz.fsf@gnu.org>
     [not found]                   ` <<<20200510153311.GH28606@protected.rcdrun.com>
     [not found]                     ` <<<83r1vrdbc0.fsf@gnu.org>
     [not found]                       ` <<<6bc132d3-2d2d-4eb3-86dd-b818c1b856a2@default>
     [not found]                         ` <<<83mu6fd9q6.fsf@gnu.org>
     [not found]                           ` <<af1d7797-47c1-4330-a767-7b4a2773fbac@default>
     [not found]                             ` <<83k11jd8bs.fsf@gnu.org>
2020-05-10 19:18                               ` Drew Adams
2020-05-10 19:54                                 ` Jean Louis
2020-05-10 21:13                                   ` Drew Adams
2020-05-11  5:26                                     ` Jean Louis
2020-05-11 16:03                                       ` Drew Adams
2020-05-11 16:58                                         ` Jean Louis
2020-05-11 17:45                                           ` Drew Adams
2020-05-20  6:37                                             ` Jean Louis
2020-05-20 16:52                                               ` Drew Adams
2020-05-20 17:08                                                 ` Robert Pluim
2020-05-12  3:21                                       ` Richard Stallman

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=8552ae27-0c1c-4048-a258-2d2dc030f502@default \
    --to=drew.adams@oracle.com \
    --cc=41097@debbugs.gnu.org \
    --cc=arthur.miller@live.com \
    --cc=bugs@gnu.support \
    --cc=michael_heerdegen@web.de \
    --cc=tomasn@posteo.net \
    /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.