From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: tomasn@posteo.net, 41097@debbugs.gnu.org,
Jean Louis <bugs@gnu.support>,
arthur.miller@live.com
Subject: bug#41097: 28.0.50; (dired-toggle-marks) not working after copy
Date: Mon, 11 May 2020 09:18:07 -0700 (PDT) [thread overview]
Message-ID: <d11bcdea-8024-4acc-9123-c381ac1f26fb@default> (raw)
In-Reply-To: <87eerrvxun.fsf@web.de>
> > IOW, explicitly say that toggling applies to `*' marks.
>
> Yes, exactly.
>
> > > But the inconsistency goes much further, we say that commands
> > > operate on the "marked" files, but we mean only the *-marked files.
>
> I mean commands, like
>
> dired-do-delete is an interactive compiled Lisp function in
> `dired.el'. [...]
>
> Delete all marked (or next ARG) files.
>
> It doesn't say *-marked. "Marked" typically means *-marked most of the
> time.
You're absolutely right. The fix for this bug could
usefully be to correct the doc of any command that
acts only on `*' marks but says it acts on "marks".
Doc that says that a command acts on "marks" should
be only for a command that acts on all marks. Doc
for a command that acts only on certain marks should
say so.
> > > (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.
>
> I only wanted to make clear that it's not a new term but one users that
> read the manual are familiar with. And it's maybe less misguiding than
> "flag" (personally I could also live with just "character", since marks
> are really just that).
I don't see the connection. "Flag" has
specifically been used only for `D', the mark
for deletion.
?D is the marker character for the mark (flag)
`D'. ?D is a character. A visual `D' mark in
the buffer is, yes, created by putting a ?D
character in the mark position.
But that's a nit. If what you're suggesting is
that the doc not speak of "flag `D'" but speak
instead of "marker character ?D" or "marker
character D" then I understand. Is that it?
That's OK by me, provided the same is done
everywhere, for each mark: "marker character C"
etc. I don't think that's really helpful - it
seems overly verbose and makes reading more
cumbersome. But if others feel it's an
improvement, fine.
My concern here is that Emacs be consistent in
its explanations and terminology. Another
concern is that things be clear and easy to
understand.
next prev parent reply other threads:[~2020-05-11 16:18 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
2020-05-11 5:34 ` Michael Heerdegen
2020-05-11 16:18 ` Drew Adams [this message]
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
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=d11bcdea-8024-4acc-9123-c381ac1f26fb@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 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).