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: Mon, 09 Dec 2019 17:36:28 +0100 [thread overview]
Message-ID: <867e35e9rn.wl-juanjose.garcia.ripoll@csic.es> (raw)
In-Reply-To: <831rteemee.fsf@gnu.org>
On Sun, 08 Dec 2019 19:51:21 +0100,
Eli Zaretskii wrote:
> Sorry, I cannot help you, as I know nothing about Nextcloud. Maybe
> someone else does. Failing that, I suggest to ask on the Nextcloud
> forum, showing them the code we have in Emacs that calls
> ShellExecuteW, or just asking whether there are known issues with
> ShellExecuteW calls for files in the Nextcloud directory.
Here it goes
https://github.com/nextcloud/desktop/issues/1671
Nextcloud's log shows that it intercepts the ShellExecute calls.
--
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
--
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-09 16:36 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
2019-12-08 17:51 ` Eli Zaretskii
2019-12-09 16:36 ` Juan Jose Garcia-Ripoll [this message]
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=867e35e9rn.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.