From: Juan Jose Garcia-Ripoll <juanjose.garcia.ripoll@csic.es>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Juan Jose Garcia-Ripoll <juanjose.garcia.ripoll@csic.es>,
38526@debbugs.gnu.org
Subject: bug#38526: 26.3; w32-shell-execute fails inside Nextcloud folder
Date: Sun, 08 Dec 2019 18:41:08 +0100 [thread overview]
Message-ID: <86pngy7m17.wl-juanjose.garcia.ripoll@csic.es> (raw)
In-Reply-To: <8336dueodg.fsf@gnu.org>
Sorry, my report was very messy. I have spent a great chunk of the day trying to debug it but did not update the already opened bug report.
I originally reported it as "spaces" being the problem because I misunderstood the cause. Later along the day I realized that moving the data outside of the Nextcloud folder solves the issues.
Let me summarize it better:
- w32-shell-execute with verb "open" fails to actually open any object that lays inside a Nextcloud folder.
- those same files can be opened from Windows Explorer
- moving those files outside of Nextcloud or switching off Nextcloud solves the issue but that is kind of pointless.
- w32-shell-execute does not generate any message or log and I do not know how to debug it.
The problem is evidenced with any type of file. Initially I was obsessed with PDF but as I explain in my previous file, it occurs with Word files and any other file that is not associated to emacs -- for instance,
(w32-shell-execute "open" "c:\\Users\\juanj\\Nextcloud\\tmp\\test.docx")
(w32-shell-execute "open" "c:\\Users\\juanj\\Nextcloud\\tmp\\test.pdf")
I am wondering whether it has to do with the permissions of the emacs.exe executable or the fact that it uses a w32 api call. I have tried investigating the Windows logs but I found no error associated to the w32-shell-execute call.
Thanks for looking into this.
Best,
--
Juan José García Ripoll
Quantum Information and Foundations Group
Institute of Fundamental Physics IFF-CSIC
Calle Serrano 113b, Madrid 28006 Spain
http://quinfog.hbar.es - http://juanjose.garcia.ripoll
next prev parent reply other threads:[~2019-12-08 17:41 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
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 [this message]
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=86pngy7m17.wl-juanjose.garcia.ripoll@csic.es \
--to=juanjose.garcia.ripoll@csic.es \
--cc=38526@debbugs.gnu.org \
--cc=eliz@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 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.