Re: [O] capture with iceweasel/firefox -- nothing works

[Samuel Wales]

hi matt,

thanks for your reply.

On 6/3/16, Matt Lundin <address@hidden> wrote:
> Here is the new style bookmark that works for me:
>
> javascript:location.href='org-protocol://capture?url='+encodeURIComponent(location.href)+'&title='+encodeURIComponent(document.title)+'&body='+encodeURIComponent(window.getSelection())
>
> I also placed the following in
> ~/.local/share/applications/emacsclient.desktop:
>
> --8<---------------cut here---------------start------------->8---
> [Desktop Entry]
> Name=Emacs Client
> Exec=emacsclient %u
> Icon=emacs-icon
> Type=Application
> Terminal=false
> MimeType=x-scheme-handler/org-protocol;
> --8<---------------cut here---------------end--------------->8---
>

will try.

> Since you are not using a desktop environment, you might also need to
> make sure that the appropriate xdg tools are installed. On arch linux
> the package is xdg-utils.

debian
xdg-utils:
  Installed: 1.1.0~rc1+git20111210-7.4

>
> I'd recommend copying and pasting the javascript line above into the
> location bar to confirm whether it works. If it does, you can then
> easily add it to your bookmarks.

will try.  this is supposed to imitate clicking on the unicorn or
calling the bookmark?

do i try with selecting and without selecting?

which capture key does it call?

i always run the emacs server in my regular emacs.  i don't
use the daemon.

however, i never found any good instructions on what to do to add js
to bookmarks.
i have a menu bar and a location bar + icons.  i'd like a button or
icon on the latter if possible.  my previous thrashing around caused a
>> symbol which is a drop down menu which contains the bookmarks.
i'll settle for that if nec.  but that is extra clicking i'd rather
avoid, and one of them brings up a page with js on it.

is this knowledge something that everybody except me possesses?  :)

===

the full error is:
Greedy org-protocol handler.  Killing client.
No server buffers remain to edit

>
> Note: There is a bug in the implementation of the new org-protocol url
> processing that can lead to multiple "greedy protocol" warnings. (I
> posted a bug report about this a week or so ago.)
>
> Hope this helps.
> Matt
>

thanks.


samuel