Re: Best way to extract info from C files?

Thanks! I'm looking into tree-sitter now just to learn how it works :) On Tue, Feb 20, 2024 at 3:01 AM Ihor Radchenko wrote: > > Stefano Ghirlanda writes: > > > I'm trying to build a simple code documentation tool for org-mode, so > > I'm looking for ways to get information from C files (to begi

Re: [BUG] beamer export

On Mon, Feb 19 2024, Ihor Radchenko wrote: > Leo Butler writes: > >>> What about not adding BEAMER_FRAME, but instead adding org-lint checker >>> that will detect when frame text contains the problematic \end{orgframe}? >> >> Ok, thanks for your feedback. I have modified the patch along the line

[proof of concept] inline language blocks

Hi, I'm dedicating a local branch to developing this proof of concept and testing it in my workflow, so far with good results. The basic idea is to provide Org with multilingual features and various methods for selecting languages. The inline-language-block is intended for small segments of text

Re: Asynchronous blocks for everything (was Re: [BUG] Unexpected result when evaluating python src block asynchronously [9.7-pre (release_9.6.17-1131-gc9ed03.dirty @ /home/yantar92/.emacs.d/straight/b

Matt writes: > AFAIK, aside from appending "&", =make-process= is the only way. It would > probably make sense to continue using =shell= though. If I understand > correctly, you (and others) jump between the Org buffer block and the comint > buffer? Yes, I typically use ob-R and ob-python i

Re: Asynchronous blocks for everything (was Re: [BUG] Unexpected result when evaluating python src block asynchronously [9.7-pre (release_9.6.17-1131-gc9ed03.dirty @ /home/yantar92/.emacs.d/straight/b

On Tue, Feb 20, 2024 at 11:00:28AM +, Ihor Radchenko wrote: > writes: [...] > > You "just" [1] need a way of stating dependencies :-) [...] > Let's not jump into this rabbit hole yet before we have async code > working for less complicated scenarios. :-) My take is: it's never too early

Re: Best way to extract info from C files?

Stefano Ghirlanda writes: > I'm trying to build a simple code documentation tool for org-mode, so > I'm looking for ways to get information from C files (to begin with, > ideally it will be easy to add other languages). Things like function > prototypes, struct definitions, etc. What would be the

Re: Asynchronous blocks for everything (was Re: [BUG] Unexpected result when evaluating python src block asynchronously [9.7-pre (release_9.6.17-1131-gc9ed03.dirty @ /home/yantar92/.emacs.d/straight/b

writes: >> Doing everything asynchronously is not always desired. >> Consider, for example, >> >> #+begin_src bash >> echo "Contents" > /tmp/tmpfile >> #+end_src bash >> >> #+begin_src bash >> cat /tmp/tmpfile # I must run after /tmp/tmpfile is created! >> #+end_src > > You "just" [1] need a wa

Re: Asynchronous blocks for everything (was Re: [BUG] Unexpected result when evaluating python src block asynchronously [9.7-pre (release_9.6.17-1131-gc9ed03.dirty @ /home/yantar92/.emacs.d/straight/b

On Tue, Feb 20, 2024 at 10:28:06AM +, Ihor Radchenko wrote: > Matt writes: > > > The blub implementation has the same shortcomings, at least for shells, as > > the current shell implementation. It has a few ideas, such as everything > > being asynchronous and completely removing the prompt

Re: Asynchronous blocks for everything (was Re: [BUG] Unexpected result when evaluating python src block asynchronously [9.7-pre (release_9.6.17-1131-gc9ed03.dirty @ /home/yantar92/.emacs.d/straight/b

Matt writes: > The blub implementation has the same shortcomings, at least for shells, as > the current shell implementation. It has a few ideas, such as everything > being asynchronous and completely removing the prompt, that may prove useful > for improving Babel generally. The blub implem

Re: Asynchronous blocks for everything (was Re: [BUG] Unexpected result when evaluating python src block asynchronously [9.7-pre (release_9.6.17-1131-gc9ed03.dirty @ /home/yantar92/.emacs.d/straight/b

Matt writes: > - Anything I could help with? https://github.com/tecosaur/org-latex-preview-todos/issues/21 It looks like the main remaining blocker is the lack of LaTeX snippet export for ox-odt. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at

Re: [BUG]: elusive vertical white-space errors in engraved source block export

gerard.vermeu...@posteo.net writes: > attached you'll find a pdf file showing the elusive vertical white-space > errors > using the engraved source block export backend that I demonstrated > yesterday > evening. Confirmed. Easier steps to reproduce (with engraved installed): 1. In Org git repo