emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Daniel Martins <danielemc@gmail.com>
To: Andreas Burtzlaff <andy13@gmx.net>
Cc: "emacs-orgmode@gnu.org" <Emacs-orgmode@gnu.org>
Subject: Re: Fireforg, a Firefox extension for Org mode interaction
Date: Sat, 8 Aug 2009 17:09:35 -0300	[thread overview]
Message-ID: <6ac505ad0908081309ob582892lb0ad0d83d13076ff@mail.gmail.com> (raw)
In-Reply-To: <20090808214503.52ab916d.andy13@gmx.net>

[-- Attachment #1.1: Type: text/plain, Size: 1848 bytes --]

The issue on org-agenda-files was solved. It was my mistake, sorry.

The firefox plugin:

(right click on the statusbar entry) : works in a limited sense. It pops up
the remember and store-links options but nothing happens when I left-click
on both fields.

(left click on the statusbar entry) : does absolutely nothing.


2009/8/8 Andreas Burtzlaff <andy13@gmx.net>

> On Sat, 8 Aug 2009 14:19:35 -0300
> Daniel Martins <danielemc@gmail.com> wrote:
> > I followed your indications but it did not work properly.
> >
> > 1. My org-agenda-files became nil I dont know the reason
> org-agenda-files is not altered in my code.
> I made a small mistake in the original posting and am changing the
> installation now anyway, but for the time being:
> Do you mean the debug message:
> "org-registry-initialize: org-agenda-files = nil"
> and did you put the lisp code into .emacs?
> In that case make
> (org-registry-initialize t)
> the very _last_ line in your .emacs .
> I'll put a page on Worg soon...
> My apologies for the inconvenience.
> By the way, these kind of emacs configuration issues are a reason why
> packaging is a bit problematic, at least at this stage of development.
> >
> > 2. The plugin was properly installed in firefox but it did not talk
> > propoerly with emacsclient. Nothing happens on emacs.
> What exactly did you try?
> Your issue 1. prevents the url lookup to work, so I'd only expect
> "store-link" and "remember" to work anyway. (right click on the statusbar
> entry)
> Does org-protocol itself work with the bookmarks described in its
> manual?
> Generally, error messages in firefox are shown in Tools->Error Console:
> Look for errors containing: "chrome://fireforg/" , and send them to me
> (privately, not through the list, perhaps).
> Thanks for your help and patience in testing
> Andreas

[-- Attachment #1.2: Type: text/html, Size: 2462 bytes --]

[-- Attachment #2: Type: text/plain, Size: 204 bytes --]

Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.

  reply	other threads:[~2009-08-08 20:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-07  4:54 Fireforg, a Firefox extension for Org mode interaction Andreas Burtzlaff
     [not found] ` <6ac505ad0908070500u46f9055fk5e3690b3ba4103d8@mail.gmail.com>
     [not found]   ` <20090807165316.93eddce6.andy13@gmx.net>
2009-08-07 15:08     ` Daniel Martins
2009-08-08 17:19       ` Daniel Martins
2009-08-08 19:45         ` Andreas Burtzlaff
2009-08-08 20:09           ` Daniel Martins [this message]
2009-08-08 20:50             ` Andreas Burtzlaff
2009-08-09  4:16 ` Fireforg, a Firefox extension for Org mode interaction (Moved to Worg) Andreas Burtzlaff

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:

  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=6ac505ad0908081309ob582892lb0ad0d83d13076ff@mail.gmail.com \
    --to=danielemc@gmail.com \
    --cc=Emacs-orgmode@gnu.org \
    --cc=andy13@gmx.net \


* 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


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).