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 12:48:13 +0200 [thread overview]
Message-ID: <87tww4xz4i.fsf@gmx.us> (raw)
In-Reply-To: <87fv7obnyb.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sat, 25 Apr 2015 10:40:28 +0200")
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Rasmus <rasmus@gmx.us> writes:
>
>> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>> Point is moved, though. If narrow shouldn't be "broken" then point
>> shouldn't be moved. I.e. no move when the definition is not within the
>> buffer.
>
> Fixed in 5954f6aa25b51a3a9a8f258fb0f15ef51be31366. Thank you.
>
>>> Outside of the most trivial case (i.e., jump back and forth between the
>>> definition and one of its references) it sounds like it would quickly
>>> get in the way.
>>
>> It would only work for the most trivial case I guess.
>
> This is why it is not worth implementing.
If it covers x%, for x large, of the realized usecases when working with a
narrowed buffer it's still "worth" it.
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.
2. Show the definition in the minibuffer as editable text (read input)
and update it if necessary.
3. A way to quickly get back to the previous narrow (this should
probably be an Emacs-core feature).
—Rasmus
--
Enough with the bla bla!
next prev parent reply other threads:[~2015-04-25 10:48 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 [this message]
2015-04-25 11:28 ` Rasmus
2015-04-25 12:17 ` Nicolas Goaziou
2015-04-25 18:17 ` Rasmus
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=87tww4xz4i.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).