Friend's problem with drafts

Friend's problem with drafts

[Karl Kleinpaste]

A new convert to Gnus is using 5.8.3 under XEmacs 20.4 on Linux.  His
setup seems to include no concept of the drafts group.  When he is
editing a message and saves it, Gnus offers to save it in his home
directory, and needs an explicit filename (no default is present).  I
tried manually creating the drafts group for him with `G m', but this
seems to have had no effect; `C-x C-s' in a *message* buffer still
asks for where to save under ~/.

I've not seen this sort of trouble before.  Any clues as to what might
be going on here?

Re: Friend's problem with drafts

[Hrvoje Niksic]

Karl Kleinpaste <karl@charcoal.com> writes:

> A new convert to Gnus is using 5.8.3 under XEmacs 20.4 on Linux.
> His setup seems to include no concept of the drafts group.  When he
> is editing a message and saves it, Gnus offers to save it in his
> home directory, and needs an explicit filename (no default is
> present).  I tried manually creating the drafts group for him with
> `G m', but this seems to have had no effect; `C-x C-s' in a
> *message* buffer still asks for where to save under ~/.

A dumb question: are you sure M-x gnus is picking up the correct Gnus
version?  XEmacs 20.4 came with an older Gnus.

Second, evaluate (buffer-file-name) and see what it returns.  It
should be something like: "/home/<user>/News/drafts/drafts/148".

If that fails, use edebug to find out how things misfail.  What's
*supposed* to happen is that message-mode calls
message-set-auto-save-file-name, which uses
nndraft-request-associate-buffer to set the buffer file name to the
correct thing.