From: "Drew Adams" <drew.adams@oracle.com>
To: "'Richard Riley'" <rileyrgdev@gmail.com>, <help-gnu-emacs@gnu.org>
Subject: RE: emacs mode line suggestions
Date: Mon, 17 Nov 2008 10:53:26 -0800 [thread overview]
Message-ID: <000c01c948e5$c6189420$0ab32382@us.oracle.com> (raw)
In-Reply-To: <gfs53m$it1$7@news.motzarella.org>
> > This is help-gnu-emacs. It's for getting help about using Emacs.
>
> But it should not be too disturbing to gauge Emacs user's views on
> certain issues. The nature of a Help group often means there are more
> new users and new users are often a catalyst for new and good
> ideas. Any half decent news reader features thread kill and keeping
> most in one or two threads is not disrupting. In addition discussion
> threads on functionality are often educational - many such threads
> have taught me new things about how and why things are in Emacs.
You can do as you like, of course; I'm not moderating this mailing list. I'm
really just trying to help.
The point is that such discussions are part of the _purpose_ of emacs-devel, and
help-gnu-emacs has a different purpose. If you want to influence Emacs
developers to make changes, emacs-devel is the place. To get changes made, there
will ultimately need to be a discussion at emacs-devel anyway - might as well
put it there to begin with.
Can discussion of possible Emacs improvements be educational and helpful for
users, new and old? Yes, of course. Absolutely. Users who are interested in
reading or participating in such discussions can subscribe to emacs-devel.
Personally, I encourage that. In the world of Emacs _in particular_, there is no
clear separation between user and designer or implementor.
Any and all users - new and old - who are interested in such discussion: Please
subscribe to emacs-devel, whether you just want to lurk or you want to
contribute. That will help improve both emacs-devel and Emacs. People, myself
included, sometimes complain that emacs-devel is not open enough or is too set
in its ways. The remedy for that is for more people to participate.
Like it or not, there is no substitute for arguing your case at emacs-devel for
a particular change you want. If you think Emacs needs fresh ideas and you have
some, bring them to emacs-devel, by all means. Be prepared to support them with
clear, logical argument, of course. And patience is advised: "You can't always
get what you want, but if you try sometimes well you just might find you get
what you need."
FWIW, I have contributed countless suggestions to emacs-devel for improving
(IMO) Emacs. Relatively few have been incorporated. But emacs-devel is still the
most effective place to discuss such things, IMO, not help-gnu-emacs. There is
no guarantee that your suggestions will be followed at emacs-devel - the
contrary is more likely. But they will be read and seriously considered.
Another, indirect way to influence Emacs development is to implement the changes
you propose and make them available somewhere in a library. That ultimately can
affect Emacs development by being food for thought or through direct inclusion
someday.
The developers who build and distribute Emacs can sometimes be persuaded by
sound argument if the idea is a good one, but working code that _shows_ them
what you want can be even more persuasive.
Even if your third-party code never changes the Emacs distribution, it can help
other users, and they will give you valuable feedback to further your own ideas
of improvement. There are many good libraries out there that have never been
added to the Emacs distribution and probably never will be. Yet they indirectly
affect the evolution of Emacs.
This is because the real designers and developers of Emacs are a much wider
group than those who modify and distribute the Emacs source code. All user
feedback and bug reports are part of Emacs development, as are third-party Emacs
libraries.
This is of course true generally, but it is all the more true for Emacs, where
many (most?) users create their own Emacs through customization, coding, and
reuse of third-party code. Emacs's users are its developers. If you are
interested in how Emacs evolves, please join the discussion at emacs-devel.
next prev parent reply other threads:[~2008-11-17 18:53 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.215.1226562978.26697.help-gnu-emacs@gnu.org>
2008-11-14 23:18 ` emacs mode line suggestions Xah
2008-11-15 1:02 ` xahlee
2008-11-15 9:23 ` Eli Zaretskii
[not found] ` <mailman.423.1226741023.26697.help-gnu-emacs@gnu.org>
2008-11-16 1:54 ` Xah
2008-11-16 18:12 ` Ian Eure
2008-11-18 9:39 ` Kevin Rodgers
2008-11-18 23:25 ` Xavier Maillard
[not found] ` <mailman.518.1226859137.26697.help-gnu-emacs@gnu.org>
2008-11-16 18:20 ` Richard Riley
2008-11-16 23:12 ` Ian Eure
2008-11-17 8:37 ` Paul R
2008-11-17 15:45 ` Drew Adams
[not found] ` <mailman.604.1226937124.26697.help-gnu-emacs@gnu.org>
2008-11-17 16:11 ` Richard Riley
2008-11-17 18:53 ` Drew Adams [this message]
2008-11-17 19:10 ` Richard Riley
2008-11-17 19:57 ` Drew Adams
2008-11-17 20:53 ` Eli Zaretskii
[not found] ` <mailman.621.1226951870.26697.help-gnu-emacs@gnu.org>
2008-11-17 21:42 ` Richard Riley
2008-11-18 0:55 ` Drew Adams
[not found] ` <mailman.641.1226969742.26697.help-gnu-emacs@gnu.org>
2008-11-18 1:08 ` Richard Riley
2008-11-18 2:55 ` Drew Adams
2008-11-17 23:37 ` Alan Mackenzie
2008-11-18 7:52 ` Paul R
2008-11-18 13:48 ` Alan Mackenzie
[not found] ` <mailman.543.1226877138.26697.help-gnu-emacs@gnu.org>
2008-11-16 23:35 ` Richard Riley
2008-11-16 22:45 ` Xah
2008-11-16 21:40 ` Eli Zaretskii
[not found] ` <mailman.536.1226871605.26697.help-gnu-emacs@gnu.org>
2008-11-16 23:17 ` Xah
2008-11-17 20:39 ` Eli Zaretskii
2008-11-17 23:46 ` Alan Mackenzie
2008-11-18 0:31 ` Lennart Borgman
2008-11-18 9:32 ` Kevin Rodgers
2008-11-18 9:58 ` Alan Mackenzie
[not found] ` <mailman.633.1226964831.26697.help-gnu-emacs@gnu.org>
2008-11-18 9:46 ` Fabrice Niessen
[not found] ` <mailman.623.1226954396.26697.help-gnu-emacs@gnu.org>
2008-11-17 22:09 ` Xah
2008-11-18 2:33 ` B. T. Raven
2008-11-18 3:24 ` Xah
2008-11-18 4:58 ` B. T. Raven
2008-11-18 6:54 ` Richard Riley
2008-11-18 4:11 ` Eli Zaretskii
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='000c01c948e5$c6189420$0ab32382@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=rileyrgdev@gmail.com \
/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.