From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fabrice Popineau Subject: Re: Emacs server and org-protocol Date: Wed, 17 Sep 2014 11:41:25 +0200 Message-ID: References: <541937A2.3040405@gmail.com> <87wq92ade6.fsf@rudin.co.uk> <87iokmy69i.fsf@gmail.com> <87k352zkdh.fsf@ucl.ac.uk> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e0116042017fafb05033fad8b Return-path: Received: from eggs.gnu.org ([208.118.235.92]:43161) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XUBkF-0007AN-QF for emacs-orgmode@gnu.org; Wed, 17 Sep 2014 05:41:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XUBkD-0007af-D3 for emacs-orgmode@gnu.org; Wed, 17 Sep 2014 05:41:51 -0400 Received: from mail-oa0-x22a.google.com ([2607:f8b0:4003:c02::22a]:44316) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XUBkD-0007ZT-4Y for emacs-orgmode@gnu.org; Wed, 17 Sep 2014 05:41:49 -0400 Received: by mail-oa0-f42.google.com with SMTP id o6so895798oag.29 for ; Wed, 17 Sep 2014 02:41:45 -0700 (PDT) In-Reply-To: <87k352zkdh.fsf@ucl.ac.uk> 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: "emacs-orgmode@gnu.org" , e.fraga@ucl.ac.uk --089e0116042017fafb05033fad8b Content-Type: text/plain; charset=UTF-8 2014-09-17 11:06 GMT+02:00 Eric S Fraga : > On Wednesday, 17 Sep 2014 at 18:54, Alexis wrote: > > [...] > > > If i may ask, which email front-end were you using? (Gnus, perhaps?) i > > used to use notmuch.el, and currently use mu4e, and basically don't have > > this issue .... > > The issue is not the email front-end per se but the email servers (IMAP, > POP, whatever). A couple of years ago, I ended up having to use an > email server that would take many seconds, often minutes, to access, > even just to query to find out if there was any new email. > > The easiest solution, for me, was to get into the habit of starting two > emacs instances. The first for all my work (org, writing, coding, etc.) > and a second just for email. The first starts the emacs server so > emacsclient always goes to the non-email instance. I've been doing this > for two years now and it has become second nature for me. > > Obviously, the real fix is to have proper multi-threading in Emacs and, > as in nuclear fusion, this will be with us *soon* ;-) > I disagree on this. The problem is less servers than the sheer slowness of elisp. And Gnus offers so many fancy opportunities to process your mail that it is easy to overuse it. Emacs won't become any more efficient without switching its own elisp implementation to something with a true compiler (or jit). Threading would gain some responsiveness, but that may not be so obvious nor so easy to implement. http://www.emacswiki.org/emacs/ConcurrentEmacs http://www.emacswiki.org/emacs/NoThreading Fabrice --089e0116042017fafb05033fad8b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


2014-09-17 11:06 GMT+02:00 Eric S Fraga <e.fraga@ucl.ac.uk>:
On Wednesday, 17 Sep 2014 at 18:54, Alexis wrote= :

[...]

> If i may ask, which email front-end were you using? (Gnus, perhaps?) i=
> used to use notmuch.el, and currently use mu4e, and basically don'= t have
> this issue ....

The issue is not the email front-end per se but the email servers (I= MAP,
POP, whatever).=C2=A0 A couple of years ago, I ended up having to use an email server that would take many seconds, often minutes, to access,
even just to query to find out if there was any new email.

The easiest solution, for me, was to get into the habit of starting two
emacs instances.=C2=A0 The first for all my work (org, writing, coding, etc= .)
and a second just for email.=C2=A0 The first starts the emacs server so
emacsclient always goes to the non-email instance.=C2=A0 I've been doin= g this
for two years now and it has become second nature for me.

Obviously, the real fix is to have proper multi-threading in Emacs and,
as in nuclear fusion, this will be with us *soon* ;-)
=
I disagree on this. The problem is less servers than the she= er slowness of elisp.
And Gnus offers so many fancy opportunities= to process your mail that it is easy to=C2=A0
overuse it.
<= div>
Emacs won't become any more efficient without switch= ing its own elisp implementation to something with a true compiler (or jit)= .

Threading would gain some responsiveness, but th= at may not be so obvious nor so easy to implement.

Fabrice
--089e0116042017fafb05033fad8b--