unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Wiegley <johnw@gnu.org>
Subject: Re: Is it just me, or did 21.3.50 get a whole lot slower?
Date: Thu, 02 Jan 2003 22:50:11 -0700	[thread overview]
Message-ID: <87u1gqpyss.fsf@alice.dynodns.net> (raw)
In-Reply-To: <E18UAEG-0003xK-00@fencepost.gnu.org> (Richard Stallman's message of "Thu, 02 Jan 2003 13:38:04 -0500")

[-- Attachment #1: Type: text/plain, Size: 720 bytes --]

>>>>> On Thu Jan  2, Richard writes:

>> This issue is now closed.  I discovered that the implementation of
>> "wide-column.el" was the culprit.  It was abusing the
>> post-command-hook in a way that worked in 21.2, but not in 21.3.
>> I have referred the problem to the author.

> Can you tell me what the problem is?  Maybe I should fix what
> broke.

I did not take the time to track it down, nor can I just yet.  I
would recommend talking with the author, as likely he will be
interested in fixing it to be compatible with 21.3.  His e-mail is:

  Phillip Lord <p.lord@russet.org.uk>

To reproduce, just load the module in 21.3 and start using it during
your regular workday.  The slow-down should become apparent.


[-- Attachment #2: wide-column.el --]
[-- Type: application/emacs-lisp, Size: 14092 bytes --]

[-- Attachment #3: Type: text/plain, Size: 6 bytes --]


John

[-- Attachment #4: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel

  reply	other threads:[~2003-01-03  5:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-14 20:32 Is it just me, or did 21.3.50 get a whole lot slower? John Wiegley
2002-06-14 20:55 ` D. Goel
2002-06-15 21:47   ` Richard Stallman
2002-06-16 18:38     ` D. Goel
2002-06-17 16:30       ` Richard Stallman
2002-06-18 16:36         ` D. Goel
2002-06-19  5:17           ` Eli Zaretskii
2002-06-19  6:01             ` John Wiegley
2002-06-19  6:23             ` D. Goel
2002-06-20 14:33           ` Richard Stallman
2002-06-15 17:19 ` Kai Großjohann
2002-06-15 21:47 ` Richard Stallman
2002-10-19  0:36   ` John Wiegley
2002-12-31  5:48     ` Richard Stallman
2002-12-31  6:12       ` John Wiegley
2003-01-02 18:38         ` Richard Stallman
2003-01-03  5:50           ` John Wiegley [this message]
2003-01-03 20:30             ` Richard Stallman
2003-01-04  4:12               ` John Wiegley
2003-01-04 23:54                 ` Kim F. Storm
2003-01-05 18:33                 ` Richard Stallman
2003-01-14 14:40               ` Phillip Lord
2003-01-14 20:12                 ` John Wiegley
2003-01-15 11:05                 ` Richard Stallman
2003-01-15 11:56                   ` Phillip Lord
2003-01-17  9:22                     ` Richard Stallman
2002-11-01  5:21   ` Looks like I found the slowdown John Wiegley
2002-11-02  3:32     ` Richard Stallman

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=87u1gqpyss.fsf@alice.dynodns.net \
    --to=johnw@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.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).