From: Eli Zaretskii <eliz@gnu.org>
To: Juan Jose Garcia-Ripoll <juanjose.garcia.ripoll@csic.es>
Cc: 38526@debbugs.gnu.org
Subject: bug#38526: 26.3; w32-shell-execute fails inside Nextcloud folder
Date: Sun, 08 Dec 2019 17:43:31 +0200 [thread overview]
Message-ID: <83blsiesbg.fsf@gnu.org> (raw)
In-Reply-To: <86eexfgjs4.wl-juanjose.garcia.ripoll@csic.es> (message from Juan Jose Garcia-Ripoll on Sun, 08 Dec 2019 12:04:59 +0100)
> Date: Sun, 08 Dec 2019 12:04:59 +0100
> From: Juan Jose Garcia-Ripoll <juanjose.garcia.ripoll@csic.es>
>
> I am using org-open-file to open files in dired. This function, for some
> file types, relies on w32-shell-execute with the "open" verb. This verb
> fails when the full path contains spaces. For instance, the first instance
> does not work, while the second does
>
> (w32-shell-execute "open" "c:\\Users\\juanj\\Nextcloud\\some-path\\CV.pdf")
>
> (w32-shell-execute "open" "c:\\Users\\juanj\\another-path\\CV.pdf")
>
> I am reporting this from a rather full image, but the problem also is shown
> in a bare-bones emacs (emacs -q)
Not reproducible here, although I tried several PDF documents on 2
different systems.
What program is configured on your system to open PDF documents? Is
it possible that its configuration is wrong?
next prev parent reply other threads:[~2019-12-08 15:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-08 11:04 bug#38526: 26.3; w32-shell-execute fails inside Nextcloud folder Juan Jose Garcia-Ripoll
2019-12-08 15:43 ` Eli Zaretskii [this message]
2019-12-08 16:12 ` Juan Jose Garcia-Ripoll
2019-12-08 17:08 ` Eli Zaretskii
2019-12-08 17:41 ` Juan Jose Garcia-Ripoll
2019-12-08 17:51 ` Eli Zaretskii
2019-12-09 16:36 ` Juan Jose Garcia-Ripoll
2019-12-09 17:22 ` Eli Zaretskii
2022-02-02 18:28 ` Lars Ingebrigtsen
2019-12-08 16:56 ` Noam Postavsky
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83blsiesbg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=38526@debbugs.gnu.org \
--cc=juanjose.garcia.ripoll@csic.es \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.