emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: [bug, org] footnote-action broken with narrowed buffer
Date: Sun, 26 Apr 2015 11:57:06 +0200	[thread overview]
Message-ID: <87oambrz4d.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87bnicxeax.fsf@gmx.us> (rasmus@gmx.us's message of "Sat, 25 Apr 2015 20:17:58 +0200")

Rasmus <rasmus@gmx.us> writes:

> The problem is that narrow can be time-consuming to recreate.

This is why we shouldn't mess with it in the first place.

> 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.

Good idea. I didn't thought about using "org-src.el", but, albeit not
perfect, it goes a long way towards avoiding these problems.

I toyed a bit with that. Now C-' on a (non inline) footnote reference
should edit it in a dedicated buffer.

Feedback welcome.


Regards,

  reply	other threads:[~2015-04-26  9:55 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
2015-04-26  9:57             ` Nicolas Goaziou [this message]
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=87oambrz4d.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    /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).