From: Adam Porter <adam@alphapapa.net>
To: emacs-orgmode@gnu.org
Subject: Re: Update to org-protocol-capture-html
Date: Sun, 23 Jul 2017 17:35:06 -0500 [thread overview]
Message-ID: <87y3relr39.fsf@alphapapa.net> (raw)
In-Reply-To: 33ff160b-3018-503c-7bba-30124c25ad64@gmail.com
Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com> writes:
> Sorry for kind of resurrecting this thread.
Not at all. :) You might consider filing an issue on the GitHub
tracker, though, because I almost didn't notice this (just haven't been
watching the ml lately).
> I've been trying to get this working and I noticed that bookmarklets
> only work with a single slash after org-protocol.
>
> Does not work:
>
> javascript:location.href = 'org-protocol://capture-html ...
>
> Does work:
>
> javascript:location.href = 'org-protocol:/capture-html ...
>
> Is this a bug in org-protocol-capture-html documentation or // before
> protocol should actually work?
It should work. Works for me and everyone else, AFAIK. What version of
Org are you using? It's currently set up to work with Org 9.0+.
> Another somewhat minor thing of note and this applies to generic
> org-protocol documentation too - we probably want to give emacsclient
> with -n flag in all protocol documentation. There's no point in
> stockpiling client processes, right?
That's an interesting point, but AFAIK that stockpiling doesn't happen.
I've never noticed it, anyway. Have you actually seen it?
next prev parent reply other threads:[~2017-07-23 22:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 5:16 Update to org-protocol-capture-html Adam Porter
2017-07-22 22:57 ` Nikolay Kudryavtsev
2017-07-23 22:35 ` Adam Porter [this message]
2017-07-24 6:52 ` Nikolay Kudryavtsev
2017-07-24 23:50 ` Adam Porter
2017-07-27 11:58 ` Nikolay Kudryavtsev
2017-07-27 15:40 ` Nikolay Kudryavtsev
2017-07-29 1:23 ` Adam Porter
2017-07-29 16:26 ` Nikolay Kudryavtsev
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=87y3relr39.fsf@alphapapa.net \
--to=adam@alphapapa.net \
--cc=emacs-orgmode@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.