From: Dan Davison <email@example.com>
To: Tom Tobin <firstname.lastname@example.org>
Subject: Re: begin_src problems
Date: Mon, 18 May 2009 23:15:51 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Tom Tobin's message of "Mon, 18 May 2009 21:32:56 -0500")
Tom Tobin <email@example.com> writes:
> On Mon, May 18, 2009 at 7:47 PM, Dan Davison <firstname.lastname@example.org> wrote:
>> Tom Tobin <email@example.com> writes:
>>> I'm having some issues using #+BEGIN_SRC; doing the following doesn't
>>> seem to use the org-code face, and doesn't seem to work correctly with
>>> "C-c i":
>> C-c i is undefined with my setup. Did you mean C-c '?
> Yeah, sorry; I meant C-c '.
>>> #+BEGIN_SRC html-mode
>> I think you want #+BEGIN_SRC html. Then it works for me.
> 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 #+.
> 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
> html" and "#+END_SRC" gets their own face if the block is against the
> left margin).
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
next prev parent reply other threads:[~2009-05-19 3:16 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 [this message]
2009-05-19 4:55 ` Tom Tobin
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 \
* 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).