---- Reported by adam@yorba.org 2012-01-25 11:31:00 -0800 ----

Original Redmine bug id: 4662
Original URL: http://redmine.yorba.org/issues/4662
Searchable id: yorba-bug-4662
Original author: Adam Dingle
Original description:

Suppose that my inbox has three messages A, B, and C, where A is the newest
and C is the oldest. If I select B and archive it, then currently Geary auto-
selects C. I think it should instead auto-select A. We can't read the user's
mind, but I think that selecting the newer message will usually be the correct
choice since newer information is usually more interesting.

It's also quite possible in this situation that A and B are both unread but C
has been read, in which case selecting A certainly makes more sense. I don't
think we need to explicitly test for the read state, though; I think the
simple heuristic of selecting the newer message will work fine.

Related issues:
duplicated by geary - 5413: iOS-style select next message (Duplicate)
duplicated by geary - Feature #6511: On delete/archive a message, select
next/previous message... (Duplicate)



---- Additional Comments From geary-maint@gnome.bugs 2013-04-03 18:26:00 -0700 ----

### History

####

#1

Updated by Eric Gregory almost 2 years ago

  * **Category** set to _13_
  * **Status** changed from _Open_ to _5_
  * **Assignee** set to _Eric Gregory_
  * **Resolution** set to _fixed_

####

#2

Updated by Adam Dingle over 1 year ago

  * **Status** changed from _5_ to _Open_
  * **Assignee** deleted (<strike>_Eric Gregory_</strike>)
  * **Resolution** deleted (<strike>_fixed_</strike>)

I'm still unsatisfied with how Geary chooses which message to select after an
archive operation. Some people read newly arrived messages from newest to
oldest, others from oldest to newest, and I bet that some people will read in
different directions at different times. I now think that after a message is
archived, if only one of the immediately preceding and following messages is
unread then Geary should auto-select that message. If they are both unread or
both read, then we may as well select the newer of those messages. Reopening.

####

#3

Updated by Adam Dingle over 1 year ago

  * **Subject** changed from _automatically select newer message after archiving_ to _automatically select unread message after archiving_

####

#4

Updated by Adam Dingle over 1 year ago

  * **Target version** deleted (<strike>_0.1_</strike>)

####

#5

Updated by Adam Dingle over 1 year ago

Actually, if the adjacent messages are either both unread or both read, I
think we should select the message which causes the selection highlight
rectangle to remain in the same position on screen before and after the
archive operation. I think that would look nicer.

####

#6

Updated by Adam Dingle over 1 year ago

  * **Subject** changed from _automatically select unread message after archiving_ to _select message more intelligently after archiving_

See #5413 for another possible solution to this problem.

####

#7

Updated by Jim Nelson 9 months ago

  * **Category** set to _client_
  * **Target version** set to _0.4.0_

At #6511, a user has suggested the following:

DELETE = go to previous message (new message)

SHIFT + DELETE = go to next message (old message)

####

#8

Updated by Michael Granados 9 months ago

Jim Nelson wrote:

> At #6551, a user has suggested the following:

>

> DELETE = go to previous message (new message)

SHIFT + DELETE = go to next message (old message)

Now, after see geary with more calm I see the "Archive" button, I suggest the
SHIFT key work here too. With shif key pressed the pointer goes to old
message.

####

#9

Updated by Adam Dingle 8 months ago

Jim, I don't see a ticket #6551. Was that a typo?

####

#10

Updated by Jim Nelson 8 months ago

Yes. I've edited the comment.

####

#11

Updated by Jim Nelson 8 months ago

  * **Target version** changed from _0.4.0_ to _0.5.0_



--- Bug imported by chaz@yorba.org 2013-11-21 20:22 UTC  ---

This bug was previously known as _bug_ 4662 at http://redmine.yorba.org/show_bug.cgi?id=4662

Unknown milestone "unknown in product geary. 
   Setting to default milestone for this product, "---".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Resolution set on an open status.
   Dropping resolution