Re: [ JDiff-devel ] Re: JDiff (fwd)

[Daniel L. <Dan...@Vi...>]

Good day,

I tend to agree with Slava here. Building everything into one monolitic (à la Emacs)
tool is fine. I like jEdit a lot and I use it everyday. I might enjoy it very much
if there was a jDiff plug-in. But at the same time, with all the plug-ins I've got
running under jEdit, it is becoming a crowded place so I'd probably enjoy using
jDiff both as a plug-in and as a separate app.

Well, in any case, I'm using jDiff as a separate tool right now and it works! Now
that it was hacked it so it doesn't have to be used as a command line tool and we
can actually use file dialogs, I find it very useful.

What I am really looking for is replacement for the "diff" command line tool. Just
like diff isn't bundled with a text editor... I don't see why jDiff should
necessarily be.

> (Mike -- is this dude subscribed to jdiff-devel?)
>
> mike dillon wrote:
> > i believe the latest concensus was that jDiff as a separate application should
> > cease to exist and instead should continue on only as a jEdit plugin. for those
> > who would have liked to see jDiff move toward being more of a visual diff _and_
> > merge tool, this is not too satisfying. being that i am more than happy with
> > command line diff and patch, this didn't bother me personally, but i was kind
> > of saddened by the curtailing of potential usefulness.
>
> Why can't it be both an app and a plugin? Doing this is not terribly hard,
> and can be done with one code base.
>
> Slava
> --
>
> jDiff-devel mailing list
> jDi...@li...
> http://lists.sourceforge.net/mailman/listinfo/jdiff-devel

--
Daniel Lemire

http://www.ondelette.com/
ICQ: 8733252