From: Justin Sheehy <dworkin@ccs.neu.edu>
Subject: Re: gnus-uu-post-length
Date: 02 Apr 1997 11:49:59 -0500 [thread overview]
Message-ID: <vndg1x95pzc.fsf@everest.ccs.neu.edu> (raw)
In-Reply-To: Jeff Murphy's message of 02 Apr 1997 09:14:42 -0500
Jeff Murphy <jcmurphy@smurfland.cit.buffalo.EDU> writes:
> ah. i figured there would be some sort of a common backend, so i
> did an symbol lookup on 'length' .. and that was the only relevant-looking
> symbol it came up with.
>
> pointers to the correct place to look are welcome! :)
[re: tm posting functions and message splitting]
Check out the variables:
mime-editor/message-default-max-length
mime-editor/message-max-length-alist
mime-editor/split-message
The simplest fix is to (setq mime-editor/split-message nil).
-Justin
next prev parent reply other threads:[~1997-04-02 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-04-01 17:06 gnus-uu-post-length Jeff Murphy
1997-04-02 9:57 ` gnus-uu-post-length Lars Magne Ingebrigtsen
1997-04-02 14:14 ` gnus-uu-post-length Jeff Murphy
1997-04-02 16:49 ` Justin Sheehy [this message]
1997-04-03 7:07 ` gnus-uu-post-length Andy Eskilsson
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=vndg1x95pzc.fsf@everest.ccs.neu.edu \
--to=dworkin@ccs.neu.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).