emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: emacs-orgmode@gnu.org
Subject: Re: Is there possibility to provide back links to each finely grained part of Org file?
Date: Mon, 9 Nov 2020 15:04:33 +0300	[thread overview]
Message-ID: <X6kwUSD6dcamcijp@protected.rcdrun.com> (raw)
In-Reply-To: <87tutyoj41.fsf@ucl.ac.uk>

* Eric S Fraga <e.fraga@ucl.ac.uk> [2020-11-09 14:39]:
> On Sunday,  8 Nov 2020 at 23:40, Jean Louis wrote:
> > I know that #names exist in HTML export for *** headings. Do they or
> > can they exist for every paragraph or item listed?
> Maybe not quite what you want but you can place anchors (aka targets)
> anywhere you want in your document using <<targetname>>.  I use these
> for within-document linking but I imagine you can link to these from
> other documents as well (untested).

Thank you.

That forms foundation for final solution as then it could be possible
to define special export that finds each new line after empty lines
and automatically adds specific anchor or target name to document.

I have tried using it in that manner as below and exported it to HTML
and #names are inside HTML. In the final solution I may need to adopt
CSS to place named anchors on the right side and to display them as
they are usually not displayed.




- [[anchor1][anchor1]]

- [[anchor2][anchor2]]

Before the export, I would like to filter the text and add anchors

If you have any pointer where I could insert a filter before
exporting, let me know.


  parent reply	other threads:[~2020-11-09 12:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-08 20:40 Is there possibility to provide back links to each finely grained part of Org file? Jean Louis
2020-11-09 11:38 ` Eric S Fraga
2020-11-09 12:01   ` Ken Mankoff
2020-11-09 12:04   ` Jean Louis [this message]
2020-11-09 12:45     ` Eric S Fraga
2020-11-09 15:38       ` Jean Louis

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:

  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=X6kwUSD6dcamcijp@protected.rcdrun.com \
    --to=bugs@gnu.support \
    --cc=emacs-orgmode@gnu.org \


* 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


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).