From: Tim Cross <email@example.com> To: John Kitchin <firstname.lastname@example.org> Cc: email@example.com Subject: Re: Using backticks for the inline code delimeter? Date: Thu, 22 Apr 2021 05:49:42 +1000 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> John Kitchin <firstname.lastname@example.org> writes: >> The challenge can be in identifying the most appropriate key bindings. >> This can depend on the platform you use as well. When I was only using >> Linux, I used the 'super' key for this and it was great. However, when I >> also started using a mac, I had to define a new scheme. It can take a >> bit of work to setup initially, but I think it is worth the effort. I >> now have the same bindings in multiple modes, so regardless of whether >> I'm writing markdown, org, html, rich text, etc, I just hit the same key >> bindings to mark content as code, bold, italic, etc. > > On a Mac, you might find these useful. I don't use the right command and > option keys, so I redefine them as hyper and super. they are right under > my thumb, and convenient. > > (setq mac-right-command-modifier 'hyper) > (setq mac-right-option-modifier 'super) That is useful information. The 'hyper key is certainly overlooked and provides a very useful mechanism to create a whole set of new, possibly short, key bindings. I like the idea of re-tasking the right hand command/option keys as it is very rare I use them (command/option is most used via left hand side for me). -- Tim Cross
next prev parent reply other threads:[~2021-04-21 19:54 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-31 18:48 George Mauer 2021-03-31 19:16 ` autofrettage 2021-03-31 19:19 ` Timothy 2021-04-01 6:03 ` Marcin Borkowski 2021-04-20 13:30 ` Matt Price 2021-04-20 20:24 ` John Kitchin 2021-04-21 22:37 ` Matt Price 2021-04-20 22:30 ` Tim Cross 2021-04-21 19:22 ` John Kitchin 2021-04-21 19:49 ` Tim Cross [this message] 2021-03-31 19:24 ` Sébastien Miquel 2021-04-01 16:49 ` Maxim Nikulin 2021-04-01 17:05 ` Timothy 2021-04-01 18:43 ` Samuel Wales 2021-04-01 23:14 ` Tim Cross 2021-04-01 23:30 ` Joost Kremers 2021-04-02 0:28 ` Tim Cross 2021-04-04 1:13 ` Tom Gillespie 2021-04-04 10:03 ` Joost Kremers 2021-04-04 12:19 ` Nicolas Goaziou 2021-04-04 16:46 ` Bill Burdick 2021-04-04 17:24 ` Nicolas Goaziou 2021-04-04 19:33 ` Joost Kremers 2021-04-04 23:06 ` Nicolas Goaziou 2021-04-06 15:03 ` Maxim Nikulin 2021-04-19 9:27 ` Nicolas Goaziou 2021-03-31 19:28 ` Timothy 2021-03-31 19:55 ` autofrettage 2021-03-31 20:31 ` Diego Zamboni 2021-03-31 21:51 ` George Mauer 2021-03-31 22:27 ` Dr. Arne Babenhauserheide 2021-03-31 22:38 ` Tim Cross 2021-04-01 0:25 ` Samuel Wales 2021-04-01 1:11 ` Bill Burdick 2021-04-01 3:42 ` Greg Minshall 2021-04-01 9:32 ` autofrettage 2021-04-02 11:23 ` Andreas Eder 2021-04-04 17:06 ` Maxim Nikulin 2022-03-19 3:17 chris 2022-03-19 3:24 ` chris
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Using backticks for the inline code delimeter?' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).