From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [bug, org] footnote-action broken with narrowed buffer
Date: Sat, 25 Apr 2015 20:17:58 +0200 [thread overview]
Message-ID: <87bnicxeax.fsf@gmx.us> (raw)
In-Reply-To: 877ft0bdw0.fsf@nicolasgoaziou.fr
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>> In any case, how about some of these alternative approaches to the issue
>> of handling footnotes from a narrowed buffer.
>>
>> 1. Retrieve the footnote in the minibuffer. E.g. org-footnote-action
>> shows the footnote-definition if it is outside of the narrow (and
>> known) in the minibuffer? E.g. 2. when using prefix.
>
> I suggested it already in this thread, i.e., if the definition is
> outside the narrowed part of the buffer, offer to widen and jump to it,
> or display the definition, or do nothing.
The problem is that narrow can be time-consuming to recreate. Consider
this narrow where I have to edit fn:1
* top
** h1
** h2
*** h3
Txt<point>[fn:1]
To recreate the narrow I have to go to *top, narrow to the subtree,
potentially collapse *h{1,2}...
> Actually, displaying the definition could be a separate binding (e.g.,
> C-u C-c C-c), since it could be useful even outside this case.
>
>> 2. Show the definition in the minibuffer as editable text (read input)
>> and update it if necessary.
>
> Then you have to deal with out of sync buffers, closed buffers,..
Wouldn't it only find definition in the same file? If you use a popup
indirect buffer narrowed to the footnote-definition in question I don't
think these problems can exist. In any case, this would seem similar to
the way ob handles code blocks.
> I'm pretty sure that in this situation, the user is able to widen the
> buffer himself and then jump to the definition in order to edit it. This
> would be a lot of trouble for a debatable benefit.
Sure, but recreating your narrow takes time. And it's annoying when you
want to review a section, say.
—Rasmus
--
And I faced endless streams of vendor-approved Ikea furniture. . .
next prev parent reply other threads:[~2015-04-25 18:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 16:41 [bug, org] footnote-action broken with narrowed buffer Rasmus
2015-04-24 19:54 ` Nicolas Goaziou
2015-04-24 20:35 ` Rasmus
2015-04-25 8:40 ` Nicolas Goaziou
2015-04-25 10:48 ` Rasmus
2015-04-25 11:28 ` Rasmus
2015-04-25 12:17 ` Nicolas Goaziou
2015-04-25 18:17 ` Rasmus [this message]
2015-04-26 9:57 ` Nicolas Goaziou
2015-04-26 21:11 ` Rasmus
2015-04-27 22:41 ` Nicolas Goaziou
2015-04-27 23:43 ` Rasmus
2015-04-28 17:35 ` Nicolas Goaziou
2015-04-28 19:10 ` Rasmus
2015-05-06 22:13 ` Nicolas Goaziou
2015-04-27 22:11 ` Rasmus
2015-04-27 22:26 ` Nicolas Goaziou
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=87bnicxeax.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).