emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: emacs-orgmode@gnu.org
Cc: Scott Otterson <scotto@sharpleaf.org>
Subject: Fwd: Re: org-open-at-point fails on internal links
Date: Mon, 09 Oct 2017 14:38:21 -0400	[thread overview]
Message-ID: <87efqc415u.fsf@kyleam.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 139 bytes --]

[Forwarding because the list was dropped earlier in the thread but I
 didn't notice.  Scott, please don't drop the list in your replies.]


[-- Attachment #2: Type: message/rfc822, Size: 1523 bytes --]

From: Kyle Meyer <kyle@kyleam.com>
To: Scott Otterson <scotto@sharpleaf.org>, Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: org-open-at-point fails on internal links
Date: Mon, 09 Oct 2017 14:32:00 -0400
Message-ID: <87info41gf.fsf@kyleam.com>

Scott Otterson <scotto@sharpleaf.org> writes:

>   org-backward-paragraph()
>   org-inside-LaTeX-fragment-p()
>   org-footnote-in-valid-context-p()
>   org-footnote-at-reference-p()
>   ad-Advice-org-open-at-point

[...]

> org-mouse.el  (line 907) adds code to org-mode-hook, and that code adds
> advice to org-open-at-point, and that advice calls
> org-footnote-at-reference-p

Thanks for digging further.  Indeed org-mouse.el's advice would result
in the org-footnote-at-reference-p path being executed.

After loading org-mouse and using your example, I'm still not able to
trigger the error.  Could you debug org-backward-paragraph to find out
where the error is occurring?  You can do that by calling C-u C-M-x on
org-backward-paragraph or by evaluating

    (edebug-instrument-function 'org-backward-paragraph)

-- 
Kyle

             reply	other threads:[~2017-10-09 18:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-09 18:38 Kyle Meyer [this message]
2017-10-10  7:04 ` org-open-at-point fails on internal links Scott Otterson

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=87efqc415u.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=scotto@sharpleaf.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).