emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Scott Otterson <scotto@sharpleaf.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: "Emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: org-open-at-point fails on internal links
Date: Tue, 10 Oct 2017 09:04:13 +0200	[thread overview]
Message-ID: <CAPY3P0TYhtH+BqDYH_E8izdLDj+PQ7zZW5H1Cg6fM-PJ484+UA@mail.gmail.com> (raw)
In-Reply-To: <87efqc415u.fsf@kyleam.com>

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

This morning, I updated my packages (Options -> Manage Emacs Packages -> U
->X) and now, internal links work perfectly.

For the record, the updated packages were:

dash-20171009.105
flycheck-20171009-1145
helm-20171009.221
kaolin-theme-20171009.1130
org-20171009
org-plus-contrib-20171009
org-ref-20171009.2019
python mode-20171005.1620


I'll let you know if the error returns.

Scott




On Mon, Oct 9, 2017 at 8:38 PM, Kyle Meyer <kyle@kyleam.com> wrote:

> [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.]
>
>
>
> ---------- Forwarded message ----------
> From: Kyle Meyer <kyle@kyleam.com>
> To: Scott Otterson <scotto@sharpleaf.org>, Nicolas Goaziou <
> mail@nicolasgoaziou.fr>
> Cc:
> Bcc:
> Date: Mon, 09 Oct 2017 14:32:00 -0400
> Subject: Re: org-open-at-point fails on internal links
> 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
>
>

[-- Attachment #2: Type: text/html, Size: 2707 bytes --]

  reply	other threads:[~2017-10-10  7:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-09 18:38 Fwd: Re: org-open-at-point fails on internal links Kyle Meyer
2017-10-10  7:04 ` Scott Otterson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-10-07  8:44 Scott Otterson
2017-10-07 15:01 ` Kyle Meyer
2017-10-07 15:04   ` Nicolas Goaziou
2017-10-09 16:08     ` 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=CAPY3P0TYhtH+BqDYH_E8izdLDj+PQ7zZW5H1Cg6fM-PJ484+UA@mail.gmail.com \
    --to=scotto@sharpleaf.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=kyle@kyleam.com \
    /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).