From: Deniz Dogan <deniz@dogan.se>
To: emacs-devel@gnu.org
Subject: Re: Is it time to create more subdirs in lisp/?
Date: Fri, 02 Sep 2011 12:13:26 +0200 [thread overview]
Message-ID: <4E60AC46.6070500@dogan.se> (raw)
In-Reply-To: <61k49rb7vk.fsf@news.eternal-september.org>
On 2011-09-02 11:39, Richard Riley wrote:
> Alan Mackenzie<acm@muc.de> writes:
>
>> Hi, Deniz.
>>
>> On Thu, Sep 01, 2011 at 07:44:02AM +0200, Deniz Dogan wrote:
>>> The lisp/ directory in trunk could use some more subdirectories.
>>
>>> Examples:
>>
>>> dired-aux.el
>>> dired-x.el
>>> dired.el
>>> epa-dired.el
>>> find-dired.el
>>> image-dired.el
>>
>>> help-at-pt.el
>>> help-fns.el
>>> help-macro.el
>>> help-mode.el
>>> help.el
>>
>>> ps-bdf.el
>>> ps-def.el
>>> ps-mule.el
>>> ps-print.el
>>> ps-samp.el
>>
>> I'd say no. once you start making small directories they're going to
>> start stacking up in an increasingly tall tree.
>>
>> I've been in proprietary projects with around 20,000 files in them, all
>> in directories with ~8-10 files in each. Visiting a file in such a
>> hierarchy is a nightmare, as you have to enter, perhaps, 6 successive
>> directory names to get there. That's a lot of names to have to navigate
>> through.
>>
>> I've been told that small directories are optimal for selecting files
>> with dialog boxes, but that's not how Emacs works. I sometimes find it
>> irritating even to have to go one level down from ../lisp to
>> ../lisp/progmodes.
>>
>> So my vote is for few large directories rather than many small ones. I
>> would go further than Stefan, and say a new directory we create should
>> have at least 100 files, not 20.
>
> Fwiw, I would agree with that. Small dirs look nice on paper in
> orgnisation charts but soon become a selection and maintenance
> nightmare. Especially with built in smart file pickers/selects like
> ido-mode there to ease the burden. Certainly my once hierarchical emacs
> setup soon became a single .emacs.d ... Smart filenames are the key -
> prefix is good.
>
I see your point, and I could definitely agree. I especially agree with
you about smart filenames! As you saw, I missed a few files in my examples.
next prev parent reply other threads:[~2011-09-02 10:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 5:44 Is it time to create more subdirs in lisp/? Deniz Dogan
2011-09-01 8:35 ` Juri Linkov
2011-09-02 2:17 ` Richard Stallman
2011-09-02 1:59 ` Stefan Monnier
2011-09-02 9:11 ` Alan Mackenzie
2011-09-02 9:39 ` Richard Riley
2011-09-02 10:13 ` Deniz Dogan [this message]
2011-09-02 13:01 ` Stefan Monnier
2011-09-02 17:52 ` chad
2011-09-04 15:30 ` Kan-Ru Chen
2011-09-06 18:13 ` Stefan Monnier
2011-09-20 13:58 ` Nix
2011-09-21 1:24 ` Stephen J. Turnbull
2011-09-21 9:40 ` chad
2011-09-02 16:26 ` Bill Wohler
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=4E60AC46.6070500@dogan.se \
--to=deniz@dogan.se \
--cc=emacs-devel@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.