Gnus development mailing list
 help / color / mirror / Atom feed
From: Wes Hardaker <wes@hardakers.net>
To: ding@gnus.org
Subject: Re: upgrade notes
Date: Fri, 04 Feb 2011 09:27:11 -0800	[thread overview]
Message-ID: <sdzkqb1zio.fsf@wjh.hardakers.net> (raw)
In-Reply-To: <87y65v91ef.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 04 Feb 2011 09:04:40 -0800")

>>>>> On Fri, 04 Feb 2011 09:04:40 -0800, Lars Ingebrigtsen <larsi@gnus.org> said:

>> + I had (require 'gpg) in my config which I had to remove
>> 
>> + I had an imap-shell-variable that had been customized that pushed a
>> 'ssh ... exec imapd' onto the stack.  I don't remember why I had that
>> set up and don't need it any longer, but because the variable no
>> longer existed it broke my config loading.

LI> I'm not sure those can be helped...

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).

But I'm not saying you need to do this, just offering suggestions.   I
work on a very very backwards compatible project elsewhere so these are
the types of things we try and do.

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

>> + 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]

>> [splitting is done via procmail on the server, and I know the new
>> marks exist there since my running qmailcheck biff window displays
>> properly "new" flagged messages, as did the older gnus version]

LI> That's interesting.  Could you post output from `G E' on one of the
LI> non-updating groups?  And then try `M-g' on the group, and then the `G
LI> E' output again?

Ok, here's a G E on one of my smaller folders (otherwise this message
was going to get very long!)

  ("nnimap+hardakers:imap.captured-on-earth" 3
   ((1 . 19)
    (22 . 33)
    (35 . 37)
    (40 . 49)
    (51 . 57)
    (59 . 81)
    (84 . 88)
    (90 . 155)
    (157 . 158)
    163)
   ((reply 20 62)
    (seen
     (1 . 120)
     (123 . 144)
     (149 . 163))
    (recent 163))
   "nnimap:hardakers"
   ((modseq . 366)
    (uidvalidity . "1228402789")
    (active 2 . 163)
    (permanent-flags %Answered %Flagged %Deleted %Seen %Draft gnus-expire gnus-forward %*)
    (imap-status . "164 2 163")))

After sending mail that arrived in the folder and updating via '3 g', it
shows:

  ("nnimap+hardakers:imap.captured-on-earth" 3
   ((1 . 19)
    (22 . 33)
    (35 . 37)
    (40 . 49)
    (51 . 57)
    (59 . 81)
    (84 . 88)
    (90 . 155)
    (157 . 158)
    163)
   ((reply 20 62)
    (seen
     (1 . 120)
     (123 . 144)
     (149 . 163))
    (recent 163))
   "nnimap:hardakers"
   ((modseq . 367)
    (uidvalidity . "1228402789")
    (active 2 . 164)
    (permanent-flags %Answered %Flagged %Deleted %Seen %Draft gnus-expire gnus-forward %*)
    (imap-status . "164 2 163")))

Which shows this via diff:

        (149 . 163))
       (recent 163))
      "nnimap:hardakers"
  -   ((modseq . 367)
  +   ((modseq . 366)
       (uidvalidity . "1228402789")
  -    (active 2 . 164)
  +    (active 2 . 163)
       (permanent-flags %Answered %Flagged %Deleted %Seen %Draft gnus-expire gnus-forward %*)
       (imap-status . "164 2 163")))

But the group buffer still doesn't have the % mark.

After a M-g on it:

  [content deleted as it's unchanged from the last set]

After a new message sent, and another '3 g':

  ("nnimap+hardakers:imap.captured-on-earth" 3
   ((1 . 19)
    (22 . 33)
    (35 . 37)
    (40 . 49)
    (51 . 57)
    (59 . 81)
    (84 . 88)
    (90 . 155)
    (157 . 158)
    163)
   ((reply 20 62)
    (seen
     (1 . 120)
     (123 . 144)
     (149 . 163))
    (recent 163))
   "nnimap:hardakers"
   ((modseq . 368)
    (uidvalidity . "1228402789")
    (active 2 . 165)
    (permanent-flags %Answered %Flagged %Deleted %Seen %Draft gnus-expire gnus-forward %*)
    (imap-status . "164 2 163")))

(which again updated the modseq and the active)

Important settings:

  (setq  gnus-group-topic-topics-only t
         gnus-topic-line-format "%i[ %(%{%n%}%) -- %g ]%v\n"

My gnus-group-line-format is unmodified and contains:

  "%L%m%S%P%5y: %(%-30G%) %6,6~(cut 2)d\n"

So it's the %m that doesn't seem to be working.
-- 
Wes Hardaker                                     
My Pictures:  http://capturedonearth.com/
My Thoughts:  http://pontifications.hardakers.net/



  reply	other threads:[~2011-02-04 17:27 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 [this message]
2011-02-04 17:42     ` Lars Ingebrigtsen
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=sdzkqb1zio.fsf@wjh.hardakers.net \
    --to=wes@hardakers.net \
    --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).