December 1998 - XEmacs-Beta - XEmacs Mailing List Archives

XEmacs -vs- glibc-2.1-pre -- ndbm.h 25 years, 11 months

SL Baur

I have recently installed glibc-2.0.108 and it saw fit to delete /usr/include/ndbm.h as part of its installation. This reveals a logic error in XEmacs. In configure, the existence of ndbm.h is tested and the symbol HAVE_NDBM_H should be defined in src/config.h. It isn't. This causes a bomb when compiling src/database.c here: #ifdef HAVE_DBM #include <ndbm.h> Lisp_Object Qdbm; #endif /* HAVE_DBM */ I think the correct guard should be `HAVE_NDBM_H', though something is twisted with glibc deleting someone else's include file. configure:10933: checking for database support configure:10940: checking for ndbm.h configure:10948: gcc -E -I/usr/X11/include conftest.c >/dev/null 2>conftest.out configure:10944: ndbm.h: No such file or directory configure: failed program was: #line 10943 "configure" #include "confdefs.h" #include <ndbm.h> Configure --extra-verbose output: checking for database support checking for ndbm.h... no checking for dbm_open... no checking for dbm_open... no checking for dbm_open in -ldbm... yes Defining HAVE_DBM Prepending "-ldbm" to $LIBS uname -a: Linux demeter.xemacs.org 2.1.132 #2 SMP Sun Dec 20 00:04:14 PST 1998 i686 unknown ./configure '--cflags=-mpentiumpro -O6 -fno-exceptions' '--error-checking=none' '--debug=no' '--with-mule=yes' '--with-dialogs=athena3d' '--with-scrollbars=athena3d' '--use-union-type=no' '--with-xim=xlib' '--with-xfs' '--mail-locking=file' '--extra-verbose=no' XEmacs 21.2-b6 "Apollo" configured for `i686-pc-linux'. Where should the build process find the source code? /devel/xemacs/xemacs-21.2 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/linux.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -mpentiumpro -O6 -fno-exceptions Should XEmacs use the GNU version of malloc? yes (Using Doug Lea's new malloc from the GNU C Library.) Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11/include Where do we find X Windows libraries? /usr/X11/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in support for TIFF image handling. Compiling in support for X-Face message headers. Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for DBM. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using raw Xlib to provide XIM support. Using XFontSet to provide bilingual menubar. Compiling in support for Canna on Mule. Compiling in support for proper session-management. Using Lucid menubars. Using Athena-3d scrollbars. Using Athena-3d dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Using Lisp_Objects with minimal tagbits.

2 participants
1 comments

Re: xemacs-fag.info (What is the status of Asian-language support...) 25 years, 11 months

Hrvoje Niksic

Kenichi Handa <handa(a)etl.go.jp> writes: > The title and the first paragraph use "MULE" (all uppercase). But, > the second paragraph uses "Mule". So, for a person who knows the > term "Mule" as a separate program "Mule Ver.2.3", the second > paragraph can read as below: > ---------------------------------------------------------------------- > As the fundings on original Mule developping team have stopped, > XEmacs should maintain MULE part by itself, thus, we are looking for > ... > ---------------------------------------------------------------------- > > I think, for instance, the following change will reduce misleading. > Could you please consider it? > ---------------------------------------------------------------------- > As the fundings for MULE support on XEmacs have stopped, we are > currently looking for a full-time maintainer for that part. ... > ---------------------------------------------------------------------- Yes, I see your point. Christian, could you please update the FAQ to make this totally unambiguous?

2 participants
1 comments

[patch, 21.0-ish] Re: bookmark.el 25 years, 11 months

Jan Vroonhof

[patch for fsf-compat package at end] Graham Todd <gtodd(a)yorku.ca> writes: > through dejanews.com it turns out I'm not alone. There's something not > working right with respect to pop-up menus and the bookmark package. The thing is that bookmark.el generates a FSF style popup menu dynamically from the bookmarks. It then tries to convert them to XEmacs style menus on the fly: (cond ((fboundp 'x-popup-menu) ; Emacs (x-popup-menu event (bookmark-menu-build-paned-menu name entries))) (t ; XEmacs (get-popup-menu-response (cons name (mapcar (function (lambda (x) (if (stringp x) (vector x nil nil) (vector (car x) (list (car x)) t)))) (bookmark-menu-build-paned-menu name entries))))))) Apparently somebody changed the format of the popup menus generated without changing the code that converts them back. > maintainer/author) so whoever is interested can see if a fix is > possible for 21.0. The funny thing is. It (almost) works correctly on 21.0. This is "by accident". The XEmacs 21.0 fsf-compat package now contains an x-popup-menu.el that emulates the function and does the conversion. Luckily the code in bookmark.el is such that it is prefers that function. you = Karl from now on. > > I just tried, in XEmacs 20.4, the bookmark.elc distributed with that > > XEmacs, and got the same problem you had. I don't really know the > > status of the bookmark.el distributed with XEmacs (I maintain to the > > FSF's copy, and only upload to their site). Are the XEmacs people > > maintaining a branch version? Not intentionally at least. In fact we would very much prefer if there were only one version that works on both emacsen. > > Do they have to make changes to each new version released with FSF > > Emacs? I think the XEmacs versions are just plain copies of what ever you release. > > Er, sorry, I'm at a loss. I can't maintain it for both versions -- > > that would nearly double the load of maintaining it now. > > > If you can find a fix, or if you want to maintain it for XEmacs (or > > contact the XEmacs maintainers and find out where they get their > > bookmark.el from), that would help. I think it would be very nice if you could maintain it for XEmacs too in the sense that you either get check-in access to the CVS yourself or simply send any new versions you release to xemacs-patches(a)xemacs.org. You then just need somebody to make sure the new releases work on XEmacs (i.e. testing). Graham? If any of you then need XEmacs specific lisp help you can just mail to xemacs-beta. As a start you can simply ditch the the XEmacs specific code above since it doesn't work anyway and is not needed on 21.0. In fact that way it is clear that you need the fsf-compat package. He, wait a second! That already happened the version in FSF 20.3 does NOT contain that particular code any more. However it does work. It calls set-text-properties on 'nil' which is bad. At the end there is a patch against the FSF 20.3 version of which makes it work on XEmacs (together with the popup menu patch). This patch just removes ALL of the XEmacs specifics. Hooray! Could you fold that into your version and then send it to xemacs-patches(a)xemacs.org/ Jan P.S. There is one but... Unfortunately the current version of x-popup-menu.el for 21.0 is broken. It needs this patch diff -u fsf-compat/x-popup-menu.el~ fsf-compat/x-popup-menu.el --- fsf-compat/x-popup-menu.el~ Thu Dec 17 19:45:39 1998 +++ fsf-compat/x-popup-menu.el Thu Dec 17 19:45:39 1998 ＠＠ -22,7 +22,7 ＠＠ ;; Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA ;; 02111-1307, USA. -;;; Synched up with: Not in FSF +;;; Synched up with: Not in FSF ;;; Commentary: ＠＠ -30,7 +30,7 ＠＠ ;;;###autoload (defun x-popup-menu (event menu) - "Pop up menu for Mouse-2 for selected date in the calendar window." + "Let user select a value with from a menu." (save-excursion (let ((title (car menu)) ;; try to ignore just a "" string, XEmacs will typically add two ＠＠ -44,16 +44,11 ＠＠ (setq selection (get-popup-menu-response (cons title (convert_fsf_popup mb-items)) event)) - ;; normally, we'll get a <#event (call-intercatively function)> - ;; return, but if nothing was selected, we'll have <#event - ;; (run-hooks menu-no-select-hook. So, if something is selected, - ;; return it, other run the hook - (if (string-match (symbol-name (event-function selection)) - "call-interactively") - (setq selection (event-object selection)) - (funcall (event-function selection) (event-object selection)) - )))) + ;; Now that we wrap the stuff to be returned in a list + ;; we can simply call the function. Really popup-menu should simply + ;; return the return value of the function run! + (funcall (event-function selection) (event-object selection))))) (defun convert_fsf_popup (menu) "Convert FSF style menu notation to the XEmacs format." ＠＠ -67,7 +62,7 ＠＠ (;; alist -> vector (and (stringp (car x)) (not (true-list-p x))) - (vector (car x) (cdr x))) + (vector (car x) (list 'identity (cdr x)))) (;; submenu (and (stringp (car x)) (true-list-p (cdr x))) [Note this is against the FSF 20.3 version of bookmark.el, for Karl] diff -u /u/users/vroonhof/scratch/xemacs/bookmark.el~ /u/users/vroonhof/scratch/xemacs/bookmark.el --- /u/users/vroonhof/scratch/xemacs/bookmark.el~ Thu Dec 17 20:44:22 1998 +++ /u/users/vroonhof/scratch/xemacs/bookmark.el Thu Dec 17 20:44:22 1998 ＠＠ -215,14 +215,6 ＠＠ ;; some random value higher than 9600 (setq baud-rate 19200)) -;; XEmacs apparently call this `buffer-substring-without-properties', -;; sigh. -(or (fboundp 'buffer-substring-no-properties) - (if (fboundp 'buffer-substring-without-properties) - (fset 'buffer-substring-no-properties - 'buffer-substring-without-properties) - (fset 'buffer-substring-no-properties 'buffer-substring))) - ;;; Keymap stuff: ＠＠ -516,10 +508,10 ＠＠ INFO-NODE, so record this fact in the bookmark's entry." (bookmark-maybe-load-default-file) (let ((stripped-name (copy-sequence name))) - (or bookmark-xemacsp ;; XEmacs's `set-text-properties' doesn't work on ;; free-standing strings, apparently. - (set-text-properties 0 (length stripped-name) nil stripped-name)) + ;; JV well it should! Just do it. + (set-text-properties 0 (length stripped-name) nil stripped-name) (if (and (bookmark-get-bookmark stripped-name) (not overwrite)) ;; already existing bookmark under that name and ;; no prefix arg means just overwrite old bookmark ＠＠ -570,13 +562,15 ＠＠ ;; Now fill in the optional parts: ;; Take no chances with text properties - (set-text-properties 0 (length annotation) nil annotation) - (set-text-properties 0 (length info-node) nil info-node) (if annotation - (nconc the-record (list (cons 'annotation annotation)))) + (progn + (set-text-properties 0 (length annotation) nil annotation) + (nconc the-record (list (cons 'annotation annotation))))) (if info-node - (nconc the-record (list (cons 'info-node info-node)))) + (progn + (set-text-properties 0 (length info-node) nil info-node) + (nconc the-record (list (cons 'info-node info-node))))) ;; Finally, return the completed record. the-record))

2 participants
1 comments

Re: 21.0-b60 missing tm files 25 years, 11 months

Raymond Toy

>>>>> "sb" == SL Baur <steve(a)xemacs.org> writes: sb> Raymond Toy <toy(a)rtp.ericsson.se> writes in sb> xemacs-beta(a)xemacs.org: sb> [relocated tm helper scripts] sb> They've been moved from the core to the tm package, and have sb> been there two months now. >> That was my first thought. I looked there. I must be blind. >> I have tm-1.12-pkg.tar.gz, the latest I can find in the >> xemacs-21.0/packages/binary-packages directory. sb> It is now up to tm-1.15. sb> That doesn't look like the right directory. XEmacs 21 sb> packages are located in sb> ftp://ftp.xemacs.org/pub/xemacs/packages/ sb> and I see a `tm-1.15-pkg.tar.gz' there. Oops. I must have missed the messages saying the package directory moved. Sorry about that. Ray

1 participants
0 comments

[OK] 21.2 "Aphrodite" XEmacs Lucid (beta5) on i586-pc-linux 25 years, 11 months

Larry Ayers

Patched up from 21.2-b4; built and runs fine. This is the first beta for quite some time which has a functional finder database (on this machine, at least). This one also seems to be snappier somehow, perhaps due to Martin's many changes? > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /usr/local/src/xemacs-21.2-b4/Installation: > (Output from most recent run of ./configure) uname -a: Linux liatris 2.1.131 #21 Sat Dec 12 09:30:16 CST 1998 i586 unknown ./configure '--prefix=/usr/local/xemacs-21.2' '--with-site-lisp' '--package-path=/usr/local/xemacs-beta/lib/xemacs/packages' '--gung-ho' '--with-xpm' '--with-tiff=no' '--with-dialogs=athena' '--error-checking=none' '--debug=no' '--without-toolbars' XEmacs 21.2-b5 "Aphrodite" configured for `i586-pc-linux'. Where should the build process find the source code? /usr/local/src/xemacs-21.2-b4 What installation prefix should install use? /usr/local/xemacs-21.2 What operating system and machine description files should XEmacs use? `s/linux.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes (Using Doug Lea's new malloc from the GNU C Library.) Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11/include Where do we find X Windows libraries? /usr/X11/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. > /usr/local/src/xemacs-21.2-b4/beta.err does not exist!

1 participants
0 comments

Re: italic text (XEmacs 21.2) 25 years, 11 months

William M. Perry

Lars Magne Ingebrigtsen <larsi(a)ifi.uio.no> writes: > So, how does XEmacs frob italic fonts? > > I have the following resources: > > *font: -b&h-lucidatypewriter-medium-r-normal-sans-12-120-75-75-m-70-iso8859-1 > Emacs.italic.attributeFont: -adobe-courier-medium-o-normal--12-120-75-75-m-70-iso8859-1 > > And yet the following > > (defface gnus-emphasis-bold-italic '((t (:bold t :italic t))) > "Face used for displaying bold italic emphasized text (/*word*/)." > :group 'gnus-article-emphasis) defface uses the font.el package, this may be the problem. -bp

1 participants
0 comments

italic text (XEmacs 21.2) 25 years, 11 months

Lars Magne Ingebrigtsen

So, how does XEmacs frob italic fonts? I have the following resources: *font: -b&h-lucidatypewriter-medium-r-normal-sans-12-120-75-75-m-70-iso8859-1 Emacs.italic.attributeFont: -adobe-courier-medium-o-normal--12-120-75-75-m-70-iso8859-1 And yet the following (defface gnus-emphasis-bold-italic '((t (:bold t :italic t))) "Face used for displaying bold italic emphasized text (/*word*/)." :group 'gnus-article-emphasis) gives me this: gnus-emphasis-bold-italic black Gainsboro -*-fixed-medium-i-*--16-*-iso8859-1 Which isn't very useful. Now, the manual says: All text is displayed in some face, defaulting to the face named `default'. To set the font of normal text, use `Emacs*default.attributeFont'. To set it in the frame named `fred', use `Emacs*fred.default.attributeFont'. If I put something like Emacs*italic.attributeFont: -b&h-lucidatypewriter-medium-r-normal-sans-12-120-75-75-m-70-iso8859-1 then I get the following warning: (2) (resource/warning) Bad resource specification encountered: something like Emacs*italic.attributeFont: -b&h-lucidatypewriter-medium-r-normal-sans-12-120-75-75-m-70-iso8859-1 You should replace the * with a . in order to get proper behavior when you use the specifier and/or `set-face-*' functions. And I still get the "fixed" italic font. The `italic' font looks OK in any case; it's just the deffaced italic fonts that look ugly. -- (domestic pets only, the antidote for overdose, milk.) larsi(a)ifi.uio.no * Lars Magne Ingebrigtsen

1 participants
0 comments

Re: XEmacs 21.0.60 crashes while opening file 25 years, 11 months

Gunnar Evermann

Michael Lundkvist <ml(a)epact.se> writes: > In XEmacs 21.0 "Poitou60" [Lucid] (sparc-sun-solaris2.5.1, Mule) of > I have a file that crashes both 21.0-b54 and 21.0.60 when I open > it. Using C-u C-x C-f and specifying 'no-conversion' makes it load OK. [snip backtrace of crash in redisplay ] If I load the file in "Apollo" (on Linux 2.0.35) compiled with-mule (and the default error-checking) I get a crash a bit earlier at file-coding.c:3907, which is: 3904 charset = str->iso2022.charset[reg]; 3905 3906 /* Error checking: */ 3907 if (NILP (charset) || str->iso2022.invalid_designated[reg] 3908 || (((c & 0x7F) == ' ' || (c & 0x7F) == ISO_CODE_DEL) 3909 && XCHARSET_CHARS (charset) == 94)) random debugging stuff follows: (gdb) p str->iso2022 $4 = {charset = {138349840, 138171016, 138170988, 138170988}, register_left = 0, register_right = 1, esc = ISO_ESC_NOTHING, esc_bytes = "\000\000\000\000\000\000\000", esc_bytes_index = 0, composite_chars = 0x0, invalid_designated = "\000\000\000", switched_dir_and_no_valid_charset_yet = 0, invalid_switch_dir = 0, output_literally = 0, output_direction_sequence = 0} (gdb) p reg $5 = 1 Of the four charsets only the first (str->iso2022.charset[0]) seems valid. charset[1] is the Symbol 't' the other two are 'nil'. Maybe one of the mule (or file-coding) people can have a look at this... Fatal error: assertion failed, file /local/srcdisk/gunnar/src/XEmacs/xemacs/src/ mule-charset.h, line 485, RECORD_TYPEP (obj, lrecord_charset) || MARKED_RECORD_P (obj) #0 0x403c6405 in __kill () #1 0x40393055 in raise (sig=136649952) #2 0x80f9d44 in error_check_charset (obj=138171016) at /local/srcdisk/gunnar/src/XEmacs/xemacs/src/mule-charset.h:485 #3 0x80f23b1 in decode_coding_iso2022 (decoding=0x860e678, src=0x861e7c9 'ÿ' <repeats 21 times>, "úUP\017", 'ÿ' <repeats 35 times>, "òU_", 'ÿ' <repeats 34 times>, "ð\rU_ð", dst=0x85e19e8, n=11999) at /local/srcdisk/gunnar/src/XEmacs/xemacs/src/file-coding.c:3907 #4 0x80eb625 in mule_decode (decoding=0x860e678, src=0x861e7c8 'ÿ' <repeats 22 times>, "úUP\017", 'ÿ' <repeats 35 times>, "òU_", 'ÿ' <repeats 34 times>, "ð\rU_ð", dst=0x85e19e8, n=12000) at /local/srcdisk/gunnar/src/XEmacs/xemacs/src/file-coding.c:2026 #5 0x80eae5d in decoding_reader (stream=0x860e678, data=0x861e7c8 'ÿ' <repeats 22 times>, "úUP\017", 'ÿ' <repeats 35 times>, "òU_", 'ÿ' <repeats 34 times>, "ð\rU_ð", size=65536) at /local/srcdisk/gunnar/src/XEmacs/xemacs/src/file-coding.c:1805 #6 0x816b620 in Lstream_raw_read (lstr=0x860e678, buffer=0x861e7c8 'ÿ' <repeats 22 times>, "úUP\017", 'ÿ' <repeats 35 times>, "òU_", 'ÿ' <repeats 34 times>, "ð\rU_ð", size=65536) at /local/srcdisk/gunnar/src/XEmacs/xemacs/src/lstream.c:509 #7 0x816b6d9 in Lstream_read_more (lstr=0x860e678) at /local/srcdisk/gunnar/src/XEmacs/xemacs/src/lstream.c:527 #8 0x816b835 in Lstream_read (lstr=0x860e678, data=0xbfff64ac, size=32768) at /local/srcdisk/gunnar/src/XEmacs/xemacs/src/lstream.c:571 #9 0x812a093 in Finsert_file_contents_internal (filename=140091796, visit=138171016, beg=1, end=24001, replace=138170988, codesys=138273096, used_codesys=139246280) at /local/srcdisk/gunnar/src/XEmacs/xemacs/src/fileio.c:2987 #10 0x80c3076 in Ffuncall (nargs=8, args=0xbfffe5dc) at /local/srcdisk/gunnar/src/XEmacs/xemacs/src/eval.c:3189 #11 0x8091475 in execute_optimized_program ( [rest snipped] -- Gunnar Evermann Speech, Vision & Robotics Group Engineering Department Cambridge University

1 participants
0 comments

Re: 21.2 patch backlog cleared 25 years, 11 months

Hrvoje Niksic

Andy Piper <andyp(a)parallax.co.uk> writes: > -- new display table functionality from Hrvoje Niksic You said you were unable to apply this.

1 participants
0 comments

Re: MANIFEST.tm 25 years, 11 months

SL Baur

Charles G Waldman <cgw(a)pgt.com> writes in xemacs-beta(a)xemacs.org: > MANIFEST.tm has some junk at the bottom, which is confusing my > automated installation builder: Noted. That's already been fixed in CVS, but hasn't been propagated out yet.

1 participants
0 comments

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 December 1998