From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oleh Krehel Subject: Re: (message "Greedy org-protocol handler. Killing client.") Date: Wed, 24 Feb 2016 09:43:21 +0100 Message-ID: <87povmjy6u.fsf@gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52224) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aYV2e-0000mp-W0 for emacs-orgmode@gnu.org; Wed, 24 Feb 2016 03:43:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aYV2Z-0002m2-SG for emacs-orgmode@gnu.org; Wed, 24 Feb 2016 03:43:28 -0500 Received: from mail-wm0-x236.google.com ([2a00:1450:400c:c09::236]:33916) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aYV2Z-0002lt-Kp for emacs-orgmode@gnu.org; Wed, 24 Feb 2016 03:43:23 -0500 Received: by mail-wm0-x236.google.com with SMTP id b205so24762366wmb.1 for ; Wed, 24 Feb 2016 00:43:23 -0800 (PST) In-Reply-To: (Samuel Wales's message of "Tue, 23 Feb 2016 17:26:47 -0700") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Samuel Wales Cc: emacs-orgmode@gnu.org Samuel Wales writes: > org-protocol works less than half the time now. > > i try it with the org-capture firefox extension on iceweasel. i also > try it with a manual bookmark created by some instruction somewhere. > > today every click puts this in my messages buffer: > > "Greedy org-protocol handler. Killing client." > > could somebody please explain what this means? i do not understand the code. org-protocol works by advising `server-visit-files' in an obsolete way. I encountered this problem this week when I tried to advice `server-done' to do something clever with Itsalltext. It seems the `defadvice' on `server-visit-files' is incompatible with any other advice in that vicinity. I would get "Greedy org-protocol handler. Killing client." when I advised `server-done'. This error would disappear immediately after I disabled the advice. So I suggest examining your custom advises. And see if disabling some of them fixes the problem. And maybe someone could look into using something better than `defadvice' in org-protocol.el. Oleh