From: Fabrice Popineau <fabrice.popineau@supelec.fr>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>, e.fraga@ucl.ac.uk
Subject: Re: Emacs server and org-protocol
Date: Wed, 17 Sep 2014 11:41:25 +0200 [thread overview]
Message-ID: <CAFgFV9NFK358rFMZiHhOj5Rb6+pkoEW5FNovtemyQXk=6zfvOQ@mail.gmail.com> (raw)
In-Reply-To: <87k352zkdh.fsf@ucl.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 1574 bytes --]
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 (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
[-- Attachment #2: Type: text/html, Size: 2306 bytes --]
next prev parent reply other threads:[~2014-09-17 9:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 7:26 Emacs server and org-protocol Gonzalo Camarillo
2014-09-17 7:36 ` Paul Rudin
2014-09-17 8:17 ` Gonzalo Camarillo
2014-09-17 7:46 ` Fabrice Popineau
2014-09-17 7:56 ` Paul Rudin
2014-09-17 8:43 ` Fabrice Popineau
2014-09-17 8:54 ` Alexis
2014-09-17 9:06 ` Eric S Fraga
2014-09-17 9:13 ` Alexis
2014-09-17 9:41 ` Fabrice Popineau [this message]
2014-09-17 10:57 ` Eric S Fraga
2014-09-17 13:50 ` Stefan Huchler
2014-09-17 14:03 ` Rainer M Krug
2014-09-17 20:11 ` Stefan Huchler
2014-09-18 1:03 ` Alexis
2014-09-17 19:57 ` Brett Viren
2014-09-17 8:03 ` Thorsten Jolitz
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='CAFgFV9NFK358rFMZiHhOj5Rb6+pkoEW5FNovtemyQXk=6zfvOQ@mail.gmail.com' \
--to=fabrice.popineau@supelec.fr \
--cc=e.fraga@ucl.ac.uk \
--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).