emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Robin Green <greenrd@greenrd.org>
To: emacs-orgmode@gnu.org
Subject: Re: adding new protocol handler in firefox
Date: Thu, 19 Nov 2009 21:43:26 +0000	[thread overview]
Message-ID: <m31vjudwch.wl%greenrd@greenrd.org> (raw)
In-Reply-To: <87y6m246q6.fsf@gmx.de>

At Thu, 19 Nov 2009 21:09:21 +0100,
Sebastian Rose wrote:
> Well, anyway, editing RDF files by hand is not the way to go.

Indeed. This was the method that worked for me (thanks to "goncheff"
for discovering it):

1. In about:config, create a boolean key
"network.protocol-handler.expose.org-protocol" and set it to False
2. Create a simple web page containing a link to the URL org-protocol://test
3. Open the web page you just created
4. Click on the link
5. Choose emacsclient as the associated application in the dialog box
that appears

and no other method worked (although I didn't know about the "edit the RDF
file" method).

It isn't, of course, necessary to create a web page - you can use an
existing one with such a link - but it *is* necessary to click on a
link in a web page - selecting a bookmarklet no longer works in the
latest Firefox release, at least on Ubuntu 9.10 and on Mac OS X, and
probably elsewhere too.

-- cut here --

I guess I should create a patch to worg to include the above
instructions for newer versions of Firefox. Unless people think the
RDF editing method is better?

> Instead, we should link to descriptions on how install the handlers
> system wide.

Nice idea, but unfortunately on Linux (as far as I know) there is no
standard way to do that.
-- 
Robin

  parent reply	other threads:[~2009-11-20 10:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-19 17:22 adding new protocol handler in firefox Thierry Volpiatto
2009-11-19 18:43 ` Sebastian Rose
2009-11-19 20:09   ` Sebastian Rose
2009-11-19 20:51     ` Thierry Volpiatto
2009-11-19 21:43     ` Robin Green [this message]
2009-11-20 22:01       ` Sebastian Rose
2009-11-21 22:39         ` Thierry Volpiatto

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=m31vjudwch.wl%greenrd@greenrd.org \
    --to=greenrd@greenrd.org \
    --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 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).