Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Eric Eide <eeide@cs.utah.edu>
Subject: Re: [PATCH] Re: New Gnus, Old XEmacs == No Smileys
Date: Sat, 17 May 2003 13:26:58 -0600 (MDT)	[thread overview]
Message-ID: <ywrhe7ts7b1.fsf@ioka.flux.utah.edu> (raw)
In-Reply-To: <87he7u2hcu.fsf@tleepslib.sk.tsukuba.ac.jp>

"Stephen" == Stephen J Turnbull <stephen@xemacs.org> writes:

	Stephen> Thanks for the analysis and the solution.  I'll add it to the
	Stephen> XEmacs FAQ.  Maybe somebody could do the same for Gnus?
	Stephen> Here's my proposed text (a slight reformatting of Kyle's
	Stephen> message).  Eric, Kyle, any comments/objections?

Rather than requiring XEmacs users to know to (setq format-alist nil) --- good
idea though it may be --- wouldn't it also be appropriate to fix Gnus to avoid
the problem?  (I don't know which fix would be more correct: using
`insert-file-contents-literally' as I suggested previously, or dynamically
binding `format-alist' to nil around the insertion of the XPM data.)

If the next version of Gnus fixes the problem, then a FAQ entry that applies
only to Oort and Gnus 5.10.{1,2} would seem to have marginal value.  But I'm
certainly not opposed to the entry you posted.

Thanks ---

Eric.

-- 
-------------------------------------------------------------------------------
Eric Eide <eeide@cs.utah.edu>  .         University of Utah School of Computing
http://www.cs.utah.edu/~eeide/ . +1 (801) 585-5512 voice, +1 (801) 581-5843 FAX


      parent reply	other threads:[~2003-05-17 19:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ywrissmbzix.fsf@ioka.flux.utah.edu>
2003-05-07 21:20 ` Jesper Harder
2003-05-07 23:09   ` Eric Eide
     [not found] ` <ywrwugqor4g.fsf@ioka.flux.utah.edu>
     [not found]   ` <ba3e5q$1noj$1@carbon.wonderworks.com>
     [not found]     ` <87he7u2hcu.fsf@tleepslib.sk.tsukuba.ac.jp>
2003-05-17 19:26       ` Eric Eide [this message]

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=ywrhe7ts7b1.fsf@ioka.flux.utah.edu \
    --to=eeide@cs.utah.edu \
    /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).