From: Robert Marshall <spam@capuchin.co.uk>
To: help-gnu-emacs@gnu.org
Subject: Re: emacs slow on dired renaming
Date: Sat, 05 Apr 2014 13:32:51 +0100 [thread overview]
Message-ID: <87r45crm6k.fsf@capuchin.co.uk> (raw)
In-Reply-To: mailman.18977.1396698988.10748.help-gnu-emacs@gnu.org
On Sat, Apr 05 2014, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Robert Marshall <spam@capuchin.co.uk>
>> Date: Sat, 05 Apr 2014 12:09:42 +0100
>>
>> - call-interactively 1227 97%
>> - dired-do-rename 1083 86%
>> - dired-do-create-files 1083 86%
>> - dired-create-files 962 76%
>> - byte-code 952 75%
>> - dired-rename-file 766 61%
>> - dired-rename-subdir 568 45%
>> - dired-fun-in-all-buffers 180 14%
>
> According to this, dired-rename-subdir, dired-rename-file, and
> dired-create-files took 70% of the time. But I have no idea why.
>
> Did you try turning on garbage-collection-messages?
>
I didn't but have just tried it and there are no garbage collection messages
> If that doesn't give any clues, I guess the only way is to selectively
> disable portions of your ~/.emacs, to find which part causes this.
>
> Alternatively, try running "emacs -Q" for some time, and see if things
> get slower there as well.
>
I'm giving it a go with -Q and will report back - thanks!
Robert
--
La grenouille songe..dans son château d'eau
Links and things http://rmstar.blogspot.com/
next prev parent reply other threads:[~2014-04-05 12:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 6:57 emacs slow on dired renaming Robert Marshall
2014-04-03 14:52 ` Eli Zaretskii
[not found] ` <mailman.18826.1396536739.10748.help-gnu-emacs@gnu.org>
2014-04-03 18:57 ` Robert Marshall
2014-04-03 20:03 ` Eli Zaretskii
[not found] ` <mailman.18866.1396555421.10748.help-gnu-emacs@gnu.org>
2014-04-04 13:17 ` Robert Marshall
2014-04-04 14:02 ` Eli Zaretskii
[not found] ` <mailman.18922.1396620169.10748.help-gnu-emacs@gnu.org>
2014-04-05 8:50 ` Robert Marshall
2014-04-05 9:22 ` Eli Zaretskii
2014-04-05 13:55 ` Stefan Monnier
[not found] ` <mailman.18986.1396706186.10748.help-gnu-emacs@gnu.org>
2014-04-05 15:09 ` Robert Marshall
[not found] ` <mailman.18966.1396689747.10748.help-gnu-emacs@gnu.org>
2014-04-05 11:09 ` Robert Marshall
2014-04-05 11:56 ` Eli Zaretskii
[not found] ` <mailman.18977.1396698988.10748.help-gnu-emacs@gnu.org>
2014-04-05 12:32 ` Robert Marshall [this message]
2014-04-06 12:39 ` Robert Marshall
2014-04-06 16:21 ` Eli Zaretskii
[not found] ` <mailman.19055.1396801288.10748.help-gnu-emacs@gnu.org>
2014-04-06 17:21 ` Robert Marshall
2014-04-09 9:41 ` Robert Marshall
2014-04-09 12:50 ` Robert Marshall
2014-04-09 13:17 ` Stefan Monnier
[not found] ` <mailman.19290.1397049474.10748.help-gnu-emacs@gnu.org>
2014-04-09 15:12 ` Robert Marshall
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=87r45crm6k.fsf@capuchin.co.uk \
--to=spam@capuchin.co.uk \
--cc=help-gnu-emacs@gnu.org \
--cc=robert@capuchin.co.uk \
/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).