Mattias Jämting matt...@jwd.se writes:
Hello again,
For reference, this is how i finally got org-protocol to work in
chrome on ubuntu 10.10:
The problem was that chrome was running xdg-open for handling external
protocols. xdg-open, or it's companion gvfs-open, couldn't parse the
rather
Richard Riley rile...@gmail.com writes:
I'm trying to get FF working with org again -
http://orgmode.org/worg/org-contrib/org-protocol.php
It says
,
|1. Type about:config into the location bar and press enter.
|2. Click I'll be careful, I promise! to continue.
|3.
Richard Riley rile...@gmail.com writes:
Richard Riley rile...@gmail.com writes:
I'm trying to get FF working with org again -
http://orgmode.org/worg/org-contrib/org-protocol.php
It says
,
|1. Type about:config into the location bar and press enter.
|2. Click I'll be
Matt Lundin m...@imapmail.org writes:
Hi Richard,
e.g I want my new org item first line to be something like the following
if I invoke org-remember from conkeror on a web page having first
hilited blah blah somewhere on the page
With the following org-remember-template:
Hi Richard,
Richard Riley rileyrg...@gmail.com writes:
Does anyone have a w template which can store a hot link using the
page title (not just the url) in addition to the selection under the
title line? The problem I find is that I havent got the combo right to
do this : if I select
Jan Böcker jan.boec...@jboecker.de writes:
On 12.02.2010 23:23, dmg wrote:
For evince, I think I have found a problem in the parsing of the link.
Evince already encodes
the URL, but it does not encode the '/', hence you will get a link like this:
emacsclient
On 12.02.2010 23:23, dmg wrote:
For evince, I think I have found a problem in the parsing of the link.
Evince already encodes
the URL, but it does not encode the '/', hence you will get a link like this:
emacsclient
Basically, it is OK to url-encode each character who's binary
representation start with 1 (i.e., the value of the character is higher
than 127). The text to be url-encoded should be UTF-8 ideally.
If you use glib::ustring, it's easy to transform any iso-8859 string to
utf-8. Each character,
Jan Böcker jan.boec...@jboecker.de writes:
On 06.02.2010 14:50, Jan Böcker wrote:
AFAIK, your current approach is correct.
I was wrong. The attached patch fixes a bug in the encode_uri function.
That fixes the non-ASCII characters problem in xournal for me.
The gchar type is just typedef'd
I have been looking around and I am not sure how to solve this
problem. Withing Evince and Xournal I am encoding any non alphanum (as
defined by the C macro) each byte that is contained in the filename
individually.
Does anybody know which are the characters above 0 (zero) that need to
be
On 06.02.2010 14:50, Jan Böcker wrote:
AFAIK, your current approach is correct.
I was wrong. The attached patch fixes a bug in the encode_uri function.
That fixes the non-ASCII characters problem in xournal for me.
The gchar type is just typedef'd to char, which means it is signed. To
get the
Hi Carsten and Andreas,
thanks to Kenichi Handa, here is a proposal to fix the issus mentioned
below. I tested it in emacs 22 and 23 and it seems to work just fine.
Carsten, as always if I use some new elisp construct, please review the
patch. I used `eval-when-compile' and `defsubst' to
On Wed, 11 Nov 2009 10:06:36 +0100
Sebastian Rose sebastian_r...@gmx.de wrote:
Andreas, could you check if it works for you, too?
Yes, it works with both 23 and 22.
Thanks for your effort.
Andreas
___
Emacs-orgmode mailing list
Remember: use
Andreas Burtzlaff and...@gmx.net writes:
On Wed, 11 Nov 2009 10:06:36 +0100
Sebastian Rose sebastian_r...@gmx.de wrote:
Andreas, could you check if it works for you, too?
Yes, it works with both 23 and 22.
Thanks for your effort.
Tanks for checking Andreas,
Sebastian
Hi Andreas,
seems this has to do with the internal encoding of Emacs.
I need some advice at this point from the emacs-devel list.
I'll be back if I find out something.
Andreas Burtzlaff and...@gmx.net writes:
Hello Sebastian,
I'm not sure you noticed the org-protocol bug in this thread
Matthew Lundin m...@imapmail.org writes:
[...]
As for FF, the instructions should work. See also:
http://kb.mozillazine.org/Register_protocol#Linux_and_Mac
These instructions are incorrect. I can confirm that setting a protocol
does not work in Firefox on Mac OS - there is a bug that's
Sebastian Rose sebastian_r...@gmx.de writes:
Greg Newman g...@20seven.org writes:
I did try to get it working with Firefox 3.x and it's not working.
I followed the worg instructions (
http://orgmode.org/worg/org-contrib/org-protocol.php ) for FF and tried the
verification links with no
Matthew Lundin m...@imapmail.org writes:
My apologies for the initial post fragment. (Note to self: C-c C-c
binding for jumping to footnote reference does not work in Gnus!)
Let's try this again:
Hi all,
I've recently begun to use org-protocol. I've been using it with the
intriguing
Sebastian Rose sebastian_r...@gmx.de writes:
Matthew Lundin m...@imapmail.org writes:
But I thought it might be a nice addition to org-protocol if there were
a variable that accomplishes this (e.g.,
org-protocol-remember-in-new-frame). I'd be eager to know if I am
missing a current way to
My apologies for the initial post fragment. (Note to self: C-c C-c
binding for jumping to footnote reference does not work in Gnus!)
Let's try this again:
Hi all,
I've recently begun to use org-protocol. I've been using it with the
intriguing emacs-inspired browser Conkeror.[1] With the help of
Sebastian, Carsten,
Carsten Dominik carsten.domi...@gmail.com wrote:
Ulf, can you do some testing, please?
done that using Emacs 23 (cvs today), Org (git today + patch), Firefox
3.0.8 on linux. Everything seems to work fine, I haven't found a single
page/text that hasn't been encoded
Sebastian Rose sebastian_r...@gmx.de writes:
Hi Sebastian,
the issue should be fixed now. The docs should now match the reality.
Your templates may refer to the page title through
%:description
See
http://orgmode.org/worg/org-contrib/org-protocol.php#example-template
once it's
Tassilo Horn tass...@member.fsf.org writes:
But one question remains. Do I have to do some special quoting in order
to allow the protocol to split URL, TITLE and TEXT correctly? Let's say
I do
emacsclient -c \
'org-protocol:/remember:/http://www.google.de/the search engine/bla fasel
23 matches
Mail list logo
