[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Files in wrong subdirs of emacs/lisp?

From: Richard Stallman
Subject: Re: Files in wrong subdirs of emacs/lisp?
Date: Tue, 16 Dec 2003 09:51:42 -0500

Thanks for looking for these rearrangements.  I agree with you on many
of them, so I'll comment on the ones I disagree with.

    Into emulations:

These are not specifically for emulation; they are just optional

    Into net:

terminal.el has nothing in particular to do with the net.
It just emulates a terminal.

    Into progmodes:

This seems to be a mode for editing a "data language",
so I don't think it belongs in progmodes.


hexl mode is for examining binary files,
and skeleton.el is a sort of advanced Emacs macro facility.
Neither of them particularly has to do with developing or debugging
programs outside Emacs.

    Into textmodes:

These modes are for editing "text" in the sense of "files whose
contents are written in a human language for humans to read".


I don't think of change logs as "text" in this sense.


Archive files certainly are not text.


I don't think these concern text, in the appropriate sense.
The canonical example is /etc/passwd, which is not a file
of text meant for humans to read.


Compression has nothing to do with whether the file's contents are


A spreadsheet certainly isn't text.

    Create a new `vc' subdirectory:

It is very useful to have identified a good candidate for
a new coherent subdirectory.  Thanks.

The name `vc' would be slightly misleading, because that refers to the
feature implemented by the vc*.el files.  It would be stretching
things to include anything but vc*.el in a directory with that name,
and including diff* and ediff* would be a big stretch.

So please use the name `versioning' instead.  That concept is more
abstract, but still clear.  With that name, diff* and ediff* fit

    It could also be considered to make a new `help' subdir for things like:

It is undesirable to make a new subdirectory with just 12 source files.
We don't want to make lots of small subdirectories.

If we could come up with a good name in which both documentation
and customization fit, then I think it would reach the threshold
of being a good idea.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]