From: Karl Fogel <kfogel@red-bean.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [FR] A more general case than footnotes
Date: Wed, 01 Nov 2023 00:46:05 -0500 [thread overview]
Message-ID: <877cn2auw2.fsf@red-bean.com> (raw)
In-Reply-To: <87bkd8m41s.fsf@localhost>
Ihor Radchenko writes:
>Maske <maske1foro@gmail.com> writes:
>
>> I propose links to arbitrary points in different files.
>>
>> Furthermore, I think it would be a very nice new feature,
>> probably more opinions than mine should be heard.
>
>See:
>-
>https://list.orgmode.org/orgmode/118435e8-0b20-46fd-af6a-88de8e19fac6@app.fastmail.com/
>-
>https://list.orgmode.org/orgmode/CAJniy+OVD0NCWZZTPit5T7wvsbLbgLLXZmPub5tgq3gsHsGhYw@mail.gmail.com/
>-
>https://list.orgmode.org/orgmode/CAJcAo8s=cjNY-7-mA1zQk3R9HEWYreTatdVeHfJ39ccM9=kMog@mail.gmail.com/
>
>The idea is not new, but we need someone to implement it one way
>or another.
At my company, I implemented something that (I think) does what
Maske and those earlier threads are getting at:
https://code.librehq.com/ots/ots-tools/-/blob/main/emacs-tools/oref.el
We often use it with Org Mode files, but it's not specific to Org
Mode -- it works with any plaintext format. In fact, our most
common use case is cross-referencing from precise locations in
LaTeX files to precise locations in Org Mode files.
A couple of days ago I happened to post [1] on the Emacs
Humanities list about a updated version of oref.el. Maske noticed
that post, and referred me to this thread here.
My original announcement post from a year ago [2] is a good place
to get a quick overview of how oref.el works.
At the time I wrote oref.el, I didn't know about org-id.el. But
it wouldn't be too hard to make oref.el automagically compatible
with Org ":ID:" properties. I.e., `oref-do-ref' would jump to
them, copy them, etc, in just the same way it currently does with
native oref references. And the oref ref files cache would just
become the union of `oref-ref-files-cache' and `org-id-files'.
While I'll hand-wave a bit on the details right now, I think there
is a natural compatibility available. If people are interested in
this extension of oref.el, let me know.
Best regards,
-Karl
[1]
https://lists.gnu.org/archive/html/emacs-humanities/2023-10/msg00001.html
[2]
https://lists.gnu.org/archive/html/emacs-humanities/2022-10/msg00009.html
next prev parent reply other threads:[~2023-11-01 5:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 10:59 [FR] A more general case than footnotes Maske
2023-10-07 11:12 ` Ihor Radchenko
2023-10-07 13:06 ` Maske
2023-10-07 13:21 ` Ihor Radchenko
2023-10-07 13:35 ` Maske
2023-10-08 9:18 ` Ihor Radchenko
2023-10-08 11:26 ` Maske
2023-10-09 11:24 ` Ihor Radchenko
2023-11-01 5:46 ` Karl Fogel [this message]
2023-11-02 19:24 ` Suhail Singh
2023-11-03 15:02 ` Karl Fogel
[not found] <x1-8Lep5Zf1G94Im4HzYi1+3VTd6wk@gwene.org>
2023-10-14 2:16 ` Maske
2023-10-14 3:00 ` Maske
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=877cn2auw2.fsf@red-bean.com \
--to=kfogel@red-bean.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).