From: Michael Albinus <michael.albinus@gmx.de>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: emacs-devel@gnu.org
Subject: Re: Recent recentf slowdown due to "/ftp:..."
Date: Sun, 05 Jul 2009 17:53:47 +0200 [thread overview]
Message-ID: <87prcfdt2s.fsf@gmx.de> (raw)
In-Reply-To: <87d48gln8p.fsf@escher.local.home> (Stephen Berman's message of "Sat, 04 Jul 2009 13:08:06 +0200")
Stephen Berman <stephen.berman@gmx.net> writes:
> I have confirmed that while the problem occurs with my first post-branch
> build, GNU Emacs 23.1.50.1 (i686-pc-linux-gnu, GTK+ Version 2.14.4) of
> 2009-06-23 on escher (and still with current build of 2009-06-30), it
> does not occur with my last pre-branch build, GNU Emacs 23.0.94.2
> (i686-pc-linux-gnu, GTK+ Version 2.14.4) of 2009-06-14 on escher.
> Whatever causes the pause seems to leave a trace in resident memory that
> prevents the pause, so testing requires a fresh login session. Because
> of this, unfortunately, I do not have time to revert from CVS to find
> the problematic change. Unless someone can suggest another way to
> locate it, I'll just add this to the bugtracker and hope it gets fixed.
I've tried to reproduce the problem exactly as you have described, it
doesn't happen to me.
What is the exact GNU/Linux distribution you are using? Which desktop
are you using (Gnome? KDE? Something different?) Is GVFS running after
your login? Is GVFS running after the first Emacs start, including the
pause?
I'm checking, whether the new tramp-gvfs.el package is involved.
> Steve Berman
Best regards, Michael.
next prev parent reply other threads:[~2009-07-05 15:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 8:06 Recent recentf slowdown? Stephen Berman
2009-06-26 3:44 ` Michael Albinus
2009-06-26 7:11 ` Stephen Berman
2009-07-02 8:56 ` Stephen Berman
2009-07-03 11:21 ` Recent recentf slowdown due to "/ftp:..." Stephen Berman
2009-07-04 11:08 ` Stephen Berman
2009-07-05 15:53 ` Michael Albinus [this message]
2009-07-06 8:06 ` Stephen Berman
2009-07-07 13:04 ` Stephen Berman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87prcfdt2s.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=stephen.berman@gmx.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.