From: Stefan Nobis <stefan-ml@snobis.de>
To: emacs-orgmode@gnu.org
Subject: Re: insert automatically a reference to a section header and a link
Date: Wed, 17 Nov 2021 20:10:42 +0100 [thread overview]
Message-ID: <m1tugaionh.fsf@nobis-it.eu> (raw)
In-Reply-To: <87a6i2k90e.fsf@mat.ucm.es> (Uwe Brauer's message of "Wed, 17 Nov 2021 18:05:37 +0100")
Uwe Brauer <oub@mat.ucm.es> writes:
> Yes, but, what do you do, if you have a 10 header and each has 20
> subheaders.
I avoid writing such complex documents for the moment. :)
[Some custom functions]
> Thanks but this did not work!
Sorry. The code is meant as an inspiration, not to be used out-of-the
box. I never tested the functions outside my highly adjusted default
configuration.
As I read in another post you seem to be a helm user. Therefore it
might be a better idea to use helm helper functions. I assume, helm
has also some function to jump around in Org files, with headings as
targets. If you find such a function, try to copy and adapt (as I did
with the similar `counsel-outline' function): I assume such a function
will use some helper function to collect the candidates for completion
and after the user selected a candidate there is code to jump to the
selected destination. Just try to change this part so that instead of
jumping, a link is inserted at the proper place (that's the part my
function `sn/org-insert-internal-link-action' is responsible for).
Maybe someone with more knowledge about helm might help you with a
complete solution.
--
Until the next mail...,
Stefan.
next prev parent reply other threads:[~2021-11-17 19:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 7:36 insert automatically a reference to a section header and a link Uwe Brauer
2021-11-17 8:28 ` Uwe Brauer
2021-11-17 10:04 ` Eric S Fraga
2021-11-17 13:58 ` Uwe Brauer
2021-11-17 14:06 ` John Kitchin
2021-11-17 14:15 ` Uwe Brauer
2021-11-17 14:59 ` Stefan Nobis
2021-11-17 15:42 ` Juan Manuel Macías
2021-11-17 16:08 ` Uwe Brauer
2021-11-17 15:55 ` Uwe Brauer
2021-11-17 16:08 ` Eric S Fraga
2021-11-17 16:44 ` Uwe Brauer
2021-11-17 16:29 ` Stefan Nobis
2021-11-17 17:05 ` Uwe Brauer
2021-11-17 19:10 ` Stefan Nobis [this message]
2021-11-23 15:20 ` Bruce D'Arcus
2021-11-17 18:17 ` Juan Manuel Macías
2021-11-17 19:00 ` Stefan Nobis
2021-11-17 14:58 ` Eric S Fraga
2021-11-17 16:00 ` Uwe Brauer
2021-11-17 16:31 ` Eric S Fraga
2021-11-17 17:06 ` Uwe Brauer
2021-11-17 16:49 ` [Problems with org-ref-helm-insert-ref-link and org-id-get-create] (was: insert automatically a reference to a section header and a link) Uwe Brauer
2021-11-17 17:57 ` John Kitchin
2021-11-17 18:58 ` [Problems with org-ref-helm-insert-ref-link and org-id-get-create] Uwe Brauer
2021-11-17 19:58 ` John Kitchin
2021-11-17 20:16 ` Uwe Brauer
2021-11-17 21:41 ` Uwe Brauer
2021-11-17 21:54 ` John Kitchin
2021-11-18 7:44 ` Uwe Brauer
2021-11-18 8:06 ` Uwe Brauer
2021-11-18 12:48 ` John Kitchin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1tugaionh.fsf@nobis-it.eu \
--to=stefan-ml@snobis.de \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).