From: Konstantin Kliakhandler <kosta@slumpy.org>
To: Ken Mankoff <mankoff@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: New Chrome Extension
Date: Tue, 7 Jul 2015 19:57:37 +0300 [thread overview]
Message-ID: <CAH+LVpkMGvRbsap1TaKaqW-XUnQpfddoPp-JoCsOjCkz4oc4_g@mail.gmail.com> (raw)
In-Reply-To: <m28uasndfo.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2233 bytes --]
Hello Ken,
The first user, hurrah!
You were right to add the capture templates - I will update the docs to be
more clear about that. I think the first thing to add to the extension now
that it is in the open is to add configuration for the targets...
Here are the templates that I use (I need to replace the captured on: with
a property at some point, but this is beside the point):
("L" "Protocol Link" entry (file+headline ,(concat org-directory "notes.org")
"Inbox") "* %? [[%:link][%:description]] \nCaptured On: %U")
("p" "Protocol" entry (file+headline ,(concat org-directory "notes.org")
"Inbox")
"* %^{Title}\nSource: %u, %c\n
#+BEGIN_QUOTE\n%i\n#+END_QUOTE\n\n\n%?")
I can't recall at the moment why I use the nicer format replacements for
the link and the shorter for the full quote, and it might not matter. Could
you try to make your "p" template similar to mine and see if it works?
Alternatively, can you paste the templates you used?
Cheers,
Kosta
--
Konstantin Kliakhandler
http://slumpy.org
)°) )°( (°(
On 7 July 2015 at 19:24, Ken Mankoff <mankoff@gmail.com> wrote:
>
> On 2015-07-07 at 12:16, Ken Mankoff <mankoff@gmail.com> wrote:
> > Hi Konstantin,
> >
> > On 2015-07-07 at 11:44, Konstantin Kliakhandler <kosta@slumpy.org>
> wrote:
> >> I wrote up a small chrome extension for org-protocol. Comments,
> >> improvements and positive criticism are all welcome.
> >
> > Thanks for making this. I just set up org-protocol and pass the
> > "install test" on that page. Now when I click on your icon/extension
> > Emacs comes to the foreground and I see the following error in the
> > modeline:
> >
> >> No capture template referred to by "L" keys
> >
> > And in *Messages* I see:
> >
> >> Greedy org-protocol handler. Killing client.
> >> No server editing buffers exist
> >> No capture template referred to by "L" keys
>
> If I add a capture template with hotkey "L" I get the same message but for
> "p". If I add a capture template with the hotkey "p" then it appears to
> mostly work, but I don't get selected text. I do get a link to the webpage
> as the capture item body.
>
> -k.
>
[-- Attachment #2: Type: text/html, Size: 3412 bytes --]
next prev parent reply other threads:[~2015-07-07 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 15:44 New Chrome Extension Konstantin Kliakhandler
2015-07-07 16:16 ` Ken Mankoff
2015-07-07 16:24 ` Ken Mankoff
2015-07-07 16:57 ` Konstantin Kliakhandler [this message]
2015-07-07 17:13 ` Ken Mankoff
2015-07-07 17:31 ` Konstantin Kliakhandler
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAH+LVpkMGvRbsap1TaKaqW-XUnQpfddoPp-JoCsOjCkz4oc4_g@mail.gmail.com \
--to=kosta@slumpy.org \
--cc=emacs-orgmode@gnu.org \
--cc=mankoff@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).