Re: Sent message still in drafts (lisp error: "Selecting deleted buffer")

Re: Sent message still in drafts (lisp error: "Selecting deleted buffer")

[Katsumi Yamaoka]

Felix Natter wrote:
> Debugger entered--Lisp error: (error "Selecting deleted buffer")
>   nnml-add-nov("expired" 12197 [nil "Rheinblick-Cache" "Felix Natter <fnat...
>   nnml-save-mail((("expired" . 12197)) "")
>   nnml-request-accept-article("expired" "" nil)

I'm unable to reproduce such an error.  Could you get a backtrace
again by loading nnml.el (or nnml.el.gz, not .elc) in advance?
I.e.:  M-x load-library RET nnml.el RET, and do mail.

Re: Sent message still in drafts (lisp error: "Selecting deleted buffer")

[Felix Natter]

Katsumi Yamaoka <yamaoka@jpl.org> writes:

hi Katsumi,

sorry that it took me so long!

> Felix Natter wrote:
>> Debugger entered--Lisp error: (error "Selecting deleted buffer")
>>   nnml-add-nov("expired" 12197 [nil "Rheinblick-Cache" "Felix Natter <fnat...
>>   nnml-save-mail((("expired" . 12197)) "")
>>   nnml-request-accept-article("expired" "" nil)
>
> I'm unable to reproduce such an error.  Could you get a backtrace
> again by loading nnml.el (or nnml.el.gz, not .elc) in advance?
> I.e.:  M-x load-library RET nnml.el RET, and do mail.

Here it is, with (setq debug-on-error t) and M-x load-library nnml.el:

Debugger entered--Lisp error: (error "Selecting deleted buffer")
  set-buffer(#<killed buffer>)
  (save-excursion (set-buffer (nnml-open-nov group)) (goto-char (point-max)) (mail-header-set-number headers article) (nnheader-insert-nov headers))
  nnml-add-nov("expired" 13982 [nil "Re: Freeplane man page" "Felix Natter <fnatter@gmx.net>" "Mon, 25 Mar 2013 21:28:16 +0100" "<87fvzjb4u3.fsf@totally-fudged-out-message-id>" "<87wqsxc1i1.fsf@bitburger.home.felix> <17253.15.195.185.81.1364221728.squirrel@my.bawue.net>" 762 28 "bitburger.home.felix expired:13982" ((To . "\"Eric Lavarde - Debian\" <deb@zorglub.s.bawue.de>"))])
  (while --cl-dolist-temp-- (setq ga (car --cl-dolist-temp--)) (nnml-add-nov (car ga) (cdr ga) headers) (setq --cl-dolist-temp-- (cdr --cl-dolist-temp--)))
  (let ((--cl-dolist-temp-- group-art) ga) (while --cl-dolist-temp-- (setq ga ...) (nnml-add-nov ... ... headers) (setq --cl-dolist-temp-- ...)) nil)
  (catch (quote --cl-block-nil--) (let (... ga) (while --cl-dolist-temp-- ... ... ...) nil))
  (cl-block-wrapper (catch (quote --cl-block-nil--) (let ... ... nil)))
  (block nil (let (... ga) (while --cl-dolist-temp-- ... ... ...) nil))
  (dolist (ga group-art) (nnml-add-nov (car ga) (cdr ga) headers))
  (if nnmail-group-names-not-encoded-p (dolist (ga group-art) (nnml-add-nov ... ... headers)) (dolist (ga group-art) (nnml-add-nov ... ... headers)))
  (let* ((chars ...) (extension ...) decoded dec file first headers) (when nnmail-group-names-not-encoded-p (dolist ... ...) (setq dec decoded)) (nnmail-insert-xref group-art) (run-hooks (quote nnmail-prepare-save-mail-hook)) (run-hooks (quote nnml-prepare-save-mail-hook)) (goto-char (point-min)) (while (looking-at "From ") (replace-match "X-From-Line: ") (forward-line 1)) (dolist (ga group-art) (if nnmail-group-names-not-encoded-p ... ... ...) (if first ... ... ...)) (setq headers (nnml-parse-head chars)) (if nnmail-group-names-not-encoded-p (dolist ... ...) (dolist ... ...)))
  nnml-save-mail((("expired" . 13982)) "")
  (car (nnml-save-mail (list ...) server))
  (setq result (car (nnml-save-mail ... server)))
  (and (nnmail-activate (quote nnml)) (setq result (car ...)) (progn (nnmail-save-active nnml-group-alist nnml-active-file) (and last ...)))
  (if (stringp group) (and (nnmail-activate ...) (setq result ...) (progn ... ...)) (and (nnmail-activate ...) (if ... ... ...) (when last ... ... ...)))
  (let (result) (when nnmail-cache-accepted-message-ids (nnmail-cache-insert ... group ... ...)) (if (stringp group) (and ... ... ...) (and ... ... ...)) result)
  nnml-request-accept-article("expired" "" nil)
  gnus-request-accept-article("nnml:expired" nil nil t)
  nnmail-expiry-target-group("nnml:expired" "drafts")
  nnmh-request-expire-articles((140) "drafts" nil t)
  apply(nnmh-request-expire-articles ((140) "drafts" nil t))
  nnoo-parent-function(nndraft nnmh-request-expire-articles ((140) "drafts" nil t))
  nndraft-request-expire-articles((140) "drafts" nil t)
  message-disassociate-draft()
  message-send(nil)
  message-send-and-exit(nil)
  call-interactively(message-send-and-exit nil nil)

Thank you very much!
-- 
Felix Natter

Re: Sent message still in drafts (lisp error: "Selecting deleted buffer")

[Katsumi Yamaoka]

Felix Natter wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:

> hi Katsumi,

> sorry that it took me so long!

>> Felix Natter wrote:
>>> Debugger entered--Lisp error: (error "Selecting deleted buffer")
>>>   nnml-add-nov("expired" 12197 [nil "Rheinblick-Cache" "Felix Natter <fnat...
>>>   nnml-save-mail((("expired" . 12197)) "")
>>>   nnml-request-accept-article("expired" "" nil)
>>
>> I'm unable to reproduce such an error.  Could you get a backtrace
>> again by loading nnml.el (or nnml.el.gz, not .elc) in advance?
>> I.e.:  M-x load-library RET nnml.el RET, and do mail.

> Here it is, with (setq debug-on-error t) and M-x load-library nnml.el:

Thanks.  Though I haven't found the cause of the error in question
yet, I found some other problems on expiring sent drafts to a group.
The principal one is that a draft is not like a normal article:

・There is a separator between the header and the body.
  - You can't read its body in an expiry group.
  - Xref herder, etc. are put at the end of the body.
・Non-ASCII text has not been encoded properly.
・Attachments do not necessarily exist when re-using it.

It will cost to improve it.  Er, archiving sent drafts in an expiry
group is not the purpose of

(setq nnmail-expiry-target "nnml:expired")

you set, isn't it?  If so, how about setting a group parameter so
that only sent drafts are deleted?  To do that:

・In the Group buffer, type `G c' on the "nndraft:drafts" group
  to open the customization buffer.
・Find the "Expiry Target" entry, check the box, and make sure
  the value is `delete'.
・Press the [done] button at the beginning of the buffer.
・Type `s' to save the customization in the ~/.newsrc.eld file.

_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

Re: Sent message still in drafts (lisp error: "Selecting deleted buffer")

[Felix Natter]

Katsumi Yamaoka <yamaoka@jpl.org> writes:

> Felix Natter wrote:
>> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>
>> hi Katsumi,
>
>> sorry that it took me so long!
>
>>> Felix Natter wrote:
>>>> Debugger entered--Lisp error: (error "Selecting deleted buffer")
>>>>   nnml-add-nov("expired" 12197 [nil "Rheinblick-Cache" "Felix Natter <fnat...
>>>>   nnml-save-mail((("expired" . 12197)) "")
>>>>   nnml-request-accept-article("expired" "" nil)
>>>
>>> I'm unable to reproduce such an error.  Could you get a backtrace
>>> again by loading nnml.el (or nnml.el.gz, not .elc) in advance?
>>> I.e.:  M-x load-library RET nnml.el RET, and do mail.
>
>> Here it is, with (setq debug-on-error t) and M-x load-library
>> nnml.el:

hello Katsumi,

> Thanks.  Though I haven't found the cause of the error in question
> yet, I found some other problems on expiring sent drafts to a group.
>
> The principal one is that a draft is not like a normal article:
>
> ・There is a separator between the header and the body.
>   - You can't read its body in an expiry group.
>   - Xref herder, etc. are put at the end of the body.
> ・Non-ASCII text has not been encoded properly.
> ・Attachments do not necessarily exist when re-using it.

So the problem is that when I send a draft, its content is subject
to expiry, and this does not work because a draft is not like
a normal article (and with the "G c" below we tell Gnus to delete
and not expire sent drafts)?

> It will cost to improve it. 

What do you mean by "costs to improve it"?

> Er, archiving sent drafts in an expiry
> group is not the purpose of
>
> (setq nnmail-expiry-target "nnml:expired")

Yes, I am doing that:

(setq nnmail-expiry-target "nnml:expired")

> you set, isn't it?  If so, how about setting a group parameter so
> that only sent drafts are deleted?  To do that:
>
> ・In the Group buffer, type `G c' on the "nndraft:drafts" group
>   to open the customization buffer.
> ・Find the "Expiry Target" entry, check the box, and make sure
>   the value is `delete'.
> ・Press the [done] button at the beginning of the buffer.
> ・Type `s' to save the customization in the ~/.newsrc.eld file.

Thank you, that looks good, I'll try that!

If that works, then I think it's a good idea to mention this problem
in the Gnus documentation?

Many thanks again and Best Regards,
-- 
Felix Natter

_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

Re: Sent message still in drafts (lisp error: "Selecting deleted buffer")

[Katsumi Yamaoka]

Felix Natter <fnatter@gmx.net> wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
[...]
>> I found some other problems on expiring sent drafts to a group.
>> The principal one is that a draft is not like a normal article:
>>
>> ・There is a separator between the header and the body.
>>   - You can't read its body in an expiry group.
>>   - Xref herder, etc. are put at the end of the body.
>> ・Non-ASCII text has not been encoded properly.
>> ・Attachments do not necessarily exist when re-using it.

> So the problem is that when I send a draft, its content is subject
> to expiry, and this does not work because a draft is not like
> a normal article (and with the "G c" below we tell Gnus to delete
> and not expire sent drafts)?

Maybe that a draft is not a normal article is not a direct cause
of your problem.  Though I haven't yet investigated why sometimes
it fails with the message "Selecting deleted buffer".

>> It will cost to improve it.

> What do you mean by "costs to improve it"?

Sorry for my funny English.  I meant that it will take time (IOW,
cost me time ;-) to improve the Lisp code so as to transform
a draft message, that is copied or moved to a normal group, to
a normal article.

[...]
> Yes, I am doing that:
> (setq nnmail-expiry-target "nnml:expired")
[...]
>> how about setting a group parameter so that only sent drafts
>> are deleted?
[...]
> If that works, then I think it's a good idea to mention this problem
> in the Gnus documentation?

I have another idea.  That is to make the behavior of expiring of
drafts be always `delete' no matter what nnmail-expiry-target is.
It lets you and friends have no need to have such a special group
parameter.  Ones who want to have a local copy of a sent message
can use Gcc, that saves it as a normal article.  WDYT?

Re: Sent message still in drafts (lisp error: "Selecting deleted buffer")

[Felix Natter]

Katsumi Yamaoka <yamaoka@jpl.org> writes:

hi Katsumi,

> Felix Natter <fnatter@gmx.net> wrote:
>> Katsumi Yamaoka <yamaoka@jpl.org> writes:
> [...]
>>> I found some other problems on expiring sent drafts to a group.
>>> The principal one is that a draft is not like a normal article:
>>>
>>> ・There is a separator between the header and the body.
>>>   - You can't read its body in an expiry group.
>>>   - Xref herder, etc. are put at the end of the body.
>>> ・Non-ASCII text has not been encoded properly.
>>> ・Attachments do not necessarily exist when re-using it.
>
>> So the problem is that when I send a draft, its content is subject
>> to expiry, and this does not work because a draft is not like
>> a normal article (and with the "G c" below we tell Gnus to delete
>> and not expire sent drafts)?
>
> Maybe that a draft is not a normal article is not a direct cause
> of your problem.  Though I haven't yet investigated why sometimes
> it fails with the message "Selecting deleted buffer".
>
>>> It will cost to improve it.
>
>> What do you mean by "costs to improve it"?
>
> Sorry for my funny English.  I meant that it will take time (IOW,
> cost me time ;-) to improve the Lisp code so as to transform
> a draft message, that is copied or moved to a normal group, to
> a normal article.

Ah ok ;-)

> [...]
>> Yes, I am doing that:
>> (setq nnmail-expiry-target "nnml:expired")
> [...]
>>> how about setting a group parameter so that only sent drafts
>>> are deleted?
> [...]
>> If that works, then I think it's a good idea to mention this problem
>> in the Gnus documentation?
>
> I have another idea.  That is to make the behavior of expiring of
> drafts be always `delete' no matter what nnmail-expiry-target is.
> It lets you and friends have no need to have such a special group
> parameter.  Ones who want to have a local copy of a sent message
> can use Gcc, that saves it as a normal article.  WDYT?

That's a really good idea, much better than just documenting a
workaround :-)

Thanks and Best Regards,
-- 
Felix Natter

_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

Expiring sent drafts does now always `delete'

[Katsumi Yamaoka]

Hi,

This might be a regression but I think it would trouble no one.
I made draft messages come to be deleted after being sent regardless
of the value of `nnmail-expiry-target'.  If it is `delete', that
is the default, the behavior is unchanged.  Before this change,
a sent draft was moved to an expiry group if `nnmail-expiry-target'
specifies it.  However, there were some problems with moved drafts:

1. A separator is left between the header and the body.  It causes
   the body of a moved draft to be unable to read.

   Even if one sets or binds `mail-header-separator' to "",

2. A message is in MML, not MIME.  I.e., non-ASCII text is as is,
   attachments are mere tags.
3. There seems to be an unresolved bug.

See also:
http://article.gmane.org/gmane.emacs.gnus.user/16110
http://article.gmane.org/gmane.emacs.gnus.user/16114
http://article.gmane.org/gmane.emacs.gnus.user/16160
http://article.gmane.org/gmane.emacs.gnus.user/16163
http://article.gmane.org/gmane.emacs.gnus.user/16164
http://article.gmane.org/gmane.emacs.gnus.user/16165
http://article.gmane.org/gmane.emacs.gnus.user/16166
(The thread is broken because info-gnus-english@gnu.org rewites
 Message-IDs. :<)

There are similar problems with draft messages that are copied
or moved to normal groups by `B c' or `B m'.  But IMHO, it's not
worth improving, since you can use Gcc or something if you want
to archive sent messages.

Regards,

Re: Sent message still in drafts (lisp error: "Selecting deleted buffer")

[Felix Natter]

hi Katsumi,

now I have another backtrace (debug-on-error=t, with M-x load-library
nnml.el) with the below fix in place:

Debugger entered--Lisp error: (error "Selecting deleted buffer")
  set-buffer(#<killed buffer>)
  (save-excursion (set-buffer (nnml-open-nov group)) (goto-char (point-max)) (mail-header-set-number headers article) (nnheader-insert-nov headers))
  nnml-add-nov("expired" 14148 [nil "Re: Freeplane Kommandozeilenoptionen" "Felix Natter <fnatter@gmx.net>" "Sun, 31 Mar 2013 20:10:31 +0200" "<877gkntp5e.fsf@totally-fudged-out-message-id>" "<87obe9dgi1.fsf@bitburger.home.felix> <514E1497.4040803@web.de> <514E58BF.5000106@web.de> <87sj3e3yz1.fsf@bitburger.home.felix> <51577FE4.1080704@web.de> <515781A5.20106@web.de>" 2393 72 "bitburger.home.felix expired:14148" ((To . "Volker B\303\266rchers <boercher@web.de>"))])
  (while --cl-dolist-temp-- (setq ga (car --cl-dolist-temp--)) (nnml-add-nov (car ga) (cdr ga) headers) (setq --cl-dolist-temp-- (cdr --cl-dolist-temp--)))
  (let ((--cl-dolist-temp-- group-art) ga) (while --cl-dolist-temp-- (setq ga ...) (nnml-add-nov ... ... headers) (setq --cl-dolist-temp-- ...)) nil)
  (catch (quote --cl-block-nil--) (let (... ga) (while --cl-dolist-temp-- ... ... ...) nil))
  (cl-block-wrapper (catch (quote --cl-block-nil--) (let ... ... nil)))
  (block nil (let (... ga) (while --cl-dolist-temp-- ... ... ...) nil))
  (dolist (ga group-art) (nnml-add-nov (car ga) (cdr ga) headers))
  (if nnmail-group-names-not-encoded-p (dolist (ga group-art) (nnml-add-nov ... ... headers)) (dolist (ga group-art) (nnml-add-nov ... ... headers)))
  (let* ((chars ...) (extension ...) decoded dec file first headers) (when nnmail-group-names-not-encoded-p (dolist ... ...) (setq dec decoded)) (nnmail-insert-xref group-art) (run-hooks (quote nnmail-prepare-save-mail-hook)) (run-hooks (quote nnml-prepare-save-mail-hook)) (goto-char (point-min)) (while (looking-at "From ") (replace-match "X-From-Line: ") (forward-line 1)) (dolist (ga group-art) (if nnmail-group-names-not-encoded-p ... ... ...) (if first ... ... ...)) (setq headers (nnml-parse-head chars)) (if nnmail-group-names-not-encoded-p (dolist ... ...) (dolist ... ...)))
  nnml-save-mail((("expired" . 14148)) "")
  (car (nnml-save-mail (list ...) server))
  (setq result (car (nnml-save-mail ... server)))
  (and (nnmail-activate (quote nnml)) (setq result (car ...)) (progn (nnmail-save-active nnml-group-alist nnml-active-file) (and last ...)))
  (if (stringp group) (and (nnmail-activate ...) (setq result ...) (progn ... ...)) (and (nnmail-activate ...) (if ... ... ...) (when last ... ... ...)))
  (let (result) (when nnmail-cache-accepted-message-ids (nnmail-cache-insert ... group ... ...)) (if (stringp group) (and ... ... ...) (and ... ... ...)) result)
  nnml-request-accept-article("expired" "" nil)
  gnus-request-accept-article("nnml:expired" nil nil t)
  nnmail-expiry-target-group("nnml:expired" "drafts")
  nnmh-request-expire-articles((145) "drafts" nil t)
  apply(nnmh-request-expire-articles ((145) "drafts" nil t))
  nnoo-parent-function(nndraft nnmh-request-expire-articles ((145) "drafts" nil t))
  nndraft-request-expire-articles((145) "drafts" nil t)
  message-disassociate-draft()
  message-send(nil)
  message-send-and-exit(nil)
  call-interactively(message-send-and-exit nil nil)

Please tell me if you need additional information.

Thank you very much!

Best Regards,
Felix

Katsumi Yamaoka <yamaoka@jpl.org> writes:
> Felix Natter <fnatter@gmx.net> wrote:
>> Katsumi Yamaoka <yamaoka@jpl.org> writes:
> [...]
>>> I found some other problems on expiring sent drafts to a group.
>>> The principal one is that a draft is not like a normal article:
>>>
>>> ・There is a separator between the header and the body.
>>>   - You can't read its body in an expiry group.
>>>   - Xref herder, etc. are put at the end of the body.
>>> ・Non-ASCII text has not been encoded properly.
>>> ・Attachments do not necessarily exist when re-using it.
>
>> So the problem is that when I send a draft, its content is subject
>> to expiry, and this does not work because a draft is not like
>> a normal article (and with the "G c" below we tell Gnus to delete
>> and not expire sent drafts)?
>
> Maybe that a draft is not a normal article is not a direct cause
> of your problem.  Though I haven't yet investigated why sometimes
> it fails with the message "Selecting deleted buffer".
>
>>> It will cost to improve it.
>
>> What do you mean by "costs to improve it"?
>
> Sorry for my funny English.  I meant that it will take time (IOW,
> cost me time ;-) to improve the Lisp code so as to transform
> a draft message, that is copied or moved to a normal group, to
> a normal article.
>
> [...]
>> Yes, I am doing that:
>> (setq nnmail-expiry-target "nnml:expired")
> [...]
>>> how about setting a group parameter so that only sent drafts
>>> are deleted?
> [...]
>> If that works, then I think it's a good idea to mention this problem
>> in the Gnus documentation?
>
> I have another idea.  That is to make the behavior of expiring of
> drafts be always `delete' no matter what nnmail-expiry-target is.
> It lets you and friends have no need to have such a special group
> parameter.  Ones who want to have a local copy of a sent message
> can use Gcc, that saves it as a normal article.  WDYT?
>

-- 
Felix Natter

_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

Re: Sent message still in drafts (lisp error: "Selecting deleted buffer")

[Katsumi Yamaoka]

Felix Natter <fnatter@gmx.net> wrote:
> now I have another backtrace (debug-on-error=t, with M-x load-library
> nnml.el) with the below fix in place:

> Debugger entered--Lisp error: (error "Selecting deleted buffer")
>   set-buffer(#<killed buffer>)
[...]
>   apply(nnmh-request-expire-articles ((145) "drafts" nil t))
>   nnoo-parent-function(nndraft nnmh-request-expire-articles ((145)
> "drafts" nil t))
>   nndraft-request-expire-articles((145) "drafts" nil t)
>   message-disassociate-draft()
>   message-send(nil)
>   message-send-and-exit(nil)
>   call-interactively(message-send-and-exit nil nil)
[...]

I see.  The recent change having aimed not to try to move a draft
to a group was insufficient.  I'm going to fix it, essentially if
possible.

Re: Sent message still in drafts (lisp error: "Selecting deleted buffer")

[Katsumi Yamaoka]

Oops, I seem to have misread the backtrace.  You aren't using
the most recent nndraft.el, are you?  In it, there should be
the FIXME comment in the 259th line.

Katsumi Yamaoka wrote:
> Felix Natter <fnatter@gmx.net> wrote:
>> now I have another backtrace (debug-on-error=t, with M-x load-library
>> nnml.el) with the below fix in place:

>> Debugger entered--Lisp error: (error "Selecting deleted buffer")
>>   set-buffer(#<killed buffer>)
> [...]
>>   apply(nnmh-request-expire-articles ((145) "drafts" nil t))
>>   nnoo-parent-function(nndraft nnmh-request-expire-articles ((145)
>> "drafts" nil t))
>>   nndraft-request-expire-articles((145) "drafts" nil t)
>>   message-disassociate-draft()
>>   message-send(nil)
>>   message-send-and-exit(nil)
>>   call-interactively(message-send-and-exit nil nil)
> [...]

> I see.  The recent change having aimed not to try to move a draft
> to a group was insufficient.  I'm going to fix it, essentially if
> possible.

Re: Sent message still in drafts (lisp error: "Selecting deleted buffer")

[Felix Natter]

Katsumi Yamaoka <yamaoka@jpl.org> writes:

hi Katsumi,

> Oops, I seem to have misread the backtrace.  You aren't using
> the most recent nndraft.el, are you?  In it, there should be
> the FIXME comment in the 259th line.

Correct, there is no FIXME on the 259th line of
/usr/share/emacs/23.4/lisp/gnus/nndraft.el.gz.

=> but I looked it up in git Gnus: Shouldn't the fix I applied manually
do the same:
---------------------------------------
How about setting a group parameter so
that only sent drafts are deleted?  To do that:

・In the Group buffer, type `G c' on the "nndraft:drafts" group
  to open the customization buffer.
・Find the "Expiry Target" entry, check the box, and make sure
  the value is `delete'.
・Press the [done] button at the beginning of the buffer.
・Type `s' to save the customization in the ~/.newsrc.eld file.
---------------------------------------

I am using Gnus v5.13 on GNU Emacs 23.4.1 (i486-pc-linux-gnu, GTK+
Version 2.24.10) of 2012-09-09 on murphy, modified by Debian.

If it is just that you want to read the backtrace: my elisp versions can
be browsed here:
  http://bzr.savannah.gnu.org/lh/emacs/emacs-23/annotate/head:/lisp/gnus/nndraft.el

Would it help to upgrade to GNU Emacs 24.2? On the other hand, I
installed Emacs24 on another machine and it also reports Gnus version
5.13.
(GNU Emacs 24.2 is in Debian unstable, that's why I'm afraid of upgrading
to it.)

Thanks and Best Regards,
Felix

> Katsumi Yamaoka wrote:
>> Felix Natter <fnatter@gmx.net> wrote:
>>> now I have another backtrace (debug-on-error=t, with M-x load-library
>>> nnml.el) with the below fix in place:
>
>>> Debugger entered--Lisp error: (error "Selecting deleted buffer")
>>>   set-buffer(#<killed buffer>)
>> [...]
>>>   apply(nnmh-request-expire-articles ((145) "drafts" nil t))
>>>   nnoo-parent-function(nndraft nnmh-request-expire-articles ((145)
>>> "drafts" nil t))
>>>   nndraft-request-expire-articles((145) "drafts" nil t)
>>>   message-disassociate-draft()
>>>   message-send(nil)
>>>   message-send-and-exit(nil)
>>>   call-interactively(message-send-and-exit nil nil)
>> [...]
>
>> I see.  The recent change having aimed not to try to move a draft
>> to a group was insufficient.  I'm going to fix it, essentially if
>> possible.
>

-- 
Felix Natter

_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

Re: Sent message still in drafts (lisp error: "Selecting deleted buffer")

[Katsumi Yamaoka]

Felix Natter <fnatter@gmx.net> wrote:
[...]
> Would it help to upgrade to GNU Emacs 24.2?

No, it doesn't.  The most recent nndraft.el is in the development
repositories, the Gnus Git master[1] and the Emacs Bzr trunk[2].
Both have not been released yet.  But you can use one of them or
both at your own risk.  Many changes were made in Gnus since Emacs
24.2 was released.  So, please note that you have to install Gnus
fully, not replacing nndraft.el only.  I think the easiest way is
to install Ma Gnus, i.e., that of the Gnus Git master.  Sorry for
this; I misunderstood that you use a development version of Gnus.

To install Ma Gnus is not so hard.  Download the repository or
a tarball[3] to somewhere and do:

・ cd gnus
・ ./configure [options]
   Run ``./configure --help'' to see the options if needed.
・ make
・ Add these snippets to your ~/.emacs file:

   (push "/Directory/Where/Gnus/Is/Installed" load-path)
   (require 'gnus-load)

   See lisp/Makefile to know the directory where the elc files
   will be installed.  That will normally be:
   /usr/local/share/emacs/24.2/site-lisp/gnus

・ su
・ make install

> On the other hand, I installed Emacs24 on another machine and it also
> reports Gnus version 5.13.

The version of Gnus bundled with Emacs is not growing for years
in spite of a lot of changes. :<

> (GNU Emacs 24.2 is in Debian unstable, that's why I'm afraid of upgrading
> to it.)

You can simply abandon Ma Gnus by:
・ rm -r site-lisp/gnus
・ remove the (require 'gnus-load) line in the ~/.emacs file.

[1] http://git.gnus.org/	...[3]
[2] http://savannah.gnu.org/bzr/?group=emacs
[3] You can get a tar archive of the Gnus Git master from:
    http://www.jpl.org/ftp/pub/tmp/mgnus-0.6-TIMESTAMP.tar.gz

_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

Re: Sent message still in drafts (lisp error: "Selecting deleted buffer")

[Felix Natter]

Katsumi Yamaoka <yamaoka@jpl.org> writes:

hi Katsumi,

> Felix Natter <fnatter@gmx.net> wrote:
> [...]
>> Would it help to upgrade to GNU Emacs 24.2?
>
> No, it doesn't.  The most recent nndraft.el is in the development
> repositories, the Gnus Git master[1] and the Emacs Bzr trunk[2].
> Both have not been released yet.  But you can use one of them or
> both at your own risk.  Many changes were made in Gnus since Emacs
> 24.2 was released.  So, please note that you have to install Gnus
> fully, not replacing nndraft.el only.  I think the easiest way is
> to install Ma Gnus, i.e., that of the Gnus Git master.  Sorry for
> this; I misunderstood that you use a development version of Gnus.
>
> To install Ma Gnus is not so hard.  Download the repository or
> a tarball[3] to somewhere and do:
>
> ・ cd gnus
> ・ ./configure [options]
>    Run ``./configure --help'' to see the options if needed.
> ・ make
> ・ Add these snippets to your ~/.emacs file:
>
>    (push "/Directory/Where/Gnus/Is/Installed" load-path)
>    (require 'gnus-load)
>
>    See lisp/Makefile to know the directory where the elc files
>    will be installed.  That will normally be:
>    /usr/local/share/emacs/24.2/site-lisp/gnus
>
> ・ su
> ・ make install

Thanks for the explanation!

Will Ma Gnus also work with GNU Emacs 23?

>> On the other hand, I installed Emacs24 on another machine and it also
>> reports Gnus version 5.13.
>
> The version of Gnus bundled with Emacs is not growing for years
> in spite of a lot of changes. :<

What a pity, if important bugs are fixed... :-/

>> (GNU Emacs 24.2 is in Debian unstable, that's why I'm afraid of upgrading
>> to it.)
>
> You can simply abandon Ma Gnus by:
> ・ rm -r site-lisp/gnus
> ・ remove the (require 'gnus-load) line in the ~/.emacs file.

But Ma Gnus won't change the configuration so that the "stable" Gnus
that comes with Emacs(23) does not run any more? In other words, can I
always go back?

Thanks and Best Regards,
-- 
Felix Natter

_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

Re: Sent message still in drafts (lisp error: "Selecting deleted buffer")

[Katsumi Yamaoka]

Felix Natter <fnatter@gmx.net> wrote:
> Will Ma Gnus also work with GNU Emacs 23?

It should work.  I tried to build Emacs 23.4 but failed (this
seems to need some tweaks to build on Cygwin).  But don't worry,
in the past I had a chance to use the Emacs 23.4 binary that
Cygwin distributed and the one I built on Linux in home, and had
no problem with Ma Ggnus.  AFAICT, the significant difference
between the old Gnus and today's one is that the marks feature
for the nnml backend, etc. has been removed.  But it won't trouble
you unless you run two or more Gnus on the same account of the
same machine.

[...]

>> You can simply abandon Ma Gnus by:
>> ・ rm -r site-lisp/gnus
>> ・ remove the (require 'gnus-load) line in the ~/.emacs file.

> But Ma Gnus won't change the configuration so that the "stable" Gnus
> that comes with Emacs(23) does not run any more? In other words, can I
> always go back?

I believe you can go back with no major problem.  If anything, I
don't think you get a reason to go back.  Even if it causes a
trouble, you will be able to get more followups in the net since
the interest of developers and expert users is in the bleeding
edge, not the old ones.  What you have to do then is to download
and rebuild the improved Gnus, or to improve it by yourself.