Same problem here -- seeing mistakes in latex/pdf generation.
i
On Tue, Nov 29, 2022 at 1:27 PM Dominik Schrempf
wrote:
>
> Hi!
>
> I wanted to chime in here, because sometimes I do have a similar
> problem.
>
> Whenever I export to LaTeX + PDF, it is pretty difficult to see if the
> compilation
from is impossible, if the language
even supports #line and #file directives (Rust still doesn't).
Immanuel Litzroth
On Wed, Aug 31, 2022 at 6:38 PM Martin Jerabek wrote:
>
> Hi!
>
> I recently started to use Org Babel for C++ programs. One of the programs
> outputs several lines
It's possible to let tangling generate comments that will link back to the
literate file where you defined the function.
https://orgmode.org/manual/Extracting-Source-Code.html
See the comment header arg.
Then you could advise the relevant functions that do emacs function lookup
to check whether
Just going by what I see, not having tried it:
(setq haskell-process-args-stack-ghci (list "--ghci-options"
"-XFlexibleContexts"))
In your version the process gets 1 argument (with a space in it). In
my version it gets 2 args.
Immanuel
On Thu, Jan 20, 2022 at 8:22 PM Roger Mason wrote:
>
>
You can set the delimiters used for noweb code.
org-babel-noweb-wrap-end and org-babel-noweb-wrap-end.
I think I set them to @@ in shell code.
Immanuel
On Thu, Nov 25, 2021 at 7:41 PM Łukasz Stelmach wrote:
>
> Hi,
>
> Is there anything I may try to stop shell syntax hihgliting in code
> blocks
You can choose which delimiters signal noweb.
see the documentation of org-babel-noweb-wrap-start and
org-babel-noweb-wrap-end.
Immanuel
On Mon, Mar 22, 2021 at 5:35 PM Sebastian Miele
wrote:
>
> Hello!
>
> The noweb syntax seems to clash with the syntax of here documents in
> shell scripts. In
d control over where and how the changes are made.
>
> --Diego
>
>
> On Mon, Jan 4, 2021 at 3:51 PM Immanuel Litzroth
> wrote:
>>
>> There's that, but you're not gonna do much with that since it is
>> global to emacs. If you're brimming
>> with vigour you
Immanuel Litzroth
wrote:
>
> Well I solved the problem by writing a tangler which can be configured
> with tangle-config
> you define a tangler by making a hash "language" -> tangle-hooks. The
> tangle-hooks are
> called at beginning of tangling, on each source block, on
ed programming/tangling when I
find the time.
Immanuel
On Mon, Jan 4, 2021 at 4:11 PM Diego Zamboni wrote:
>
> Agree. It should be possible to make the hook file-local, but still it's not
> trivial to have good control over where and how the changes are made.
>
> --Diego
>
>
is mentioned at
> https://orgmode.org/manual/Extracting-Source-Code.html#Hooks-3
>
> --Diego
>
>
>
>
>
> On Fri, Jan 1, 2021 at 1:31 PM Immanuel Litzroth
> wrote:
>>
>> I don't think there is an arg for that. I have written a tangler that
>> reuses
I don't think there is an arg for that. I have written a tangler that
reuses a lot
of the org-babel machinery and has a more flexible mechanism to decide what
to do with the tangled code -- I use it for example to not write a
tangled file if it
hasn't changed, meaning that it will not trigger
kell made with their REPL and babel really can't do much about it, I
> suppose. The Haskell .lhs literate option is interesting. Yes, I'd like to
> see your tangle option, please.
>
> On Thu, Dec 10, 2020 at 4:28 AM Immanuel Litzroth
> wrote:
>>
>> I don't think org-babel
I don't think org-babel is a good fit for compiled languages. If the
idea is to just take 1 snippet,
and "execute" that it means that to have a consistent whole you'd need
to put all the modules of
your program into that snippet (already impossible in Haskell, you can
have only 1 module per file),
c".
Weren't there supposed to be maintainers for this stuff? Has no plantuml
maintainer been found?
Immanuel
On Mon, Nov 23, 2020 at 11:28 AM Heinz Tuechler wrote:
>
> Immanuel Litzroth wrote/hat geschrieben on/am 15.11.2020 13:27:
> > (defun org-babel-plantuml-make-body
(defun org-babel-plantuml-make-body (body params)
"Return PlantUML input string.
BODY is the content of the source block and PARAMS is a property list
of source block parameters. This function relies on the
`org-babel-expand-body:generic' function to extract `:var' entries
from PARAMS and on
I think the org way of tangling just doesn't work well for compiled languages.
Here are some reasons:
- Not possible to tangle all code going to a specified file
- Not possible to add line directives without major surgery
- Not all language modes do the correct thing
- No way to prevent
You want me to do that and send a new patch or are you going
to do it after you apply the patch?
Regards,
Immanuel
On Mon, Sep 2, 2019 at 9:41 PM Nicolas Goaziou wrote:
>
> Hello,
>
> immanuel writes:
>
> > When org-edit-src-code is called with org-window-setup equal to
> > 'split-window-below
No problem! I have some more coming up :-)
I've been looking at getting org-babel to add line directives for
languages that support it.
(c, c++, haskell...). It would make literate programming for these
kinds of languages much
better, and other people have been complaining e.g.
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
19 matches
Mail list logo
