From: Thierry Banel <tbanelwebmin@free.fr>
To: emacs-orgmode@gnu.org
Subject: Re: babel: ob-C with Visual C++ and compilation-mode
Date: Mon, 11 Aug 2014 21:40:34 +0200 [thread overview]
Message-ID: <53E91C32.4000002@free.fr> (raw)
In-Reply-To: <878un4ut6c.fsf@gmail.com>
Le 04/08/2014 18:16, Ernesto Durante a écrit :
> One suggestion. It will be nice to put the error buffer in
> compilation-mode, this way errors are highlighted and we can jump
> directly into the source code. I modified org-babel-eval to launch the
> compilation mode in case of errors. I also removed the read-only
> attribute, else the buffer content of org-babel-error-buffer-name cannot
> be erased.
The compilation mode is a very good idea !
I tried it.
>
> Clearly, it's not a good patch because org-babel-eval seems to be
> a core function in babel. Maybe for ob-C, this function should be
> replaced by a new function.
It works well for C++, D, Dot
It fails for Perl, R, Elisp
But when it fails, it does not do any harm: the behavior is as before.
So... I vote for your patch.
> Thanks to everyone for orgmode and babel to exist.
>
> Best
> Ernesto
>
>
next prev parent reply other threads:[~2014-08-11 19:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 16:16 babel: ob-C with Visual C++ and compilation-mode Ernesto Durante
2014-08-11 19:40 ` Thierry Banel [this message]
2014-08-12 14:24 ` Ernesto Durante
2014-08-12 22:03 ` Thierry Banel
2014-08-13 20:58 ` Ernesto Durante
2014-08-14 20:40 ` Thierry Banel
2014-08-15 17:22 ` Ernesto Durante
2014-08-17 11:20 ` Thierry Banel
2014-08-18 11:19 ` Ernesto Durante
2014-08-18 12:51 ` Eric Schulte
2014-08-24 13:05 ` Ernesto Durante
2014-08-28 14:02 ` Eric Schulte
2014-08-18 19:59 ` Thierry Banel
2014-08-20 20:40 ` Ernesto Durante
2014-08-21 19:48 ` Thierry Banel
2014-08-24 12:57 ` Ernesto Durante
2014-08-28 19:44 ` Thierry Banel
2014-08-18 2:41 ` Eric Schulte
2014-08-18 2:40 ` Eric Schulte
2014-08-23 11:03 ` Ernesto Durante
2014-08-25 16:35 ` [PATCH] " Ernesto Durante
2014-08-28 14:46 ` Eric Schulte
2014-09-10 9:27 ` Achim Gratz
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=53E91C32.4000002@free.fr \
--to=tbanelwebmin@free.fr \
--cc=emacs-orgmode@gnu.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).