all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Arthur Miller <arthur.miller@live.com>
Cc: michael_heerdegen@web.de, 41097@debbugs.gnu.org,
	tomasn@posteo.net, Jean Louis <bugs@gnu.support>
Subject: bug#41097: 28.0.50; (dired-toggle-marks) not working after copy
Date: Mon, 11 May 2020 09:41:10 -0700 (PDT)	[thread overview]
Message-ID: <28ab7673-c1da-4be9-a428-cd4bfded001a@default> (raw)
In-Reply-To: <VI1PR06MB4526DA5422AD163FF28588D296A10@VI1PR06MB4526.eurprd06.prod.outlook.com>

> So people are supposed to keep in their mind all this distinction when
> it is a flag and when it is a mark? 

Not necessary, really, I think.  Pretty much every
time "flag" is used it's accompanied by "deletion".
(Extra emphasis, I imagine.)

> So we are supposed to "flag" for
> deletion, but "mark" for copy. Is it really necessary?

Necessary?  No.  What's necessary, besides read,
eval, print?  Someone thought it was helpful.
Probably someone who was worried about users
accidentally deleting files.  Maybe the same
someone who implemented prompting for deletion
confirmation.

> Does it really need to be that complicated,

Is it really complicated?  As one user, I don't
think so.  But YMMV.

> I mean, cognitively speaking? Does it
> really add anything in quality if you distinct between "marking" and
> "flagging" for deletion?

Someone thought so.  I agree with whoever that
was.  But I'm just one user, like you.

> What is wrong to just simply "mark" files
> with different "flags"?

I don't think anyone said there's anything wrong
with that.  But in that case, there's also no
reason to introduce two different terms - just
"mark" with different "marks".

> I am not native english speaker, but it feels I could equally "flag"
> and "mark" my files for deletion.

It's fine with me if everyone wants to remove mention
of "flag" and "flagging".  If you do that, please do
it well, everywhere.  Say explicitly which marks are
involved for each action, unless an action applies to
all marks.

If you make such a change, it's not just a fix for
this minor bug.  You'll need to adjust text, menus,
etc. everywhere, to be consistent.

(IMHO, there's no need in that case to also change
function and variable names.  Ideally, yes, if use of
"flag" is removed then Dired functions and vars with
"flag" in their name should be renamed.  Similarly, but
with less importance, functions and vars with "mark" in
their name should ideally be renamed if they affect
only certain marks - to say that.  But I wouldn't ask
for any such renamings, personally.)

My only position here has been to say what the Dired
convention is and has always been.  And to say that
I think it should be respected consistently.  Any
inconsistencies are candidates for correction.

The convention doesn't come from me.  I'm just the
messenger, reminding us about it.  As a user who knows
it, I've benefitted from it (when I see "flag" I know
it's about deletion).  But I won't argue that the
convention can't be changed.

If someone proposes to change the convention, e.g. to
remove any mention of "flag", then please do that
consistently.  That's all.






  reply	other threads:[~2020-05-11 16:41 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
2020-05-11 13:15                         ` Arthur Miller
2020-05-11 16:41                           ` Drew Adams [this message]
     [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=28ab7673-c1da-4be9-a428-cd4bfded001a@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.