[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] org-protocol: Fix missing '+' in js snippet
From: |
David Asabina |
Subject: |
Re: [PATCH] org-protocol: Fix missing '+' in js snippet |
Date: |
Sun, 9 May 2021 00:32:45 +0200 |
> Thank you. However on linux there is another degree of freedom: various
> desktop environments can be different in respect to treatment of URLs before
> passing them to protocol handlers. I have tried KDE and a kind of
> minimalistic setup inside container (xdg-utils) so far. Anyway it is good to
> receive confirmation that it could work for other people.
Perhaps the following helps provide more context:
- OS: NixOS 20.09
- WM: Xmonad 0.15
> In the meanwhile I have realized that bug report I mentioned was for Windows
> with emacs running in WSL
> https://orgmode.org/list/87zhbq7zin.fsf@pie.tf/
I have no access to Windows setups at the moment to test that -- just
NixOS and macOS.
> P.S. Since your response was private, I am unsure if Cc:
> emacs-orgmode@gnu.org should be added.
I'm definitely new with this workflow of `git send-email` so I totally
missed that I didn't reply to the group -- I didn't reply-to-group in
mutt so that was on me.
Not sure what the policy is on keeping the signal-to-noise manageably
low on the mailing groups as I'm very much of a noob here 🤣 so I'll
just add the CC address and I trust that I'll hear when I'm contributing
to more noise than signal. 😉
On Tue, May 04, 2021 at 11:44:34PM +0700, Maxim Nikulin wrote:
> On 03/05/2021 22:25, David Asabina wrote:
> > > I have a question that is a bit off-topic in this thread however. Since
> > > you
> > > are setting up org-protocol, you may notice other issues. There were
> > > reports
> > > that two slashes after "org-protocol:" cause some problems. My guess is
> > > that
> > > capture is recognized as hostname, so another slash is inserted after it.
> > > There was a patch allowing "/" before "?" to get things work (perhaps on
> > > Windows). Could you try, please, if one or three slashes in org-protocol
> > > URIs ("org-protocol:/capture?url=..." and
> > > "org-protocol:///capture?url=...")
> > > works properly in your environment? Maybe code examples in docs would
> > > benefit from one more correction.
> >
> > I've tried:
> > - org-protocol:/capture?template=t&url=emacs.org and
> > - org-protocol:///capture?template=t&url=emacs.org
> > and both worked like a charm on my setup (Firefox on NixOS).
>
> Thank you. However on linux there is another degree of freedom: various
> desktop environments can be different in respect to treatment of URLs before
> passing them to protocol handlers. I have tried KDE and a kind of
> minimalistic setup inside container (xdg-utils) so far. Anyway it is good to
> receive confirmation that it could work for other people.
>
> In the meanwhile I have realized that bug report I mentioned was for Windows
> with emacs running in WSL
> https://orgmode.org/list/87zhbq7zin.fsf@pie.tf/
>
> P.S. Since your response was private, I am unsure if Cc:
> emacs-orgmode@gnu.org should be added.
--
David Asabina
@vidbina on GitHub, Twitter, Instagram, etc.
+49 1768 7062 719
signature.asc
Description: PGP signature