Hi Uwe!
Uwe Brauer <oub(a)mat.ucm.es> writes:
I would like to clarify the issues on the shy-groups bug (finally it
was because of this bug, that 21.4.16 got withdrawn).
- it seems that I (using 21.4.16 _no Mule_) did not suffer this
bug in any noticeable way: gnus auctex x-symbol behaved in
the same way as they did in 21.4.15. So I asked for a way
to test the bug. Ralf Angeli proposed the following
example
Ralf> Here is one of my all time favorites regarding font
Ralf> locking which is working fine in Emacs but fails in
Ralf> XEmacs, i.e. fontification is spilling out of the
Ralf> verbatim environment:
Ralf> \documentclass{article}
Ralf> \begin{document}
Ralf> \begin{verbatim}
Ralf> echo $LANG
Ralf> \end{verbatim}
Ralf> \end{document}
The fortification indeed did not work correctly in 21.4.16,
so I took this as a test of the shy groups bug; I tested
this on Friday night on pre 21.4.17 and found the same
behaviour and reported it as if the BUG is still
there. However it seems *this conclusion is not correct*,
for Fabrice reported the same font lock behaviour in the
21.5 series.
This is probably some kind of syntactic analysis bug. (I'm completely
guessing here.) I do not think it has to do with shy groups.
So the first question I would like to ask:
How can one test the shy groups bug???????
Here is the test that we added to the regexp regression test.
;; Test Arnaud Giersch's shy group fix
(Assert (progn (string-match "\\(a\\)" "a")
(string-match "\\(?:a\\)" "a")
(not (match-beginning 1))))
This test passes on 21.4.17 and fails on 21.4.16.
- the next issue concerns the fortification problem. Already
Farbrice is in discussion with the auctex development team
and I hope this issue can be solved. I would therefore
recommend a phase of debugging and _testing_ for the
21.4.17 release. I have already seen that Ben is going to
submit quite some changes in various packages. May be it
would be better to resolve this 2 issues before continuing
with the merge of those changes.
Packages are not my responsibility, so I cannot guarantee package
stability, but I can assure you that 21.4.17 will provide a fairly
stable base for debugging and verification.
- Finally there is a bug or better say hang of xemacs
together with x-symbol I have noted ever since I started
to use the 21.4.x series. Unfortunately Christoph Wedler
has not done anything on his package since almost a
year. The issue concerns the use of either
lazy-shot vs lazy-lock. The first one is a C implementation
the second one a lisp implementation.
My experience is that lazy-shot works neither, but let
Xemacs freeze while lazy-lock is more stable.
Can anybody please comment on the use of these packages?
Which is preferable. I suggest some testing would be bad.
I use lazy-shot. I think more testing would definitely be good.
- Vin