From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [bug, org] footnote-action broken with narrowed buffer
Date: Fri, 24 Apr 2015 22:35:58 +0200 [thread overview]
Message-ID: <87h9s5z2kx.fsf@gmx.us> (raw)
In-Reply-To: 87bnidcnfq.fsf@nicolasgoaziou.fr
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Hello,
>
> Rasmus <rasmus@gmx.us> writes:
>
>> Narrow to h1 in the following example and run org-footnote-action on the
>> footnote-reference. Expected behavior is IMO to go to the definition.
>> This does not happen.
>
> I disagree. Interactive commands are not expected to break current
> narrowing (try, e.g., C-c C-n).
> We might however ask the user if he wants to widen in order to reach
> footnote definition, or display said definition in the echo area if he
> doesn't, and maybe introduce a variable to always do one of these.
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.
>> Ideally, it should be possible to get back to the narrowed stage again,
>> but I'm not sure how this would work. Perhaps hooking into next C-& or
>> org-footnote-action if it's performed from within the [:begin, :end] range
>> of the footnote-definition...
>
> I suggest to stay away from this kind of "smart" behaviour.
>
> 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.
—Rasmus
--
It was you, Jezebel, it was you
next prev parent reply other threads:[~2015-04-24 20:36 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 [this message]
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
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=87h9s5z2kx.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).