unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: Accelerating Emacs?
Date: Fri, 28 Oct 2005 15:16:35 +0200	[thread overview]
Message-ID: <u3bmleq8c.fsf@gnu.org> (raw)
In-Reply-To: <BAY112-F32470D1EA45AA4DAEA7C08DA6B0@phx.gbl> (herberteuler@hotmail.com)

> From: "Herbert Euler" <herberteuler@hotmail.com>
> Date: Fri, 28 Oct 2005 19:38:26 +0800
> 
> >Primitive operations that are used a lot and need to be fast are
> >written in C, not in Lisp.
> 
> But at least the searching, syntax highlighting, tags processing,
> and some other modules are written in Lisp

They are written in Lisp, but they make heavy use of search and syntax
primitives that are written in C.

> >FWIW, on a reasonably fast machine, I find Emacs reasonably fast for
> >day-to-day operation.
> 
> I believe this is true. But hey, lots of algorithms that are very effective
> in general cases have to face some really bad situation, just like I
> mentioned here.

Sure, but making decisions about the tools you use based on such rare
bad situations is not a very wise thing to do, is it?

> Is it possible to improve the behaviour of Emacs in such situations?

It might be.  Feel free to report such cases as bugs, and the
developers will see if there's something that should be done.

  reply	other threads:[~2005-10-28 13:16 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-28  2:25 Accelerating Emacs? Herbert Euler
2005-10-28  8:25 ` Eli Zaretskii
2005-10-28 11:38   ` Herbert Euler
2005-10-28 13:16     ` Eli Zaretskii [this message]
     [not found] ` <mailman.13045.1130488013.20277.help-gnu-emacs@gnu.org>
2005-11-28  1:09   ` Christopher C. Stacy
2005-11-28  5:21     ` Eli Zaretskii
     [not found]     ` <mailman.17015.1133155279.20277.help-gnu-emacs@gnu.org>
2005-11-28  5:46       ` Pascal Bourguignon
2005-11-28 10:26         ` Thien-Thi Nguyen
2005-12-01  4:43         ` Stefan Monnier
     [not found] <mailman.12998.1130466347.20277.help-gnu-emacs@gnu.org>
2005-10-28  2:59 ` Flying Grass
2005-10-28  5:53   ` Herbert Euler
2005-10-28  8:23     ` Eli Zaretskii
2005-10-28 11:31       ` Herbert Euler
2005-10-28 13:13         ` Eli Zaretskii
     [not found]     ` <mailman.13044.1130487836.20277.help-gnu-emacs@gnu.org>
2005-10-28 10:36       ` Per Abrahamsen
     [not found] <mailman.13033.1130478796.20277.help-gnu-emacs@gnu.org>
2005-10-28  8:59 ` Alan Mackenzie
2005-10-28 18:28   ` Herbert Euler
2005-10-29 10:18     ` Eli Zaretskii
2005-10-29 11:44       ` Herbert Euler
2005-10-29 15:43         ` Eli Zaretskii
2005-10-31  3:26           ` Herbert Euler
     [not found] <mailman.13061.1130499101.20277.help-gnu-emacs@gnu.org>
2005-10-28 12:08 ` David Kastrup
2005-10-28 13:43   ` Herbert Euler
2005-10-28 12:49 ` Thien-Thi Nguyen
2005-11-01  4:55 ` Stefan Monnier

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=u3bmleq8c.fsf@gnu.org \
    --to=eliz@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.
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).