Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: David Carlton <carlton@math.stanford.edu>
Subject: Re: splitting mail of >1000 lines?
Date: 12 Sep 2002 18:42:28 -0700	[thread overview]
Message-ID: <ro1ofb2y8aj.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <m3vg5aeo3d.fsf@defun.localdomain>

On Fri, 13 Sep 2002 02:21:26 +0200, Jesper Harder <harder@myrealbox.com> said:
> David Carlton <carlton@math.stanford.edu> writes:
>> 
>> I must say, though: given the presence (and default values) of
>> mime-editor/split-message and mime-editor/message-default-max-lines,

> These two options are definitely not part of Gnus.  Look at your config
> to see if are loading some other MIME package, SEMI, APEL or
> some such.  What does `C-h v mime-editor/split-message' say?

> Gnus gets upset if you use another non-Gnus MIME-package -- actually,
> I'm a bit surprised that you haven't seen any other problems.

All right, I'm a bit of a dolt today.  Sigh.

I just noticed that I have the line

(require 'mime-setup)

at the bottom of my .gnus.  I assume it's been there for years and
years, that at one point it was useful or even necessary, but that
this no longer is the case (and probably hasn't been for a while).
I'll take it out tomorrow and restart Emacs and see what happens.

Silly me.

David Carlton              |  <http://math.stanford.edu/~carlton/>
carlton@math.stanford.edu  |  Go books: <http://www.gobooks.info/>

       ..  he dominates the DECADENT SUBWAY SCENE.


      parent reply	other threads:[~2002-09-13  1:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-12 21:34 David Carlton
     [not found] ` <ro1vg5aydd9.fsf@jackfruit.Stanford.EDU>
     [not found]   ` <m3vg5aeo3d.fsf@defun.localdomain>
2002-09-13  1:42     ` David Carlton [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=ro1ofb2y8aj.fsf@jackfruit.Stanford.EDU \
    --to=carlton@math.stanford.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).