Weird problems in Drafts.

Weird problems in Drafts.

[Rui Zhu]

Hello, all,

I've some questions about nndraft:

1. Why doesn't nndraft delete *~ files, after I've sent them?

2. Why does nndraft always show me contents of old *~ files, when I've
   saved article (C-x C-s) some times during editing and changed to
   Drafts to see what'd happend?

I use p-gnus 0.84 now.

Regards,
        Rui

Re: Weird problems in Drafts.

[Lars Magne Ingebrigtsen]

Rui Zhu <sprache@iname.com> writes:

> 1. Why doesn't nndraft delete *~ files, after I've sent them?

Hm.  Is it supposed to?

> 2. Why does nndraft always show me contents of old *~ files, when I've
>    saved article (C-x C-s) some times during editing and changed to
>    Drafts to see what'd happend?

It doesn't seem to do that when I try that -- nndraft just shows me
a copy of the article that I'm editing.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Weird problems in Drafts.

[Rui Zhu]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Rui Zhu <sprache@iname.com> writes:
> 
> > 1. Why doesn't nndraft delete *~ files, after I've sent them?
> 
> Hm.  Is it supposed to?

Think the number will be reused, it is not a big problem now, just
taste (sooner or _later_ they will be overridden).  In my previous
message I really thought all those *~ files would stay there for ever
;).

> > 2. Why does nndraft always show me contents of old *~ files, when I've
> >    saved article (C-x C-s) some times during editing and changed to
> >    Drafts to see what'd happend?
> 
> It doesn't seem to do that when I try that -- nndraft just shows me
> a copy of the article that I'm editing.

Maybe I didn't make me clear.  It keeps showing me the contents which
I saved first time, though I might have saved more times later.  You
must do exactly as following:

`m' in group buffer or like
editing
`C-x C-s'
`C-x b' go to group then nndraft to see article. This is OK.
`C-x b' back to *mail* buffer
editing
`C-x C-s'
`C-x b' go to group then nndraft to see article. This is _not_ OK!

But if I look at one article (not just go into group) in any other
group before I go to see draft, it does show me the up-to-date
contents.  It is just annoying but not fatal.

It's in v0.84, maybe not there any more.

Regards,
        Rui

Re: Weird problems in Drafts.

[Lars Magne Ingebrigtsen]

Rui Zhu <zhurui@cs.tu-berlin.de> writes:

> Think the number will be reused, it is not a big problem now, just
> taste (sooner or _later_ they will be overridden).  In my previous
> message I really thought all those *~ files would stay there for ever
> ;).

Well, ok, but how does one identify all the backup files for a
particular file?  I've looked around slightly, and I couldn't find
anything that looked promising...

> `m' in group buffer or like
> editing
> `C-x C-s'
> `C-x b' go to group then nndraft to see article. This is OK.
> `C-x b' back to *mail* buffer
> editing
> `C-x C-s'
> `C-x b' go to group then nndraft to see article. This is _not_ OK!
> 
> But if I look at one article (not just go into group) in any other
> group before I go to see draft, it does show me the up-to-date
> contents.  It is just annoying but not fatal.

nndraft behaves as all the other backends here -- it does not
re-request a message from its source unless you really ask it to.
`C-u g' to do that.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Weird problems in Drafts.

[Kai.Grossjohann]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Well, ok, but how does one identify all the backup files for a
> particular file?  I've looked around slightly, and I couldn't find
> anything that looked promising...

Hm.  find-backup-file-name seems to do something hardwired when
version-control is non-nil, and calls make-backup-file-name otherwise.

Or were you looking for something else?

kai
-- 
Life is hard and then you die.

Re: Weird problems in Drafts.

[Lars Magne Ingebrigtsen]

Kai.Grossjohann@CS.Uni-Dortmund.DE writes:

> Hm.  find-backup-file-name seems to do something hardwired when
> version-control is non-nil, and calls make-backup-file-name otherwise.

  -rw-rw-r--   1 larsi    larsi        1123 Jul  5 06:44 76
  -rw-rw-r--   1 larsi    larsi        1123 Jul  5 06:44 76.~1~

(find-backup-file-name "~/News/drafts/drafts/76")
=> ("~/News/drafts/drafts/76.~2~")

So it seems to do the reverse thing -- it suggests a new backup file
name; it doesn't say what the current backup file names to a given
file are.

----------
(find-backup-file-name FN)

Documentation:
Find a file name for a backup file, and suggestions for deletions.
Value is a list whose car is the name for the backup file
 and whose cdr is a list of old versions to consider deleting now.
If the value is nil, don't make a backup.
----------

But the "old versions" thing sounds good, but how does one control
what "old versions" are?

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Weird problems in Drafts.

[Kai.Grossjohann]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> But the "old versions" thing sounds good, but how does one control
> what "old versions" are?

Variables kept-new-versions and kept-old-versions.  Well, maybe it is
sufficient to bind these to strange values then call
find-backup-file-name. 

kai
-- 
Life is hard and then you die.

Re: Weird problems in Drafts.

[Lars Magne Ingebrigtsen]

Kai.Grossjohann@CS.Uni-Dortmund.DE writes:

> Variables kept-new-versions and kept-old-versions.  Well, maybe it is
> sufficient to bind these to strange values then call
> find-backup-file-name. 

(let ((kept-new-versions 1)
      (kept-old-versions 0))
  (find-backup-file-name "~/News/drafts/drafts/76"))
=> ("~/News/drafts/drafts/76.~3~" "~/News/drafts/drafts/76.~1~" "~/News/drafts/drafts/76.~2~")

so that seems to do the trick.  I've now made nndraft delete the
backup files, but I'm not quite sure whether doing so is dangerous or
not...  I mean, is there any possibility at all that this might return 
a list of files that should probably not be deleted?

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Weird problems in Drafts.

[Kai.Grossjohann]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Kai.Grossjohann@CS.Uni-Dortmund.DE writes:
> 
> > Hm.  find-backup-file-name seems to do something hardwired when
> > version-control is non-nil, and calls make-backup-file-name otherwise.
> 
>   -rw-rw-r--   1 larsi    larsi        1123 Jul  5 06:44 76
>   -rw-rw-r--   1 larsi    larsi        1123 Jul  5 06:44 76.~1~
> 
> (find-backup-file-name "~/News/drafts/drafts/76")
> => ("~/News/drafts/drafts/76.~2~")
> 
> So it seems to do the reverse thing -- it suggests a new backup file
> name; it doesn't say what the current backup file names to a given
> file are.

Well, yes, but since what it does is hardwired...  But that's ugly.

kai
-- 
Life is hard and then you die.