From: Jambunathan K <kjambunathan@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: Re: Frequently Enabled Packages - Emacs-24.4 survey (Please participate)
Date: Sun, 08 Dec 2013 22:42:28 +0530 [thread overview]
Message-ID: <87txejnu6b.fsf@gmail.com> (raw)
In-Reply-To: <0fa69156-fdc1-4f59-8784-79d6ca899ec6@default> (Drew Adams's message of "Sun, 8 Dec 2013 07:23:40 -0800 (PST)")
Drew Adams <drew.adams@oracle.com> writes:
> Another thing to consider is that the table was empty to start
> with, and different entries appeared at different points, when
> someone thought to add them.
Actually, it was seeded with my .emacs + Tom's initial list + Andrew's
list - 1 vote for each of the features.
> So, e.g., if the first person happened to add feature `blah'
> to the list, then subsequent "voters" saw `blah' and considered
> it. If `floop' was not added until much later (for whatever
> reason), subsequent voters did not see `floop' until then.
It was for this reason that at around the time when the participant
count stood at 17, I added a list of all major and minor modes (by
rgrepping for define-derived-mode and define-minor-mode in the src
tree). It was generally felt by others that such a big and
comprehensive list would actually drive people away. (This reasoning is
perfeclty understandable.)
I have dumped the list of major and minor modes in to a separate page of
it's own. There are around 244 minor modes and 293 major/derived modes.
See
http://www.emacswiki.org/emacs/List_Of_Major_And_Minor_Modes
I couldn't think of any good reason why such a list would be useful. I
generated the list and I felt why not save it for posterity?
> It is what it is.
Sure it is. It is Emacs users telling how they relate to their Emacs.
next prev parent reply other threads:[~2013-12-08 17:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 6:22 Frequently Enabled Packages - Emacs-24.4 survey (Please participate) Jambunathan K
2013-12-08 11:39 ` Jambunathan K
2013-12-08 13:56 ` Michael Albinus
2013-12-08 15:23 ` Drew Adams
2013-12-08 15:27 ` Drew Adams
2013-12-08 17:12 ` Jambunathan K [this message]
2013-12-08 21:13 ` Matthias Meulien
2013-12-08 22:19 ` Rüdiger Sonderfeld
2013-12-17 10:43 ` Jambunathan K
-- strict thread matches above, loose matches on Subject: below --
2013-12-08 18:26 Jambunathan K
2013-12-08 22:22 ` William G. Gardella
2013-12-09 5:03 ` Jambunathan K
2013-12-09 5:24 ` William G. Gardella
2013-12-09 5:42 ` Jambunathan K
2013-12-09 6:01 ` Jambunathan K
2013-12-09 6:23 ` William G. Gardella
2013-12-09 9:31 ` Jambunathan K
2013-12-09 11:45 ` Andreas Röhler
2013-12-09 13:46 ` William G. Gardella
2013-12-09 13:54 ` Jambunathan K
[not found] ` <mailman.8664.1386597315.10748.help-gnu-emacs@gnu.org>
2013-12-10 22:08 ` Emanuel Berg
[not found] ` <mailman.8662.1386596857.10748.help-gnu-emacs@gnu.org>
2013-12-09 17:34 ` Joost Kremers
[not found] <mailman.8606.1386527424.10748.help-gnu-emacs@gnu.org>
2013-12-10 16:44 ` Emanuel Berg
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=87txejnu6b.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=drew.adams@oracle.com \
--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.