From: Nick Dokos <nicholas.dokos@hp.com>
To: Rainer M Krug <r.m.krug@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
Eric Schulte <schulte.eric@gmail.com>
Subject: Re: "Generic" Source block language specification?
Date: Fri, 23 Nov 2012 12:35:52 -0500 [thread overview]
Message-ID: <18033.1353692152@alphaville> (raw)
In-Reply-To: Message from Rainer M Krug <r.m.krug@gmail.com> of "Fri, 23 Nov 2012 16:26:27 +0100." <50AF95A3.7080109@gmail.com>
Rainer M Krug <r.m.krug@gmail.com> wrote:
> On 23/11/12 16:02, Eric Schulte wrote:
> > Rainer M Krug <r.m.krug@gmail.com> writes:
> >
> >> On 23/11/12 00:17, Eric Schulte wrote:
> >>> Rainer M Krug <r.m.krug@gmail.com> writes:
> >>>
> >>>> Hi
> >>>>
> >>>> I have in a document a definition of a projection, which is essentially a text as
> >>>> follow:
> >>>>
> >>>> #+BEGIN_src +proj=aea +lat_1=-28.25 +lat_2=-29.75 +lat_0=29 +lon_0=30.75 +x_0=0 +y_0=0
> >>>> +datum=WGS84 +units=m +no_defs #+END_src
> >>>>
> >>>> Now this does obviously not export, as the source block language is missing. Is there a
> >>>> way that I can get the same formating of the source in the exportes output but without
> >>>> the syntax highlighting?
> >>>>
> >>>> BEGIN_EXAMPLE END_EXAMPLE
> >>>>
> >>>> is similar, but I would like the block to be formated as the SRC blocks.
> >>>>
> >>>
> >>> I bet "fundamental" would work, e.g.,
> >>
> >> Yes, it does - works perfectly. Is this documented?
> >>
> >
> > Yes. Whatever language string is placed at the top of the source block will define the mode
> > used for export and in-block editing. I believe that is documented.
>
> OK - then I thought that I can use all languages *for formating* which are defined in the listings
> package in LaTeX, but it doesn't matter what I take: it always formats it in as a source block but
> obviously without syntax highlighting.
>
> For editing: C-c ' only works ehen using "fundamental" - other non-existent languages are not
> accepted (obviously).
>
> So I assume in org, there is support for "fundamental", but I could not find it in the
> documentation when I looked.
>
> At the moment, my org info documentation seems to be not accessible (blank page when opening it).
>
In order for this to work, emacs has to have a mode to handle it:
"fundamental" as a language works, because emacs has a mode called
fundamental-mode.
I append the relevant portion of the documentation (section 14.2,
Editing source code) I hope it comes in useful until you get your info
problems resolved, but note that it's also available online at
http://orgmode.org/org.html#Editing-source-code
See org-src-lang-modes below for the details:
,----
|
| 14.2 Editing source code
| ========================
|
| Use `C-c '' to edit the current code block. This brings up a language
| major-mode edit buffer containing the body of the code block. Saving
| this buffer will write the new contents back to the Org buffer. Use
| `C-c '' again to exit.
|
| The `org-src-mode' minor mode will be active in the edit buffer. The
| following variables can be used to configure the behavior of the edit
| buffer. See also the customization group `org-edit-structure' for
| further configuration options.
|
| `org-src-lang-modes'
| If an Emacs major-mode named `<lang>-mode' exists, where `<lang>'
| is the language named in the header line of the code block, then
| the edit buffer will be placed in that major-mode. This variable
| can be used to map arbitrary language names to existing major
| modes.
|
| `org-src-window-setup'
| Controls the way Emacs windows are rearranged when the edit buffer
| is created.
|
| `org-src-preserve-indentation'
| This variable is especially useful for tangling languages such as
| Python, in which whitespace indentation in the output is critical.
|
| `org-src-ask-before-returning-to-edit-buffer'
| By default, Org will ask before returning to an open edit buffer.
| Set this variable to nil to switch without asking.
|
| To turn on native code fontification in the _Org_ buffer, configure
| the variable `org-src-fontify-natively'.
|
`----
HTH,
Nick
next prev parent reply other threads:[~2012-11-23 17:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 14:08 "Generic" Source block language specification? Rainer M Krug
2012-11-22 23:17 ` Eric Schulte
2012-11-23 8:17 ` Rainer M Krug
2012-11-23 15:02 ` Eric Schulte
2012-11-23 15:26 ` Rainer M Krug
2012-11-23 16:40 ` Eric Schulte
2012-11-23 17:35 ` Nick Dokos [this message]
2012-11-23 18:11 ` Jambunathan K
2012-11-25 0:28 ` Nicolas Goaziou
2012-11-25 15:28 ` Rainer M Krug
2012-11-25 15:37 ` Nicolas Goaziou
2012-11-25 16:01 ` Rainer M Krug
2012-11-25 16:03 ` Rainer M Krug
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=18033.1353692152@alphaville \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=r.m.krug@gmail.com \
--cc=schulte.eric@gmail.com \
/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).