drafts/queue and edited messages.

drafts/queue and edited messages.

[Harry Putnam]

This has come up a few times but I've lost track of any resolution to
it.

Using a semi-stock outgoing message archive and then several
particular groups where I've set gcc in the group params.

If I happen to edit a message that has collected in
~/News/drafts/queue

The archived or gcc'ed copy is no longer a faithful copy.

Is this just unavoidable or can we have code that governs drafts/queue
and knows where the message came from, its file number and whether
it is gcc'ed?  If so write them back to the sending group overwriting
the original.  Maybe the same with the global archive, if the message
is not gcc'ed.

Maybe make it a requirement for this code that all groups involved be
under that same backend.  Avoiding that major problem.

Re: drafts/queue and edited messages.

[ShengHuo ZHU]

Harry Putnam <reader@newsguy.com> writes:

> This has come up a few times but I've lost track of any resolution to
> it.
> 
> Using a semi-stock outgoing message archive and then several
> particular groups where I've set gcc in the group params.
> 
> If I happen to edit a message that has collected in
> ~/News/drafts/queue
> 
> The archived or gcc'ed copy is no longer a faithful copy.
> 
> Is this just unavoidable or can we have code that governs drafts/queue
> and knows where the message came from, its file number and whether
> it is gcc'ed?  If so write them back to the sending group overwriting
> the original.  Maybe the same with the global archive, if the message
> is not gcc'ed.
> 
> Maybe make it a requirement for this code that all groups involved be
> under that same backend.  Avoiding that major problem.

nndraft:queue is not designed for editing. nndraft:drafts is.

ShengHuo

Re: drafts/queue and edited messages.

[Harry Putnam]

ShengHuo ZHU <zsh@cs.rochester.edu> writes:

> Harry Putnam <reader@newsguy.com> writes:
> 
> > This has come up a few times but I've lost track of any resolution to
> > it.
> > 
> > Using a semi-stock outgoing message archive and then several
> > particular groups where I've set gcc in the group params.
> > 
> > If I happen to edit a message that has collected in
> > ~/News/drafts/queue
> > 
> > The archived or gcc'ed copy is no longer a faithful copy.
> > 
> > Is this just unavoidable or can we have code that governs drafts/queue
> > and knows where the message came from, its file number and whether
> > it is gcc'ed?  If so write them back to the sending group overwriting
> > the original.  Maybe the same with the global archive, if the message
> > is not gcc'ed.
> > 
> > Maybe make it a requirement for this code that all groups involved be
> > under that same backend.  Avoiding that major problem.
> 
> nndraft:queue is not designed for editing. nndraft:drafts is.

Whether it is or not, it still servers that purpose in those cases
where you think of something after posting and discover its queued and
available. The drafts editing commands work there as well, so why not
use it that way?

he he... like I just did with this one when I realized I'd sent to
both you and list.  I caught it in queue and removed the Cc:.  Very
handy I think but still would like to make the saved copy be the same.

My archived copy of this message will not have the above para or this line.