emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tom Tobin <korpios@korpios.com>
To: emacs-orgmode@gnu.org
Subject: Re: begin_src problems
Date: Mon, 18 May 2009 23:55:28 -0500	[thread overview]
Message-ID: <bf0b20a90905182155g7361d0cfh7379d82742d65684@mail.gmail.com> (raw)
In-Reply-To: <87pre5wzo8.fsf@stats.ox.ac.uk>

On Mon, May 18, 2009 at 10:15 PM, Dan Davison <davison@stats.ox.ac.uk> wrote:
> Tom Tobin <korpios@korpios.com> writes:
>> Hmm ... C-c ' now works only if the block is flush with the left
>> margin.  Is this intentional?
> Yes, it's intentional. The # has to be the first character on the
> line. It's the same with the other org syntax which starts #+.

Ahh, that explains it.  It looks kind of odd not indented like the
rest of the content under a header, which is probably what threw me

>> Org-mode tries to align it with the
>> header it falls under, which seems "right" to me.  The block still
>> doesn't get the org-code face either way (although the "#+BEGIN_SRC
> Not quite sure what you mean by 'org-code' face. The source code gets
> fontified, in a different buffer, when you hit C-c ' (fontification is
> according to the language major mode specified in the header,
> i.e. html-mode in your example). Does this happen for you? The code in
> the original org buffer never gets fontified according to language. It
> used to be the case that nothing much happened to it, but if you are
> using bleeding-edge org from today's commits then it is subject to some
> different magic.

Yes, that happens for me (now that I have it left-flushed); I think my
expectation was that the lines between the #+ lines would become light
gray, like lines starting with ": " (colon-space) do (by default,

Thanks, though!

      reply	other threads:[~2009-05-19  4:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19  0:23 begin_src problems Tom Tobin
2009-05-19  0:47 ` Dan Davison
2009-05-19  2:32   ` Tom Tobin
2009-05-19  3:15     ` Dan Davison
2009-05-19  4:55       ` Tom Tobin [this message]

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:

  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=bf0b20a90905182155g7361d0cfh7379d82742d65684@mail.gmail.com \
    --to=korpios@korpios.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).