Re: [O] [PATCH] protocol: allow users to disable warning about old style links

2017-06-21 Thread Mario Martelli
> The default capture template didn't work for me: > >(*"w"* > *"Default template"* > entry > (file+headline *"~/org/capture.org "* *"Notes"*) > *"* %^{Title}\n\n Source: %u, %c\n\n %i"* > *:empty-lines* 1) There are some

Re: [O] [PATCH] protocol: allow users to disable warning about old style links

2017-06-21 Thread Tyler Smith
On Wed, Jun 21, 2017, at 12:51 PM, Mario Martelli wrote: > >>  it would make sense to suggest the >> new style syntax as the default for use by us newbies. > > yeah, thought about that too. At the moment it’s still a copy of the old doc.  > > Got no feedback so far wether my approach would be

Re: [O] [PATCH] protocol: allow users to disable warning about old style links

2017-06-21 Thread Mario Martelli
> it would make sense to suggest the > new style syntax as the default for use by us newbies. yeah, thought about that too. At the moment it’s still a copy of the old doc. Got no feedback so far wether my approach would be acceptable or not. Therefore I did not put much effort into it. But

Re: [O] [PATCH] protocol: allow users to disable warning about old style links

2017-06-21 Thread Mario Martelli
> I'm just starting to use org-protocol, and I'm confused by this warning. > I can't find any description of the differences between the old and new > link styles in the documentation, or any pointers as to how and what I > should change to adopt the new syntax. The org manual links to >

Re: [O] [PATCH] protocol: allow users to disable warning about old style links

2017-06-21 Thread Tyler Smith
On Wed, Jun 21, 2017, at 12:24 PM, Tyler Smith wrote: > > whereas the new-style key-value links would be: > > javascript:location.href='org-protocol://sub-protocol?url='+ > encodeURIComponent(location.href)+'='+ > encodeURIComponent(document.title)+'='+ >

Re: [O] [PATCH] protocol: allow users to disable warning about old style links

2017-06-21 Thread Tyler Smith
On Wed, Jun 21, 2017, at 12:01 PM, Mario Martelli wrote: > > I have shared a proposal to move org-protocol documentation to core > documentation. > It’s mainly copied together from the old one and 9.0 NEWS. > > The important part regarding the new syntax could be found here: > >

Re: [O] [PATCH] protocol: allow users to disable warning about old style links

2017-06-21 Thread Tyler Smith
On Fri, Jun 16, 2017, at 02:13 AM, Nicolas Goaziou wrote: > > Wouldn't it be better to report it upstream as a bug? I don't think > there are many Org protocols applications out there and the conversion > to the new syntax is easy. I'm just starting to use org-protocol, and I'm confused by this

Re: [O] [PATCH] protocol: allow users to disable warning about old style links

2017-06-16 Thread Nicolas Goaziou
Alex Branham writes: > I did report it upstream as a bug. The maintainer is (understandably, > I think) hesitant to change since 1) old style links continue to be > supported But it will break at some point, hence the warning. > and 2) there’s no way for a browser extension

Re: [O] [PATCH] protocol: allow users to disable warning about old style links

2017-06-16 Thread Alex Branham
Hi, thanks for the reply. On Fri 16 Jun 2017 at 06:13, Nicolas Goaziou wrote: > Hello, > > Alex Branham writes: > >> This patch allows org mode users to disable the warning issued about >>old org protocol style links. This is important because

Re: [O] [PATCH] protocol: allow users to disable warning about old style links

2017-06-16 Thread Nicolas Goaziou
Hello, Alex Branham writes: > This patch allows org mode users to disable the warning issued about >old org protocol style links. This is important because sometimes (e.g. >browser extensions), we don’t have easy control over the format >specified. Thank you. Wouldn't it

[O] [PATCH] protocol: allow users to disable warning about old style links

2017-06-14 Thread Alex Branham
Hello, This patch allows org mode users to disable the warning issued about old org protocol style links. This is important because sometimes (e.g. browser extensions), we don’t have easy control over the format specified. Issuing the warning is annoying because it pops up in a new window.