unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Chris Withers <chris@simplistix.co.uk>
Cc: 3252@emacsbugs.donarmstrong.com
Subject: bug#3252: 23.0.93; extremely slow to open file on windows network drive
Date: Tue, 12 May 2009 00:49:11 -0400	[thread overview]
Message-ID: <E1M3jvT-0005Et-VQ@fencepost.gnu.org> (raw)
In-Reply-To: <4A08A152.2060101@simplistix.co.uk> (message from Chris Withers on Mon, 11 May 2009 23:06:10 +0100)

> Date: Mon, 11 May 2009 23:06:10 +0100
> From: Chris Withers <chris@simplistix.co.uk>
> CC: 3252@emacsbugs.donarmstrong.com, Eli Zaretskii <eliz@gnu.org>
> 
> >   (setq vc-handled-backends nil)
> 
> With this, drag'n'drop time isstil about 8 seconds, and C-X d time is 
> about 12 seconds.
> 
> I guess it must be something else then...

I guess it is.

How large is the file, and what's in it?  Is it plain ASCII text or
does it have non-ASCII characters? if the latter, can you tell more
about the contents?

What mode does Emacs turn on when you visit that file?

Next, can you copy the file to your local filesystem and visit it from
there?  If you do, how much time does it take then?

Finally, is the time to visit the file with "C-x C-f" comparable with
the time needed when you drag-n-drop it?  How about the time to visit
it with "M-x find-file-literally RET"?






  reply	other threads:[~2009-05-12  4:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4A13FD0A.5070306@gnu.org>
2009-05-10 22:13 ` bug#3252: 23.0.93; extremely slow to open file on windows network drive Chris Withers
2009-05-11  3:06   ` Eli Zaretskii
2009-05-11  8:36     ` Chris Withers
2009-05-11 18:08       ` Eli Zaretskii
2009-05-11 18:11         ` Chris Withers
2009-05-11 18:25           ` Eli Zaretskii
2009-05-11 18:28             ` Chris Withers
2009-05-11 18:41               ` Eli Zaretskii
2009-05-11 21:15           ` Stefan Monnier
2009-05-11 22:06             ` Chris Withers
2009-05-12  4:49               ` Eli Zaretskii [this message]
2009-05-16 16:23                 ` Chris Withers
2009-05-16 17:48                   ` Eli Zaretskii
2009-05-18 10:16                     ` Chris Withers
2009-05-18 10:37                       ` Lennart Borgman
2009-05-18 12:41                         ` Jason Rumney
2009-05-18 12:49                           ` Lennart Borgman
2009-05-18 18:19                       ` Eli Zaretskii
2009-05-18 19:13                         ` Chris Withers
2009-05-18 20:31                           ` Eli Zaretskii
2009-05-19  2:12                           ` Stefan Monnier
2009-05-20 10:35                             ` Chris Withers
2009-05-20 13:00   ` bug#3252: marked as done (23.0.93; extremely slow to open file on windows network drive) Emacs bug Tracking System

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=E1M3jvT-0005Et-VQ@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=3252@emacsbugs.donarmstrong.com \
    --cc=chris@simplistix.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.
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).