all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
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: Wed, 02 Feb 2022 19:28:54 +0100	[thread overview]
Message-ID: <878rutqg0p.fsf@gnus.org> (raw)
In-Reply-To: <83zhg1bei9.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 09 Dec 2019 19:22:22 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> https://github.com/nextcloud/desktop/issues/1671
>> Nextcloud's log shows that it intercepts the ShellExecute calls.
>
> Intercepts, but doesn't support "open", and doesn't call the next
> handler in the chain?  That sounds like a terrible bug to me, and I
> have hard time believing in such problematic behavior.

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

Skimming this thread, it seems like the problem is in Nextcloud and not
in Emacs, and I'm therefore closing this bug report.  If I've
misunderstood, please respond to the debbugs address and we'll reopen.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-02-02 18:28 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
2019-12-09 17:22             ` Eli Zaretskii
2022-02-02 18:28               ` Lars Ingebrigtsen [this message]
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=878rutqg0p.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=38526@debbugs.gnu.org \
    --cc=eliz@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.