unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Emanuel Berg <embe8573@student.uu.se>, help-gnu-emacs@gnu.org
Subject: RE: Elispers all around the world (was: Re: describe-mode "some-mode"?)
Date: Mon, 1 Sep 2014 15:29:06 -0700 (PDT)	[thread overview]
Message-ID: <3883811d-10d9-4a97-8841-87979cc48868@default> (raw)
In-Reply-To: <87egvvrpi0.fsf_-_@debian.uxu>

> > If you want something added to vanilla Emacs, use
> > `M-x report-emacs-bug'. That is for enhancement
> > requests and bug reports. It will bring the request
> > to the attention of Emacs Dev, you will get their
> > response, and the request or issue will be tracked.
> 
> You don't think that the thousands of Joe Elisp Hackers
> all over the world with their .emacs and .gnus and
> private libraries; and all the packages in ELPA, MELPA,
> and Marmalade; and all the code in the EmacsWiki; and
> all the code published on Usenet and listbots and on
> the SX sites and other forums - you don't think this
> total diaspora could benefit from a more elaborate
> review system than `report-emacs-bug'?

Same advice applies.

If you want your "more elaborate review system" to come
into being to benefit that diaspora, and if you want it to
be available in Emacs itself or to affect anything that is
distributed with GNU Emacs, then `M-x report-emacs-bug' is
the best way to communicate your suggestion about it.

Your suggestion can include code, of course, if you have
some to offer for this.

And if you want that but you have nothing concrete or
specific to request or offer now, and you want to invite
discussion about your incipient idea that might eventually
lead to something real, you can open a thread to discuss
it on emacs-devel@gnu.org, the Emacs development list.

In short, such developments do not fall from the sky.
If you want to affect GNU Emacs then my advice is to
contact those who develop and maintain it.

All of this applies *IF* you care about affecting vanilla
Emacs - see that qualification in the first line you quoted,
above.



  parent reply	other threads:[~2014-09-01 22:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22 17:27 describe-mode "some-mode"? lee
2014-08-22 18:21 ` Drew Adams
2014-08-23 12:49   ` lee
2014-08-23 15:29     ` Drew Adams
2014-08-30 11:29       ` lee
     [not found]     ` <mailman.7432.1408807808.1147.help-gnu-emacs@gnu.org>
2014-08-24  1:56       ` Emanuel Berg
2014-08-24  2:46         ` Drew Adams
     [not found]         ` <mailman.7448.1408848386.1147.help-gnu-emacs@gnu.org>
2014-08-31 22:27           ` Emanuel Berg
2014-09-01  3:37             ` Drew Adams
     [not found]             ` <mailman.8013.1409542696.1147.help-gnu-emacs@gnu.org>
2014-09-01 21:37               ` Elispers all around the world (was: Re: describe-mode "some-mode"?) Emanuel Berg
2014-09-01 22:27                 ` Jorge Araya Navarro
2014-09-01 22:29                 ` Drew Adams [this message]
     [not found]                 ` <mailman.8073.1409610571.1147.help-gnu-emacs@gnu.org>
2014-09-01 23:10                   ` Emanuel Berg
     [not found]                 ` <mailman.8074.1409610608.1147.help-gnu-emacs@gnu.org>
2014-09-01 23:17                   ` Emanuel Berg
     [not found]   ` <mailman.7427.1408798399.1147.help-gnu-emacs@gnu.org>
2014-08-24  2:22     ` describe-mode "some-mode"? Emanuel Berg
     [not found] ` <mailman.7404.1408731692.1147.help-gnu-emacs@gnu.org>
2014-08-22 19:04   ` Emanuel Berg
2014-08-23  3:27     ` IELM (was: Re: describe-mode "some-mode"?) Emanuel Berg
2014-08-23 13:20       ` describe-mode "some-mode": (documentation some-mode) (was: IELM) lee
     [not found]       ` <mailman.7429.1408800080.1147.help-gnu-emacs@gnu.org>
2014-08-24  2:05         ` Emanuel Berg
2014-08-30 11:42           ` describe-mode "some-mode": (documentation some-mode) lee
2014-08-30 22:30             ` Michael Heerdegen

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=3883811d-10d9-4a97-8841-87979cc48868@default \
    --to=drew.adams@oracle.com \
    --cc=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).