Gnus development mailing list
 help / color / mirror / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: rgm@gnu.org, ding@gnus.org, Reiner.Steib@gmx.de, emacs-devel@gnu.org
Subject: Re: syncing from Emacs to Gnus
Date: Mon, 03 Dec 2007 13:43:11 -0500	[thread overview]
Message-ID: <E1IzGG7-0006Rs-3Q@fencepost.gnu.org> (raw)
In-Reply-To: <jwvhcj0seg0.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sun, 02 Dec 2007 21:25:19 -0500)

    > Gnus depends on lots of files in Emacs.  These are just like the
    > others -- general purpose facilities (we moved them BECAUSE they are
    > general purpose) which Gnus happens to use.  They should NEVER have
    > been included in Gnus.

    In many/most cases they were written specifically for Gnus, so I cannot
    agree with the above.

Perhaps a few of them seemed to be special-purpose for Gnus when first
installed.  But some of them were clearly always general-purpose
facilities.  Those should be installed in Emacs as ordinary parts of
Emacs, after a suitable discussion here.  We should discuss the
right design for them, just as we would if some other part of Emacs
had been the motive for writing them.




  reply	other threads:[~2007-12-03 18:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30 22:56 declare-function in files from Gnus (hashcash.el, imap.el) Reiner Steib
2007-11-30 23:27 ` Glenn Morris
2007-12-01 18:35   ` Reiner Steib
2007-12-01 18:54     ` Dan Nicolaescu
2007-12-01 20:35       ` Glenn Morris
2007-12-01 20:40         ` Dan Nicolaescu
2007-12-01 21:50     ` Glenn Morris
2007-12-01 21:42 ` syncing from Emacs to Gnus [was Re: declare-function in files from Gnus (hashcash.el, imap.el)] Glenn Morris
2007-12-01 23:22   ` syncing from Emacs to Gnus Reiner Steib
2007-12-02 14:56     ` Stefan Monnier
2007-12-02 18:39     ` Richard Stallman
2007-12-03  2:25       ` Stefan Monnier
2007-12-03 18:43         ` Richard Stallman [this message]
2007-12-03 18:59           ` Stefan Monnier
2007-12-06  2:12             ` Richard Stallman
     [not found] ` <fir8np$3br$1@ger.gmane.org>
     [not found]   ` <200712011634.lB1GYCkr018222@oogie-boogie.ics.uci.edu>
     [not found]     ` <87mysuwdcx.fsf@neutrino.caeruleus.net>
     [not found]       ` <E1IybxG-0000AT-DD@fencepost.gnu.org>
     [not found]         ` <87ac27w4lz.fsf@neutrino.caeruleus.net>
     [not found]           ` <E1IywKa-0006WN-2v@fencepost.gnu.org>
     [not found]             ` <87u00eufga.fsf@neutrino.caeruleus.net>
     [not found]               ` <200712022237.lB2MbNC8016800@oogie-boogie.ics.uci.edu>
     [not found]                 ` <v9d4tnxtiw.fsf@marauder.physik.uni-ulm.de>
     [not found]                   ` <200712032340.lB3Ne3Vt009200@oogie-boogie.ics.uci.edu>
2007-12-05 20:35                     ` declare-function in files from Gnus (hashcash.el, imap.el) Reiner Steib
2007-12-05 21:01                       ` Glenn Morris
2007-12-08 19:42                         ` Reiner Steib
2007-12-08 22:58                           ` Dan Nicolaescu
2007-12-09  2:20                             ` Glenn Morris
2007-12-09 20:10                               ` Austin Frank
2007-12-09 21:22                                 ` Reiner Steib

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=E1IzGG7-0006Rs-3Q@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rgm@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 NNTP newsgroup(s).