Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: upgrade notes
Date: Fri, 04 Feb 2011 09:42:21 -0800	[thread overview]
Message-ID: <87hbcj8znm.fsf@gnus.org> (raw)
In-Reply-To: <sdzkqb1zio.fsf@wjh.hardakers.net>

Wes Hardaker <wes@hardakers.net> writes:

> Well, you could do things like use empty variables and empty files to
> ensure that existing config at least loads even if the contents no
> longer work (and the imap-shell-variable would have a "obsolete"
> variable in the variable document text).

Yes...  reintroducing the imap-shell-variable as an obsolete variable
would make sense, but in my experience having non-used variables around
just confuses people even more.  But erroring out when starting up
certainly isn't nice, either.

>   gpg.el:
>     (error "The gpg.el file is no longer needed; please stop requiring
>     it.  In 2020 this file will be removed permanently")

I don't know what happened to gpg.el, exactly.  Anybody?

Anyway, we've removed a bazillion files (for some values of bazillion)
from Gnus in this cycle, which I think is the right thing to do.  People
shouldn't require files in that way.  :-)

>>> + My folders no longer show which folders have new messages in them.
>
> [btw, I meant the % mark in the group buffer; I may not have made that
> clear]

Oh, right.  Otherwise everything is OK?  It's showing the correct number
of messages and everything?

The % mark is something that I must admit I can't recall ever hearing
about, even though "git blame" claims that I added it in 1998.  So it's
supposed to appear on groups that have new mail after you do a `g'?
That sounds quite useful, actually.  :-)

Let's see...

Hm, it just looks up stuff in `nnmail-split-history', and that variable
is only filled when we're doing client-side splits, which explains why
it's never triggering for you.  Since you're not doing client-side
splits.  I wonder what the old nnimap did...

Ah:

		(when (> (or (imap-mailbox-get 'recent group
					       nnimap-server-buffer) 0)
			 0)
		  (push (list (cons group 0)) nnmail-split-history))

Whenever there's any messages marked as `recent' (which is the same as
unseen, in Gnus parlance), then it just pushes a dummy thing that
matches onto nnmail-split-history.

This is totally different from what other mail backends do -- the % mark
will only show up on groups that had new messages *this* `g', and not
show up on all groups that have unseen messages.

Is this correct?  The `%' would stay there over several `g' runs?  I may
be misreading the code.

The ?U spec shows the number of unseen messages.

So I don't know what the right fix here would be.

1) Ignore the issue.  "% is for client-side splits"

2) Have nnimap follow the semantics for the other mail backends, and add
a dummy thing to nnmail-split-history if a `g' registers new messages.
Simple enough to do.

3) Add a new ?W spec (or something) that would just show a "%" on all
groups with unseen messages.
                  
-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen




  reply	other threads:[~2011-02-04 17:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04 16:31 Wes Hardaker
2011-02-04 17:04 ` Lars Ingebrigtsen
2011-02-04 17:27   ` Wes Hardaker
2011-02-04 17:42     ` Lars Ingebrigtsen [this message]
2011-02-04 20:29       ` Wes Hardaker
2011-02-07 10:25         ` Lars Ingebrigtsen
2011-02-07 16:43           ` Wes Hardaker
2011-02-07 18:37             ` Wes Hardaker
2011-02-07 20:42               ` Eric S Fraga
2011-02-07 21:12                 ` Wes Hardaker
2011-02-06 18:29       ` Reiner Steib
2011-02-07  9:58         ` Lars Ingebrigtsen
2011-02-05 17:07 ` Steinar Bang
2011-02-07 16:45   ` Wes Hardaker

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=87hbcj8znm.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=ding@gnus.org \
    /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).