March 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: failed compilation of xemacs-21.2.11 26 years, 1 month

Enrico Scholz

Kyle Jones <kyle_jones(a)wonderworks.com> writes: > Enrico Scholz writes: > > The messages seems to be right because of "A period or comma > > *must* follow the closing brace of an `＠xref'. It is required to > > terminate the cross reference." [texinfo.info, node "Reference > > syntax"]. So I'm wondering nobody else has detected this error. > > Nobody has detected it probably because the rule was unenforced. > makeinfo has a grim history (with me at least) of complaining > about stuff that nobody should care about. What difference does > it make if a period or a comma comes after the closing brace? > > But we should definitely fix the manuals so that makeinfo shuts > up, because there will be no peace in the valley until we do. > Yes, fixing wasn't very difficulty. I've attached a patch which should solve the problem. Enrico -- eMail: enrico.scholz(a)wirtschaft.tu-chemnitz.de talk: ensc(a)ultra.csn.tu-chemnitz.de

1 participants
0 comments

Re: failed compilation of xemacs-21.2.11 26 years, 1 month

Adrian Aichner

>>>>> "Enrico" == Enrico Scholz <enrico.scholz(a)wirtschaft.tu-chemnitz.de> writes: Enrico> SL Baur <steve(a)xemacs.org> writes: >> Enrico Scholz <enrico.scholz(a)wirtschaft.tu-chemnitz.de> writes in Enrico> xemacs-beta(a)xemacs.org: >> >> > While compiling xemacs I get following error messages: >> ... [lots and lots of makeinfo messages] >> >> >> What version of makeinfo do you have installed? The _oldest_ makeinfo >> you can use is: >> >> $ makeinfo --version >> makeinfo (GNU texinfo 3.12) 1.68 >> >> Enrico> $ makeinfo --version Enrico> makeinfo (GNU texinfo) 3.12c Enrico> The messages seems to be right because of "A period or Enrico> comma *must* follow the closing brace of an `＠xref'. It Enrico> is required to terminate the cross reference." Enrico> [texinfo.info, node "Reference syntax"]. So I'm wondering Enrico> nobody else has detected this error. Enrico, I don't have makeinfo available for my Windows NT native build of XEmacs. What I do is this: I let XEmacs build the info files from the texi sources, which takes about 4 minutes for me. You need to have the texinfo package installed for that. This is what I have installed: texinfo 1.14 XEmacs TeXinfo support. Just load the attached build-info.el and then use M-x makeinfo-xemacs I did just that and texinfo.texi, like all the other texi files, gave me no errors at all. 8< 8= 8< 8= 8< 8= 8< 8= cut here 8< 8= 8< 8= 8< 8= 8< 8= (require 'config) (defun makeinfo-from-texinfo (file) "Run XEmacs in batch-mode to produce info files from Texinfo input FILE." (interactive "Fxemacs Texinfo file: ") (shell-command (concat "" (expand-file-name "src/xemacs" (gethash 'blddir (config-value-hash-table))) " -no-site-file -no-init-file" " -batch -l texinfmt -f batch-texinfo-format" " " (if (file-name-absolute-p file) (expand-file-name file) (expand-file-name file (expand-file-name "man" (gethash 'blddir (config-value-hash-table))))) "") (concat file ".err"))) ;;; Last used with (emacs-version) "XEmacs 21.2 \"Apollo\" [Lucid] ;;; (i386-pc-win32) of Sat Dec 19 1998 on TWILIGHT" (defun makeinfo-xemacs () (interactive) ;;; These are all texinfo files to be converted into info format as of ;;; XEmacs-21.0-b46 (they include other texinfo files, though: (mapc (function makeinfo-from-texinfo) '( ;;; man/Makefile: "cl.texi" "custom.texi" "external-widget.texi" "info.texi" "standards.texi" "term.texi" "termcap.texi" "texinfo.texi" "widget.texi" "xemacs-faq.texi" ;;; man/internals/Makefile "internals/internals.texi" ;;; man/lispref/Makefile "lispref/lispref.texi" ;;; man/new-users-guide/Makefile "new-users-guide/new-users-guide.texi" ;;; man/xemacs/Makefile "xemacs/xemacs.texi" ))) (defun makeinfo-gnus () (interactive) (mapc (function makeinfo-from-texinfo) '( "/temp/texi/emacs-mime.texi" ;;; gnus-faq is included by gnus ;;; "/temp/texi/gnus-faq.texi" "/temp/texi/gnus.texi" "/temp/texi/message.texi" ))) 8< 8= 8< 8= 8< 8= 8< 8= cut here 8< 8= 8< 8= 8< 8= 8< 8= Enrico> Enrico Enrico> -- Enrico> eMail: enrico.scholz(a)wirtschaft.tu-chemnitz.de Enrico> talk: ensc(a)ultra.csn.tu-chemnitz.de -- Adrian Aichner Teradyne GmbH, European Design Center Integra Test Division Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

1 participants
0 comments

Re: problem with 21.0.64/AIX 4.3.1.0: exiting a process hangs emacs 26 years, 1 month

Michael Sperber

>>>>> "Kevin" == Kevin Layer <layer(a)franz.com> writes: >>>>>> "Kevin" == Kevin Layer <layer(a)franz.com> writes: Kevin> I start a process from emacs. When that process exits, xemacs hangs. Kevin> I ran under dbx and this is where it was: Kevin> ./configure --with-dialogs=athena Kevin> make Kevin> Let me know if I can send any other information. Kevin> This looks as if you're compiling against IBM's libXt, which is bad Kevin> juju. Link against vanilla X. This is mentioned in the PROBLEMS Kevin> file. Kevin> I'm sure I am. Can you explain what "linking agaist vanilla X" means? Kevin> Does it mean getting the sources to Xt, compiling and Kevin> installing it? Yes. Kevin> If so, where would I get it? /ftp.x.org:/pub/R6.[34] Kevin> Do you have one already compiled up you can put somewhere Kevin> (ftp://ftp.franz.com/incoming/ would be a good place)? Unfortunately, no. I don't even have an AIX 4.3 machine. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: failed compilation of xemacs-21.2.11 26 years, 1 month

Enrico Scholz

SL Baur <steve(a)xemacs.org> writes: > Enrico Scholz <enrico.scholz(a)wirtschaft.tu-chemnitz.de> writes in xemacs-beta(a)xemacs.org: > > > While compiling xemacs I get following error messages: > ... [lots and lots of makeinfo messages] > > > What version of makeinfo do you have installed? The _oldest_ makeinfo > you can use is: > > $ makeinfo --version > makeinfo (GNU texinfo 3.12) 1.68 > > $ makeinfo --version makeinfo (GNU texinfo) 3.12c The messages seems to be right because of "A period or comma *must* follow the closing brace of an `＠xref'. It is required to terminate the cross reference." [texinfo.info, node "Reference syntax"]. So I'm wondering nobody else has detected this error. Enrico -- eMail: enrico.scholz(a)wirtschaft.tu-chemnitz.de talk: ensc(a)ultra.csn.tu-chemnitz.de

2 participants
1 comments

Re: (image-mode.el) Symbol's function definition is void: exec-installed-p 26 years, 1 month

Adrian Aichner

>>>>> "SL" == SL Baur <steve(a)xemacs.org> writes: SL> John H Palmieri <palmieri.2(a)nd.edu> writes in xemacs-beta(a)xemacs.org: >> XEmacs 21.2 "Calliope" [Lucid] (sparc-sun-solaris2.5) of Mon Mar 1 >> 1999 on ahoward >> When I try to open a png file (e.g., one of the files in >> xemacs/etc/photos), I get these messages: >> Loading image-mode... >> Symbol's function definition is void: exec-installed-p SL> I get a host of: SL> allocate_nearest_color returned 0!!! SL> messages. I have NO problems to view those png files. Is every single png file in etc/photos giving you the error? I look at the files with e runs the command dired-find-file from the dired buffer and have no trouble to look at these as distributeed with 21.2-b11: -rw-rw-rw- 1 AichnerA 5 16611 Feb 05 16:58 stigb.png -rw-rw-rw- 1 AichnerA 5 16647 Feb 05 16:57 mcook.png -rw-rw-rw- 1 AichnerA 5 16908 Feb 05 16:57 jareth.png -rw-rw-rw- 1 AichnerA 5 17865 Feb 05 16:57 dv.png -rw-rw-rw- 1 AichnerA 5 18053 Feb 05 16:58 vinm.png -rw-rw-rw- 1 AichnerA 5 18275 Feb 05 16:57 dvm.png -rw-rw-rw- 1 AichnerA 5 18644 Feb 05 16:58 pezm.png -rw-rw-rw- 1 AichnerA 5 19185 Feb 05 16:58 slbm.png -rw-rw-rw- 1 AichnerA 5 20137 Feb 05 16:58 ografm.png -rw-rw-rw- 1 AichnerA 5 22026 Feb 05 16:58 pez.png -rw-rw-rw- 1 AichnerA 5 22332 Feb 05 16:57 ograf.png -rw-rw-rw- 1 AichnerA 5 22686 Feb 05 16:58 slb.png I am running (emacs-version) "XEmacs 21.0 \"Pyrenean63\" [Lucid] (i386-pc-win32) of Sat Feb 06 1999 on ZJ75T" with 64k of colors. HTH, Adrian >> Am I missing some package or something like that? image-mode is in >> the text-modes package, and this requires ispell, fsf-compat, and >> xemacs-base, all of which I seem to have. What's going on? SL> That function is in the apel package. -- Adrian Aichner Teradyne GmbH, European Design Center Integra Test Division Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

1 participants
0 comments

Double calls to font-lock when reverting a buffer 26 years, 1 month

SL Baur

I think I found the problem. As it turns out you can easily explore the phenomenon by creating a dummy function, attaching it to the font-lock-mode-hook and putting a debug-on-entry breakpoint there. (defun foo () (message "font-lock-mode-hook evaluated")) (add-hook 'font-lock-mode-hook 'foo) M-x debug-on-entry foo Then get a buffer and revert it. For buffer reversion, I see font-lock being called via the font-lock-revert-cleanup alias which looks like (from font-lock.el): ;; If the buffer has just been reverted, normally that turns off ;; Font Lock mode. So turn the mode back on if necessary. (defalias 'font-lock-revert-cleanup 'turn-on-font-lock) It appears that the comment is no longer operative as I see the buffer being font-locked when normal-mode is called initially. So this appears to be a different problem than the one I was originally thinking of. Could people who are experiencing this problem please try eliminating the font-lock-revert-cleanup function and see what, if anything, breaks? Ie. after starting XEmacs and loading font-lock.elc, evaluate the following in *scratch*: (defun font-lock-revert-cleanup ())

1 participants
0 comments

Re: ChangeLog wierdness 26 years, 1 month

SL Baur

John Whitley <whitley(a)cse.Buffalo.EDU> writes in xemacs-beta(a)xemacs.org: > Someone buried in birdtracks wrote: That would be me. >> >> Yes, but not with ChangeLogs in specific. Anything font-locked takes >> >> longer to be font-locked after a revert because it appears to be doing >> >> it twice. I thought I fixed this at some point, but it does not >> >> appear to be working optimally now. > SL Baur writes: >> The code that sets major modes (and indirectly fires off font-lock) is >> twisted at best. Everything gets run at least twice, but there is >> very careful dance done to ensure some things don't get run twice. > Hah! No sooner was this posted than it bit me on the rear. > Tuareg mode, for editing Objective Caml programs, includes an > extension to font-lock called "sym-lock" which converts certain > keywords into atomic symbols under XEmacs. > With sym-lock enabled, vc-register causes the error message: > Symbol's function definition is void: t Excellent! Can you please make Lisp backtraces for both of the times the hook gets called? In order to get the most information in the backtrace, evaluate in a buffer each lisp file that appears (ie. make sure the backtrace contains only stuff evaluated from .el's instead of .elc's). Thanks.

1 participants
0 comments

Re: ChangeLog wierdness 26 years, 1 month

SL Baur

Andy Piper <andy(a)xemacs.org> writes in xemacs-beta(a)xemacs.org: >> Did you cut & paste into the minibuffer to spell out the file name when >> you were doing C-x C-f? > No. I simply typed in part of the file name and hit <Tab><Return>. I think > its a bug - but I suspect it might be mswindows specific since there > appears to be some wierdness with msw selections. Yes. That example works fine for me. >>> 2) Font-locking of ChangeLog's from C-x C-f is much faster than reverting a >>> ChangeLog buffer that has been changed externally. >> >>> Does anyone esle see this? >> >> Yes, but not with ChangeLogs in specific. Anything font-locked takes >> longer to be font-locked after a revert because it appears to be doing >> it twice. I thought I fixed this at some point, but it does not >> appear to be working optimally now. > I remember reporting something similar again 19.12 or so :) The code that sets major modes (and indirectly fires off font-lock) is twisted at best. Everything gets run at least twice, but there is very careful dance done to ensure some things don't get run twice.

2 participants
1 comments

Re: PATCH for datbase.c 26 years, 1 month

SL Baur

I have no way of testing this patch myself. Could someone with appropriate access to Berkeley DB 2 please check to be sure this doesn't break older systems? Thanks. pkeusem <pkeusem(a)visi.com> writes in xemacs-beta(a)xemacs.org: > I ran into a problem compiling database.c while building 21.0.64, > I have Berkely DB 2.6.4 installed and it wants four arguments to the > cursor function not three. The new fourth argument is a flags > parameter and must be zero according to the docs. > I've attached a Changelog entry and two diffs, the first is a > cvs context diff, the second is a unified diff from my build tree. You can get a unified diff from cvs with `cvs diff -u', btw. ... > * database.c: Add flags argument to cursor call (must be 0 > according to docs) required for Berkely DB 2.6.4. > [3 CVS context diff <text/plain; us-ascii (7bit)>]

2 participants
1 comments

Re: failed compilation of xemacs-21.2.11 26 years, 1 month

SL Baur

Enrico Scholz <enrico.scholz(a)wirtschaft.tu-chemnitz.de> writes in xemacs-beta(a)xemacs.org: > While compiling xemacs I get following error messages: ... [lots and lots of makeinfo messages] What version of makeinfo do you have installed? The _oldest_ makeinfo you can use is: $ makeinfo --version makeinfo (GNU texinfo 3.12) 1.68

1 participants
0 comments

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta March 1999