From: Vladimir Nikishkin <firstname.lastname@example.org>
To: Kyle Meyer <email@example.com>
Subject: Re: Specifying the execution function and/or nested major mode for babel blocks
Date: Mon, 27 Apr 2020 12:32:21 +0800 [thread overview]
Message-ID: <CA+A2iZYwvv9rQEBKS6i87TYOS=x-pgrE9PD_UM2foSvquLVZzQ@mail.gmail.com> (raw)
>> (add-to-list 'org-src-lang-modes '("f90" . fortran))
Language alignment is fine. What needs to be done is to make org-babel
use org-babel-execute:fortran for both begin_src fortran, and for
пн, 27 апр. 2020 г. в 12:12, Kyle Meyer <firstname.lastname@example.org>:
> Vladimir Nikishkin <email@example.com> writes:
> > This is fine most of the time, however, there are exceptions.
> > The one I am interested in is fortran/f90. There are separate
> > fortran-mode and f90-mode, however, afaiu, just a single
> > ob-fortran.el, which works fine with both of those.
> In that case, you'd just need (fortran . t) in org-babel-load-languages,
> I think.
> > #+begin_src fortran
> > #+end_src
> > or turns on syntax highlighting for fortran-mode, not for f90-mode.
> > I can make blocks like:
> > #+begin_src f90
> > #+end_src
> > This makes syntax highlighting work, but evaluation doesn't, because
> > org doesn't know that f90 and fortran have the same evaluation
> > (compilation) function.
> > I feel that this is a super minor thing that can be solved in, like,
> > one line of code. But I don't seem to be able to find which one.
> > Any suggestions?
> Perhaps you're looking for org-src-lang-modes? This (untested) might do
> what you want:
> (add-to-list 'org-src-lang-modes '("f90" . fortran))
Yours sincerely, Vladimir Nikishkin
next prev parent reply other threads:[~2020-04-27 4:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 3:54 Specifying the execution function and/or nested major mode for babel blocks Vladimir Nikishkin
2020-04-27 4:12 ` Kyle Meyer
2020-04-27 4:32 ` Vladimir Nikishkin [this message]
2020-04-27 16:33 ` Kyle Meyer
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).