From: Michael R. Wolf <MichaelRunningWolf@att.net>
Subject: Re: possible bug: article marks are wrong when moving article
Date: Sun, 25 May 2003 16:52:42 -0700 [thread overview]
Message-ID: <uadda37p1.fsf@att.net> (raw)
In-Reply-To: <iluznlb851q.fsf@latte.josefsson.org>
Simon Josefsson <jas@extundo.com> writes:
> "Michael R. Wolf" <MichaelRunningWolf@att.net> writes:
>
>> Simon Josefsson <jas@extundo.com> writes:
>>
>>> Ted Zlatanov <tzz@lifelogs.com> writes:
>>
>> [...]
>>
>>>> So the temporary solution is to quit the summary, go back and then
>>>> move?
>>>
>>> Yup. Or move it and mark it in the new folder.
>>>
>>>> Is the "update marks on server" command a stand-alone function that
>>>> the article move/copy operation can trigger? If you could point me to
>>>> where it happens, maybe I can do the rest.
>>>
>>> gnus-summary-update-info is run on 'q' and propagates the flags, but
>>
>> Is it also called with 'M-g' (gnus-summary-rescan-group)? If so, then
>> it's an easier solution than doing the exit and reentry.
>
> Yup. Still only as a workaround, though.
Yeah, but it's only one command, and confines you to the group of
interest. I was glad to find this command because it prevented me from
escaping into the Group buffer where the normal flow control dropped
me down a few groups to the unread group, requiring me to remember
which group to get back into. I like my machines to remember my return
location for me since my brain can only hold so many things at once
(on a good day).
--
Michael R. Wolf
All mammals learn by playing!
MichaelRunningWolf@att.net
prev parent reply other threads:[~2003-05-25 23:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 17:59 Ted Zlatanov
2003-05-23 21:19 ` Simon Josefsson
2003-05-24 11:01 ` Ted Zlatanov
2003-05-24 14:07 ` Simon Josefsson
2003-05-25 11:02 ` Michael R. Wolf
2003-05-25 14:38 ` Simon Josefsson
2003-05-25 23:52 ` Michael R. Wolf [this message]
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=uadda37p1.fsf@att.net \
--to=michaelrunningwolf@att.net \
/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).