From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: org-src-fontify-natively makes things very, very slow
Date: Sat, 19 Mar 2011 05:28:42 -0700 [thread overview]
Message-ID: <AANLkTi=n7aryDurNc5FTA3ikxjoGaOUZw68rHn1_xFHU@mail.gmail.com> (raw)
In-Reply-To: <80fwqjqxfj.fsf@somewhere.org>
2011/3/19 Sébastien Vauban <wxhgmqzgwmuf@spammotel.com>:
>> My solution, by the way, is to insert the #+end_src line immediately upon
>> writing a #+begin_src line and then back up a line to start writing the
>> code.
>
> "My" solution is even simpler: just use a yasnippet template, that prompts you
> for the language and puts the begin/end upfront:
Or use org's own template mechanism[fn:1],
1. <s - for source blocks
2. <e - for example blocks
and so on ...
Footnotes:
[fn:1] [[info:org#Easy%20Templates][info:org#Easy Templates]]
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2011-03-19 12:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 13:59 org-src-fontify-natively makes things very, very slow Julian Burgos
2011-03-17 18:28 ` Eric S Fraga
2011-03-17 20:34 ` Sébastien Vauban
2011-03-18 0:11 ` Julian Burgos
2011-03-18 8:38 ` Eric S Fraga
2011-03-18 12:44 ` Julian Burgos
2011-03-19 9:20 ` Sébastien Vauban
2011-03-19 12:28 ` suvayu ali [this message]
2011-03-19 20:37 ` Eric S Fraga
2011-03-19 20:34 ` Eric S Fraga
2011-03-20 4:23 ` Le Wang
2011-03-20 19:41 ` Eric S Fraga
2011-03-21 2:37 ` Le Wang
2011-03-21 13:57 ` Eric Schulte
2011-03-21 17:06 ` Eric S Fraga
2011-03-21 22:23 ` Sébastien Vauban
2011-03-22 9:18 ` Ulf Stegemann
2011-03-29 14:49 ` Matt Lundin
2011-03-29 16:49 ` Eric S Fraga
2011-03-30 7:34 ` Sébastien Vauban
2011-04-28 20:59 ` Carsten Dominik
2011-04-28 23:32 ` Eric S Fraga
2011-04-30 19:45 ` Eric S Fraga
2011-05-01 13:37 ` Carsten Dominik
2011-03-29 14:12 ` Matt Lundin
2011-03-29 16:44 ` Eric S Fraga
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='AANLkTi=n7aryDurNc5FTA3ikxjoGaOUZw68rHn1_xFHU@mail.gmail.com' \
--to=fatkasuvayu+linux@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.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).