From: Berndl, K. <kla...@sd...> - 2004-02-12 07:17:58
|
Ole Arndt wrote: > "Berndl, Klaus" <kla...@sd...> writes: >=20 >> Of course we should to try to make ECB with its current design so >> stable and flexible that Xref will work again... maybe hard but it >> should be done. >=20 > Exactly my opinion :-) >=20 >>=20 >> I will have to run some tests with Xref so i can't give you an >> answer today.=20 >>=20 >=20 > Take your time. If I can help you or provide you with details, let me > know. Please note, that the lisp part of Xref is GPL, though the > binary is commercial. So changing xref, in case it is the misbehaving > part, isn't out of the question. Yes, some details would be very fine and helpful. Could you please = provide some scenarios where you describe: 1. Which xref-command you call 2. The state of ECB (number of edit-windows, compile-windows visible, = ecb-windows hidden or not... 3. The wrong behavior of ecb 2.20 4. The correct behavior what you would expect. Ole, this would be very helpful for me, because i do not use Xref - i = have installed one for testing reports like yours but..... >=20 >> For the "source browser mode" of Xref: Its strongly recommended to >> run this by using a window-manager like winring.el or escreen.el. >=20 > I used escreen for this before, but with ecb 2.11 it wasn't necessary > any more. Saved me two keystrokes. Hmm, concerning the misbehavior of ECB/Xref besides the source browser = mode i agree with you that this should be also work with ECB 2.20 But for the browser mode i can not guarantee that we can fix this - for = being compatible with packages like Xref, Gnus with completely own = window-management there is the window-manager support of ECB - maybe the two keystrokes = come back to you ;-)) Ciao, Klaus > Gru=DF, > Ole |