Ihor Radchenko writes:
> [...]
> It would make sense then to include `org-quote-vert' call into
> `org-columns--clean-item' then.
Good point. I'll move the call to `org-quote-vert' there.
> [...]
>> (defun org-columns--capture-view (maxlevel match skip-empty exclude-tags
>> format local)
>>
* etc/ORG-NEWS
(New and changed options): Describe the new option
'org-babel-lua-multiple-values-separator'.
(New features): Describe the main change, as per the title of this
commit message.
* lisp/ob-lua.el
(org-babel-lua-multiple-values-separator): Enable the user to
customize the string that
Rudolf Adamkovič writes:
> +Lua code blocks can now return values of any type and can also return
> +multiple values. Previously, values of certain types were incorrectly
> +converted to the empty string =""=, which broke HTML export for inline
> +code blocks, and multiple values were
On 23/04/2024 17:51, Max Nikulin wrote:
I am in favor of dropping `shell-command-switch' in the latter case to
pass arguments literally in both cases.
Dropping "-c" may have side effects. Instead of :shebang, a source block
may have shebang in the body
#+begin_src bash
#!/bin/bash -e
echo
Alexander Adolf writes:
>>> + (let ((search (org-link-heading-search-string
>>> raw)))
>>> +(org-link-make-string
>>> + (if (not (buffer-file-name)) search
>>> + (format "file:%s::%s"
On 23/04/2024 18:47, Ihor Radchenko wrote:
Max Nikulin writes:
There should be a way to align tags for a specific heading even when
`org-auto-align-tags' is nil.
I can convert org-align-tags into a command.
I would prefer to have C-u C-c C-q (`org-set-tags-command') applied just
to the
Org mode version 9.6.15
* CURRENT BEHAVIOR
Exporting to text fails when ~org-export-with-broken-links~ is set to ~mark~.
[[help:org-export-with-broken-links]]
The following are minimal examples using source blocks in org. I'm using an
LLM-generated function to call ~org-export-string-as~,
Jeff Trull writes:
> I notice that multiple #+PLOT lines before a table will be coalesced and
> handled as one. However, this is
> accomplished through specific code in org-plot.el that does a reverse
> search through the buffer for
> additional lines. org-element has a built-in mechanism for
Ihor Radchenko writes:
> Thanks!
> Applied, onto main.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=ff9d00c9c
Thanks for considering this.
Best, Arash
Emmanuel Charpentier writes:
> I'd like to create a function able to set some options, namely
>
> - `#+options: tex:`{t|dvipng|imagemagick}
>
> - `#+export-file-name:`
>
> I have been unable to find a *documented* way to do that from `elacs-lisp`.
>
> I *think* that an `org` source block
Alexander Adolf writes:
> Ihor Radchenko writes:
>
>> [...]
>> Calling `org-columns--clean-item' is a must to create a valid table.
>
> True.
>
> Additionally, it would seem advisable to call `org-quote-vert' on the
> data, too, as `org-columns--clean-item' does not take care of vertical
>
Arash Esbati writes:
> Thanks for your response. I'm not really familiar with Org development,
> but I hope the attached change fits the bill. Please feel free to
> adjust when necessary.
Thanks!
Applied, onto main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=ff9d00c9c
--
Max Nikulin writes:
> There should be a way to align tags for a specific heading even when
> `org-auto-align-tags' is nil.
>
>> - (org-align-tags)
>> + (when org-auto-align-tags (org-align-tags))
I can convert org-align-tags into a command.
> Instead of repetitive changes I would
On 21/04/2024 22:09, Matt wrote:
The proposed solution assumes we intend to parse the characters
following :cmdline as space delimited and grouped by quotes. However,
AFAICT, the parsing issue makes this solution ambiguous.
Matt, I am sorry, but I do not agree with your proposal. I do not
Alexander Gogl writes:
> you mean like this?
Not really, but I now squashed the previous patches manually.
Applied, onto main, with amendments.
I fixed some wording in the etc/NEWS entry, added description of %s%s to
the docstring, and removed BEHAVIOR=t from the new option - all other
similar
Matt writes:
> Whether this is a solution, in part, depends on the perennial problem of
> shell blocks: knowing what's wrong means knowing what's right.
>
> The proposed solution assumes we intend to parse the characters following
> :cmdline as space delimited and grouped by quotes. However,
16 matches
Mail list logo
