From: Stephen Zander <srz@mckesson.com>
Cc: Ding mailing list <ding@gnus.org>
Subject: Re: T ^ command change request (labels in gnus)
Date: 22 Jan 1998 09:40:53 -0800 [thread overview]
Message-ID: <87n2goh0ey.fsf@wsuse5.mckesson.com> (raw)
In-Reply-To: 's message of "22 Jan 1998 13:43:57 +0200"
<jari.aalto@poboxes.com> writes:
> 2. Reparenting aricles are difficult. If I mark parent with # and then
> go to child and press T ^, the article is moved, but also the
> the parent mark is removed
>
> --> Request: Please do not removed the parent #, because I want
> to move several articles under one parent.
Whouldn't the reverse be better, ie add a command (T v ?) to reparent
all #'d messages to the current message? I picked T v 'cause it's the
visual inverse of (T ^).
Of course, I could just shut up and wrte the thing too.... :)
--
Stephen
---
"Normality is a statistical illusion." -- me
next prev parent reply other threads:[~1998-01-22 17:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-22 11:43 jari.aalto
1998-01-22 11:58 ` Per Abrahamsen
1998-01-23 14:10 ` jari.aalto
1998-01-23 14:44 ` Per Abrahamsen
1998-01-22 17:40 ` Stephen Zander [this message]
1998-01-23 14:11 ` jari.aalto
1998-02-08 15:30 ` Lars Magne Ingebrigtsen
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=87n2goh0ey.fsf@wsuse5.mckesson.com \
--to=srz@mckesson.com \
--cc=ding@gnus.org \
--cc=stephen.zander@interlock.mckesson.com \
/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).