- Subject: Re: [jed-users] Jed modes
- From: Guenter Milde <milde@xxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 20 Mar 2017 10:58:12 +0100
On 18.03.17, Jay Belanger wrote:
> I was going through the old maillists, and I came across
> m_history, which allows you to have different minibuffer histories for
> different prompts. It's something I can use, but I hadn't seen it before;
> it turns out it isn't listed on the mode list at http://jedmodes.sourceforge.net/
> but it is at http://jedmodes.cvs.sourceforge.net/viewvc/jedmodes/mode/.
As this is not my mode, I don't know why it misses the metadata file and
entry in the modes list.
> Should all the modes be listed on the mode list?
Generally, no, not necessarily.
* Some interdependent *.sl files appear together in one jedmodes/mode/*
directory and do not have a separate meta data (dcdata) file.
* Some modes are for internal/special use:
> jedmodes
is a developer tool only linked from http://jedmodes.sourceforge.net/doc/
> kp_keydefs
is probably obsoleted by x-keydefs and only on jedmodes by accident.
> tests
is a collection of unit tests for some of the jedmodes modes.
...
> On the list, but not in jedmodes.cvs (and so, apparently, not in the
> jed-extras package available for Debian):
* Some modes are only listed in the repository but kept the sources elsewhere.
> latex-jlm
* Some modes have a separate archive file and don't use the CVS repository
> apache
> awk
> kcomplete
> outline
> rmail
The jed-extra package would require some download and setup script (or
manual action) for these.
Günter
_______________________________________________
For list information, visit <http://jedsoft.org/jed/mailinglists.html>.
[2017 date index]
[2017 thread index]
[Thread Prev] [Thread Next]
[Date Prev] [Date Next]