unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Richard Riley <rileyrgdev@googlemail.com>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 'Richard Riley' <rileyrgdev@gmail.com>, help-gnu-emacs@gnu.org
Subject: Re: emacs mode line suggestions
Date: Mon, 17 Nov 2008 20:10:23 +0100	[thread overview]
Message-ID: <t3y6ziman4.fsf@development.richardriley.net> (raw)
In-Reply-To: <000c01c948e5$c6189420$0ab32382@us.oracle.com> (Drew Adams's message of "Mon, 17 Nov 2008 10:53:26 -0800")

"Drew Adams" <drew.adams@oracle.com> writes:

>> > 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.

You seem to miss the point slightly. Many beginners do not, for obvious
reasons, frequent emacs development. And it is beginners I was referring
to.

>
> 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.

Nearly all users tend to develop their own add ons and/or
customisations. Looks at the far reaching Icicles for a good example :-;
It would be a pretty poor sample if the the only new users you could
discuss things with were the ones willing and able to subscribe to emacs
development. Few users do. And having read some of the sniping there one
can readily see why :-;

>
> 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.

If you want to discuss hard core stuff then yes I would concur. But
gauging NEW users feeling about certain emacs defaults can hardly be
done if there are no new users there. And you are an optimist if you
feel that new users will be subscribing to emacs development where it
can be slightly frightening for the non clued in new user IMO.

While I realise you are not policing per se, I find it hard to agree
with you that a discussion about some emacs basics here is a bad thing
since the kind of people whose input would be most valuable are indeed
here. Consider the "help" part of the group name as including helping
people understand why certain things are as they are or even "help"ing
someone come to a design suggestion on how to improve it.






  reply	other threads:[~2008-11-17 19:10 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
2008-11-16 21:40       ` Eli Zaretskii
     [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
2008-11-17 19:10                     ` Richard Riley [this message]
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
     [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

  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=t3y6ziman4.fsf@development.richardriley.net \
    --to=rileyrgdev@googlemail.com \
    --cc=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.
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).