Gnus development mailing list
 help / color / mirror / Atom feed
From: nyc4bos@aol.com
To: ding@gnus.org
Subject: Re: Cannot subscribe or see nndrafts folder upon startup
Date: Sat, 02 Jul 2011 14:58:16 -0400	[thread overview]
Message-ID: <yriaacwik6v.fsf@aol.com> (raw)
In-Reply-To: <b4mmxgy8f3a.fsf@jpl.org>

Katsumi Yamaoka <yamaoka@jpl.org> writes:

> Katsumi Yamaoka wrote:
>> Katsumi Yamaoka wrote:
>>> Lars Magne Ingebrigtsen wrote:
>>>> However, the drafts group could update itself when you delete a message
>>>> from it, for instance.  That would only be slightly inconsistent.
>
> [...]
>>> I've installed a fix.
>
>> Er, the fix was incomplete.  It doesn't work properly if there're
>> sparse draft messages.
> [...]
>
> I found the easiest way to fix it.  Installed.
>
> Lars Magne Ingebrigtsen wrote:
>> The drafts group doesn't update until you hit `g', like other normal
>> groups.  It's somewhat difficult to have the group buffer update itself
>> when a message lands in the draft buffer -- it lands there by you just
>> saving the message you're composing.  And I don't want any Gnus stuff to
>> run off of `save-buffer-hook' or the like.
>
> I tried this.  A patch is below.  Not tested fully, though.

I tried this patch (below).

I still have the original problem (nndraft:drafts group not listed
in *Group* buffer when starting Gnus).

Is that problem fixed (and waiting to be synced into bzr Gnus)?

Thanks.


>
>
> --- nndraft.el~	2011-04-05 05:00:10.178750000 +0000
> +++ nndraft.el	2011-07-01 10:31:26.218750000 +0000
> @@ -161,6 +161,13 @@
>       (message-headers-to-generate
>        nndraft-required-headers message-draft-headers nil))))
>  
> +(defun nndraft-update-unread-articles (group)
> +  "Return a function that updates unread articles of GROUP."
> +  `(lambda nil
> +     (with-current-buffer gnus-group-buffer
> +       (let ((gnus-group-marked (list ,(concat "nndraft:" group))))
> +	 (gnus-group-get-new-news-this-group nil t)))))
> +
>  (deffoo nndraft-request-associate-buffer (group)
>    "Associate the current buffer with some article in the draft group."
>    (nndraft-open-server "")
> @@ -182,6 +189,10 @@
>  		  'write-contents-hooks)))
>        (gnus-make-local-hook hook)
>        (add-hook hook 'nndraft-generate-headers nil t))
> +    (let ((fn (nndraft-update-unread-articles group)))
> +      (gnus-make-local-hook 'after-save-hook)
> +      (add-hook 'after-save-hook fn nil t)
> +      (message-add-action (caddr fn) 'exit 'postpone 'kill))
>      article))
>  
>  (deffoo nndraft-request-group (group &optional server dont-check info)




  reply	other threads:[~2011-07-02 18:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-13 23:27 nyc4bos
2011-06-26  9:41 ` Lars Magne Ingebrigtsen
2011-06-27 22:36   ` nyc4bos
2011-06-28  0:12     ` Katsumi Yamaoka
2011-06-29 11:27       ` Katsumi Yamaoka
2011-06-30  1:25         ` Katsumi Yamaoka
2011-06-30  2:26           ` Lars Magne Ingebrigtsen
2011-06-30 10:43             ` Richard Riley
2011-06-30 17:02               ` Lars Magne Ingebrigtsen
2011-07-01  4:06                 ` Katsumi Yamaoka
2011-07-01  6:34                   ` Katsumi Yamaoka
2011-07-01 10:34                     ` Katsumi Yamaoka
2011-07-02 18:58                       ` nyc4bos [this message]
2011-07-03 23:23                         ` Katsumi Yamaoka
2011-07-04  1:14                           ` Katsumi Yamaoka
2011-07-06 23:26                             ` nyc4bos
2011-07-02 18:51           ` nyc4bos

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=yriaacwik6v.fsf@aol.com \
    --to=nyc4bos@aol.com \
    --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).