emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Andrea Lazzarini <andrea.lazzarini1@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Fwd: [FR] Enhancing footnote managment (via indirect buffer)?
Date: Fri, 26 May 2023 11:08:25 +0200	[thread overview]
Message-ID: <BA497434-FA3C-49AD-99AC-72F2367A1E1A@gmail.com> (raw)
In-Reply-To: 990C578F-176B-4166-868C-0BC59759CC19@gmail.com

Il giorno 24 mag 2023, alle ore 11:03, Ihor Radchenko <yantar92@posteo.net> ha scritto:
> 
> Payas Relekar <relekarpayas@gmail.com> writes:
> 
>> I've been playing with org-footnote-assistance, and this is again just
>> another opinion, but I'm also preferring the indirect buffer. It just
>> puts things in better perspective.
> 
> I'd prefer to integrate things with `org-edit-special', if possible.
> Possibly extending `org-edit-special' functionality.
> 
> The pros for `org-edit-special' are that we can escape certain edge
> cases. In particular, there is a known edge case when footnote
> definition contains an src block with 2+ blank lines. The blank lines
> are treated as the end of the footnote definition and src block is not
> recognized. Also, `org-edit-footnote-reference' takes care about
> removing common indentation.
> 

I've tried to use org-edit-special with a src block with 2+ blank lines and the second #+end_src is not seen as part of the footnote.
Is this the edge problem you were addressing? I get the same result with the indirect buffer.

I'll try to implement at least footnote previewing functionalities with eldoc!

> -- 
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at <https://orgmode.org/>.
> Support Org development at <https://liberapay.com/org-mode>,
> or support my work at <https://liberapay.com/yantar92>




  parent reply	other threads:[~2023-05-26  9:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 10:59 [FR] Enhancing footnote managment (via indirect buffer)? Payas Relekar
2023-05-24  9:03 ` Ihor Radchenko
     [not found]   ` <990C578F-176B-4166-868C-0BC59759CC19@gmail.com>
2023-05-26  9:08     ` Andrea Lazzarini [this message]
     [not found]       ` <877cria8f9.fsf@localhost>
2023-07-03 15:32         ` Andrea Lazzarini
2023-07-03 16:19           ` Ihor Radchenko
2023-09-02 10:09             ` Ihor Radchenko
2023-12-09 11:20               ` Ihor Radchenko
2023-05-26  9:13     ` Ihor Radchenko

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=BA497434-FA3C-49AD-99AC-72F2367A1E1A@gmail.com \
    --to=andrea.lazzarini1@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).