Summary | Inconsistent folder refresh location |
Queue | IMP |
Queue Version | HEAD |
Type | Bug |
State | Not A Bug |
Priority | 1. Low |
Owners | |
Requester | kevin_myer (at) iu13 (dot) org |
Created | 07/01/2005 (7383 days ago) |
Due | |
Updated | 07/06/2005 (7378 days ago) |
Assigned | 07/01/2005 (7383 days ago) |
Resolved | 07/03/2005 (7381 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
supports choosing which folders to include in the Inbox).
mail. You can always create a different virtual folder with only the
folders you want.
that way.
new message, it should. For all the normal users you have a
experience with, the mailbox_start value would be set to Do Nothing (a
new value I just created for the sake of keeping the refreshed view
the same). But I have a reasonable workaround.
automatically pulled away from your current view, and made a comment
about something similar that Gmail does that bugs her. She's
frequently shot down my own ideas, and is a pretty astute beta
tester. She's savvier than most, but certainly not technical. FYI.
rearranged on a refresh (especially in Thread mode, where "Horde
frameset" is treated the same as "Horde Frame Set", but that, I think
is the topic for an RFC enhancement to the IMAP THREAD extension).
But Jan's comment about using the Folder menu will do the trick. I
could have sworn, not too long ago, that the folder menu got reset to
INBOX, regardless of what folder you were in, which would force you to
navigate to find the current folder. But it appears to be sticky now,
so, with an AccessKey N, that should do a Refresh and JumpTo new mail.
supports choosing which folders to include in the Inbox). I think the
AccessKey N should work (and that either accidentally or intentionally
coincides with other programs Next message command). Although I just
had WHUPS generate a _New ticket, when my focus was on IMP in another
tab.. Have to see if that was a fluke or is reproducible.
that way.
I posed the scenario to my wife. She thinks it'd be rude if you were
automatically pulled away from your current view, and made a comment
about something similar that Gmail does that bugs her. She's
frequently shot down my own ideas, and is a pretty astute beta tester.
She's savvier than most, but certainly not technical. FYI.
Maybe you want to be using the Virtual Inbox or something like it?
location of the next unread message, how do you do that?
refresh icon behaves. You want a direct way to go to the next unread
message. Using the INBOX icon or a refresh is a developer-like
workaround IMHO, not normal user behavior. A normal user wants a
button for it.
taken to the first unread message (or the end of the messages, if I
have no unread messages). I'm looking at a generalized implementation
of the behavior of the INBOX icon and since you've already got a
Refresh, rather than take up any more screen real estate, roll the
functionality into refresh. I'll grant that there will likely be
users who dont' set mailbox_start to first unread, but who would still
use a navigation feature to go to the next unread message. But I
still think that Refresh should incorporate the mailbox_start
preference.
tricky to define the "next" new message, but the sort order should
handle it. If we can figure out a good UI/flow for it and someone
writes the code, I have no problem including it.
display when you initially open a folder? The message you initially
were taken to is now read (if you chose to read it). So getting the
next unread message would be the same as choosing a folder, no?
messages in the mailbox view, and an automatic refresh happens, and
they're taken to new mail and they then have to go *find* the
messages they were looking at I don't think that will ever be
intuitive, even for someone who checked off "always show me new
mail". They *might* make the connection, but they'll still be annoyed.
granted. But the fact of the matter is that I believe most mail
clients, when they refresh, will reset the state of your view. I find
myself trying to figure out how to get to next screen with an unread
message way more often than I find my screen getting refreshed when
I'm reading senders and subjects. If I configure a mail client to
take me to new mail, thats a choice I make, and I realize a mail
client can't possibly know what my conscious thought stream is and
elect not to refresh a screen, if I happen to be looking at it :)
normal end-users, and vice versa?
time to time we all get tunnel vision. Developers make decisions
based on what they think or want. Admins configure software with
settings that, after testing, reveal that they need to be changed,
based on user-feedback. And users want features (now) that do XYZ
because they see XYZ elsewhere, or because thats the way they've
always done things. Why these decisions are oft-times unintuitive is
a) developers don't always fully vette their ideas with real
non-technical end-users, b) admins don't use a wide-enough audience in
determining initial settings, and c) end-users have unreasonable
expectations about what it takes to develop software, and in some
cases, the way they do things is just plain wrong. Hence, from time
to time (not intended to be a blanket statement) what's intuitive to
one group is not intuitive to another.
statement, as clarified above. That will learn me to wait until I'm
not so frustrated, to respond, so that the proper modifiers and
qualifiers make it into a statement.
problem,
as obviously I must be the only one in the world who thinks the fetchmail
behavior is inconsistent too (2211). It isn't quite noone, but onlyone (who
has taken the time to document and report it).
argument that noone has reported it is a valid argument. I can
certainly see where noone else may agree with an idea, in which case
it either dies or is refined. But the fact that noone has reported it
doesn't mean a lot. Thats a little bit insulting to first time bug
reporters, who take the time to formally document a bug.
normal end-users, and vice versa?
a). I'd say that more than 50% of your requests/suggestions/etc. have
been implemented, if not better.
b). The above is downright insulting. Sometimes developers are out of
touch with users, but most of the core developers use IMP as their
primary and/or only email client. I fix crap all the time in IMP and
other Horde apps because it bugs me - as a user. We respond to
requests from users - like you - all the time. ...
as obviously I must be the only one in the world who thinks the fetchmail
behavior is inconsistent too (2211). It isn't quite noone, but onlyone (who
has taken the time to document and report it).
location of the next unread message, how do you do that?
refresh icon behaves. You want a direct way to go to the next unread
message. Using the INBOX icon or a refresh is a developer-like
workaround IMHO, not normal user behavior. A normal user wants a
button for it.
That's a not unreasonable feature request. It's sometimes going to be
tricky to define the "next" new message, but the sort order should
handle it. If we can figure out a good UI/flow for it and someone
writes the code, I have no problem including it.
choose for mailbox_start, whether that refresh is automatic, forced,
or implied, by clicking on a folder. Which really amounts to
mailbox_start being expanded to be "When opening or refreshing a
mailbox, which page do you want to start on?", which I think is a
logical, useful extension.
messages in the mailbox view, and an automatic refresh happens, and
they're taken to new mail and they then have to go *find* the messages
they were looking at I don't think that will ever be intuitive, even
for someone who checked off "always show me new mail". They *might*
make the connection, but they'll still be annoyed.
folder I want exists, as expanding the folders in the left side bar.
behaviour in the past and two developers already considered such a
behaviour unintuitive.
normal end-users, and vice versa? Obviously, I must be the only one
in the world who has run into this problem, as obviously I must be the
only one in the world who thinks the fetchmail behavior is
inconsistent too (2211). It isn't quite noone, but onlyone (who has
taken the time to document and report it).
I've used IMP as my primary email client for the past four years so
I'm not up to speed on how some of the fat clients behave but a quick
glance reveals that most, if not all of them, have an easy way to get
to the next unread message (CTL-N in Thunderbird, shift+. in
Evolution, for example). And as new messages come in, and your screen
is refreshed, they'll take you to and display the new message (I don't
like the display part, I may not want to read the message, but I do
like having the message subject and sender shown to me).
you can use the INBOX icon to get an updated message count and move
to the next unread message location. If its not the INBOX, you have
to expand your folder structure and choose the folder, then click on
it.
choose for mailbox_start, whether that refresh is automatic, forced,
or implied, by clicking on a folder. Which really amounts to
behaviour in the past and two developers already considered such a
behaviour unintuitive.
jump to the first unread message in a folder. Take a non-hypothetical
situation, such as this: 1000 messages in a folder, sorted by any
criteria. Most of the time, new messages will show up at either the
end or the beginning of the view, depending if you sort ascending or
descending. But you'll get a fair number of stray messages dispersed
throughout the index too. If you go and read one of those messages,
and are ready to move onto the location of the next unread message,
how do you do that? If the folder is the INBOX, you can use the INBOX
icon to get an updated message count and move to the next unread
message location. If its not the INBOX, you have to expand your
folder structure and choose the folder, then click on it. Or skip
from screenful of message to screenful of messages, and keep skipping
until you find the next unread message. Whereas if the refresh was
both a refresh and a jumpto function, a quick Accesskey R would get
you there - no folder navigation and expansion necessary, no wasted
time trying to find the next unread message. Software should provide
functionality to process messages more quickly, not force me to wade
to find the next message to process.
I believe the behavior of a refresh should honor whatever value I
choose for mailbox_start, whether that refresh is automatic, forced,
or implied, by clicking on a folder. Which really amounts to
mailbox_start being expanded to be "When opening or refreshing a
mailbox, which page do you want to start on?", which I think is a
logical, useful extension.
State ⇒ Not A Bug
the current view.
message index refresh (which is fine). If the intent is to have them
behave differently than the INBOX icon, thats fine. It basically
serves the function of new mail notification only, either with audio,
or with an incrementing number. I just thought it would be useful to
also take you to the new message(s), because I'm going to have to
click on the INBOX icon after a notification anyway. Why not roll
that into a refresh?
State ⇒ Feedback
I'm not sure that changing that would be any more intuitive.
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Inconsistent folder refresh location
Queue ⇒ IMP
State ⇒ Unconfirmed
If you use the refresh link for the folder that's display (the
circular arrows icon), you're not taken to the first unread message,
but the message index is updated. Same thing if you have auto-refresh
configured for IMP. If you click on the INBOX icon in the menu, you
are taken to the first unread message.
Any refresh should honor the value you have set for mailbox_start.