From: stardiviner <numbchild@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [BUG] Recently master branch commit breaks open file: link
Date: Mon, 24 Feb 2020 20:06:13 +0800 [thread overview]
Message-ID: <87lfosfave.fsf@gmail.com> (raw)
In-Reply-To: <87lfosz8ai.fsf@gnu.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Bastien <bzg@gnu.org> writes:
> 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?
I confirm this link directory and file exists. Including the headline exists too.
So I did a git bisect. Found this bad commit caused this problem "afd3b04ec * bad ol: Extend open tooling in link parameters".
This commit introduced new open file link function.
>
> Thanks,
- --
[ stardiviner ]
I try to make every word tell the meaning what I want to express.
Blog: https://stardiviner.github.io/
IRC(freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
-----BEGIN PGP SIGNATURE-----
iQFIBAEBCAAyFiEE8J9lDX1nSBmJJZFAG13xyVromsMFAl5TvDUUHG51bWJjaGls
ZEBnbWFpbC5jb20ACgkQG13xyVromsPWNAgAiGRD65HV+3j7jl+xxJgOuvRgy+O8
Os2BJkiKTrM8YYTX9icLnygAPQN9oXLOTYVXdShQWo1lHtpx0417bGBW+L7TglPW
hfdTYFl99No1+T0mnam0qnR44YDOrOYzPb83TqQnUOyhK/uWsk18pOhrvPf2UYpK
YxiIhGdlyosb41P+9gVzPfTM0akWHddNY/LZuJT+Irr84zpIAYwiXc24VXN6qhnB
/gDBosDGPbRl/XniFU3fUYSklHsBvUWuXb88df442pK+AfKEsh3c6lUqJ5AKtIm5
qmjye5OqZoQwt/zOpMakldvoK/hO/jT0UusRv1QqvKDpcyDAT7qrxIaODw==
=oJQL
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2020-02-24 12:06 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
2020-02-24 12:06 ` stardiviner [this message]
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=87lfosfave.fsf@gmail.com \
--to=numbchild@gmail.com \
--cc=bzg@gnu.org \
--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).