After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 714377 - reply command should possibly reply to message currently in view
reply command should possibly reply to message currently in view
Status: RESOLVED OBSOLETE
Product: geary
Classification: Other
Component: client
unspecified
Other All
: High normal
: ---
Assigned To: Geary Maintainers
Geary Maintainers
needs-design
Depends on: 765516 778725
Blocks:
 
 
Reported: 2012-08-10 08:42 UTC by Adam Dingle
Modified: 2021-07-05 13:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Charles Lindsay 2013-11-21 20:26:02 UTC


---- Reported by adam@yorba.org 2012-08-10 13:42:00 -0700 ----

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

The following has happened to me many times:

1. I'm looking at the first message in a conversation in Geary. I want to
reply to it.

2. I press 'r'.

3. I'm surprised when a compose window pops up replying to the **last**
message in the conversation.

So I don't think we've gotten this right. Perhaps 'r' should reply to the last
message which is currently in view, or something like that. I'm opening a
ticket for discussing this at least.



---- Additional Comments From geary-maint@gnome.bugs 2012-09-20 15:29:00 -0700 ----

### History

####

#1

Updated by Adam Dingle about 1 year ago

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



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

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

Unknown version " in product geary. 
   Setting version to "!unspecified".
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 

Comment 1 Michael Gratton 2016-10-07 13:30:09 UTC
To fix this, we need an obvious, visible notion of the targeted message, so it's clear to the user what message will be replied to.

Working on Bug 765516, I tried enabling selection mode for the GtkListBox but the selection colour was really garish. I have a feeling a solution to this will need to be some other visual mechanism, than just colour.
Comment 2 Michael Gratton 2016-10-07 13:47:42 UTC
See also Bug 714908, which has the same problem.
Comment 3 Frédéric Parrenin 2018-01-29 09:20:54 UTC
I have the same problem using geary: I often want to reply to a particular message in a thread, not the last one.
I am wondering wether we could put the three buttons at the bottom of each message, or in the header of each message.
Having a global button which applies only to the last message does not make a lot of sense to me.
Comment 4 Federico Bruni 2018-01-29 11:57:15 UTC
(In reply to Frédéric Parrenin from comment #3)
> I am wondering wether we could put the three buttons at the bottom of each
> message, or in the header of each message.
> Having a global button which applies only to the last message does not make
> a lot of sense to me.

I agree, in fact I think I've never used the reply buttons in the header bar.
I would prefer leave in the header the buttons which act on conversations (move, label, delete, archive, undo) and move the reply/forward buttons, which act on messages, within the conversation viewer.

If put in the header of each message, we won't have to lose time clicking on the sandwich icon each time. I don't think it would clutter the UI.

Still I'd be happy, when I use keyboard shortcuts, if Geary could reply to the message where the focus is.
Comment 5 GNOME Infrastructure Team 2021-07-05 13:24:59 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/geary/-/issues/

Thank you for your understanding and your help.