emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: insert automatically a reference to a section header and a link
Date: Tue, 23 Nov 2021 10:20:45 -0500	[thread overview]
Message-ID: <CAF-FPGPkjx0AV0h4s5do1pTk1uZ8oF3XOuYEJqybJ=Ke6ZYpBQ@mail.gmail.com> (raw)
In-Reply-To: <87a6i2k90e.fsf@mat.ucm.es>

On Wed, Nov 17, 2021 at 12:18 PM Uwe Brauer <oub@mat.ucm.es> wrote:

> > I type "As we have seen in section [[*Intro]]" (literally, I tend to
> > not use any keybindings or function to insert the link). This (the
> > "*Intro" inside double square brackets) is called an internal link to
> > headlines and they are a default feature of Org:
>
> Yes, but, what do you do, if you have a 10 header and each has 20
> subheaders. How do you remember all these names?

Seems like completion could help, either at point, or with completing-read?

I've been playing a bit with something using the latter, and it's not
alway so straightforward how to do this given the flexibility of org,
but here's what it looks like using the Emacs 28 grouping support and
Emacs 27 annotation support:

https://raw.githubusercontent.com/bdarcus/oxr/main/images/oxr-insert.png

Bruce


  parent reply	other threads:[~2021-11-23 15:21 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
2021-11-23 15:20                 ` Bruce D'Arcus [this message]
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='CAF-FPGPkjx0AV0h4s5do1pTk1uZ8oF3XOuYEJqybJ=Ke6ZYpBQ@mail.gmail.com' \
    --to=bdarcus@gmail.com \
    --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).