i. Pick a keywork that will select several messages
in a message search. The search selects all of
these messages *plus* any currently selected msgs.
Is this the desired behavior? I would think the
desired behavior would be the following.
a. If only one message is currently selected,
unselect it and select messages matching the
search pattern.
b. If multiple messages are already selected change
the selection to the subset matching the search pattern
(i.e., unselect all that do not match the search pattern
and leave selected *only* those previously selected msgs
that match the search pattern: an intersection
rather than a union)
ii. There is a closely related user interface problem.
Select several messages and mark them unread. Now press ctrl-u to go
to the next unread msg. The current behavior is to extend the select
to include the next unread message. I think this is undesirable: I
cannot imagine the use of extending the selection this way. I think
after ctrl-u *only* the one msg should be selected.
But the user interface problem is much more serious than this. It is
easy not to recognize the current behavior if the selected msgs are
not simultaneously visible. This produced a bad outcome for me. I did
not realize this was the behavior. When I hit ctrl-u I moved to an
isolated message (the msgs matching my search were widely separated,
and I marked them as unread so that I could move to them). It looked
just like a single selected msg always looked. I read it and deleted
it. This deleted *all* the selected messages, which was not my
intention.
So I urge that the current behavior be considered a serious
user interface problem, likely to make almost every user very
unhappy at least once. At the level of minimum changes,
I think a dialogue should open. (E.g.: "Delete all 5 selected
messages?")
Much better I think would be the following change in behavior.
"d" deletes the current message (so this is always consistent)
"ctrl-d" deletes the current selection
"a" opens the address book for editing (since ctrl-d will be
taken now; am I right that "a" is not taken?)
This would yield better mnemonics and more consistency.
iii. Related note: when multiple msgs are selected,
try pressing <shift> to force the selection to the current msg.
No good. In fact there seems to be no keystroke to change the
selection to the currrent msg. I assume this is a bug.
iv. Can we please have a keystroke for "move to next selected msg"? I
suggest "n" (when multiple msgs are selected, move to the next
selected msg, otherwise move to the next msg). This would be very
helpful. Right now to move among selected msgs I believe you have to
either mark the selection unread and then move to the next unread with
ctrl-u or else flag the selection and move to the next flagged msg
(with no available keystroke?? how about ctrl-*, which is currently
unassigned?)
Thanks,
Alan
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Oh, it's good to be a geek.
http://thinkgeek.com/sf
_______________________________________________
Mahogany-Users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mahogany-users
