Gnus development mailing list
 help / color / mirror / Atom feed
From: Russ Allbery <rra@stanford.edu>
Cc: John Moreno <phenix@interpath.com>,
	Karl-Johan Noren <k-j-nore@dsv.su.se>
Subject: Re: GNKSA and Gnus
Date: 05 Jan 1998 12:31:09 -0800	[thread overview]
Message-ID: <m3k9cepss2.fsf@windlord.Stanford.EDU> (raw)
In-Reply-To: Per Abrahamsen's message of 05 Jan 1998 20:54:52 +0100

Per Abrahamsen <abraham@dina.kvl.dk> writes:

> I often have to manually edit the references line when posting followups
> in gnu.misc.discuss in order to make INN accept it.  I guess it happens
> in gnu.misc.discuss because

> 1) The threads there are very deep.
> 2) There are a high fraction of Gnus users, thus none of the posters
>    software will restrict the header.

I stand corrected.

> ##  Maximum size of a single header.
> #### =()<MAXHEADERSIZE          @<MAXHEADERSIZE>@>()=
> MAXHEADERSIZE           1024

I believe this only affects headers which are not continued.  If one uses
continuation lines, headers can be much larger.  (Or that at least is my
understanding.)  Keep in mind that the version of Gnus that I'm using
still wraps References using continuation lines; I think Lars took that
out at some point?

It sounds like either the header wrapping code needs to be put back in or
Gnus needs to shorten the Reference headers it generates, in the short
term.  In the long term, I expect the new news RFC to require References
headers not be truncated.

> This is something Gravity does, and in general a good idea.  It migth
> make less sense for Gnus.  However, I think it would be nice if quoting
> would be restricted to the currently region in the messsage being
> quoted, iff `transient-message-mode' is on, and the region is active.

I still don't think this idea makes any sense.  But YMMV.

-- 
Russ Allbery (rra@stanford.edu)         <URL:http://www.eyrie.org/~eagle/>


  reply	other threads:[~1998-01-05 20:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199712280107.UAA02498@mail.interpath.net>
1998-01-05 19:54 ` Per Abrahamsen
1998-01-05 20:31   ` Russ Allbery [this message]
1998-01-05 21:29     ` Selective quoting (was: Re: GNKSA and Gnus) Per Abrahamsen
1998-01-12 22:15   ` GNKSA and Gnus Lars Magne Ingebrigtsen
1998-01-12 22:45     ` Russ Allbery
1998-02-02 18:25       ` Lars Magne Ingebrigtsen
1998-01-12 22:48     ` Hrvoje Niksic
1998-01-13 15:58     ` PATCH: Don't quote signature (was: Re: GNKSA and Gnus) Per Abrahamsen
1998-01-14 23:57       ` Kim-Minh Kaplan
1998-01-15  0:15         ` Hrvoje Niksic
1998-01-15  8:52           ` Stig Sandbeck Mathisen
1998-01-15 13:55             ` Per Abrahamsen
1998-01-15 14:16               ` Lars Balker Rasmussen
1998-01-15 14:42                 ` Per Abrahamsen
1998-01-15 14:49                   ` Lars Balker Rasmussen
1998-01-15 15:36                     ` Per Abrahamsen
1998-01-18 13:16           ` Kim-Minh Kaplan
1998-02-08 15:18       ` Lars Magne Ingebrigtsen
1998-01-05 21:22 GNKSA and Gnus John Moreno
1998-01-05 22:02 ` Lars Balker Rasmussen
  -- strict thread matches above, loose matches on Subject: below --
1998-01-04 22:04 [John Moreno <phenix@interpath.com>] " John Moreno
1998-01-08  9:14 ` Russ Allbery
1998-01-04 21:45 [John Moreno <phenix@interpath.com>] " Russ Allbery
1998-01-04 22:27 ` John Moreno
1998-01-04 23:58   ` Matt Simmons
1998-01-05 13:42     ` Robert Bihlmeyer

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=m3k9cepss2.fsf@windlord.Stanford.EDU \
    --to=rra@stanford.edu \
    --cc=k-j-nore@dsv.su.se \
    --cc=phenix@interpath.com \
    /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).