From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: winkler@gnu.org, 21746@debbugs.gnu.org
Subject: bug#21746: 24.5; purpose of dired-keep-marker-copy?
Date: Sat, 24 Oct 2015 01:30:31 -0700 (PDT) [thread overview]
Message-ID: <779ec8c7-4899-437f-8c71-d3970975ee65@default> (raw)
In-Reply-To: <<834mhgy8pv.fsf@gnu.org>>
> Would you like to propose documentation patches for the Dired stuff
> you think is important, but is missing from the manual? TIA.
No, sorry.
What would presumably be easy to do would be to load all
of the Dired files together. I think that would be an
easy way to help understanding, discovery, and visibility.
More doc could be helpful too, but it is less important than
loading the files automatically (upon using `C-x d'), and it
requires more work (by someone).
next parent reply other threads:[~2015-10-24 8:30 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<875f037b-3321-42b7-9128-bb4dd2bd1f7f@default>
[not found] ` <<834mhgy8pv.fsf@gnu.org>
2015-10-24 8:30 ` Drew Adams [this message]
[not found] <<b3efc431-90b5-4012-acbb-664f8b54e63b@default>
[not found] ` <<83611wy995.fsf@gnu.org>
2015-10-24 8:21 ` bug#21746: 24.5; purpose of dired-keep-marker-copy? Drew Adams
2015-10-24 8:28 ` Eli Zaretskii
[not found] ` <<cf6c5e6b-78d8-432a-8639-7c630e89c74c@default>
[not found] ` <<8337x0y8j8.fsf@gnu.org>
2015-10-24 8:34 ` Drew Adams
2015-10-24 8:50 ` Eli Zaretskii
[not found] ` <<eeff7ef4-08cd-49b6-bfb2-a4680b996a36@default>
[not found] ` <<831tcky7it.fsf@gnu.org>
2015-10-24 16:05 ` Drew Adams
[not found] <<36360.86247.586145.22058@gargle.gargle.HOWL>
[not found] ` <<69182d70-1f68-4105-9f24-7bbef43e7ecb@default>
[not found] ` <<40607.80402.459249.22058@gargle.gargle.HOWL>
[not found] ` <<987d58d9-30d3-4067-a0ae-7a7722a3f2fb@default>
[not found] ` <<83k2qcygzk.fsf@gnu.org>
2015-10-24 8:04 ` Drew Adams
2015-10-24 8:13 ` Eli Zaretskii
[not found] ` <<56535.83174.772198.22058@gargle.gargle.HOWL>
[not found] ` <<be0730e5-48a6-41c9-97dd-9eb676947d89@default>
[not found] ` <<837fmcy9ck.fsf@gnu.org>
2015-10-24 8:17 ` Drew Adams
2015-10-24 8:25 ` Eli Zaretskii
2015-10-23 19:44 Roland Winkler
2015-10-23 20:30 ` Drew Adams
2015-10-23 20:54 ` Roland Winkler
2015-10-23 21:57 ` Drew Adams
2015-10-24 1:20 ` Roland Winkler
2015-10-24 8:04 ` Drew Adams
2015-10-24 8:11 ` Eli Zaretskii
2015-10-24 9:35 ` Andreas Schwab
2015-10-24 16:05 ` Drew Adams
2015-10-24 16:14 ` Drew Adams
2015-10-24 20:51 ` Roland Winkler
2015-10-24 21:09 ` Andreas Schwab
2015-10-24 21:34 ` Drew Adams
2015-10-24 22:00 ` Andreas Schwab
2015-10-24 21:30 ` Drew Adams
2015-10-25 0:15 ` Michael Heerdegen
2015-10-25 4:01 ` Roland Winkler
2015-10-25 5:12 ` Drew Adams
2015-10-25 17:40 ` Richard Stallman
2015-10-25 12:55 ` Andreas Schwab
2015-10-25 18:40 ` Eli Zaretskii
2022-04-28 11:50 ` Lars Ingebrigtsen
2015-10-29 0:14 ` Juri Linkov
2015-10-29 0:37 ` Michael Heerdegen
2015-10-29 0:53 ` Drew Adams
2015-10-24 5:26 ` Eli Zaretskii
2015-10-24 6:10 ` Eli Zaretskii
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=779ec8c7-4899-437f-8c71-d3970975ee65@default \
--to=drew.adams@oracle.com \
--cc=21746@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=winkler@gnu.org \
/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).