From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: Willing to debug bug #3542 (23.0.94; File access via UNC path slow again under Windows) Date: Thu, 9 Jul 2009 10:03:42 -0700 Message-ID: References: <7dbe73ed0907051401o26903ca3t9a67060f3a3417ad@mail.gmail.com> <83fxda1pef.fsf@gnu.org><7dbe73ed0907060038w53699f77ie742996955ae8118@mail.gmail.com> <838wj11sz4.fsf@gnu.org> <83my7fz09s.fsf@gnu.org><7dbe73ed0907081347q12dfd1a2lbbff915c49362f75@mail.gmail.com> <4A55D68D.8050407@gnu.org> <7dbe73ed0907090453s3e125b4ar142b90a268b105e2@mail.gmail.com> <7DAFC004A33C486A9E29A59689E7F02E@us.oracle.com> <4A5619F5.8010008@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1247159078 10625 80.91.229.12 (9 Jul 2009 17:04:38 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 9 Jul 2009 17:04:38 +0000 (UTC) Cc: 'Eli Zaretskii' , emacs-devel@gnu.org, 'Mathias Dahl' To: "'Jason Rumney'" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 09 19:04:30 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MOx2r-0004uj-Lp for ged-emacs-devel@m.gmane.org; Thu, 09 Jul 2009 19:04:29 +0200 Original-Received: from localhost ([127.0.0.1]:52464 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MOx2q-0005xl-SS for ged-emacs-devel@m.gmane.org; Thu, 09 Jul 2009 13:04:28 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MOx2K-0005jR-S3 for emacs-devel@gnu.org; Thu, 09 Jul 2009 13:03:56 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MOx2F-0005gw-Et for emacs-devel@gnu.org; Thu, 09 Jul 2009 13:03:55 -0400 Original-Received: from [199.232.76.173] (port=48064 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MOx2F-0005gm-9v for emacs-devel@gnu.org; Thu, 09 Jul 2009 13:03:51 -0400 Original-Received: from acsinet11.oracle.com ([141.146.126.233]:47444) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MOx2B-0000wo-55; Thu, 09 Jul 2009 13:03:47 -0400 Original-Received: from rgminet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by acsinet11.oracle.com (Switch-3.3.1/Switch-3.3.1) with ESMTP id n69H3fIE032451 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 9 Jul 2009 17:03:43 GMT Original-Received: from abhmt002.oracle.com (abhmt002.oracle.com [141.146.116.11]) by rgminet15.oracle.com (Switch-3.3.1/Switch-3.3.1) with ESMTP id n69H3mUR027704; Thu, 9 Jul 2009 17:03:48 GMT Original-Received: from dradamslap1 (/130.35.178.194) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 09 Jul 2009 10:03:39 -0700 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <4A5619F5.8010008@gnu.org> Thread-Index: AcoAsi1w7tSA6LoUTEi/tUgjzNQCWAABLBmA X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-Source-IP: abhmt002.oracle.com [141.146.116.11] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A010209.4A5622EC.015C:SCFSTAT5015188,ss=1,fgs=0 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 1) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:112249 Archived-At: > > Dumb question: Is there a way for Emacs to know whether the > > format is NTFS or FAT(32)? If so, then Emacs could use nil > > for FAT volumes. > > That suggestion dates back to the days when "fast machines" > were running at 200MHz or so. The problem here is not the > speed of the machine, but the network. The default value of > w32-get-true-file-attributes is 'local, which means nil when > going across the network, but apparently that is not being > recognized in all places - which I think is what Eli > is investigating. I see (I think). I thought that the doc was saying that it should be non-nil only for NTFS, which should be independent of whether the file system is local or over a network.