Ihor Radchenko writes:
> I'm afraid that trying to replicate Python REPL behavior for
> non-interactive src blocks will be beyond what we can reasonably do in
> Org: we would somehow need to detect the last statement in the src
> blocks, which may or may not span a single line; and multiline stat
Ihor Radchenko writes:
> Previously, the point was always at process-mark when BODY is
> called. Now, it may not be the case. It may cause problems.
On the one hand -- I'm not sure I agree that it would cause
problems. IMO setting point to process mark goes hand-in-hand with
cutting the dangling
On 2024-10-20 18:35 +05:30, Dr. Volker Zell wrote:
how would you do it with the export-filter mechanism of Org mode...
mayb this comes in handy later
For example, as follows.
#+title: Org Tables to DataTables
#+html_doctype: html5
#+html_head: https://code.jquery.com/jquery-3.7.1.min.js";
Cool! Thanks!
Ihor Radchenko writes:
> Nick Dokos writes:
>
>> Patch attached.
>
> Thanks!
> Applied, onto main.
> Fixed.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=8b4b89b14b
>
> I changed the docstring of the newly introduced function to follow the
> usual Elisp conventions.
Noted -
Hi
The columns.footer option of DataTables works like a charm ... but just
curious how would you do it with the export-filter mechanism of Org
mode... mayb this comes in handy later
Thx for you help
Volker
Christian Moe writes:
> It's due to Latex refusing to commit the typographic crime of leaving a
> heading at the bottom of the page.
> ...
and is committing another typographic crime :)
I am wondering if this may somehow be addressed.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn
Daniel Clemente writes:
>> May you try
>> https://git.sr.ht/~yantar92/org-mode/log/feature/org-crypt-refactor branch?
>> Is encryption speed satisfactory then?
>>
>
> This branch improved the speed of org-crypt. It's not merged yet. Is
> anything missing? You may start a new thread to discuss the
Dan Drake writes:
> I like that idea. It's consistent, uses "prior art", so to speak, and most
> of all , archiving involves cutting the subtree, so it's a very similar
> change to the buffer / structure.
I looked into doing this using a very simple variant of the command:
(defun org-cut-subtre
Phil Estival writes:
>>> ob-sql-session :
>>> - handle large results
>>> - has :results tables
>>> - accept header variables (:var)
>>> - accept sql client shell commands
>>> - keep login parameters
>>> - prompt only for blank connection parameters
>>> - can use `with-environment-variables'
>>> -
Section 4.5 [Handling Links], page 42 says:
"For Org files, if there is a '<>' at point, the link points to the
target. If there is a named block (using '#+name:') at point, the link points
to that name. Otherwise it points to the current headline, which is also the
description."
I don't unders
Nikolay Kudryavtsev writes:
> Recently I reworked some of my task workflows and now I have an agenda
> view that's all web links. Opening those with mouse is pretty natural.
>
> But every time I do, I get this warning:
>
> Warning (org-element): ‘org-element-at-point’ cannot be used in non-Org
Bruno Barbier writes:
> Ihor Radchenko writes:
>
>> Org mode fontification routines do not support multiple different
>> variants of major mode in src blocks.
>> We also cannot handle major modes prompting user when they are
>> activated.
>>
>
> In case you missed it, the workaround that solved
Hi Ihor,
Ihor Radchenko writes:
> Org mode fontification routines do not support multiple different
> variants of major mode in src blocks.
> We also cannot handle major modes prompting user when they are
> activated.
>
In case you missed it, the workaround that solved
the OP problem is:
(s
Ihor Radchenko writes:
> Bruno Barbier writes:
>
#+begin_src scheme :scheme chez
(+ 3 4)
#+end_src
and also with ':scheme racket'.
Unfortunately, it does not seem to work when exporting the document.
>
> :scheme header argument does not affect export by defau
[ Changing subject line, so that the thread is registered as a proper request
for comments ]
Charles Choi writes:
> I recently made a blog post describing a means of calculating an Org table
> reference from a selected text region or rectangle. I think this feature is
> compelling enough to p
Jack Kamm writes:
>>> So I think WORG needs to be fixed.
>>>
>>> Can you send a patch?
>>> https://git.sr.ht/~bzg/worg
>>
>> Yes, patch would be welcome.
>
> As Sebastian mentioned, Worg already documents the behavior, under the
> section "Return values":
>
> https://orgmode.org/worg/org-contrib/
Jack Kamm writes:
>> Rather than `t', I'd use something more descriptive like
>> 'disable-prompt-filtering.
>
> Is the attached patch what you had in mind? If so I will squash it with
> the previous patch.
Your variant is even better than what I had in mind.
> But first -- note that the curren
Benjamin McMillan writes:
> Granted that it is not worth changing behavior of the function, would it be
> reasonable to update the docstring? Something like
> "When optional argument FULL is t, also skip planning information,
> clocking lines, any kind of drawer, and blank lines.
> When FULL is
Ihor Radchenko writes:
>> In the org-mode documentation I read:
>>
>> For languages like Python, an explicit return statement is mandatory
>> when using ‘:results value’.
>> https://orgmode.org/manual/Results-of-Evaluation.html
>>
>> So I think WORG needs to be fixed.
>>
>> Can you send
Ihor Radchenko writes:
> I have one small nipick comment on the patch:
>
>>(org-babel-comint-async-register
>> session (current-buffer)
>> "ob_comint_async_python_\\(start\\|end\\|file\\)_\\(.+\\)"
>> - 'org-babel-chomp 'org-babel-python-async-value-callback)
>> + 'org-babel-chomp
21 matches
Mail list logo
