emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [bug] Tangling a LaTeX code block creates a .latex file
Date: Thu, 30 Jan 2014 11:05:00 +0100	[thread overview]
Message-ID: <86txcliy43.fsf@somewhere.org> (raw)
In-Reply-To: 87d2jacoc4.fsf@bzg.ath.cx

Hi Bastien,

Bastien wrote:
> "Sebastien Vauban" writes:
>
>> This one is quite new: tangling a code block in `latex' language now
>> produces a file with a `.latex' extension, instead of the common
>> `.tex' extension.
>
> AFAIU you need to (require 'ob-latex) first.

I never did that explicitly.

But, doing it does effectively solve the problem at hand.

> Could you say since when you get this error, since obviously it worked
> before

The last time I tangled such an Org file containing `latex' code blocks
and generating (at that time) a `file.tex' was on 2014-01-13.

> and you didn't change your setup wrt this?

So did I think. Though, I had to edit `org-babel-load-languages' to
support Org installations with the latest Git version and Org
installations with the latest ELPA version:

--8<---------------cut here---------------start------------->8---
    (if (locate-library "ob-shell")     ; ob-sh renamed on Dec 13th, 2013
        (org-babel-do-load-languages
         'org-babel-load-languages
         '((R          . t)
           (awk        . t)
           (ditaa      . t)
           (dot        . t)
           (emacs-lisp . t)
           ;; (latex   . t)
           (ledger     . t)
           (org        . t)
           (shell      . t)
           (sql        . t)))
      (org-babel-do-load-languages
       'org-babel-load-languages
       '((R          . t)
         (awk        . t)
         (ditaa      . t)
         (dot        . t)
         (emacs-lisp . t)
         ;; (latex   . t)
         (ledger     . t)
         (org        . t)
         (sh         . t)
         (sql        . t))))
--8<---------------cut here---------------end--------------->8---

... and I did comment `latex', thinking that, in such cases, I should
certainly use #+begin/end_latex blocks instead.

In the file I tangled, this wasn't the case.

So, yes, I did change something, which lead to some peculiar
observation.

Thanks for putting me right on track!

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2014-01-30 10:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-29 20:19 [bug] Tangling a LaTeX code block creates a .latex file Sebastien Vauban
2014-01-30  0:20 ` Bastien
2014-01-30 10:05   ` Sebastien Vauban [this message]
2014-01-30 10:40     ` Bastien
2014-01-30 10:40 ` Julian Gehring
2014-01-30 10:43   ` Bastien

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=86txcliy43.fsf@somewhere.org \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).