From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: RFC: Flavors - naming significant sets of customizations
Date: Sun, 01 Dec 2013 17:27:12 +0100 [thread overview]
Message-ID: <87y544k03q.fsf@nl106-137-194.student.uu.se> (raw)
In-Reply-To: mailman.7689.1385878732.10748.help-gnu-emacs@gnu.org
Jambunathan K <kjambunathan@gmail.com> writes:
>> ...because if there are those suite files available,
>> people don't have to do that configuration
>> themselves.
>
> It is not just the question of availability. It should
> be available in a centralized place and that it should
> be improved upon.
>
> Merely having a "common" customization shared in a
> centralized place like Gnu Emacs or Gnu Elpa is a
> great way to build consensus or build on (or atleast
> learn from) each other efforts.
Yes, availability and quality and "focal point" of
efforts.
> May be you want to share some of your Emacs
> customization in these places
Yes, I will go through my Elisp and for each defun, ask
myself if it is something I did just because I like it
that way or if it is something others could benefit
from. I think most of it isn't, but I know some is, so
I will do it. When I'm done, should I post it on
gnu.emacs.sources and then someone will decide if it
is? I'm fine with that method and I don't think
discussion will be needed: I did this for myself and I
will continue to use it, so there is no potential loss
(on my part at least :)).
By the way, I configured Gnus to show a short comment
for each group and for gnu.emacs.sources it says "Lisp
and C only" (pseudo-quote) emphatically - is this a
remnant of some glorious past? Because I don't see lots
of people spamming the group with Perl and C++...
--
Emanuel Berg, programmer-for-rent. CV, projects, etc at uXu
underground experts united: http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2013-12-01 16:27 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 19:31 RFC: Flavors - naming significant sets of customizations ian.tegebo
2013-11-25 19:44 ` Jambunathan K
2013-11-25 19:54 ` Drew Adams
2013-11-25 20:04 ` Jambunathan K
2013-11-25 21:14 ` Drew Adams
2013-11-25 19:54 ` Stefan Monnier
2013-11-25 20:19 ` Dirk-Jan C. Binnema
2013-11-25 20:27 ` Jambunathan K
2013-11-25 20:50 ` Stefan Monnier
2013-11-25 21:11 ` Drew Adams
2013-11-26 2:12 ` William G. Gardella
2013-11-26 2:15 ` William G. Gardella
2013-11-26 2:25 ` William G. Gardella
[not found] ` <mailman.7131.1385432744.10748.help-gnu-emacs@gnu.org>
2013-11-26 3:12 ` Emanuel Berg
2013-11-26 14:35 ` Drew Adams
[not found] ` <mailman.7112.1385413891.10748.help-gnu-emacs@gnu.org>
2013-11-26 0:13 ` Stefan Monnier
2013-11-26 1:41 ` Drew Adams
2013-11-25 21:10 ` Drew Adams
2013-11-25 21:05 ` Peter Dyballa
2013-11-25 21:25 ` Jambunathan K
2013-11-26 1:03 ` Emanuel Berg
2013-11-26 9:42 ` Thien-Thi Nguyen
[not found] ` <mailman.7101.1385409281.10748.help-gnu-emacs@gnu.org>
2013-11-25 20:04 ` ian.tegebo
2013-11-26 20:15 ` Ted Zlatanov
2013-11-26 20:33 ` Emanuel Berg
2013-11-26 21:00 ` Peter Dyballa
2013-11-27 1:22 ` Stefan Monnier
[not found] ` <mailman.7149.1385458742.10748.help-gnu-emacs@gnu.org>
2013-11-27 4:03 ` Emanuel Berg
2013-11-29 1:40 ` Rustom Mody
2013-11-29 4:24 ` Emanuel Berg
2013-11-29 5:56 ` Rustom Mody
2013-11-30 1:05 ` Emanuel Berg
2013-11-30 5:52 ` Jambunathan K
2013-11-30 6:06 ` Jambunathan K
2013-11-30 6:56 ` Jambunathan K
[not found] ` <mailman.7606.1385794704.10748.help-gnu-emacs@gnu.org>
2013-11-30 7:49 ` Emanuel Berg
[not found] ` <mailman.7603.1385790839.10748.help-gnu-emacs@gnu.org>
2013-11-30 7:57 ` Emanuel Berg
2013-11-30 14:22 ` Emanuel Berg
2013-12-01 6:18 ` Jambunathan K
2013-12-01 6:30 ` Jambunathan K
[not found] ` <mailman.7689.1385878732.10748.help-gnu-emacs@gnu.org>
2013-12-01 16:27 ` Emanuel Berg [this message]
2013-12-02 5:21 ` Jambunathan K
2013-12-02 16:29 ` Emanuel Berg
2013-12-02 17:07 ` Emanuel Berg
2013-12-03 12:29 ` Jambunathan K
[not found] ` <mailman.7971.1386070312.10748.help-gnu-emacs@gnu.org>
2013-12-03 21:27 ` Emanuel Berg
2013-12-04 7:25 ` Jambunathan K
[not found] ` <mailman.8057.1386141963.10748.help-gnu-emacs@gnu.org>
2013-12-04 17:50 ` Emanuel Berg
[not found] ` <mailman.7691.1385879486.10748.help-gnu-emacs@gnu.org>
2013-12-01 16:29 ` Emanuel Berg
2013-11-29 8:31 ` Yuri Khan
2013-11-29 18:00 ` Jambunathan K
[not found] ` <mailman.7486.1385748092.10748.help-gnu-emacs@gnu.org>
2013-11-29 19:13 ` Emanuel Berg
2013-12-01 7:09 ` Jambunathan K
2013-12-01 20:57 ` Emanuel Berg
2013-12-02 5:25 ` Jambunathan K
2013-12-02 5:57 ` Jambunathan K
2013-12-02 16:47 ` Emanuel Berg
2013-12-02 16:34 ` Emanuel Berg
[not found] ` <mailman.7875.1386002111.10748.help-gnu-emacs@gnu.org>
2013-12-02 22:23 ` Emanuel Berg
2013-12-02 0:51 ` Emanuel Berg
[not found] ` <mailman.7693.1385881824.10748.help-gnu-emacs@gnu.org>
2013-12-01 16:35 ` Emanuel Berg
2013-12-01 20:40 ` Emanuel Berg
2013-11-29 19:55 ` Emanuel Berg
2013-11-30 2:52 ` Rustom Mody
2013-11-30 3:28 ` Emanuel Berg
[not found] ` <mailman.7436.1385713911.10748.help-gnu-emacs@gnu.org>
2013-12-04 17:52 ` Ted Zlatanov
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y544k03q.fsf@nl106-137-194.student.uu.se \
--to=embe8573@student.uu.se \
--cc=help-gnu-emacs@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).