21.5-b28 strange behaviour: buffer modification flag set, even though I can't remember having changed anything
1:18 p.m.
Hallo,
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?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
8:42 p.m.
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.
I would appreciate it if you would update to the most recent version
(if you don't have a Mercurial workspace yet, install Mercurial, then
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
1:33 p.m.
New subject: 21.5-b28 strange behaviour: buffer modification flag set, even though I can't remember having changed anything, patch for configure on aix
Stephen,
I would appreciate it if you would update to the most recent version
(if you don't have a Mercurial workspace yet, install Mercurial, then
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.
>
I would appreciate it if you would update to the most recent version
(if you don't have a Mercurial workspace yet, install Mercurial, then
>
> 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
6:44 p.m.
New subject: 21.5-b28 strange behaviour: buffer modification flag set, even though I can't remember having changed anything, patch for configure on aix
Thomas Mittelstaedt writes:
I also had to change configure to use -pthread instead -mthreads:
I guess this is a version dependency of AIX. Do you have any idea
what the right thing to do is?
1. If POSIX threads were never reported as buggy, maybe a feature
check for the pthreads library?
2. If there was an AIX version where pthreads became the "official"
way to go, do you know how to check for version on AIX, and what
the version to check for would be?
3. If "mthreads" is truly ancient we could deprecate it, but I'd
rather not.
Regards,
Steve
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
9:33 a.m.
New subject: 21.5-b28 strange behaviour: buffer modification flag set, even though I can't remember having changed anything, patch for configure on aix
Stephen J. Turnbull schrieb:
Thomas Mittelstaedt writes:
> I also had to change configure to use -pthread instead -mthreads:
I guess this is a version dependency of AIX. Do you have any idea
what the right thing to do is?
Just built xemacs without -pthread (or -mthreads) and it runs. The gcc
4.2.2 man page says about -mthreads that it's needed
for multi-threaded exception handling on mingw.
We use -pthread to link with the correct, multi-threaded version of the
libstdc++ library, which on aix 5.2
are in separate directories:
tmstaedt＠buildaix3$ find /opt/gcc-4.2.2/lib -name libstdc++*
/opt/gcc-4.2.2/lib/gcc/powerpc-ibm-aix5.2.0.0/4.2.2/pthread/ppc64/libstdc++.a
/opt/gcc-4.2.2/lib/gcc/powerpc-ibm-aix5.2.0.0/4.2.2/pthread/ppc64/libstdc++.la
/opt/gcc-4.2.2/lib/gcc/powerpc-ibm-aix5.2.0.0/4.2.2/pthread/libstdc++.a
/opt/gcc-4.2.2/lib/gcc/powerpc-ibm-aix5.2.0.0/4.2.2/pthread/libstdc++.la
/opt/gcc-4.2.2/lib/gcc/powerpc-ibm-aix5.2.0.0/4.2.2/ppc64/libstdc++.a
/opt/gcc-4.2.2/lib/gcc/powerpc-ibm-aix5.2.0.0/4.2.2/ppc64/libstdc++.la
/opt/gcc-4.2.2/lib/gcc/powerpc-ibm-aix5.2.0.0/4.2.2/libstdc++.a
/opt/gcc-4.2.2/lib/gcc/powerpc-ibm-aix5.2.0.0/4.2.2/libstdc++.la
tmstaedt＠buildaix3$ gcc -v
Using built-in specs.
Target: powerpc-ibm-aix5.2.0.0
Configured with: ../gcc-4.2.2/configure
--enable-version-specific-runtime-libs --enable-static --enable-shared
--enable-threads --with-as=/usr/bin/as --without-gnu-ld
--with-ld=/usr/bin/ld --prefix=/opt/gcc-4.2.2 --disable-nls --with-pic
--disable-symvers --enable-symvers=no --enable-languages=c,c++,objc
Thread model: aix
gcc version 4.2.2
1. If POSIX threads were never reported as buggy, maybe a feature
check for the pthreads library?
2. If there was an AIX version where pthreads became the "official"
way to go, do you know how to check for version on AIX, and what
the version to check for would be?
3. If "mthreads" is truly ancient we could deprecate it, but I'd
rather not.
Regards,
Steve
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
3:30 a.m.
New subject: 21.5-b28 strange behaviour: buffer modification flag set, even though I can't remember having changed anything, patch for configure on aix
Thomas Mittelstaedt writes:
Thanks for following up! BTW, is the buffer modification problem gone?
Just built xemacs without -pthread (or -mthreads) and it runs. The
gcc
4.2.2 man page says about -mthreads that it's needed
for multi-threaded exception handling on mingw.
That looks like an irrelevancy to me, since mingw is a GCC runtime
environment for Microsoft Windows. I suspect that some other AIX
compiler (possibly obsolete) does need -mthreads, which has semantics
specific to that compiler.
Don't feel you *need* to dig, but if you do find any references or
conversation at an AIX user group or whatever, we'd greatly appreciate
an update!
We use -pthread to link with the correct, multi-threaded version of
the libstdc++ library, which on aix 5.2 are in separate directories:
pthreads should be irrelevant to XEmacs, even with --xemacs-compiler=c++.
tmstaedt＠buildaix3$ find /opt/gcc-4.2.2/lib -name libstdc++*
/opt/gcc-4.2.2/lib/gcc/powerpc-ibm-aix5.2.0.0/4.2.2/pthread/ppc64/libstdc++.a
/opt/gcc-4.2.2/lib/gcc/powerpc-ibm-aix5.2.0.0/4.2.2/pthread/ppc64/libstdc++.la
/opt/gcc-4.2.2/lib/gcc/powerpc-ibm-aix5.2.0.0/4.2.2/pthread/libstdc++.a
/opt/gcc-4.2.2/lib/gcc/powerpc-ibm-aix5.2.0.0/4.2.2/pthread/libstdc++.la
/opt/gcc-4.2.2/lib/gcc/powerpc-ibm-aix5.2.0.0/4.2.2/ppc64/libstdc++.a
tmstaedt＠buildaix3$ gcc -v
Using built-in specs.
Target: powerpc-ibm-aix5.2.0.0
Configured with: ../gcc-4.2.2/configure
--enable-version-specific-runtime-libs --enable-static --enable-shared
--enable-threads --with-as=/usr/bin/as --without-gnu-ld
--with-ld=/usr/bin/ld --prefix=/opt/gcc-4.2.2 --disable-nls --with-pic
--disable-symvers --enable-symvers=no --enable-languages=c,c++,objc
Thread model: aix
gcc version 4.2.2
Thank you!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
6:46 p.m.
New subject: 21.5-b28 strange behaviour: buffer modification flag set, even though I can't remember having changed anything, patch for configure on aix
Thomas Mittelstaedt writes:
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.
Did you try the configure option
--with-late-packages=/usr/local/lib/xemacs ?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
6138
days inactive
6141
days old
6 comments
2 participants
participants (2)
-
Stephen J. Turnbull -
Thomas Mittelstädt