Re: wdired doesn't work on files with backslash in their names

[Chris Moore]

Yes, that's what I was trying to say.  :)

Chris.

On 2/7/06, Stefan Monnier <address@hidden> wrote:
> >>>>> "Chris" == Chris Moore <address@hidden> writes:
>
> > This seems to fix it:
> > --- Backup/wdired.el.~1~      2006-02-07 05:10:38.000000000 +0100
> > +++ wdired.el 2006-02-07 05:10:48.000000000 +0100
> > @@ -323,8 +323,8 @@
> >       (if old
> >           (setq file (get-text-property beg 'old-name))
> >         (setq end (next-single-property-change (1+ beg) 'end-name))
> > -       (setq file (buffer-substring-no-properties (+ 2 beg) end)))
> > -     (and file (setq file (wdired-normalize-filename file))))
> > +       (setq file (buffer-substring-no-properties (+ 2 beg) end))
> > +       (and file (setq file (wdired-normalize-filename file)))))
> >        (if (or no-dir old)
> >         file
> >       (and file (> (length file) 0)
>
> > Basically, we don't want to call wdired-normalize-filename if the
> > filename has been pulled from a text property rather than from a
> > substring of the dired buffer.
>
> You mean we don't want to use wdired-normalize-filename on the name stored
> in the `old-name' property?  Yes, that makes sense since that property's
> value comes from dired-get-filename which we should assume to be correct.
>
>
>         Stefan
>