Hello. For internal links, the manual states that
To insert a link targeting a headline, in-buffer completion can be
used. Just type a star followed by a few optional letters into the
buffer and press ‘M-’. All headlines in the current buffer
are offered as completions."
Is there
No Wayman writes:
> Ihor Radchenko writes:
>
>>> - Removes the optional TEST parameter, which is unused and
>>> better
>>> served through debugging tools.
>>
>> This is technically a breaking change. So, we (1) need to
>> mention it in
>> ORG-NEWS; (2) may consider (file-name &optional _)
No Wayman writes:
> See attached.
>
> From 9b21849b9b7d9f36f57241e80d005535f07b788c Mon Sep 17 00:00:00 2001
> From: Nicholas Vollmer
> Date: Sun, 3 Sep 2023 15:41:51 -0400
> Subject: [PATCH] ob-lilypond.el: Fix docstring typos
Thanks!
Applied, onto main.
https://git.savannah.gnu.org/cgit/emacs
Paul Stansell writes:
> The attached file is an example of how tangle wraps the Fortran module in
>
> program main
> end program main
>
> which prevents the code from compiling.
>
> There are more instructions on how to reproduce the bug in the attached
> bug.org file.
I opened the latest Or
Juan Manuel Macías writes:
>> #+language: ancientgreek russian arabic
>
> Of course, this syntax would be the most appropriate and consistent
> within Org. The problem is LaTeX, specifically babel, and that certain
> inconsistencies would be created with the rest of the backends. At first
> some
alain.coch...@unistra.fr writes:
>C-c C-l (org-insert-link)
>
>[...]
>
>Completion support
>
> Completion with TAB helps you to insert valid link prefixes
> like ‘http’ or ‘ftp’, including the prefixes defined
> through link abbreviations (see Link Ab
>
> I opened the latest Org git repo, ran make repro, opened the file,
> clicked on "tangle" link, moved to the linked source code, and executed
> it. It worked.
>
> So, I am unable to reproduce the problem on my system.
>
Hello Ihor,
Thanks for investigating. Can you please post your tangled fi
On 03/09/2023 14:53, Ihor Radchenko wrote:
Max Nikulin writes:
I missed this feature, but anyway it does not work as expected.
(org-link-set-parameters "tel")
...
\href{321}{call}
"tel:" is missed.
I have realized that it is possible to take advantage of current behavior:
(org-l
On 02/09/2023 14:26, Ihor Radchenko wrote:
With my proposal, it would become
(link :type "sec" :path "spielbeispiel" ...)
However, "sec" link type will still not be listed in the output
`org-link-types' (not registered).
Then, ox.el and other link processing code, when encountering a link
type
On 01/09/2023 16:04, Ihor Radchenko wrote:
And introduce [[::fig:something]] to allow explicit internal links.
I would consider an explicit link type for internal links, e.g. org: or
o: to allow search links in angle brackets or
.
In an emacs -Q, create an Org buffer with the following contents:
--8<---cut here---start->8---
* AB
** C
--8<---cut here---end--->8---
Fold the subtree under the heading AB, so that only a single line is
displayed (ending in
Ihor Radchenko writes:
> Juan Manuel Macías writes:
>
>>> #+language: ancientgreek russian arabic
>>
>> Of course, this syntax would be the most appropriate and consistent
>> within Org. The problem is LaTeX, specifically babel, and that certain
>> inconsistencies would be created with the rest o
12 matches
Mail list logo