all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eduard Wiebe <usenet@pusto.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 7308@debbugs.gnu.org
Subject: bug#7308: [patch] locate under windoze
Date: Sun, 31 Oct 2010 10:36:21 +0100	[thread overview]
Message-ID: <87eib6d7qi.fsf@pusto.de> (raw)
In-Reply-To: <83mxpv5qde.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 30 Oct 2010 23:21:01 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Eduard Wiebe <usenet@pusto.de>
>> 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.

> 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.

-- 
Eduard Wiebe





  reply	other threads:[~2010-10-31  9:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-30 19:50 bug#7308: [patch] locate under windoze Eduard Wiebe
2010-10-30 21:21 ` Eli Zaretskii
2010-10-31  9:36   ` Eduard Wiebe [this message]
2010-10-31  9:48     ` Thierry Volpiatto
2010-10-31 10:51     ` Eli Zaretskii
2010-10-31 19:54       ` Eduard Wiebe
2010-10-31 20:26         ` Eli Zaretskii
2010-10-31  6:56 ` Thierry Volpiatto
2010-10-31  7:49   ` Eli Zaretskii
2010-10-31  9:41     ` Thierry Volpiatto
2010-10-31 10:47       ` Eli Zaretskii
2010-10-31 11:13         ` Thierry Volpiatto
2010-11-01  6:54 ` Glenn Morris
2010-11-01  7:46   ` Eduard Wiebe
2010-11-01 14:06   ` Stefan Monnier
2010-11-01 14:59 ` Eduard Wiebe
2010-11-12 20:28   ` Eduard Wiebe
2010-11-13 18:57     ` Chong Yidong
2010-11-13 21:18       ` Eli Zaretskii
2010-11-13 22:33         ` Eduard Wiebe
2010-11-14  3:59           ` Eli Zaretskii
2010-11-14  9:15             ` Eduard Wiebe
2010-11-27  9:59               ` Eli Zaretskii
     [not found]                 ` <87bp5970hs.fsf@pusto.de>
2010-11-28 19:46                   ` bug#5462: " Eli Zaretskii

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=87eib6d7qi.fsf@pusto.de \
    --to=usenet@pusto.de \
    --cc=7308@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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.