On Monday, 20 September 2021 16:13:24 CEST Max Nikulin wrote:
> On 20/09/2021 07:05, chris wrote:
> > On Tuesday, 14 September 2021 18:33:43 CEST Max Nikulin wrote:
> >> As a kind of summary:
> >>
> >> During publishing of a project
> >> - "id:" links to headings from the same file are exported as
On 20/09/2021 07:05, chris wrote:
On Tuesday, 14 September 2021 18:33:43 CEST Max Nikulin wrote:
As a kind of summary:
During publishing of a project
- "id:" links to headings from the same file are exported as short
generated anchors like #org032777e or as anchors to custom ids when the
latter
On Tuesday, 14 September 2021 18:33:43 CEST Max Nikulin wrote:
> As a kind of summary:
>
> During publishing of a project
> - "id:" links to headings from the same file are exported as short
> generated anchors like #org032777e or as anchors to custom ids when the
> latter are available
> - "Searc
As a kind of summary:
During publishing of a project
- "id:" links to headings from the same file are exported as short
generated anchors like #org032777e or as anchors to custom ids when the
latter are available
- "Search heading" links to other files are exported as short generated
anchors o
On Tuesday, 24 August 2021 17:23:24 CEST Maxim Nikulin wrote:
> On 23/08/2021 03:42, inkbottle wrote:
> > Links between two different files, like
> > `[[id:e54113f9-2ad7-4a86-94be-68ffc696de0b][hello]]`, get broken when
> > publishing. (whatever the settings).
> >
> > I haven't found any workaroun
On 23/08/2021 03:42, inkbottle wrote:
Links between two different files, like
`[[id:e54113f9-2ad7-4a86-94be-68ffc696de0b][hello]]`, get broken when
publishing. (whatever the settings).
I haven't found any workaround.
Being able to move around entries, functionality provided by `org-id-link-to-
Links between two different files, like
`[[id:e54113f9-2ad7-4a86-94be-68ffc696de0b][hello]]`, get broken when
publishing. (whatever the settings).
I haven't found any workaround.
Being able to move around entries, functionality provided by `org-id-link-to-
org-use-id`, is pivotal, IMO.
I've done a lot of investigation.
I totally agree with internal links not being stable through publishing:
`3c5997f1-205a-437e-8722-d5f52239a207` => `"bye.org#orgfa9c151"`
I totally agree with what Nicolas Goaziou says there:
https://lists.gnu.org/archive/html/emacs-orgmode/2021-05/msg01254.html
I cannot have the following minimal example working consistently:
$ cat hello.org
* hello
:PROPERTIES:
:ID: e54113f9-2ad7-4a86-94be-68ffc696de0b
:END:
#+INDEX: hello-keyword
#+begin_src emacs-lisp
(org-id-update-id-locations '("hello.org" "bye.org" "theindex.org"))
#+end_
Just adding one element. When I open `theindex.inc` in emacs, then do `M-x
org-mode`, then go on one of the links and do `M-x org-open-at-point`, the
link is correctly followed.
But when exported to html, the link from `theindex.html` is broken, because no
target has been actually created usin
Hi,
I want an `org-id / :ID:` publishing workflow.
To eliminate "xy-case" I first describe what I've been trying to do.
First I've added an `:ID:` to many headlines through `M-x org-id-get-create`.
Then I've added one `#+INDEX: word` under one of those headlines.
Then I've executed that (I do
11 matches
Mail list logo
