Hi Max,
Max Nikulin writes:
> I had some test cases for decoding of "+" in org-protocol URIs, so I
> have put them to test-org-protocol.el.
Applied too, thanks again.
--
Bastien
Max Nikulin writes:
> Surprisingly there is no conflicts during rebase. I expected changed
> context in ORG-NEWS.
Applied, thanks!
--
Bastien
On 27/09/2021 21:31, Max Nikulin wrote:
On 27/09/2021 17:38, Bastien wrote:
Maxim Nikulin writes:
I have realized that only a half of new apostrophes in doc strings
were properly escaped, so I am attaching updated patch. I still
consider the change as a minor improvement.
Probably given the
On 27/09/2021 17:38, Bastien wrote:
Maxim Nikulin writes:
I have realized that only a half of new apostrophes in doc strings
were properly escaped, so I am attaching updated patch. I still
consider the change as a minor improvement.
Probably given the delay, the patch does not apply anymore.
Hi Maxim,
Maxim Nikulin writes:
> I have realized that only a half of new apostrophes in doc strings
> were properly escaped, so I am attaching updated patch. I still
> consider the change as a minor improvement.
Probably given the delay, the patch does not apply anymore.
Would you be able to
I have realized that only a half of new apostrophes in doc strings were
properly escaped, so I am attaching updated patch. I still consider the
change as a minor improvement.
On 06/04/2021 21:47, Maxim Nikulin wrote:
When I tried org-protocol for the first time, I was quite surprised that
qu
Hi,
Some time ago, when I tried org-protocol, I was quite surprised that
query parameters generated using URLSearchParams JavaScript class are
decoded incorrectly. "+" characters representing space are passed as is.
I hope, I have found a proper place in the code to handle such case.
It does
