December 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Customize and :version? 23 years, 11 months

Simon Josefsson

If this has been discussed before (not unlikely), please forgive my bandwidth waste... I noticed that Emacs have a :version tag on `defcustom' and `defgroup' when syncing some mail-lib files. I think it's used to indicate in what version a certain group/variable was introduced. It raise a sort-of fundamental problems, should XEmacs custom.el support this? (I don't know in what way Emacs actually use the field.) How? It mixes badly with the packaging system and it's separate versioning mechanism. Why I ask: If XEmacs custom.el don't support :version (which is the current case), do you think it's good to include :version fields in FSF synced files in XEmacs just for sake of minimizing differences? I'd like to do that, but I guess it could cause problems if XEmacs at some point changed their mind about supporting :version.

2 participants
2 comments

Re: 21.2.38 Xlib errors 23 years, 11 months

Andy Piper

At 23:42 28/12/00 -0500, Isaac Hollander wrote: > Andy> Please apply this patch and see if the assert gets triggered. > If it does > Andy> please send me a C backtrace (you need to rebuild with -g so we > can get > Andy> line numbers). When are you actually getting these errors? > >Still no joy. I think I've got it. Please try this. 2000-12-30 Andy Piper <andy(a)xemacs.org> * xlwtabs.c: remove assertion definitions and put them in lwlib-internal.h. This has the effect of enabling assertions which should have been done from the very start. (TabsShuffleRows): fix duff assertion. (PreferredSize3): use dimensions throughout. (PreferredSize2): ditto. (TabLayout): ditto. (DrawFrame): be clever about the enclosing frame if the child height is 0. (TabsResize): don't configure children that are no visible anyway. Make sure geometry calculations don't end up negative. * lwlib-internal.h: put in assertion definitions. andy -------------------------------------------------------------- Dr Andy Piper Principal Consultant, BEA Systems Ltd

1 participants
0 comments

Re: Background pixmaps do not change properly 23 years, 11 months

Alexander G. Burchell

>>>>> "Kilian" == Kilian A Foth <foth(a)informatik.uni-hamburg.de> writes: Kilian> Doing (set-face-background-pixmap 'default Kilian> "/my/pretty/file1.jpeg") correctly sets the background Kilian> pixmap the image in file1, but following up with Kilian> (set-face-background-pixmap 'default Kilian> "/my/pretty/file2.jpeg") displays the same image again, Kilian> not the second one as under 21.1. I have also found this problem, with Cygwin-compiled XEmacs. A workaround is the following: (set-face-foreground face foreground locale) (remove-face-property face 'background-pixmap locale) (set-face-background-pixmap face pixmap locale) ;; Setting background to the foreground color is intentional: (set-face-background face foreground locale) BTW, locale is optional (try using "(current-buffer)" for that). I think that's about it. It's been a while since I tried it since I am back to XEmacs 21.1. By the way, does anyone know about the problem with background pixmaps/font lock that causes this error (with no stack trace): Fatal error: assertion failed, file specifier.c, line 1375, !inst_list || EQ (locale, Qglobal) Another problem I've found with background pixmaps (XEmacs 21.1) is that when having different buffers with different background pixmaps, when switching buffers, sometimes the bottom, blank portion of the screen is left with the old pixmap while areas containing new text at the top have the new pixmap. I guess this is some kind of display optimization gone wrong. Thanks! -- Alexander G. Burchell Wilshire Associates aburchel(a)wilshire.com (310) 899-2303

1 participants
0 comments

Re: Find architecture-specific directories correctly 23 years, 11 months

Jerry James

Doggone. I'm having a hard time getting used to this Kinesis keyboard. I was trying to hit C-left, but left is right under the letter C, so I accidentally sent a partially edited message. Here's what I really meant to send. "Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> wrote: > I don't understand why you don't have anything in your > module-load-path, but what's in mine (and Yoshiki's) I believe is > coming because there is no startup code in current CVS to set > module-load-path; it's only done at dump time AFAICT. I wonder if > maybe Yoshiki's got a modules -> $srcdir/modules symlink in the build > directory? > > Maybe you fixed this already and forgot to diff this file? A quick experiment on my end seems to indicate that the value dumped in module-load-path is different in these two situations: - a (previous) build of XEmacs is installed in the place where this build will eventually be installed (it's enough for the directories to exist); - the directories will be created when this build of XEmacs is eventually installed. I'll note that this is *with* my last patch, though. I'll try backing the patch out and see if the same thing happens. I suspect it will, though, since it was getting nil the first time that took me down the path to creating that patch. -- Jerry James

1 participants
0 comments

Re: Find architecture-specific directories correctly 23 years, 11 months

Jerry James

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> wrote: > I don't understand why you don't have anything in your > module-load-path, but what's in mine (and Yoshiki's) I believe is > coming because there is no startup code in current CVS to set > module-load-path; it's only done at dump time AFAICT. I wonder if > maybe Yoshiki's got a modules -> $srcdir/modules symlink in the build > directory? > > Maybe you fixed this already and forgot to diff this file? A quick experiment on my end seems to indicate that the value dumped in module-load-path is different in these two situations: - a (previous) build of XEmacs is installed in the place where this build will eventually be installed (it's enough for the directories to exist); - the directories will be created when XEmacs I was puzzled about this, too, so I rebuilt it ... and module-load-path was not nil. But then it occurred to me... - The first time I built XEmacs 21.2 and got nil in my module-load-path, I didn't have an installed XEmacs 21.2 tree. - The second time I built XEmacs 21.2 and got a non-nil module-load-path, I had an installed XEmacs 21.2 tree (from the first build). A quick experiment seems to confirm this: the value dumped into module-load-path is affected by the existence of directories in the location where XEmacs will be installed once it is dumped. Ugh! I'll note that this is *with* my last patch, though. I'll try backing the patch out and see if the same thing happens. I suspect it will, though, since it was getting nil the first time that took me down the path to creating that patch. -- Jerry James

1 participants
0 comments

21.2.38 Xlib errors 23 years, 11 months

Isaac Hollander

I built 21.2.38 (with mule, fwiw) on my Redhat 6.2+HelixCode GNOME+OpenMotif+XFree86 4.0.1 system. I opened ~/.xemacs/init.el, and got the below Xlib error. Any hints to help debug this? Thanks Isaac Xlib: unexpected async reply (sequence 0x567)! xemacs: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 12 (X_ConfigureWindow) Value in failed request: 0x0 Serial number of failed request: 1283 Current serial number in output stream: 1383 uname -a: Linux yitzchak 2.2.14-5.0 #1 Tue Mar 7 21:07:39 EST 2000 i686 unknown ./configure '-debug' '--with-mule' '--cache-file=/dev/null' XEmacs 21.2-b38 "Peisino,Ak(B" configured for `i686-pc-linux'. Compilation / Installation: Source code location: /home/ysh/xemacs-21.2.38 Installation prefix: /usr/local Operating system description file: `s/linux.h' Machine description file: `m/intel386.h' Compiler: gcc -g -O3 -Wall -Wno-switch -Wpointer-arith -Winline -Wmissing-prototypes -Wshadow 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 Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Using Motif native widgets. 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 ESD (Enlightened Sound Daemon). Databases: Compiling in support for Berkeley database. Compiling in support for LDAP. Internationalization: Compiling in support for Mule (multi-lingual Emacs). Compiling in support for XIM (X11R5+ I18N input method). - Using Motif to provide XIM support. Mail: Compiling in support for "dot-locking" mail spool file locking method. Other Features: Compiling in support for dynamic shared object modules. Compiling in support for extra debugging code. WARNING: --------------------------------------------------------- WARNING: Compiling in support for runtime error checking. WARNING: XEmacs will run noticeably more slowly as a result. WARNING: Error checking is on by default for XEmacs beta releases. WARNING: ---------------------------------------------------------

2 participants
1 comments

X Error of failed request:... 23 years, 11 months

Robin S. Socha

Does that have to make me worried? xemacs: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 12 (X_ConfigureWindow) Value in failed request: 0x0 Serial number of failed request: 26944 Current serial number in output stream: 27066 -- Robin S. Socha <http://socha.net/> ``The funniest part is that on this system, Robin S. Socha is the "kinder, gentler" sysadmin...'' (Kate <http://www.katewerk.com/>)

5 participants
4 comments

more antialiased text fun 23 years, 11 months

Vladimir Vukicevic

I just redid the antialiased text/xrender patch against the latest on the 21.2 branch; everything mostly works. It's available at http://www.intrepid.com/~vladimir/xemacs_beta_aa.patch.gz . The fonts are specified now in normal XLFD fashion, and the code will attempt to find a truetype font that can be rendered antialiased first, and if it fails, will fall back to core fonts. However, I'm having some expose/redraw issues. When an expose event is received, most of the time the relevant portions of the frame don't get redrawn. Is there some sort of pixmap caching going on, so that x_output_string doesn't always get called? Strangely enough, if I slowly drag a window over the xemacs window, the letters do mostly get redrawn as they appear, but if I speed up the dragging, then nothing gets redrawn. Note that this only happens if the window is obscured by another window, and then uncovered -- everything updates correctly from events inside the window (text editing, moving, selecting, etc.). Hitting C-l always causes the window to render correctly. There's also an issue with the tabs -- I put in patch to xlwtabs.c to avoid crashing if the font that was passed in was NULL (which shouldn't happen, but crashes shouldn't happen either :-) and then code in glyphs-x.c, which when setting the font for the tabs will check if an Xft font is in use, and if it is, it will attempt to get an equivalent core font from the library and use that. This works (the tabs get displayed fine), but XEmacs then every once in a while spews XConfigWindow errors and locks up (easily repeatable). I haven't had a chance to track this one down, but hiding the tabs gets rid of this problem. Any help into either issue would be appreciated... also if anyone wants to give this code a shot but needs help setting things up, feel free to email me.. -- Vladimir -- vladimir(a)helixcode.com

4 participants
3 comments

[Chmouel Boudjnah <devel@mandrakesoft.com>] [CHRPM] xemacs-21.1.12-9mdk 23 years, 11 months

Chmouel Boudjnah

Can the "Mandrake is not supported" patch could be removed ? -------------------- Start of forwarded message -------------------- X-From-Line: changelog-owner(a)linux-mandrake.com Mon Dec 25 13:31:58 2000 >From chmou Mon Dec 25 13:31:58 2000 Return-Path: <changelog-owner(a)linux-mandrake.com> Delivered-To: chmou(a)localhost.mandrakesoft.com Received: from localhost (localhost.localdomain [127.0.0.1]) by seatle.mandrakesoft.com (Postfix) with ESMTP id E982083A for <chmou＠localhost>; Mon, 25 Dec 2000 13:31:57 +0100 (CET) Received: from mandrakesoft.mandrakesoft.com [216.71.116.162] by localhost with POP3 (fetchmail-5.6.0) for chmou＠localhost (single-drop); Mon, 25 Dec 2000 13:31:58 +0100 (CET) Received: from yavin.mandrax.org (moseisley.mandrax.org [63.209.80.226]) by mandrakesoft.mandrakesoft.com (8.8.5/8.8.5) with ESMTP id GAA20030 for <chmouelb(a)mandrakesoft.com>; Mon, 25 Dec 2000 06:31:43 -0600 Received: by yavin.mandrax.org (Postfix, from userid 500) id D5FC11CEE4; Mon, 25 Dec 2000 04:31:43 -0800 (PST) Delivered-To: sympa(a)mandrax.org Received: from mandrakesoft.mandrakesoft.com (mandrakesoft.mandrakesoft.com [216.71.84.35]) by yavin.mandrax.org (Postfix) with ESMTP id 7C5821CE9B for <sympa(a)mandrax.org>; Mon, 25 Dec 2000 04:30:03 -0800 (PST) Received: from kenobi.mandrakesoft.com (office [195.68.114.34]) by mandrakesoft.mandrakesoft.com (8.8.5/8.8.5) with ESMTP id GAA19661 for <changelog(a)linux-mandrake.com>; Mon, 25 Dec 2000 06:30:00 -0600 Received: by kenobi.mandrakesoft.com (Postfix, from userid 554) id 1DC3760379; Mon, 25 Dec 2000 14:30:01 +0100 (CET) From: Chmouel Boudjnah <devel(a)mandrakesoft.com> To: Changelog List <changelog(a)linux-mandrake.com> Reply-To: cooker(a)linux-mandrake.com Sender: devel(a)mandrakesoft.com Subject: [CHRPM] xemacs-21.1.12-9mdk Message-Id: <20001225133001.1DC3760379(a)kenobi.mandrakesoft.com> Date: Mon, 25 Dec 2000 14:30:01 +0100 (CET) X-Loop: changelog(a)linux-mandrake.com X-Sequence: 2892 Precedence: list List-Help: <mailto:sympa＠linux-mandrake.com?subject=help> List-Subscribe: <mailto:sympa＠linux-mandrake.com?subject=subscribe%20changelog> List-Unsubscribe: <mailto:sympa＠linux-mandrake.com?subject=unsubscribe%20changelog> List-Post: <mailto:changelog＠linux-mandrake.com> List-Owner: <mailto:changelog-request＠linux-mandrake.com> X-UIDL: ]$\"!~G1"!S4R"!ko""! Lines: 37 Xref: seatle.mandrakesoft.com mandrake.changelog:10870 --=-=-= Name : xemacs Relocations: (not relocateable) Version : 21.1.12 Vendor: MandrakeSoft Release : 9mdk Build Date: Mon Dec 25 14:15:01 2000 Install date: (not installed) Build Host: no.mandrakesoft.com Group : Editors Source RPM: (none) Size : 25361314 License: GPL Packager : Chmouel Boudjnah <chmouel(a)mandrakesoft.com> URL : http://www.xemacs.org/ Summary : An X Window System based version of GNU Emacs. Description : XEmacs (and regular GNU Emacs, too) is a self-documenting, customizable, extensible, real-time display editor. XEmacs is self-documenting because at any time you can type in control-h to find out what your options are or to find out what a command does. XEmacs is customizable because you can change the definitions of XEmacs commands to anything you want. XEmacs is extensible because you can write entirely new commands--programs in the Lisp language to be run by Emacs' own Lisp interpreter. XEmacs includes a real-time display, which means that the text being edited is visible on the screen and is updated very frequently (usually after every character or pair of characters) as you type. To use XEmacs, you'll need to install the XEmacs binary. The xemacs package includes the standard XEmacs binary that most people will use. The XEmacs binary is dynamically linked, with both X11 and TTY (ncurses) support, but without mule (MUlti-Lingual Emacs, the Asian character set) support. --=-=-= * Mon Dec 25 2000 Chmouel Boudjnah <chmouel(a)mandrakesoft.com> 21.1.12-9mdk - Remove the metamod patch. -- http://www.linux-mandrake.com/en/cookerdevel.php3 -------------------- End of forwarded message -------------------- -- MandrakeSoft Inc http://www.chmouel.org --Chmouel

3 participants
5 comments

[comp.emacs.xemacs] Package incompatibility 23 years, 11 months

Vin Shelton

As the maintainer of the current stable release, I must concur. Steve Youngs (I know you're out of touch at the moment, perhaps you'll comment when you get back) please build with the latest stable release, in this case 21.1. - vin x-uunet-gateway: mr1.ash.ops.us.uu.net from xemacs to comp.emacs.xemacs; Wed, 13 Dec 2000 10:59:23 GMT Sender: davby(a)ida.liu.se Subject: Package incompatibility X-face: (＠~#v$c[GP"T}a;|MU<%Dpm5*6yv"NR|7k;uk8MAISFxdZ(Og$C{u(j"9X7v$qonp}SKfhT g|5[Pu~/3F7XQEk70gK'4z%1R%%gg7]}=>/jD`qcBeHDgo&HS,^S!&.zoTSxh<>-O6EB?SSy96&m37 X-url: http://www.ida.liu.se/~davby/ From: davby(a)ida.liu.se (David Byers) Date: 13 Dec 2000 11:58:50 +0100 Message-ID: <414s08oadx.fsf(a)sen5.ida.liu.se> Newsgroups: comp.emacs.xemacs Path: reader4.news.rcn.net!feed1.news.rcn.net!feed2.news.rcn.net!rcn!cpk-news-hub1.bbnplanet.com!news.gtei.net!yellow.newsread.com!netaxs.com!newsread.com!uunet!ffx.uu.net!spool1.news.uu.net!wendy-fate.uu.net!xemacs Lines: 24 Xref: reader4.news.rcn.net comp.emacs.xemacs:54838 In XEmacs 21.1 (patch 8) "Bryce Canyon" [Lucid] (sparc-sun-solaris2.7, Mule) of Thu Nov 18 1999 on sen2.ida.liu.se configured using `configure --prefix=/home/pelab/pub/pkg/xemacs-21.1.8 --with-mule '--site-includes=/home/pelab/pub/include /home/pelab/include' '--site-libraries=/home/pelab/pub/lib /home/pelab/lib' '--site-runtime-libraries=/home/pelab/pub/lib /usr/dt/lib /home/pelab/lib'' I updated all packages using the interface accessible through the "Options" menu by first selecting "Add download site" (adding ftp.xemacs.org) and then "List and install". It is now impossible to use M-x calendar. The exact error message I get when doing M-x calendar is: invalid lazy-loaded byte code: k«Ã The file calendar.elc is generated by XEmacs 21.2 (beta36). It appears that the output of this byte compiler is not entirely compatible with XEmacs 21.1.8. For pacakges to work, this sort of thing *has* to be avoided. Either by using separate package directories for separate versions of XEmacs or by recompiling packages as they are retreived if they are not precompiled with a compatible version of XEmacs. -- David Byers.

4 participants
13 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 2000