From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Davison Subject: org-edit-src-code font lock problem Date: Wed, 29 Apr 2009 15:23:24 -0400 Message-ID: <87bpqf5knn.fsf@stats.ox.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LzFNT-0003UL-RY for emacs-orgmode@gnu.org; Wed, 29 Apr 2009 15:23:31 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LzFNT-0003U7-AF for emacs-orgmode@gnu.org; Wed, 29 Apr 2009 15:23:31 -0400 Received: from [199.232.76.173] (port=54480 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LzFNT-0003U4-7M for emacs-orgmode@gnu.org; Wed, 29 Apr 2009 15:23:31 -0400 Received: from markov.stats.ox.ac.uk ([163.1.210.1]:65095) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LzFNS-0001Hq-Ab for emacs-orgmode@gnu.org; Wed, 29 Apr 2009 15:23:30 -0400 Received: from blackcap.stats.ox.ac.uk (blackcap.stats [163.1.210.5]) by markov.stats.ox.ac.uk (8.13.6/8.13.6) with ESMTP id n3TJNRZv012514 for ; Wed, 29 Apr 2009 20:23:27 +0100 (BST) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs org-mode mailing list I'm finding that the font-lock in the indirect buffer spawned by C-c ' on a source code block is not correct when there is a preceding (odd number of) apostrophes / backticks etc (depending on the language). E.g. * this works fine as there is no apostrophe #+begin_src sh for i in $(seq -w 1 22) ; do echo $i done #+end_src * but this doesn't work correctly because of the single-quote / apostrophe #+begin_src sh for i in $(seq -w 1 22) ; do echo $i done #+end_src The second example thinks it's in a single-quote-delimited string. org-version 6.26trans emacs-version 23.0.91.1 Dan p.s. A minor wish-list item: would it be possible to introduce a variable (say org-expert or something like that) which, when non-nil, prevents the appearance of instructive messages such as the one that appears on org-edit-src-code?