GNOME Bugzilla – Bug 714908
Keyboard shortcut (ctrl+P) to print
Last modified: 2021-07-05 13:24:53 UTC
---- Reported by geary-maint@gnome.bugs 2012-10-11 20:25:00 -0700 ---- Original Redmine bug id: 5988 Original URL: http://redmine.yorba.org/issues/5988 Searchable id: yorba-bug-5988 Original author: John Kim Original description: When I look at an email, I feel like pressing ctrl+p to get the print dialog out, but the ctrl+p doesn't work. Guess the shortcut isn't implemented yet. ---- Additional Comments From geary-maint@gnome.bugs 2013-11-14 17:15:00 -0800 ---- ### History #### #1 Updated by Jim Nelson about 1 year ago * **Priority** changed from _Normal_ to _High_ * **Target version** set to _0.3.0_ Using an accelerator is s a little more difficult when a conversation has more than one message, as then Geary will either need to deduce which message to print, ask the user, or assume Ctrl+P means print all messages in a conversation. The first and last are questionable and may not result in what the user expects. I also don't know how we could efficiently ask the user to pick which message(s) to print in a dialog box. These are the challenges of having a UI where multiple documents may be presented in a single page. Here's my suggestion for an initial stab at this: * Ctrl+P with one message present simply prints that message. * Ctrl+P with a multi-message conversation prompts the user with a dialog box: "Print %d messages?" (where %d is the number of messages in the conversation). There's also the question of where this should exist as a menu item. I don't believe this feature would be used often enough to warrant a toolbar button, but I think it's worth exposing in the gear menu (Chrome does this as well). So let's put it there. The Gtk.Action should only be active if a conversation is selected. I noticed you set the Assignee for this ticket to yourself. Do you plan on working on this ticket? #### #2 Updated by John Kim about 1 year ago Yes, I plan to work on this ticket. But the problem is that I have zero programming experience. :-( What do I have to do or know before I dive to writing the code? Currently, I'm trying to crash course through C during the weekend. #### #3 Updated by Jim Nelson about 1 year ago * **Assignee** deleted (<strike>_John Kim_</strike>) Geary is entirely written in Vala, and you'll need to know it before proceeding. Knowing C is certainly helpful. You can find a tutorial for learning Vala at https://live.gnome.org/Vala/Tutorial I'm going to remove you as an Assignee for now. We use that field for people actively working on a ticket. If you pick up on Vala and fill like you're ready to jump in, let us know and we'll assign this to you. #### #4 Updated by Jim Nelson 10 months ago * **Category** set to _client_ #### #5 Updated by Jim Nelson 9 months ago * **Target version** changed from _0.3.0_ to _0.4.0_ #### #6 Updated by Jim Nelson 8 months ago * **Target version** changed from _0.4.0_ to _0.5.0_ #### #7 Updated by Jim Nelson 7 days ago * **Target version** deleted (<strike>_0.5.0_</strike>) --- Bug imported by chaz@yorba.org 2013-11-21 23:13 UTC --- This bug was previously known as _bug_ 5988 at http://redmine.yorba.org/show_bug.cgi?id=5988 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
This might be easier once Bug 765516 lands since it's looking like it will have a notion of a currently focused message in the conversation.
Actually, this basically has the same problem as Bug 714377 - we need an obvious, visible notion of the targeted message, so it's clear to the user what message will be printed.
Mass-reassigning bugs that won't make 0.12.
Bump tickets to 0.14 that aren't going to make 0.13.
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.