From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>, <jidanni@jidanni.org>
Cc: 6117@debbugs.gnu.org
Subject: bug#6117: 24.0.50; dired-marked-face same as dired-flagged-face
Date: Thu, 6 May 2010 08:20:46 -0700 [thread overview]
Message-ID: <A53244C563D54608BA976DEE768FEDCC@us.oracle.com> (raw)
In-Reply-To: <jwv6331npa2.fsf-monnier+emacs@gnu.org>
> Agreed. And while there, please fix the docstrings so they say more
> clearly what's different about "flagged vs marked".
Yes, thanks.
Some Emacs doc and source-code comments refer to deletion flags as "marks"
(which they are), so it helps to always specifically say "flagged for deletion"
instead of just "flagged".
Then any ambiguity will arise only wrt the terms "marked" or (more likely)
"mark", and that needs to be taken care of contextually. For example, Dired lets
you use `* c' to change "marks", and in that context the `D' flag is considered
a mark.
Always associating "flag" with "deletion" will go a long way to making things
clear.
next prev parent reply other threads:[~2010-05-06 15:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 20:31 bug#6117: 24.0.50; dired-marked-face same as dired-flagged-face jidanni
2010-05-06 13:17 ` Stefan Monnier
2010-05-06 15:20 ` Drew Adams [this message]
2011-07-13 21:28 ` Lars Magne Ingebrigtsen
2011-07-13 22:28 ` Drew Adams
2011-07-16 19:53 ` Lars Magne Ingebrigtsen
2011-08-02 19:05 ` Lars Magne Ingebrigtsen
2011-08-10 9:45 ` Juri Linkov
2011-08-10 13:45 ` Drew Adams
2011-08-17 19:35 ` Juri Linkov
2011-08-17 21:36 ` Chong Yidong
2011-08-18 11:46 ` Juri Linkov
2011-08-24 18:09 ` Juri Linkov
2011-08-24 18:16 ` Drew Adams
2010-05-06 20:57 ` Juri Linkov
2010-05-07 2:43 ` Drew Adams
2010-05-07 18:16 ` Juri Linkov
2010-05-10 18:45 ` bug#6163: 24.0.50; be sure the color of the mark matches that of the filename jidanni
2011-08-02 16:00 ` Lars Magne Ingebrigtsen
2011-08-17 20:02 ` bug#6117: 24.0.50; dired-marked-face same as dired-flagged-face jidanni
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=A53244C563D54608BA976DEE768FEDCC@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=6117@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=monnier@iro.umontreal.ca \
/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.