emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dan Davison <davison@stats.ox.ac.uk>
To: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: org-edit-src-code font lock problem
Date: Tue, 05 May 2009 10:17:36 -0400	[thread overview]
Message-ID: <87y6tbvdkv.fsf@stats.ox.ac.uk> (raw)
In-Reply-To: <D262C765-BBC0-4042-8944-BBD2CB3AB6B7@gmail.com> (Carsten Dominik's message of "Tue, 5 May 2009 14:46:09 +0200")

Carsten Dominik <carsten.dominik@gmail.com> writes:

> Hi Dan,
>
> On Apr 29, 2009, at 9:23 PM, Dan Davison wrote:
>
>> 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.
>
> Hmmm, this is a serious problem................. time passing ......
> OK, I have addressed it by using not a narrowed indirect buffer to
> edit these snippets, but a truly separate buffer. 

Great, thanks.

> Thanks for the report.
>
>>
>> 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?
>
> Which one do you mean?  The message in the echo area (last line of
> the frame), or the one appearing permanently in the first line of
> the buffer window?

The permanent one in the first line. 

>
> And which other cases of messages did you have in mind?

None at the moment! I just thought, seeing as the header is used to give
a help message by org-edit-src-code, it might be worth introducing a
mechanism whereby one can choose between two "levels" of help
messages. I didn't mean to give the impression that I had several things
I wanted to change.

>
> I am not sure if I understand how these are bothering you.

I admit this is a personal and mainly aesthetic preference -- once I've
learned how to use it and the relevant key binding, I prefer to have
(the option to have) a screen free from content other than the minimum
necessary (the echo area will still provide the information). I'm
guessing that quite a few org users have dispensed with the emacs menu
bar (and scroll bars), and was thinking that the proposed option might
appeal to those sorts of people.

Dan

p.s. I think the docstring in org-edit-src-code needs updating to
reflect the change.

>
> - Carsten
>
>
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Remember: use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2009-05-05 14:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-29 19:23 org-edit-src-code font lock problem Dan Davison
2009-05-05 12:46 ` Carsten Dominik
2009-05-05 14:17   ` Dan Davison [this message]
2009-05-05 16:15     ` Carsten Dominik

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=87y6tbvdkv.fsf@stats.ox.ac.uk \
    --to=davison@stats.ox.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    /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).