emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Maske <maske1foro@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [FR] A more general case than footnotes
Date: Sat, 7 Oct 2023 15:35:11 +0200	[thread overview]
Message-ID: <8ba636d2-7fd6-784c-75c7-128645343133@gmail.com> (raw)
In-Reply-To: <87y1gey3e2.fsf@localhost>

[-- Attachment #1: Type: text/plain, Size: 2145 bytes --]


On 07/10/2023 15:21, Ihor Radchenko wrote:
> Maske<maske1foro@gmail.com>  writes:
>
>> The headings could be in different files, yes.
>>
>> AFAIK, citations don't link two exact points. Footnotes do.
> Do you mean that you also want to jump back-and-forth between footnote
> definition in the another file and its footnote references?


Right: With C-c.

And maybe there could work directly commands like "org-footnote-action", 
being unneeded to create new commands like "org-note-action" with almost 
the same functionality.


>
>> I don't understand the option of "include", but I think it wouldn't be
>> the case.
> Seehttps://orgmode.org/manual/Include-Files.html
Thanks, I save it.
>
>> I really think footnotes would be a particular case of this option.
>>
>> ** Reference in file A
>> :PROPERTIES:
>> :ID:       978-84-362-7195-9
>> :END:
>>
>> ...
>> A “comment line” starts with a hash character (#)
>> *[n:102@978-84-362-7195-9]* and either a whitespace character or the
>> immediate end of the line.
>> ...
>>
>>
>> ** Notes in file B
>>
>> *[n:102@978-84-362-7195-9]* The hash character is important in orgmode.
> May you explain the purpose of @978-84-... part?
> You seem to assume that a footnote always has a single reference,
> which may or may not be the case in practice.

If there would be more than one reference, a behavior like that of footnotes would be appropriate?

The purpose of the @978-84-... part:
@978-84-362-7195-9 would work like the ID for internal links: [[id:978-84-362-7195-9]]. That would allow jumping to the correct heading from any file.
I am not a programmer, so the syntax I am sure could be more solid.  Example:


** Reference in file A
:PROPERTIES:
:ID:       978-84-362-7195-9
:END:
...
A “comment line” starts with a hash character (#) [n:102@978-84-362-7195-9] and either a whitespace character or the immediate end of the line.
...


** Notes in file B
[[id:978-84-362-7195-9]]: Link to heading in file A

[n:102@978-84-362-7195-9]: Link to an exact point in file A. Where the point is defined by the LABEL 102, and the file can be find thanks to the ID 978-84-362-7195-9

[-- Attachment #2: Type: text/html, Size: 3551 bytes --]

  reply	other threads:[~2023-10-07 13:41 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 [this message]
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
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=8ba636d2-7fd6-784c-75c7-128645343133@gmail.com \
    --to=maske1foro@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \
    /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).