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 741573 - Document keyboard composer shortcuts
Document keyboard composer shortcuts
Status: RESOLVED FIXED
Product: geary
Classification: Other
Component: documentation
master
Other Linux
: Normal normal
: ---
Assigned To: Geary Maintainers
Geary Maintainers
review
Depends on:
Blocks:
 
 
Reported: 2014-12-15 20:25 UTC by Jim Nelson
Modified: 2014-12-19 05:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Add composer shortcuts to documentation (3.26 KB, patch)
2014-12-17 07:01 UTC, Robert Schroll
committed Details | Review

Description Jim Nelson 2014-12-15 20:25:05 UTC
As mentioned in the mailing list:

The composer shortcuts should be listed in "Keyboard shortcuts" in a separate section than the "normal" shortcuts, i.e. "Composer keyboard shortcuts".  We should link to the "Keyboard shortcuts" page from the "Write a message" page; bonus points for linking to the new section's anchor.
Comment 1 Robert Schroll 2014-12-17 07:01:14 UTC
Created attachment 292869 [details] [review]
Add composer shortcuts to documentation

I left out the undo, redo, cut, copy, paste, and paste with formatting 
shortcuts.  The first five are standard, and the last is discoverable 
via the context menu.  (It's also broken right now....)

I first put all of the shortcuts in a single table, with the intention 
of marking those only available in rich text mode with an asterisk.  But 
I couldn't figure out how to do this, so I tried italicizing some of the 
labels.  That didn't look very good, so now there are two separate 
tables.
Comment 2 Jim Nelson 2014-12-18 21:50:58 UTC
Review of attachment 292869 [details] [review]:

Looks great!  I think the separate table is warranted.  Agree about copy/paste.

Only concern is that I *think* the usual standard is for the shortcut descriptions to describe what the operation will do, not did.  For example, "Strike text" instead of "Struck text", "Italicize text" instead of "Italic text", and "Underline text" instead of "Underlined text".

Make those changes and commit!
Comment 3 Robert Schroll 2014-12-19 05:43:14 UTC
Attachment 292869 [details] pushed as 8a302a9 - Add composer shortcuts to documentation