From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: Accelerating Emacs?
Date: Sat, 29 Oct 2005 12:18:27 +0200 [thread overview]
Message-ID: <u7jbwsk24.fsf@gnu.org> (raw)
In-Reply-To: <BAY112-F21766C03DD342B1D57D6F0DA6B0@phx.gbl> (herberteuler@hotmail.com)
> From: "Herbert Euler" <herberteuler@hotmail.com>
> Date: Sat, 29 Oct 2005 02:28:30 +0800
>
> And are there some configuration steps before using Emacs
> in Windows?
Not as far as performance is concerned, no (to the best of my
knowledge).
> I typed
>
> M-x texinfo-format-buffer
>
> in the buffer associated with 'emacs-lisp-intro.texi'. On the same
> machine, Emacs in Windows didn't finish it in 10min, while Emacs
> in Debian finished it very quickly in no more than 1min.
That's very strange. On my 3GHz box, the above takes 6 seconds in the
Windows port of the CVS Emacs. What version of Emacs are you using
(what does "M-x emacs-version RET" display)?
> Am I having some config problems?
There's a problem, allright, but I'm unsure what kind, exactly. When
you invoke "M-x texinfo-format-buffer", do you see in the echo area
messages like the following:
Formatting: Passing the argument ...
Formatting: Passing a negative argument ...
Formatting: @code{yank-pop} ...
Formatting: The @file{ring.el} File ...
Formatting: A Graph with Labelled Axes ...
Formatting: Labelled Example Graph ...
Formatting: The @code{print-graph} Varlist ...
Formatting: The @code{print-Y-axis} Function ...
Formatting: What height should the label be? ...
Formatting: Side Trip: Compute a Remainder ...
Formatting: Construct a Y Axis Element ...
Formatting: Create a Y Axis Column ...
Formatting: The Not Quite Final Version of @code{print-Y-axis} ...
Formatting: The @code{print-X-axis} Function ...
Formatting: Similarities and differences ...
next prev parent reply other threads:[~2005-10-29 10:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.13033.1130478796.20277.help-gnu-emacs@gnu.org>
2005-10-28 8:59 ` Accelerating Emacs? Alan Mackenzie
2005-10-28 18:28 ` Herbert Euler
2005-10-29 10:18 ` Eli Zaretskii [this message]
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
[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
2005-10-28 2:25 Herbert Euler
2005-10-28 8:25 ` Eli Zaretskii
2005-10-28 11:38 ` Herbert Euler
2005-10-28 13:16 ` Eli Zaretskii
[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
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=u7jbwsk24.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).