Ralf Angeli <angeli(a)caeruleus.net> writes:
> * Artemio Gonzalez Lopez (2007-03-11) writes:
>
>> I just built the latest CVS auctex, which includes the font locking
>> changes. Unfortunately, under xemacs 21.5-b27 syntax highlighting is now
>> completely broken (most of the text is in green, the font is a huge sans
>> serif, etc.)
>
> That's due to a bug in XEmacs 21.5 related to the function
> `with-syntax-table' I reported over two years ago to the XEmacs
> project. See <URL:http://mid.gmane.org/cp7323$qm7$1%40sea.gmane.org>.
> Unfortunately they don't seem to care about such bug reports or don't
> have the manpower to fix these bugs. We are using `with-syntax-table'
> at several places, so I'm not sure if I can code around it in a
> sensible way.
Since the XEmacs project is not updating its version of AUCTeX,
anyway, it will probably take some time before there is a massive
uproar about this.
The standard answer to problem reports of the AUCTeX developers to the
XEmacs developer list is "we never get any complaints from AUCTeX
users, so there is no priority to fix this".
So Artemio, you might want to add your voice to this problem getting
fixed.
I am copying this mail to the XEmacs developer list in order to remind
them of this problem, but my own track record in getting things fixed
in XEmacs that I complain about is abysmal, so you might try
separately, maybe with example files and recipes (using the nightly
snapshot XEmacs package from Reiner, perhaps?) illustrating the
seriousness, perhaps with a screenshot.
There seems to be little point in making a _contained_, reproduceable
"non-real-world" example, since Ralf already did this years ago (see
the above link). That should be sufficient for debugging and fixing
the problem.
So your task is "merely" to demonstrate that ignoring it is a bad
idea. Maybe a screenshot will be all it takes. No idea.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Ar an fichiú lá de mí Aibréan, scríobh Stephen J. Turnbull:
> Aidan Kehoe writes:
>
> > I’ve made a log of all the file accesses that installed XEmacs makes on a
> > -vanilla start available here:
> >
> > http://www.parhasard.net/xemacs/filemon-xemacs-startup-20070420.log.gz
>
> Did you observe 11 requests for media?
No, and nothing appeared to be unrelated to my system. But then I’m on XP,
not Vista--Sean, if you can run Process Monitor:
http://www.microsoft.com/technet/sysinternals/utilities/processmonitor.mspx
and examine what files XEmacs tries to load on starting, then send us a list
of them, that would be really helpful.
> If not, and you don't have an e: drive, maybe it would be possible to
> alias e: to a removable media device, remove the media, and see if you
> can correlate accesses with Windows bitching.
I have an E: drive, and it’s empty right now.
> (ISTR from the Win2k fiasco that if you don't have a drive at all,
> Windows won't complain. It's only for a drive with removable media, and
> the file doesn't exist on that medium, that the complaint pops up.)
>
> This suggests a possible workaround for Sean: rename the offending
> device.
>
> BTW, I gather that your opinion is that since help looks in DOC for
> source file names, your patch has nothing to do with this? (Just to
> confirm, since you're the expert.)
Unless some of the startup Lisp tries to find the C source of a function or
variable, I can’t see how it could.
--
On the quay of the little Black Sea port, where the rescued pair came once
more into contact with civilization, Dobrinton was bitten by a dog which was
assumed to be mad, though it may only have been indiscriminating. (Saki)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Ar an fichiú lá de mí Aibréan, scríobh Vin Shelton:
> On 4/20/07, Aidan Kehoe <kehoea(a)parhasard.net> wrote:
> > I've made a log of all the file accesses that installed XEmacs makes on a
> > -vanilla start available here:
> >
> > http://www.parhasard.net/xemacs/filemon-xemacs-startup-20070420.log.gz
>
> Thanks, but that's an empty file. The gzipped version is 33 bytes long.
Bah, Windows and exclusive file access. I’ve updated it to actually contain
something other than the gzip header.
--
On the quay of the little Black Sea port, where the rescued pair came once
more into contact with civilization, Dobrinton was bitten by a dog which was
assumed to be mad, though it may only have been indiscriminating. (Saki)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Hi,
ecb-activate makes XEmacs go into an endless loop. Start with -vanilla
and do M-x ecb-activate. That's it.
The build-report follows below for reference:
----------------------------------------------------------------------
uname -a: Linux spencer 2.6.19-gentoo-r5 #28 SMP Sun Apr 8 11:36:42 CEST 2007 i686 Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz GenuineIntel GNU/Linux
./configure '--prefix=/src/beta/xemacs' '--enable-mule' '--with-package-path=/src/xemacs/xemacs-packages:/src/xemacs/mule-packages:/src/xemacs/site-packages' '--enable-sound=esd' '--enable-database=no' '--enable-widgets=athena' '--enable-dialogs=athena' '--with-athena=3d' '--with-newgc' '--with-xft=emacs,tabs,menubars,gauges' '--with-xim=no'
XEmacs 21.5-b27 "fiddleheads" (+CVS-20070414) configured for `i686-pc-linux'.
Compilation Environment and Installation Defaults:
Source code location: /src/xemacs/working
Installation prefix: /src/beta/xemacs
Operating system description file: `s/linux.h'
Machine description file: `m/intel386.h'
Compiler version: gcc (GCC) 4.1.1 (Gentoo 4.1.1-r3)
- GCC specs file: specs.
- Compiler command: gcc -Wall -Wno-switch -Wundef -Wsign-compare -Wno-char-subscripts -Wpacked -Wunused-parameter -g
libc version: 2.5
Relocating allocator for buffers: no
GNU version of malloc: yes
- Using Doug Lea's new malloc from the GNU C Library.
Window System:
Compiling in support for the X window system:
- X Windows headers location: /usr/X11R6/include
- X Windows libraries location: /usr/X11R6/lib
- Handling WM_COMMAND properly.
- Using fontconfig to manage fonts.
- Compiling in support for Xft antialiased fonts (EXPERIMENTAL).
Compiling in support for the Athena widget set:
- Athena headers location: X11/Xaw3d
- Athena library to link: Xaw3d
Using Lucid menubars.
- Using Xft to render antialiased fonts in menubars.
WARNING: This feature will be replaced with a face.
Using Lucid scrollbars.
Using Athena dialog boxes.
Using Athena native widgets.
- Using Xft to render antialiased fonts in tab controls.
WARNING: This feature will be replaced with a face.
- Using Xft to render antialiased fonts in progress bars.
WARNING: This feature will be replaced with a face.
WARNING: This feature not yet implemented; setting ignored.
TTY:
Compiling in support for ncurses.
Compiling in support for GPM (General Purpose Mouse).
Images:
Compiling in support for GIF images (builtin).
Compiling in support for XPM images.
Compiling in support for PNG images.
Compiling in support for JPEG images.
Compiling in support for TIFF images.
Sound:
Compiling in support for sound (native).
Compiling in support for ALSA (Advanced Linux Sound Architecture).
Compiling in support for ESD (Enlightened Sound Daemon).
Databases:
Compiling in support for LDAP.
Internationalization:
Compiling in support for Mule (multi-lingual Emacs).
Mail:
Compiling in support for "file" mail spool file locking method.
Other Features:
Inhibiting IPv6 canonicalization at startup.
Compiling in support for dynamic shared object modules.
Using the new GC mark algorithms (KKCC).
WARNING: ---------------------------------------------------------
WARNING: The new algorithms are experimental. They are enabled by
WARNING: default for this release. Use `--disable-kkcc' to
WARNING: turn it off.
WARNING: ---------------------------------------------------------
Using the new incremental garbage collector and the new allocator.
Using POSIX sigaction() to install fault handler.
Using the new portable dumper.
Compiling in support for extra debugging code.
Compiling in support for runtime error checking.
WARNING: ---------------------------------------------------------
WARNING: XEmacs will run noticeably more slowly as a result.
WARNING: Error checking is on by default for XEmacs beta releases.
WARNING: ---------------------------------------------------------
Contents of file xemacs-make-all.err
Keeping lines matching (in python regexp syntax): "^--\[\[|\]\]$|^(cd|n?make)\s|errors?|warnings?|pure.*(space|size)|hides|strange|shadowings|^Compil(ing\s+in|ation)|^Using|not\s+found|^Note:|Installing|[Ff]ile\(s\) copied|\s+tests\s+|^[A-Z] [^ ]+$|^Wrong number of arguments:|^ \*\* |^(FAIL|SKIP):"
... and then deleting lines matching (in python regexp syntax): "confl.*with.*auto-inlining|^Formatting:|^PASS:|\(100%\) tests successful"
------------------------------------------------------------------------------
cd ./lib-src && make all
cd ./lwlib && make all
cd ./src && make all
emacs.c:3371: warning: statement with no effect
objects-xlike-inc.c:435: warning: pointer targets in initialization differ in signedness
objects-xlike-inc.c:439: warning: pointer targets in initialization differ in signedness
objects-xlike-inc.c:441: warning: pointer targets in initialization differ in signedness
objects-xlike-inc.c:445: warning: pointer targets in initialization differ in signedness
objects-xlike-inc.c:521: warning: pointer targets in initialization differ in signedness
objects-xlike-inc.c:789: warning: pointer targets in passing argument 2 of 'qxestrcasecmp' differ in signedness
Using load-path (/src/xemacs/working/lisp/)
Using module-load-path (/src/xemacs/working/modules)
Generating autoloads for lisp/next-error.el...
** the function sort-numeric-fields is not known to be defined.
Using load-path (/src/xemacs/working/lisp/)
Using module-load-path (/src/xemacs/working/modules)
Computing custom-loads for next-error...
cd ./modules/ldap && make all
eldap.c:161: warning: implicit declaration of function 'ldap_unbind'
eldap.c:310: warning: implicit declaration of function 'ldap_open'
eldap.c:310: warning: assignment makes pointer from integer without a cast
eldap.c:345: warning: implicit declaration of function 'ldap_bind_s'
eldap.c:500: warning: implicit declaration of function 'ldap_search'
eldap.c:693: warning: implicit declaration of function 'ldap_add_s'
eldap.c:786: warning: implicit declaration of function 'ldap_modify_s'
eldap.c:811: warning: implicit declaration of function 'ldap_delete_s'
cd /src/xemacs/working/man && make info
------------------------------------------------------------------------------
Contents of file xemacs-make-check.err
Keeping lines matching (in python regexp syntax): "^--\[\[|\]\]$|^(cd|n?make)\s|errors?|warnings?|pure.*(space|size)|hides|strange|shadowings|^Compil(ing\s+in|ation)|^Using|not\s+found|^Note:|Installing|[Ff]ile\(s\) copied|\s+tests\s+|^[A-Z] [^ ]+$|^Wrong number of arguments:|^ \*\* |^(FAIL|SKIP):"
... and then deleting lines matching (in python regexp syntax): "confl.*with.*auto-inlining|^Formatting:|^PASS:|\(100%\) tests successful"
------------------------------------------------------------------------------
cd ./src && make check
base64-tests.el: 1234 of 1234 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
byte-compiler-tests.el: 104 of 104 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
c-tests.el: 4 of 4 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
case-tests.el: 1148 of 1148 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
ccl-tests.el: 4570 of 4570 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
database-tests.el: No tests run.
0 errors that should have been generated, but weren't
0 wrong-error failures
extent-tests.el: 194 of 194 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
hash-table-tests.el: 9866 of 9866 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
iso-ir-196-test.el: 2 of 2 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
lisp-reader-tests.el: 52 of 52 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
lisp-tests.el: 3672 of 3672 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
md5-tests.el: 56 of 56 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
mule-tests.el: 296 of 296 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
os-tests.el: 20 of 20 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
regexp-tests.el: 350 of 350 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
region-tests.el: 28 of 28 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
symbol-tests.el: 246 of 246 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
KNOWN BUG: (backward-up-list-moves-point-from-to 23 3) ==> error: (syntax-error "Unbalanced parentheses")
KNOWN BUG: (backward-up-list-moves-point-from-to 23 3) ==> error: (syntax-error "Unbalanced parentheses")
syntax-tests.el: 72 of 78 tests successful ( 92%).
KNOWN BUG: (backward-up-list-moves-point-from-to 23 3) ==> error: (syntax-error "Unbalanced parentheses")
KNOWN BUG: (backward-up-list-moves-point-from-to 23 3) ==> error: (syntax-error "Unbalanced parentheses")
0 errors that should have been generated, but weren't
0 wrong-error failures
tag-tests.el: 6 of 6 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
weak-tests.el: 140 of 140 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
base64-tests.el: 1234 of 1234 tests successful (100%).
byte-compiler-tests.el: 104 of 104 tests successful (100%).
c-tests.el: 4 of 4 tests successful (100%).
case-tests.el: 1148 of 1148 tests successful (100%).
ccl-tests.el: 4570 of 4570 tests successful (100%).
database-tests.el: No tests run.
extent-tests.el: 194 of 194 tests successful (100%).
hash-table-tests.el: 9866 of 9866 tests successful (100%).
iso-ir-196-test.el: 2 of 2 tests successful (100%).
lisp-reader-tests.el: 52 of 52 tests successful (100%).
lisp-tests.el: 3672 of 3672 tests successful (100%).
md5-tests.el: 56 of 56 tests successful (100%).
mule-tests.el: 296 of 296 tests successful (100%).
os-tests.el: 20 of 20 tests successful (100%).
regexp-tests.el: 350 of 350 tests successful (100%).
region-tests.el: 28 of 28 tests successful (100%).
symbol-tests.el: 246 of 246 tests successful (100%).
syntax-tests.el: 72 of 78 tests successful ( 92%).
tag-tests.el: 6 of 6 tests successful (100%).
weak-tests.el: 140 of 140 tests successful (100%).
------------------------------------------------------------------------------
Contents of file xemacs-make-install.err
Keeping lines matching (in python regexp syntax): "^--\[\[|\]\]$|^(cd|n?make)\s|errors?|warnings?|pure.*(space|size)|hides|strange|shadowings|^Compil(ing\s+in|ation)|^Using|not\s+found|^Note:|Installing|[Ff]ile\(s\) copied|\s+tests\s+|^[A-Z] [^ ]+$|^Wrong number of arguments:|^ \*\* |^(FAIL|SKIP):"
... and then deleting lines matching (in python regexp syntax): "confl.*with.*auto-inlining|^Formatting:|^PASS:|\(100%\) tests successful"
------------------------------------------------------------------------------
cd ./lib-src && make all
cd ./lwlib && make all
cd ./src && make all
cd ./modules/ldap && make all
cd /src/xemacs/working/man && make info
cd ./src && make check-features
Installing utilities run internally by XEmacs.
Installing utilities for users to run.
cd /src/beta/xemacs/bin && rm -f ./xemacs && ln -s xemacs-21.5-b27 ./xemacs
cd /src/xemacs/working/etc && \
make gzip-el
------------------------------------------------------------------------------
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Sean -
(I've taken the liberty of forwarding your info to the xemacs-beta
list; I hope that's OK - I thought it was acceptable since you
originally posted to a public list.)
Sean wrote:
> Follow-up on the issue of xemacs-21.5-2007-03-01 asking for a disk when
> I start it up under Vista Enterprise. I happened to be poking around
> trying (unsuccessfully) to figure out how to start xemacs with a
> different font, and found the config.values file, whose contents follow.
> Note several references to the e: drive, which (on my system) has no
> media attached. Perhaps this is the source of the complaints? (counter
> to this would be that the config.values for xemacs-21.4.19, while
> different, has some similar e: drive values)
Thanks for sending along the info, although it got word-wrapped in
transit. I've attached an unmangled version to this message. The
debug-paths output looks normal.
I agree that the config.values thing looks suspicious, however. Even
though (as you note) the 21.4 build doesn't exhibit the problems, the
startup code is substantially different in 21.5 from 21.4
Michael -
Do you have any thoughts on how the values expressed in config.values
get used during XEmacs startup? In particular, that lispdir value
looks suspicious to me. Note that some paths (generated on my system
when I built the installkit) do not exist on Sean's target system.
Here are the contents of the config.values file:
;;; Do not edit this file!
blddir
"e:\\acs\\software\\XEmacsWindowsKit\\xemacs-21.5-2007-03-01"
srcdir
"e:\\acs\\software\\XEmacsWindowsKit\\xemacs-21.5-2007-03-01"
CC
"cl"
CFLAGS
"-nologo -W3 -DSTRICT -Zi -Od -MD"
CPP
"cl"
CPPFLAGS
""
LISPDIR
"\\e:\\acs\\software\\XEmacsWindowsKit\\xemacs-21.5-2007-03-01\\lisp"
Thanks for any thoughts you may have, Michael.
- Vin
--
The Journey by Mary Oliver
http://www.poemhunter.com/p/m/poem.asp?poet=6771&poem=30506
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
"Sean Boisen" <sean(a)logos.com> writes:
> (user-home-directory)
> "c:\\Users\\sboisen"
Wow. So I can't see a reference to a drive other than C: anywhere,
which makes this pretty much the end of my rope. Having tangled with
Vista before, I'm inclined to point the finger in that direction.
Is there anything on Windows to, like, trace system calls or
something?
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
On 4/19/07, Sean Boisen <sean(a)logos.com> wrote:
> I'm afraid I don't know any way to trace system calls or the like. Certainly something about
> Vista is the most likely culprit.
Hi Sean,
What was the result of running "-no-autoloads" ?
- Vin
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
OK, thanks, this looks all perfectly normal.
Now, what does
(user-home-directory)
return?
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta