Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: Steve Youngs <sryoungs@bigpond.net.au>, bugs@gnus.org, ding@gnus.org
Subject: gnus-util.el loads rmail
Date: Fri, 05 Dec 2003 09:45:36 +0900	[thread overview]
Message-ID: <b9yu14g2itr.fsf@jpl.org> (raw)

Hi,

Steve Youngs applied your patch to gnus-util.el with the
following ChangeLog entry:

	* gnus-util.el: Get rmail definitions when compiling.
	From Jerry James <james@xemacs.org>.

I am opposed to it.  In XEmacs, since rmail is supplied by the
package, there may be those who have not installed it.
Furthermore, since rmail of the XEmacs version uses tm and also
apel, that packages are also required for it (rmail.el requires
tm-view, tm-view requires std11 which is in apel).  It became
impossible therefore, for such people to build Gnus.

Loading of rmail is only for the `rmail-select-summary' macro,
isn't it?  If so, it can be solved by not compiling that section:

--- gnus-util.el~	2003-12-03 23:28:53 +0000
+++ gnus-util.el	2003-12-05 00:44:47 +0000
@@ -864,8 +864,9 @@
 	      (narrow-to-region (point) (point-max))
 	      (rmail-count-new-messages t)
 	      (when (rmail-summary-exists)
-		(rmail-select-summary
-		 (rmail-update-summary)))
+		(dont-compile
+		  (rmail-select-summary
+		   (rmail-update-summary))))
 	      (rmail-count-new-messages t)
 	      (rmail-show-message msg))
 	    (save-buffer)))))

How about it?  I wish you give aid to the users of minorities
who don't need rmail.

Regards,
-- 
Katsumi Yamaoka <yamaoka@jpl.org>



             reply	other threads:[~2003-12-05  0:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-05  0:45 Katsumi Yamaoka [this message]
2003-12-05  1:25 ` Steve Youngs
2003-12-05  2:52   ` Katsumi Yamaoka
2003-12-07 20:25     ` Steve Youngs
2003-12-08  2:35       ` Katsumi Yamaoka
2003-12-08  4:15         ` Steve Youngs
2003-12-08  9:01           ` Katsumi Yamaoka
2003-12-08 20:05             ` Steve Youngs

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=b9yu14g2itr.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=bugs@gnus.org \
    --cc=ding@gnus.org \
    --cc=sryoungs@bigpond.net.au \
    /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).