emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: stardiviner <numbchild@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [BUG] Recently master branch commit breaks open file: link
Date: Mon, 24 Feb 2020 09:41:41 +0100	[thread overview]
Message-ID: <87lfosz8ai.fsf@gnu.org> (raw)
In-Reply-To: <87o8tofq1b.fsf@gmail.com> (stardiviner's message of "Mon, 24 Feb 2020 14:38:40 +0800")

Hi Stardiviner,

stardiviner <numbchild@gmail.com> writes:

> When I open a link like this:

Thanks for testing links, the master branch contains a few changes.

> #+begin_src org
> [[file:~/Org/Tasks/Computer Todos.org::*TODO 厉害的人是怎么分析问题的？][厉害的人是怎么分析问题的？]]
> #+end_src
>
> I =[M-x toggle-debug-on-error]= got following stacktrace:
>
> #+begin_example
> Debugger entered--Lisp error: (file-missing "Reading directory" "No
> such file or directory"
> "/home/stardiviner/Org/Wiki/Thought/Data/Manuals/My...")
>   access-file("/home/stardiviner/Org/Wiki/Thought/Data/Manuals/My..." "Reading directory")

Is this directory* existing in your setup?

* /home/stardiviner/Org/Wiki/Thought/Data/Manuals/My...

If yes, do you know what causes Org to check for its existence?

Thanks,

-- 
 Bastien

  reply	other threads:[~2020-02-24  8:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-24  6:38 [BUG] Recently master branch commit breaks open file: link stardiviner
2020-02-24  8:41 ` Bastien [this message]
2020-02-24 12:06   ` stardiviner
2020-02-24 12:15     ` Bastien
2020-02-24 15:09       ` stardiviner
2020-02-24 20:30         ` Bastien
2020-02-24 20:35         ` Document backward-incompatible change in ORG-NEWS? (was: [BUG] Recently master branch commit breaks open file: link) Bastien
2020-02-24 21:31           ` Samuel Wales
2020-02-25  7:02             ` stardiviner
2020-02-25  9:10           ` Document backward-incompatible change in ORG-NEWS? Nicolas Goaziou
2020-02-25 19:34             ` Bastien

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=87lfosz8ai.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=numbchild@gmail.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).