Hi,
The ability to tangle to multiple destinations is a very convenient way
to manage cluster configurations. No, it's more than that: it's an
*awesome* way to deploy and keep clusters configs and repros well
organized.
The following *org-babel-n-tangle*, is just a small derivation
of *org-babel
Ihor Radchenko writes:
> Or we can just document that ESS defaults are used for sessions and ask
> users to customize inferior-ess-R-program if they need something
> non-standard for sessions.
>
> The problem with `inferior-ess-R-program' is that it must be executable
> name, and cannot be comman
On 08/07/2024 19:56, András Simonyi wrote:
What I've been arguing for in this thread and what motivates the
current default behavior is that it is a general, style-independent
CSL assumption that the processor's input for title fields is in
sentence-case, and this requires converting the BibLaTeX
Samuel Wales writes:
> 18018 99% - command-execute
> ...
>17488 96% - org-capture
>17434 96% - org-capture-place-template
>17398 96%- org-fold-show-all
>17370 96% - org-fold-region
>11415 63% - o
Phil writes:
> The ability to tangle to multiple destinations is a very convenient way
> to manage cluster configurations. No, it's more than that: it's an
> *awesome* way to deploy and keep clusters configs and repros well
> organized.
> ...
> #+begin_example
> #+begin_src elisp :n-tangle "hosts
Sébastien Gendre writes:
> Ihor Radchenko writes:
>> I wrote https://github.com/yantar92/org-capture-ref to do exactly
>> this.
>
> Is it meant to be used with org-ref ?
No. It has nothing to do with org-ref.
> I didn't plan to build a bibliography with bibtex (at least for now). I
> just pla
Jakob Schöttl writes:
>> Thanks for the reproducer!
>> I committed a fix onto main.
>> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=58c5c5882
>
> Hi Ihor, do you know anything on the merge progress of your fix into emacs?
>
> I just tested with GNU Emacs 29.4 with --no-init-fil
Ihor Radchenko writes:
>> I just tested with GNU Emacs 29.4 with --no-init-file and the minimal
>> example still doesn't produce a correct table.
>
> May you please elaborate what exactly is not correct in the table?
> I am not seeing any problem - no extra empty lines are added by the
> second
On 12/07/2024 03:36, Sébastien Gendre wrote:
Max Nikulin writes:
See the "Link type, Available keywords" table in this section.
`org-capture' may be executed in various Emacs buffers and available
keywords may depend on major mode.
Is it necessary to call "org-store-link" before calling "org-c
Am 12.07.24 um 13:56 schrieb Ihor Radchenko:
Emacs 29.4 does not include Org 9.7, where the bug has been fixed.
You need either upcoming Emacs 30 or upgrade Org mode from ELPA.
Thanks!
Thank you for your reply.
I wrote more after the quotes below.
Max Nikulin writes:
> Have a look into `org-capture' code. It calls `org-store-link'.
Thank you for this information.
Max Nikulin writes:
>> Is there a way to discover the keywords that a major mode provide to a
>> capture templa
Thank you for your clarification. I will take a look.
Ihor Radchenko writes:
> Sébastien Gendre writes:
>
>> Ihor Radchenko writes:
>>> I wrote https://github.com/yantar92/org-capture-ref to do exactly
>>> this.
>>
>> Is it meant to be used with org-ref ?
>
> No. It has nothing to do with or
Daniel Fleischer writes:
> You can override the ID generation and the ID-to-path function to create
> an attachment hierarchy of your liking, e.g.
>
> ATTACH-DIR/year/month-day/*files*
>
> Checkout `org-attach-id-to-path-function-list' and `org-id-new'.
Thank you. That gives me some ideas.
--
Ihor Radchenko writes:
> David Masterson writes:
>
>> It's taking awhile to get through my hard head, but I think I'm
>> beginning to understand the directory structure of attachments.
>>
>> org-attach-id-dir/IDx/attachment-file
>>
>> I don't understand the value of IDx. I would think that "at
14 matches
Mail list logo
