Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
--
[again, the specific implementation or syntax isn't the issue for me
here, just hte ability to have global custom id in addition to
existing .org local custom id]
[in case not obvious, i used org-link-minor-mode to implement the
equivalent of global custom id's, including non-org. i'd say, like,
";; mypackage-whatever-parsing-thingie". that is a kludge if we can
do it right with an oref-concept-ish org minor mode, but it was hugely
useful.]
to throw a cat among the pigeons, [[file:contacts.org::#custom_id][My
text]] made me think of the need for global custom id in addition to a
file-specific one like this. idk what a good ui for it would be given
all the options we have considered over the years and recently. just
thought to bring
On 02 Nov 2023, Suhail Singh wrote:
Karl Fogel writes:
My original announcement post from a year ago [2] is a good
place to get a quick
overview of how oref.el works.
...
[2]
https://lists.gnu.org/archive/html/emacs-humanities/2022-10/msg9.html
From [2]:
Thus, in "jones-interview.or
On 03/11/2023 13:29, David Masterson wrote:
the generated LaTeX href looks like
\href{contacts.tex}{My text}
which looks wrong.
Search part definitely should be retained.
I have realized that in the LaTeX world inter-document cross-linking
works differently. With the xr-hyper package, la
