RE: [OT] FileMerge as a vacuum (Re: What are your top desiredimprovements in Xcode ?)
RE: [OT] FileMerge as a vacuum (Re: What are your top desiredimprovements in Xcode ?)
- Subject: RE: [OT] FileMerge as a vacuum (Re: What are your top desiredimprovements in Xcode ?)
- From: "James Larcombe" <email@hidden>
- Date: Mon, 19 Feb 2007 15:05:03 -0000
- Thread-topic: [OT] FileMerge as a vacuum (Re: What are your top desiredimprovements in Xcode ?)
Laurence Harris wrote:
> I just used FileMerge 2.2.1 to compare two HTML files. It
> sucks because:
>
> - It says there's only one difference even though there are
> dozens of differences. The one line it says is different is
> not.
Alas, FileMerge only works correctly with Unix line endings.
This can be inconvenient, but as soon as I realised what was
going on, I checked out a fresh repository from CVS with the
required line endings, and have had no problems since. You
should be able to do the same thing with your source control
system.
> - The names of the commands in that menu are misleading.
> They have names like "Choose left" even though they don't
> actually "choose" anything.
They do - they choose the changes from one file or the other
to put into the merge file. Drag the splitter bar at the bottom
of the window up to see (and even edit) the merge file.
> - There's an empty space separating the two panes at the top
> from the text at the bottom. It's 40 pixels high. Looks like
> a big waste of space to me.
Dragging the splitter bar up may change matters. There is still
a bit of a gap between the splitter and the combo box above the
merge file, but it's not a big deal.
Granted, certain aspects of the UI of FileMerge leave a lot to
be desired. Quirks aside, it works well.
James
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden