Thorsten Jolitz writes:
Hi Thorsten,
Great package. Thanks for all your explanation.
Ernesto
> Are you aware of navi-mode.el?
>
> It does exactly this - put the overview (-> content) in a second
> window next to the details (-> showall). Only that the overview is a
> *Navi* buffer that is
>
>
Florian Knupfer writes:
> Hello,
>
> I've written a function that enables a three pane view on org files.
> I'm quite new to emacs but I'd like to contribute and receive
> feedbacks, improvement etc.
>
> It can be found at:
> https://github.com/knupfer/org-panes
>
> Best regards
very good and i
+ Third patch, add to ob-C the missing function org-babel-expand-body:cpp
Best
Ernesto
>From 3e4f163a2b357c58a52b7811539ff4032d432aaf Mon Sep 17 00:00:00 2001
From: Ernesto Durante
Date: Mon, 25 Aug 2014 17:27:24 +0200
Subject: [PATCH 1/3] org-babel-eval: compilation-mode to deal with errors
Eric Schulte writes:
> Ernesto Durante writes:
>
> Perhaps a new header argument should be added for C-Family languages
> which will inhibit this main wrapping behavior?
>
> -- Eric
Hi Eric,
According to me, we can already inhibit the wrapping with the following
header :
Thierry Banel writes:
> Le 20/08/2014 22:40, Ernesto Durante a écrit :
>
> as the source org file is not guarantied to be in utf-8.
>
> You may want to give it a try an provide a patch for that.
> 3 files are involved:
> - lisp/ob-C.el (you know this one)
> - testing/lisp
Eric Schulte writes:
> Hi Ernesto,
>
> This looks like a good change and I'd like to apply it. Could you
> re-submit this commit after doing the following.
>
> 1. ensure no lines go beyond 80 characters in length
> 2. remove all lines which include only closing parens
>(such lines are genera
Thierry Banel writes:
> You are trying to create a C++ project bigger than a few lines, in Org-mode.
> This is very close to the idea of "literate programming" from Donal Knuth.
> You may find inspiration here:
> http://orgmode.org/worg/org-contrib/babel/intro.html#literate-programming
>
> There
Thierry Banel writes:
> Le 15/08/2014 19:22, Ernesto Durante a écrit :
>
> True.
> And to achieve that the :includes header tag was added:
> #+BEGIN_SRC C++ :includes
>
> (Because otherwise a #include statement would end up in the main() function)
>
> For me thi
> Well... In this example, we go down from 9 lines to 7 lines. Ok fair.
> But the price is a new syntax to learn:
> main
> Is it wise to add an org-mode specific syntax to C++ (which already has
> a lot) ?
>
> Being noisy is a weakness of C++.
> I think it is not the responsibility of org-
Thierry Banel writes:
>> I have identified a minor bug. When a source code block has the mode
>> cpp, we cannot expand the code or more precisely the code is not
>> expanded in the correct way because the following function is missing
>>
>> (defun org-babel-expand-body:cpp (body params)
>> "E
Thierry Banel writes:
> 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 th
Hi,
I am using ob-C with gcc and Microsoft Visual C++. These two compilers
have two different behaviours for outputting errors. Gcc uses the
standard error output and Visual C++ uses the regular output.
Under Windows, errors are not displayed because of the way
org-babel-eval is coded. To work
12 matches
Mail list logo
