[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#7308: [patch] locate under windoze

From: Thierry Volpiatto
Subject: bug#7308: [patch] locate under windoze
Date: Sun, 31 Oct 2010 10:48:20 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2.50 (gnu/linux)

Eduard Wiebe <address@hidden> writes:

> Eli Zaretskii <address@hidden> writes:
>>> From: Eduard Wiebe <address@hidden>
>>> Date: Sat, 30 Oct 2010 21:50:18 +0200
>>> Cc: 
>>> i want to use `locate' under windoze system.  Unfortunately locate (in
>>> interaction with dired) doesn't work proper in such a case.
>>> The problem is the unquoted backslash in a located file path.
>>> So i fix this issue by following patch.
>> Thanks.
>> Please tell what version of `locate' is that, and in which Emacs
>> version it happened to you.
> I use emacs-23.2 with command line interface of everything search engine
> from http://www.voidtools.com (es.exe) as locate command under MS
> Windows XP.

So if you use this, you should try anything-locate that work fine with
everything.(no setting needed)

>> I understand that the problem happens because your version of `locate'
>> returns Windows file names with backslashes as directory separators
>> (as opposed to forward slashes), is that right?
> Yes, that is correct. 
> The second culprit is `directory-listing-before-filename-regex', which
> is to restrict and cause fails under Windoze. Under Linux leads the
> restricted regexp only to incorrect display (the point is always after
> the first slash character).
> I tested the simplyfied version of
> `directory-listing-before-filename-regex' under Windoze with everything
> (es.exe)m and Linux with GNU locate and it works well.
>> If so, wouldn't it be better to replace backslashes with forward
>> slashes before the unquote loop?
> Hmm. I'm not sure. How about an UNC path ala \\sever\share\path?
> If emacs correctly resolve an UNC path with forward slashes so i would
> agree.
>> If backslashes as directory separators are not the reason, could you
>> please elaborate about the reason?
> See above.

A+ Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]