From: Eric S Fraga <firstname.lastname@example.org> To: "Sébastien Vauban" <email@example.com> Cc: firstname.lastname@example.org Subject: Re: Re: org-src-fontify-natively makes things very, very slow Date: Sat, 19 Mar 2011 20:34:58 +0000 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> (=?utf-8?Q?=22S=C3=A9bastien?= Vauban"'s message of "Sat, 19 Mar 2011 10:20:00 +0100") Sébastien Vauban <email@example.com> writes: > Hi Eric, > > Eric S Fraga wrote: [...] >> where there is no matching #+end_src or, more precisely, the next #+end_src >> line is one that does not belong to this current source block. Your search >> (in org.el) for the end of the block assumes that it does have the end >> statement in place already. I'm not sure how to fix this because it's an >> ill-defined situation. > > You say "your search..." but I only added the overlay-put command... and I > must admit this whole block is difficult to follow (so many cases). Yes but the overlay needs to know where to end; I am using search in a more general sense here in that you are defining the start and end of a region to overlay using regular expressions, are you not? [...] >> 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: yes, I used to use yasnippet a lot but I don't any longer. I am actually in confusion as to which completion mechanism to use in Emacs these days and am going a little crazy... :( I'm currently playing with auto-complete. Thanks, eric -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 188.8.131.52 : using Org-mode version 7.5 (release_7.5.83.g1bd87.dirty)
next prev parent reply other threads:[~2011-03-19 20:35 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-17 13:59 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 2011-03-19 20:37 ` Eric S Fraga 2011-03-19 20:34 ` Eric S Fraga [this message] 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Re: org-src-fontify-natively makes things very, very slow' \ /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).