From: Grant Rettke <gcr@wisdomandwonder.com>
To: Thorsten Jolitz <tjolitz@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Is <s TAB supposed to expand into upper case #+BEGIN_SRC?
Date: Sun, 8 Jun 2014 15:04:02 -0500 [thread overview]
Message-ID: <CAAjq1meuLfbV0DyYjLDD13eA3Wzebu8a8YiomY2Rk8SOHegOSA@mail.gmail.com> (raw)
In-Reply-To: <CAAjq1meqC9q6YAiy=qyuAx5-tn7MOhcNgq5cE5PQR2unMHO=CA@mail.gmail.com>
Just added this to my init file to do that work:
(mapc (lambda (asc)
(let ((org-sce-dc (downcase (nth 1 asc))))
(setf (nth 1 asc) org-sce-dc)))
org-structure-template-alist)
Grant Rettke | AAAS, ACM, ASA, FSF, IEEE, SIAM, Sigma Xi
gcr@wisdomandwonder.com | http://www.wisdomandwonder.com/
“Wisdom begins in wonder.” --Socrates
((λ (x) (x x)) (λ (x) (x x)))
“Life has become immeasurably better since I have been forced to stop
taking it seriously.” --Thompson
On Sat, Jun 7, 2014 at 4:44 PM, Grant Rettke <gcr@wisdomandwonder.com> wrote:
> Thank you Thorsten.
> Grant Rettke | AAAS, ACM, ASA, FSF, IEEE, SIAM, Sigma Xi
> gcr@wisdomandwonder.com | http://www.wisdomandwonder.com/
> “Wisdom begins in wonder.” --Socrates
> ((λ (x) (x x)) (λ (x) (x x)))
> “Life has become immeasurably better since I have been forced to stop
> taking it seriously.” --Thompson
>
>
> On Sat, Jun 7, 2014 at 3:39 PM, Thorsten Jolitz <tjolitz@gmail.com> wrote:
>> Grant Rettke <gcr@wisdomandwonder.com> writes:
>>
>>
>>> #+BEGIN_SRC
>>>
>>> #+END_SRC
>>>
>>> Is supposed to expand into upper case letters?
>>
>> or put this in your init.el:
>>
>> #+BEGIN_SRC emacs-lisp
>> (setq org-structure-template-alist
>> (quote (("s" "#+begin_src ?\n\n#+end_src"
>> "<src lang=\"?\">\n\n</src>")
>> ("e" "#+begin_example\n?\n#+end_example"
>> "<example>\n?\n</example>")
>> ("q" "#+begin_quote\n?\n#+end_quote"
>> "<quote>\n?\n</quote>")
>> ("v" "#+begin_verse\n?\n#+end_verse"
>> "<verse>\n?\n/verse>")
>> ("c" "#+begin_center\n?\n#+end_center"
>> "<center>\n?\n/center>")
>> ("l" "#+begin_latex\n?\n#+end_latex"
>> "<literal style=\"latex\">\n?\n</literal>")
>> ("L" "#+latex:"
>> "<literal style=\"latex\">?</literal>")
>> ("h" "#+begin_html\n?\n#+end_html"
>> "<literal style=\"html\">\n?\n</literal>")
>> ("H" "#+html:"
>> "<literal style=\"html\">?</literal>")
>> ("a" "#+begin_ascii\n?\n#+end_ascii")
>> ("A" "#+ascii:")
>> ("i" "#+index:?" "#+index: ?")
>> ("I" "#+include%file ?"
>> "<include file=%file markup=\"?\">"))))
>> #+END_SRC
>>
>>
>> --
>> cheers,
>> Thorsten
>>
>>
next prev parent reply other threads:[~2014-06-08 20:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-07 19:55 Is <s TAB supposed to expand into upper case #+BEGIN_SRC? Grant Rettke
2014-06-07 20:37 ` Thorsten Jolitz
2014-06-07 20:39 ` Thorsten Jolitz
2014-06-07 21:44 ` Grant Rettke
2014-06-08 20:04 ` Grant Rettke [this message]
2014-06-08 21:29 ` Thorsten Jolitz
2014-06-09 0:05 ` Grant Rettke
2014-06-09 4:15 ` Nick Dokos
2014-06-09 21:25 ` Grant Rettke
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 \
--in-reply-to=CAAjq1meuLfbV0DyYjLDD13eA3Wzebu8a8YiomY2Rk8SOHegOSA@mail.gmail.com \
--to=gcr@wisdomandwonder.com \
--cc=emacs-orgmode@gnu.org \
--cc=tjolitz@gmail.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public 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).