From: Rainer M Krug <r.m.krug@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Rainer@krugs.de, emacs-orgmode <emacs-orgmode@gnu.org>,
Jambunathan K <kjambunathan@gmail.com>
Subject: Re: "Generic" Source block language specification?
Date: Sun, 25 Nov 2012 16:28:45 +0100 [thread overview]
Message-ID: <50B2392D.6030201@gmail.com> (raw)
In-Reply-To: <87sj7y4jbe.fsf@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 25/11/12 01:28, Nicolas Goaziou wrote:
> Hello,
>
> Jambunathan K <kjambunathan@gmail.com> writes:
>
>> 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.
>>
>> Marking the src block as `fundamental' has a drawback. One can no longer have in-buffer
>> fontification of src blocks.
>>
>> A better option would be to have a custom variable which produces black-and-white src blocks
>> on export.
>>
>> ODT already has this option.
>>
>> C-h v org-e-odt-fontify-srcblocks RET
>>
>> I am CCing Nicolas, to check whether he would be interested in introducing an export knob for
>> this.
>
> I still don't get what is wrong with example blocks (wrt export). Would someone care to
> elaborate?
Yes.
In a document, I have several source blocks with "real" code (i.e. bash and R in this case) Now I
have one block, which is not really source code, but which is "kind of" source code, in my case a
definition of a projection for a GIS project. Now I would like to have this definition of the
projection displayed in the exported document as the other source blocks, If I put it into an
EXAMPLE block, it is exported to LaTeX as verbatin and not listing, and all customisations ai have
for listings (smaller font, grey background, ...) do *not* apply to the EXAMPLE block, but woyuld
to a "fundamental" source block. So the EXAMPLE block is in this case not equivalent to the
fundamental source block.
Hope this clarifies the difference,
Cheers,
Rainer
>
>
> Regards,
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iEYEARECAAYFAlCyOSUACgkQoYgNqgF2egrxdACeKk1/9hvuGv4PGEj9EAXipjOK
CW8An0KJAUM0ejDcy9n1Gq2jxEHkvmZp
=oKbK
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-11-25 15:28 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
2012-11-23 18:11 ` Jambunathan K
2012-11-25 0:28 ` Nicolas Goaziou
2012-11-25 15:28 ` Rainer M Krug [this message]
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=50B2392D.6030201@gmail.com \
--to=r.m.krug@gmail.com \
--cc=Rainer@krugs.de \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@gmail.com \
--cc=n.goaziou@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).