New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Things cheat sheet #332

Merged
merged 4 commits into from Oct 3, 2018

Conversation

Projects
None yet
2 participants
@osteele
Contributor

osteele commented Oct 3, 2018

@Kapeli

This comment has been minimized.

Show comment
Hide comment
@Kapeli

Kapeli Oct 3, 2018

Owner

Please follow the guidelines for naming and keyboard shortcuts: https://github.com/Kapeli/cheatsheets#guidelines. Also don't use symbols for the keyboard shortcuts, as they're hard to search for.

Owner

Kapeli commented Oct 3, 2018

Please follow the guidelines for naming and keyboard shortcuts: https://github.com/Kapeli/cheatsheets#guidelines. Also don't use symbols for the keyboard shortcuts, as they're hard to search for.

@Kapeli

This comment has been minimized.

Show comment
Hide comment
@Kapeli

Kapeli Oct 3, 2018

Owner

Don't use title case for entries please.

Owner

Kapeli commented on cheatsheets/Things.rb in 06cbbdf Oct 3, 2018

Don't use title case for entries please.

@osteele

This comment has been minimized.

Show comment
Hide comment
@osteele

osteele Oct 3, 2018

Contributor
  • Please follow the guidelines for naming and keyboard shortcuts: https://github.com/Kapeli/cheatsheets#guidelines
    • "Keyboard modifiers should be listed in this order: CMD+CTRL+ALT+SHIFT"
  • Also don't use symbols for the keyboard shortcuts, as they're hard to search for.

"Try not to include really common keyboard shortcuts (e.g. Copy, Paste, Undo, Select All)."

This cheatsheet does include one Copy and two Paste commands with the standard shortcut:

Category Command Name
Create new items CTRL+C Paste plain text to create new to-dos
Edit items CTRL+C Copy a to-do or project
Edit items CTRL+V Paste a to-do or project

IMO at least the inclusion of “Paste plain text to create new to-dos" is justified, because pasting to create an item, when there is no editable text area and no text insertion point, is not a standard behavior.

This seems consistent with the inclusion of "Copy line (empty selection)" and "Cut line (empty selection)" in the existing Visual Studio Code cheatsheat: these VS Code commands extend the standard shortcut with nonstandard behavior, and are listed in the current VS Code cheatsheet. This Things shortcut seems like those.

I kept "Edit items" Copy and Paste, in order to have a place to note that these work on both to-do items and projects (which wasn't obvious to me as a user), but this is more debatable.

Let me know if you want me to remove the last two of these, or all of them.

Contributor

osteele commented Oct 3, 2018

  • Please follow the guidelines for naming and keyboard shortcuts: https://github.com/Kapeli/cheatsheets#guidelines
    • "Keyboard modifiers should be listed in this order: CMD+CTRL+ALT+SHIFT"
  • Also don't use symbols for the keyboard shortcuts, as they're hard to search for.

"Try not to include really common keyboard shortcuts (e.g. Copy, Paste, Undo, Select All)."

This cheatsheet does include one Copy and two Paste commands with the standard shortcut:

Category Command Name
Create new items CTRL+C Paste plain text to create new to-dos
Edit items CTRL+C Copy a to-do or project
Edit items CTRL+V Paste a to-do or project

IMO at least the inclusion of “Paste plain text to create new to-dos" is justified, because pasting to create an item, when there is no editable text area and no text insertion point, is not a standard behavior.

This seems consistent with the inclusion of "Copy line (empty selection)" and "Cut line (empty selection)" in the existing Visual Studio Code cheatsheat: these VS Code commands extend the standard shortcut with nonstandard behavior, and are listed in the current VS Code cheatsheet. This Things shortcut seems like those.

I kept "Edit items" Copy and Paste, in order to have a place to note that these work on both to-do items and projects (which wasn't obvious to me as a user), but this is more debatable.

Let me know if you want me to remove the last two of these, or all of them.

@Kapeli

This comment has been minimized.

Show comment
Hide comment
@Kapeli

Kapeli Oct 3, 2018

Owner

This cheatsheet does include one Copy and two Paste commands with the standard shortcut:

They're ok to be included. As long as it's not just "Copy" or "Paste" I'm ok with it.

Owner

Kapeli commented Oct 3, 2018

This cheatsheet does include one Copy and two Paste commands with the standard shortcut:

They're ok to be included. As long as it's not just "Copy" or "Paste" I'm ok with it.

@osteele

This comment has been minimized.

Show comment
Hide comment
@osteele

osteele Oct 3, 2018

Contributor

I just committed a changed to downcast "autofill". I now believe everything complies with "Try to use Title Case only for categories."

There are still names that include uppercase words in non-initial position, but I believe these are all proper names within Thing's domain, that the Things documentation capitalizes thus; for example "Quick Entry" and "Today".

Contributor

osteele commented Oct 3, 2018

I just committed a changed to downcast "autofill". I now believe everything complies with "Try to use Title Case only for categories."

There are still names that include uppercase words in non-initial position, but I believe these are all proper names within Thing's domain, that the Things documentation capitalizes thus; for example "Quick Entry" and "Today".

@Kapeli Kapeli merged commit a2fa5ff into Kapeli:master Oct 3, 2018

1 check was pending

continuous-integration/travis-ci/pr The Travis CI build is in progress
Details
@Kapeli

This comment has been minimized.

Show comment
Hide comment
@Kapeli

Kapeli Oct 3, 2018

Owner

Thank you! 👍

Owner

Kapeli commented Oct 3, 2018

Thank you! 👍

@osteele osteele deleted the osteele:things branch Oct 3, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment