/o unexpected behaviour

/o unexpected behaviour

[Max Froumentin]

When I'm in an nnfolder group summary (which displays unread
and !-marked articles) I often want to see the expired articles too.

What I found that sort of does it is /o
(gnus-summary-insert-old-articles). This works fine except in folders
that are marked as never expirable, where /o just adds a bunch of old
messages to the summary. Subsequent /o add older messages and so on
until the summary stops growing (while still not displaying all the
old articles).

Bug?

Max.

New nnml groups not shown in *Groups*, `j' shows them as Killed?

[Chris Shenton]

My .gnus.el file uses nnmail-split-methods to put mail in different
groups, but when mail starts populating a new group, the group name
doesn't show up in the *Groups* buffer.

Likewise if I move a tree of old mail under my existing tree, the new
dirs are not shown in *Groups*.

If I use `j' (gnus-group-jump-to-group) and type in the group name,
per the split or dir respectively, the group appears but with a `K'
flag indicating it is killed. The phantom groups appear in my
.newsrc.eld file in gnus-killed-list. I don't understand why it was
created killed and therefore invisible. They stay invisible even after
doing an nnml-generate-nov-databases, which I tried in desperation.

Can someone enlighten me how to force new nnml groups to be visible?
Or let me know what I'm doing wrong?  Here's the relevant part of my
.gnus.el file.  I don't have a local news server, so I just specify
the secondary select method for mail.  Thanks!

(setq
 gnus-secondary-select-methods '((nnml ""))
 mail-source-delete-incoming t		;remove Mail/Incoming* files 5.8.7 bug
 mail-sources '((maildir	:plugged	t) ; qmail ~/Maildir/ default
		(file		:path		"/home/chris/Mailbox"
				:plugged	t) ; qmail mbox (NOT maildir)
		(file		:path		"/home/chris/Mailbox-tmdabounce"
				:plugged	t) ; qmail mbox (NOT maildir)
		(directory	:path		"/home/chris/newsfish/"
				:suffix		""
				:plugged	t)
		)
 gnus-subscribe-newsgroup-method 'gnus-subscribe-randomly ; top insert
 gnus-auto-select-first nil             ; don't show first message until I say
 gnus-show-mime t                       ; all the time / manually request
 gnus-strict-mime t                     ; only with Mime-Version?
 gnus-view-pseudo-asynchronously t      ; don't make Gnus wait
 gnus-view-pseudos 'not-confirm		; no summary buffer insert; 'automatic
 gnus-view-pseudos-separately t         ; create pseudo articles for viewing
 bbdb/gnus-summary-mark-known-posters t ;can't make work??
 gnus-score-find-score-files-function '(gnus-score-find-bnews bbdb/gnus-score)
 nnmail-use-long-file-names nil	;hierarchies
 nnmail-expiry-wait 7		;days; see group param total-expire
 user-mail-address "chris@shenton.org"	; hide thanatos -- sets Sender:!!
 message-send-mail-function 'message-send-mail-with-qmail
 message-dont-reply-to-names "chris@shenton\\.org\\|cshenton@uucom\\.com"
 mm-discouraged-alternatives '("text/html" "text/richtext")
)

Re: New nnml groups not shown in *Groups*, `j' shows them as Killed?

[Josh Huber]

Chris Shenton <chris@shenton.org> writes:

[snip]

try setting gnus-subscribe-options-newsgroup-method to something
else...

Look at the documentation for gnus-auto-subscribed-groups:

*All new groups that match this regexp will be subscribed automatically.
Note that this variable only deals with new groups.  It has no effect
whatsoever on old groups.

New groups that match this regexp will not be handled by
`gnus-subscribe-newsgroup-method'.  Instead, they will
be subscribed using `gnus-subscribe-options-newsgroup-method'.

In particular, the final sentence is important!

ttyl,

-- 
Josh Huber

Re: New nnml groups not shown in *Groups*, `j' shows them as Killed?

[Chris Shenton]

Josh Huber <huber@alum.wpi.edu> writes:

> try setting gnus-subscribe-options-newsgroup-method to something
> else...
> 
> Look at the documentation for gnus-auto-subscribed-groups:

It looks like it should get my nnml groups:

  gnus-auto-subscribed-groups's value is 
  "nnml\\|^nnfolder\\|^nnmbox\\|^nnmh\\|^nnbabyl"


> New groups that match this regexp will not be handled by
> `gnus-subscribe-newsgroup-method'.  Instead, they will
> be subscribed using `gnus-subscribe-options-newsgroup-method'.

And it looks like it should subscribe in alpha order:

  gnus-subscribe-options-newsgroup-method's value is 
  gnus-subscribe-alphabetically


Perhaps it is, but these groups have Killed status so I'd never see
them, whether auto-subscribed alpha, or any other way. It's as if it's
instead set to gnus-subscribe-killed.  I'll try setting it to
gnus-subscribe-hierarchically.

In the mean time, is there a convenient way to unkill all my new and
killed nnml groups so I can see them, short of using `j' to get into
them over and over?

Thanks.

Re: New nnml groups not shown in *Groups*, `j' shows them as Killed?

[Kai Großjohann]

Chris Shenton <chris@shenton.org> writes:

> In the mean time, is there a convenient way to unkill all my new and
> killed nnml groups so I can see them, short of using `j' to get into
> them over and over?

Use "A k" to get a list of killed groups, then "u" on the ones you
want to subscribe.

kai
-- 
~/.signature is: umop 3p!sdn    (Frank Nobis)

Re: New nnml groups not shown in *Groups*, `j' shows them as Killed?

[Josh Huber]

Chris Shenton <chris@shenton.org> writes:

> And it looks like it should subscribe in alpha order:
>
>   gnus-subscribe-options-newsgroup-method's value is 
>   gnus-subscribe-alphabetically

Yes, it looks that way, doesn't it? :)

Personally, I'd edebug gnus-subscribe-alphabetically and see what's
going on...

I use topic subscription, which works fine for me.

> In the mean time, is there a convenient way to unkill all my new and
> killed nnml groups so I can see them, short of using `j' to get into
> them over and over?

There may be a better way, but one way would be something like:

list all killed groups (S k)
mark the ones you want to subscribe (using #)
subscribe them all at once (M-& u)

that should work.

-- 
Josh Huber

Re: /o unexpected behaviour

[ShengHuo ZHU]

Max Froumentin <mf@w3.org> writes:

> When I'm in an nnfolder group summary (which displays unread
> and !-marked articles) I often want to see the expired articles too.
>
> What I found that sort of does it is /o
> (gnus-summary-insert-old-articles). This works fine except in folders
> that are marked as never expirable, where /o just adds a bunch of old
> messages to the summary. Subsequent /o add older messages and so on
> until the summary stops growing (while still not displaying all the
> old articles).

What kind of old articles are not displayed?  I just make some changes
in gnus-summary-insert-old-articles. Could you try the latest CVS
version?  Maybe the bug has been fixed.

ShengHuo

Re: /o unexpected behaviour

[Max Froumentin]

ShengHuo ZHU <zsh@cs.rochester.edu> writes:

> What kind of old articles are not displayed?  I just make some changes
> in gnus-summary-insert-old-articles. Could you try the latest CVS
> version?  Maybe the bug has been fixed.

It's hard to tell, especially as I noticed that in some circumstances
it does display all the articles at the first /o. I'll investigate
further.

Max.