From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: winkler@gnu.org, 21746@debbugs.gnu.org
Subject: bug#21746: 24.5; purpose of dired-keep-marker-copy?
Date: Sat, 24 Oct 2015 11:13:26 +0300 [thread overview]
Message-ID: <83611wy995.fsf@gnu.org> (raw)
In-Reply-To: <b3efc431-90b5-4012-acbb-664f8b54e63b@default>
> Date: Sat, 24 Oct 2015 01:04:08 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: winkler@gnu.org, 21746@debbugs.gnu.org
>
> > > There is a lot in Dired that I think should be exposed/documented
> > > better/more. By default we don't even load dired-x.el or
> > > dired-aux.el, and they provide lots of stuff useful even for
> > > beginners, including lots of menus.
> > >
> > > I would be in favor of our loading both of these Dired libraries
> > > by default. There is lots in Dired that users can benefit from,
> > > but they are typically unaware of it.
> >
> > Aren't the commands and options there autoloaded?
>
> No.
>
> > If not, we could autoload them, which would solve the
> > visibility problem without bloating the minimal memory
> > footprint too much. Patches welcome.
>
> No, it would not solve the visibility or discoverability
> problem, IMO. Users are much more likely to find and use
> the commands and keys they provide when they are (a) in
> the menus and (b) documented in `C-h m'.
>
> As for the minimal footprint: dired.el is not even loaded
> by default (`C-x d' is autoloaded).
You said above that we don't load dired-x and dired-aux, so I thought
you meant this in contrast with dired.el itself which is preloaded. I
should have checked, sorry.
But if none of them is preloaded, what is it that we do with dired.el
and don't do with the other two packages?
next prev parent reply other threads:[~2015-10-24 8:13 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 ` bug#21746: 24.5; purpose of dired-keep-marker-copy? Drew Adams
2015-10-24 8:13 ` Eli Zaretskii [this message]
[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
[not found] <<875f037b-3321-42b7-9128-bb4dd2bd1f7f@default>
[not found] ` <<834mhgy8pv.fsf@gnu.org>
2015-10-24 8:30 ` Drew Adams
[not found] <<b3efc431-90b5-4012-acbb-664f8b54e63b@default>
[not found] ` <<83611wy995.fsf@gnu.org>
2015-10-24 8:21 ` 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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83611wy995.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21746@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--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 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.