System: Linux kato 2.2.10-smp #8 SMP Fri Sep 17 16:45:09 CEST 1999 i686 unknown Architecture: i686 (1) in contrast to emacs 20.3 the find-tag function of xemacs 20.4 cannot find tags associated with c/c++ struct/union/class members like "stack_s::nof_objects". Such tags are generated by the gnu etags program if the "--members" flag is set. (2) in contrast to emacs 20.3 the find-tag function of xemacs 20.4 may fail to find the definition of a type directly. (1) consider the file "include.h" which contains the following single line: calling the gnu etags program with /usr/bin/X11/etags -C --members -S include.h gives the following TAGS file: (here i substituted each cntrl character by 2 ascii characters for transport via email). passing "abc_s::counter" to the find-tag command gives the message "No entries matching abc_s::counter". (2) consider the file etags_test.h containing the single line and a file etags_test.c containing the two following lines: calling the gnu etags program with /usr/bin/X11/etags -C --members -S etags_test.c etags_test.h gives the following TAGS file: passing "obj_t" as a tag to xemacs' find-tag command positions the curser first to the typdef statement in etags_test.c, whereas emacs first positions to the correct typedef statement in etags_test.h. in both cases i use the same TAGS file. i admit that this example is fairly artificial. however, the problem may become really disturbing for real life code, especially if you use other etags programs like that of darren hiebert (http://darren.hiebert.com/ctags/index.html). the problem is a consequence of the fact that (x)emacs does not only scan the tag fields of a TAGS file but also its context fields. it would be very useful if one could direct (x)emacs to scan only the tag fields of a TAGS file. --=-=-=--