Re: 21.5-b28 strange behaviour: buffer modification flag set, even though I can't remember having changed anything, patch for configure on aix

Stephen, Done! And it comes up, even though I had to set EMACSLATEPACKAGES=/usr/local/lib/xemacs so that it would pick up my package path. I also had to change configure to use -pthread instead -mthreads: *** configure.orig 2008-01-31 10:42:27.000000000 +0100 --- configure 2008-01-31 12:23:12.000000000 +0100 *************** *** 19587,19594 **** if test "$unexec" = "unexaix.o" -a "$x11_release" = "6"; then if test "$GCC" = "yes"; then ! X_CFLAGS="-mthreads $X_CFLAGS" && if test "$verbose" = "yes"; then echo " Prepending \"-mthreads\" to \$X_CFLAGS"; fi ! libs_x="-mthreads $libs_x" && if test "$verbose" = "yes"; then echo " Prepending \"-mthreads\" to \$libs_x"; fi else case "$CC" in "xlc" ) CC="xlc_r" ;; --- 19587,19594 ---- if test "$unexec" = "unexaix.o" -a "$x11_release" = "6"; then if test "$GCC" = "yes"; then ! X_CFLAGS="-pthread $X_CFLAGS" && if test "$verbose" = "yes"; then echo " Prepending \"-pthread\" to \$X_CFLAGS"; fi ! libs_x="-pthread $libs_x" && if test "$verbose" = "yes"; then echo " Prepending \"-pthread\" to \$libs_x"; fi else case "$CC" in "xlc" ) CC="xlc_r" ;; Stephen J. Turnbull schrieb: > Thomas Mittelstaedt writes: > > > This happens sometimes, especially with (generated) Makefiles. When I > > try undo, xemacs tells me that there is no undo information. > > When I reload the buffer, I can't see any visible changes. > > What could that be? > > There was a bug that setting the buffer's coding system set the > modified flag, resulting in similar behavior. This would be very > noticable after reverting a buffer. Why this would happen for > generated Makefiles, I'm not sure. Do you revert them often? The bug > I'm referring to was fixed after the release of 21.5.28. > > > hg clone http://hg.debian.org/hg/xemacs/xemacs > > should do the trick). From your description it might be a different > bug, though probably related. > > Also, even for something as simple as this it helps to use M-x > report-xemacs-bug, since that will tell us whether the bug should be > fixed in the version you are using. Don't worry about our bandwidth, > and we appreciate you taking the extra effort if it means cutting and > pasting into T-bird or something like that. > > > > > > > _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta