Re: meld filename scans entire tree



On 2010-04-24, Kai Willadsen <kai willadsen gmail com> wrote:
> On 22 April 2010 03:51, Grant Edwards <grant b edwards gmail com> wrote:
>
>> Recently I noticed that I can no longer look at the changes I've made
>> to a single file under SVN control by doing "meld filename".  I swear
>> that used to just show me the changes for the specified file.
>
> Do you mean that this doesn't work, or that it does work, but also
> uselessly scans the directory tree? From my testing, this works in
> git (modulo the scanning).

I mean that it works, but it uselessly scans the entire tree, and I
don't remember it doing the scan.

>> Now it goes ahead on its own and scans the entire directory tree
>> underneath the current directory.
>
> As far as I can tell, Meld has always done this.

I would have sworn it didn't start doing this until the past month or
so, but I have no way to verify that -- so you're probably right.
Perhaps our server has slowed down for some reason so that now it's a
lot more noticable or perhaps I'm just higher up the tree on larger
projects now.

> The problem is that viewing differences of a single file under VC is
> hacked on to the existing version control view. What we actually do
> when asked to view a single file from the command line is open (but
> not display) a version control tab, fully populate it, and ask it to
> launch a comparison of the file we actually wanted in the first
> place.

Ah, I see.

> I don't think we can just not populate the view and still have things
> work, but it shouldn't be that hard to add a new pathway to VcView to
> initiate a single file comparison.

AFAICT all of underlying the VC systems have a "compare single file"
command, but I can't comment on how easy it would be to use that
inside meld.

-- 
Grant




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