Gnus development mailing list
 help / color / mirror / Atom feed
From: Amos Gouaux <amos+lists.ding@utdallas.edu>
Subject: Re: Can't post-followup or post-forward in nnml groups
Date: Sun, 05 Aug 2001 12:34:30 -0500	[thread overview]
Message-ID: <q6mhevmpg0p.fsf@spartacus.utdallas.edu> (raw)
In-Reply-To: <vaf3d7dj8by.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Tue, 31 Jul 2001 19:51:13 +0200")

[-- Attachment #1: Type: text/plain, Size: 999 bytes --]

>>>>> On Tue, 31 Jul 2001 19:51:13 +0200,
>>>>> Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> (kg) writes:

kg> You could mark the old messages as read...

I do.  Oh, I should point out that for nnimap groups I tend to have
`(display . all)'.  While I prefer to only show new articles for
USENET groups, that's something I've never gotten used to with IMAP
groups.  Before setting `(display . all)', I tended to flag all my
messages, which kinda defeats the usefulness of that feature.  It
also pissed off others using the same shared folders as me.  ;-)

kg> Or hit `9 9 =' or `1 1 1 =' which is easy to do, at least on a US
kg> kbd.  But `1 1 1 RET' should be easy on all keyboards.

Yeah, but I was pondering something perhaps a bit more streamlined.
As an experiment, I came up with the following cheesy hack.  I
suspect there's probably a better way already available in gnus, or
maybe I ought to be better at adapting my mail management.  Anyway,
here it is such as it is....

-- 
Amos


[-- Attachment #2: gnus.el._diff --]
[-- Type: text/plain, Size: 855 bytes --]

*** gnus.el._orig	Sun Aug  5 11:57:34 2001
--- gnus.el	Sun Aug  5 12:11:43 2001
***************
*** 1229,1234 ****
--- 1229,1243 ----
    :group 'gnus-group-select
    :type 'integer)
  
+ (defcustom gnus-limit-to-x-articles nil 
+   "*The maximum number of articles to display by default.  If the number
+ number of articles in the group is less than this value, then just those
+ articles will be displayed.  May override by manually specifying number
+ of articles to display.  This may be useful if you utilize the group
+ parameter `(display . all)'."
+   :group 'gnus-group-select 
+   :type 'integer) 
+  
  (defcustom gnus-use-long-file-name (not (memq system-type '(usg-unix-v xenix)))
    "*Non-nil means that the default name of a file to save articles in is the group name.
  If it's nil, the directory form of the group name is used instead.

[-- Attachment #3: gnus-sum._diff --]
[-- Type: text/plain, Size: 521 bytes --]

*** gnus-sum.el._orig	Sun Aug  5 11:37:37 2001
--- gnus-sum.el	Sun Aug  5 12:09:12 2001
***************
*** 4611,4616 ****
--- 4611,4620 ----
  	   (t
  	    (condition-case ()
  		(cond
+                  ((numberp gnus-limit-to-x-articles)
+                   (if (> number gnus-limit-to-x-articles)
+                       gnus-limit-to-x-articles
+                     number))
  		 ((and (or (<= scored marked) (= scored number))
  		       (numberp gnus-large-newsgroup)
  		       (> number gnus-large-newsgroup))

  reply	other threads:[~2001-08-05 17:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-31  9:01 Katsumi Yamaoka
2001-07-31 11:07 ` Kai Großjohann
2001-07-31 12:28   ` Katsumi Yamaoka
2001-07-31 13:53     ` Kai Großjohann
2001-07-31 17:30       ` Amos Gouaux
2001-07-31 17:51         ` Kai Großjohann
2001-08-05 17:34           ` Amos Gouaux [this message]
2001-08-05 20:04             ` Kai Großjohann
2001-08-05 20:56               ` Amos Gouaux
2001-08-05 21:35                 ` Kai Großjohann
2001-07-31 22:45       ` Katsumi Yamaoka
2001-08-01  0:53         ` ShengHuo ZHU
2001-08-01  8:43         ` Didier Verna
2001-08-01  9:55         ` Kai Großjohann
2001-08-01 10:18           ` Katsumi Yamaoka
2001-08-01 11:04             ` Kai Großjohann
2001-08-01 11:38               ` Katsumi Yamaoka
2001-08-02 10:59                 ` Katsumi Yamaoka
2001-08-03  4:57                   ` ShengHuo ZHU
2001-08-03  7:03                     ` Katsumi Yamaoka

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=q6mhevmpg0p.fsf@spartacus.utdallas.edu \
    --to=amos+lists.ding@utdallas.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).