unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Richard M. Stallman" <rms@gnu.org>
To: martin rudalics <rudalics@gmx.at>, 961@emacsbugs.donarmstrong.com
Cc: 961@emacsbugs.donarmstrong.com, bug-gnu-emacs@gnu.org,
	bug-submit-list@donarmstrong.com
Subject: bug#961: 23.0.60; Excess consing visiting files
Date: Thu, 11 Sep 2008 13:08:05 -0400	[thread overview]
Message-ID: <E1KdpeH-0004SE-Li@fencepost.gnu.org> (raw)
In-Reply-To: <48C90392.7090604@gmx.at> (message from martin rudalics on Thu, 11 Sep 2008 13:40:02 +0200)

    It might be completely unrelated but did you look at Bug#122?  Len Trigg
    reports that he had 200 open buffers "(about 170 of which are named like
    *code-conversion-work*<nnn>)".

I just saw that a few minutes ago.

Just now I have one buffer called ` *code-conversion-work*'
and one called ` *code-converting-work*'.  I think these names
are confusingly similar; they should be changed so that it is clear
why they are different and what each one is used for.

But there is only one of each.  This certainly does not explain why,
shortly after `emacs -Q', visiting that short file makes 40k of strings.

Next time it gets slow, I will investigate what hidden buffers I
have,







      reply	other threads:[~2008-09-11 17:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-11 11:03 bug#961: 23.0.60; Excess consing visiting files Richard M. Stallman
2008-09-11 11:40 ` martin rudalics
2008-09-11 17:08   ` Richard M. Stallman [this message]

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=E1KdpeH-0004SE-Li@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=961@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=bug-submit-list@donarmstrong.com \
    --cc=rudalics@gmx.at \
    /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).