> >I think you should instead patch the library to accept a configurable
> >line ending. Ditto for HTML.
> I agree.
I disagree, because I think that PrettyPrinter behaves right: it uses the
line separator native to the current OS. The problem is, that jEdit
internally does _not_ use the native line separator, it enforces the use of \n, even
though you're on a Windows platform.
Don't get me wrong: I don't think this is bad; it's a wise thing to do for
a cross-platform editor. But, consequently, problems resulting from this
approach have to be fixed in jEdit, not in the external libraries.
> For one thing, the change only affects the output, so it's
> pretty safe (it's working fine for me, anyway). For another, jEdit
> is far from the only editor to incorporate Seguin's
> PrettyPrinter--Seguin's website lists
> JBuilder and ElixirIDE, and I believe Jext and J.O.O.D.A use it as well.
> Probably every one of those implementations has had to deal with this
With the same argument one could say that JBuilder, ElixirIDE, Jext, JOODA
etc. all need to implement configurable line separator, just because
> By the way, the comment-reformatting fix that I proposed is still not
> satisfactory; now it _removes_ asterisks from the beginning of lines
> and replaces them with spaces. To fix this thing right means having
> the user choose between leaving multiline comments as they are,
> converting them all to wing comments (no asterisks), or converting them
> all to box comments. I'm looking into doing that now--let me know if
> you're interested in the result.
Sent through GMX FreeMail - http://www.gmx.net