May 2000 - XEmacs-Beta - XEmacs Mailing List Archives

pdump: Zapping start_files is evil 24 years, 6 months

Michael Sperber

The latest CVS has this in configure.in: if test "$pdump" = "yes"; then ordinary_link="yes" ld="${ordinary_ld}" start_files= libs_standard= unexec= lib_gcc= fi Unfortunately, some OSes still need, for example, pre-crt0.c in start_files because of the reference to data_start in sysdep.c. (FreeBSD 4.0-RELEASE, for one.) I suspect the data_start business in sysdep.c can go away, but haven't had time to investigate. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

[Various] Is `ilisp' DFSG free? 24 years, 6 months

Karl M. Hegbloom

[ CC'd to xemacs-beta since `ilisp' is in the xemacs-packages CVS also.] What's the status of GPLing `ilisp', as mentioned in the version 5.10.1 COPYING file? ------- Start of forwarded message ------- Date: Fri May 12 23:33:10 2000 From: Various Subject: Is `ilisp' DFSG free? Topics: Is `ilisp' DFSG free? Re: Is `ilisp' DFSG free? Re: Is `ilisp' DFSG free? ---------------------------------------------------------------------- Date: 11 May 2000 14:52:32 -0700 From: karlheg(a)debian.org (Karl M. Hegbloom) To: The Debian Legal Eagles <debian-legal(a)lists.debian.org> Subject: Is `ilisp' DFSG free? Message-ID: <87vh0keov3.fsf(a)bittersweet.intra> Please advise. I am not subscribed, so Cc. Is this licence (from ilisp 5.10.1) DFSG free? COPYING -- TERMS AND LICENSING AGREEMENT FOR ILISP - ------------------------------------------------------------------------------ This file is part of ILISP. Version: 5.10.1 Date: 15 June 1999 Copyright (C) 1990, 1991, 1992, 1993 Chris McConnell 1993, 1994 Ivan Vasquez 1994, 1995, 1996 Marco Antoniotti and Rick Busdiecker 1996-2000 Marco Antoniotti and Rick Campbell Other authors' names for which this Copyright notice also holds may appear later in this file. Send mail to 'majordomo(a)cons.org' to be included in the ILISP mailing list (a message with 'subscribe ilisp' in the body should suffice). 'ilisp(a)cons.org' is the general ILISP mailing list were bugs and improvements are discussed. - ------------------------------------------------------------------------------ ILISP if freely redistributable. Eventually it may become part of GNU Emacs and it will in that case comply with the GPL. For the time being we adopt the following licensing agreement. Such licensing agreement may be overridden by the licensing notice contained in an individual file and for that file only. - ------------------------------------------------------------------------------ GENERAL LICENSE AGREEMENT AND LACK OF WARRANTY This software is distributed in the hope that it will be useful (both in and of itself and as an example of lisp programming), but WITHOUT ANY WARRANTY. The author(s) do not accept responsibility to anyone for the consequences of using it or for whether it serves any particular purpose or works at all. No warranty is made about the software or its performance. Use and copying of this software and the preparation of derivative works based on this software are permitted, so long as the following conditions are met: o The copyright notice and this entire notice are included intact and prominently carried on all copies and supporting documentation. o No fees or compensation are charged for use, copies, or access to this software. You may charge a nominal distribution fee for the physical act of transferring a copy, but you may not charge for the program itself. o If you modify this software, you must cause the modified file(s) to carry prominent notices (a Change Log) describing the changes, who made the changes, and the date of those changes. o Any work distributed or published that in whole or in part contains or is a derivative of this software or any part thereof is subject to the terms of this agreement. The aggregation of another unrelated program with this software or its derivative on a volume of storage or distribution medium does not bring the other program under the scope of these terms. o Permission is granted to manufacturers and distributors of lisp compilers and interpreters to include this software with their distribution. This software is made available AS IS, and is distributed without warranty of any kind, either expressed or implied. In no event will the author(s) or their institutions be liable to you for damages, including lost profits, lost monies, or other special, incidental or consequential damages arising out of or in connection with the use or inability to use (including but not limited to loss of data or data being rendered inaccurate or losses sustained by third parties or a failure of the program to operate as documented) the program, even if you have been advised of the possibility of such damanges, or for any claim by any other party, whether in an action of contract, negligence, or other tortious action. January 4th, 1995 # end of file -- COPYING -- - - I am karlheg of deB-ORG. You will be freed. mailto:karlheg＠debian.org (Karl M. Hegbloom) Portland, OR USA Debian GNU Potato Linux 2.2 AMD K6-200(＠233) XEmacs-21.2beta ------------------------------ Date: 12 May 2000 17:11:09 +0200 From: Henning Makholm <henning(a)makholm.net> To: karlheg(a)debian.org (Karl M. Hegbloom), debian-legal(a)lists.debian.org Subject: Re: Is `ilisp' DFSG free? Message-ID: <yahitwjn6r6.fsf(a)freja.diku.dk> References: <200005121411.KAA10376(a)mixing.qc.dfo.ca> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Scripsit Peter S Galbraith <GalbraithP(a)dfo-mpo.gc.ca> > > Use and copying of this software and the preparation of derivative > > works based on this software are permitted > `copying' doesn't mean `redistribution', does it? "Copying" is the only thing you need permission for. Copyright does not imply that the author can prevent people from giving or selling legal copies to each other. > > o Permission is granted to manufacturers and distributors of > > lisp compilers and interpreters to include this software > > with their distribution. > Why is the above specified if everyone is allowed to redistribute > it? It seems to be a permission to redistribute the software under the license terms of the Lisp interpretation (which may bee less free than the license itself). - - Henning Makholm "Han råber og skriger, vakler ud på kørebanen og ind på fortorvet igen, hæver knytnæven mod en bil, hilser overmådigt venligt på en mor med barn, bryder ud i sang og stiller sig til sidst op og pisser i en port." ------------------------------ Date: Fri, 12 May 2000 10:11:22 -0400 From: Peter S Galbraith <GalbraithP(a)dfo-mpo.gc.ca> To: karlheg(a)debian.org (Karl M. Hegbloom) Cc: debian-legal(a)lists.debian.org Subject: Re: Is `ilisp' DFSG free? Message-Id: <200005121411.KAA10376(a)mixing.qc.dfo.ca> > Please advise. I am not subscribed, so Cc. > > Is this licence (from ilisp 5.10.1) DFSG free? > > > COPYING -- TERMS AND LICENSING AGREEMENT FOR ILISP > ----------------------------------------------------------------------------- [cut] > ILISP if freely redistributable. Eventually it may become part of GNU > Emacs and it will in that case comply with the GPL. > > For the time being we adopt the following licensing agreement. [cut] They say above `freely redistributable' but then say `we adopt the following licensing agreement', so that sentence becomes somewhat irrelevant (they don't talk much about redistribution in the license itself). > ----------------------------------------------------------------------------- > GENERAL LICENSE AGREEMENT AND LACK OF WARRANTY [cut `no-warranty' text] > Use and copying of this software and the preparation of derivative > works based on this software are permitted `copying' doesn't mean `redistribution', does it? > , so long as the following > conditions are met: [cut] > o No fees or compensation are charged for use, copies, or > access to this software. You may charge a nominal > distribution fee for the physical act of transferring a > copy, but you may not charge for the program itself. This is not strictly DFSG-compliant. The Artistic license gets away with by stating that the clause is not enforced by the copyright holder. > o Any work distributed or published that in whole or in part > contains or is a derivative of this software or any part > thereof is subject to the terms of this agreement. The > aggregation of another unrelated program with this software > or its derivative on a volume of storage or distribution > medium does not bring the other program under the scope > of these terms. Is the above permission to re-distribute? > o Permission is granted to manufacturers and distributors of > lisp compilers and interpreters to include this software > with their distribution. Why is the above specified if everyone is allowed to redistribute it? If only `manufacturers and distributors of lisp compilers and interpreters' are allowed to redistribute it, then it discriminates and is non-free. I find it unclear, and if it were me packaging it, it'd go in non-free. The no-sell clause is enough to put it into non-free, and the unclear permission on who is allowed to redistribute it might mean we're not allowed to include it even in non-free (surely not their intent, but perhaps the letter of their license). IANAL, my two-cents only, grain of salt, etc. - - Peter Galbraith, research scientist <GalbraithP(a)dfo-mpo.gc.ca> Maurice Lamontagne Institute, Department of Fisheries and Oceans Canada P.O. Box 1000, Mont-Joli Qc, G5H 3Z4 Canada. 418-775-0852 FAX: 775-0546 6623'rd GNU/Linux user at the Counter - http://counter.li.org/ ------------------------------ End of forwardMwEQjU Digest *************************** ------- End of forwarded message -------

2 participants
1 comments

Re: XEmacs/GTK does menus... 24 years, 6 months

Karl M. Hegbloom

>>>>> "William" == William M Perry <wmperry(a)aventail.com> writes: William> karlheg(a)bittersweet.inetarena.com (Karl M. Hegbloom) writes: >> Are you using `glade' to build the interface, Bill? William> Nope, but I plan on allowing you to call libglade from elisp, eventually. William> The generic representation of the UI that I plan on working on next week William> will be really close to a parsed glade file. >> `apt-get install glade' William> :) That doesn't work on FreeBSD Bummer. They're more than welcome to add it to their ports collection, I imagine... along with `dpkg' and `console-apt'.

1 participants
0 comments

[BUG] Crash after dumping XEmacs from CVS @ ~ 1PM AEST 2000/05/13 24 years, 6 months

Daniel Pittman

I still cannot successfully build an XEmacs, but following Ben Wing committing his changes to the error handling, I get a new stack trace. The build log and GDB stack trace is included. Daniel -- If a voice inside tells you that you are not a painter, then by all means paint! And that voice will be silenced... -- Vincent Van Gogh

1 participants
0 comments

xemacs-21.2-b33 vs. package x-symbol 24 years, 6 months

Richard Ketchersid

Latest couple of cvs xemacs-21.2-b33 don't like x-symbol. Unfortunately I like x-symbol. The cvs version of May 10 had no such problem. Fatal error: assertion failed, file /usr/src/CVS/xemacs/release-21-2/src/lisp.h, line 993, RECORD_TYPEP (obj, lrecord_type_vector) Fatal error (6). Your files have been auto-saved. Use `M-x recover-session' to recover them. If you have access to the PROBLEMS file that came with your version of XEmacs, please check to see if your crash is described there, as there may be a workaround available. Otherwise, please report this bug by running the send-pr script included with XEmacs, or selecting `Send Bug Report' from the help menu. As a last resort send ordinary email to `crashes(a)xemacs.org'. *MAKE SURE* to include the information in the command M-x describe-installation. If at all possible, *please* try to obtain a C stack backtrace; it will help us immensely in determining what went wrong. To do this, locate the core file that was produced as a result of this crash (it's usually called `core' and is located in the directory in which you started the editor, or maybe in your home directory), and type gdb /usr/local/share/xemacs/21.2/bin/xemacs-21.2 core then type `where' when the debugger prompt comes up. (If you don't have GDB on your system, you might have DBX, or XDB, or SDB. A similar procedure should work for all of these. Ask your system administrator if you need more help.) Lisp backtrace follows: # (unwind-protect ...) # (catch #<INTERNAL OBJECT (XEmacs bug?) (opaque-ptr, adr=0x8291a9c) 0x82ed8d0 > ...) # (unwind-protect ...) make-image-instance([xpm :file "/usr/local/share/xemacs/lib/xemacs/site-packag es/etc/x-symbol/colormap138.xpm"] nil nil t) # bind (value var) x-symbol-image-set-colormap(nil nil) # bind (arg) x-symbol-initialize() byte-code("..." [x-symbol-initialize nil x-symbol-all-charsyms x-symbol-init-c set x-symbol-latin1-cset x-symbol-latin1-fonts x-symbol-latin1-table x-symbol-la tin2-cset x-symbol-latin2-fonts x-symbol-latin2-table x-symbol-latin3-cset x-sym bol-latin3-fonts x-symbol-latin3-table x-symbol-latin5-cset x-symbol-latin5-font s x-symbol-latin5-table x-symbol-init-latin-decoding x-symbol-xsymb0-cset x-symb ol-xsymb0-fonts x-symbol-xsymb0-table x-symbol-xsymb1-cset x-symbol-xsymb1-fonts x-symbol-xsymb1-table] 4) # bind (current-load-list) # (unwind-protect ...) # bind (load-file-name) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) load-internal("x-symbol" nil nil nil binary) # bind (path handler filename nosuffix nomessage noerror file) load("x-symbol" nil nil nil) # (unwind-protect ...) (x-symbol-auto-coding-alist x-symbol-tex-auto-coding-alist 10000) ) eval((x-symbol-auto-coding-alist x-symbol-tex-auto-coding-alist 10000)) # bind (form symbol) x-symbol-auto-set-variable(x-symbol-coding (x-symbol-auto-coding-alist x-symbo l-tex-auto-coding-alist 10000)) # bind (old-mode values init arg) x-symbol-mode(nil) # bind (command-debug-status) call-interactively(x-symbol-mode) command-execute(x-symbol-mode t) # bind (_execute_command_keys_ _execute_command_name_ prefix-arg) execute-extended-command(nil) # bind (command-debug-status) call-interactively(execute-extended-command) # (condition-case ... . error) # (catch top-level ...) zsh: 7871 abort xemacs-21.2 hyp-test.tex

1 participants
0 comments

Re: Redisplay weirdness... No '^' in front of control chars? 24 years, 6 months

William M. Perry

Hrvoje Niksic <hniksic(a)iskon.hr> writes: > wmperry(a)aventail.com (William M. Perry) writes: > > > Does anybody have any idea why control characters would show up as > > their ASCII counterpart (ie 'L' instead of '^L')? > > Because the glyph handling is fucked up? The `^' arrow thing is a > glyph, controlled through `control-arrow-glyph'. AHA! So it would help if i set it to anything, right? That is one less thing to worry about. Thanks hrvoje! -bp

1 participants
0 comments

Re: fatal error handling 24 years, 6 months

Jan Vroonhof

Ben Wing <ben(a)666.com> writes: > + and DISABLES AUTO-SAVING ENTIRELY during crashes! Way way bad idea. > + > + Instead let's just be more intelligent about avoiding crashing > + when possible, esp. nested crashes. I think I like the new code for the assert() case. Especially given the fact you preserve the message if we crash in assert. I still think that for SIG_SEGV we really shouldn't be doing anything apart from printing the backtrace. Jan

1 participants
0 comments

Re: Redisplay weirdness... No '^' in front of control chars? 24 years, 6 months

Hrvoje Niksic

wmperry(a)aventail.com (William M. Perry) writes: > Does anybody have any idea why control characters would show up as > their ASCII counterpart (ie 'L' instead of '^L')? Because the glyph handling is fucked up? The `^' arrow thing is a glyph, controlled through `control-arrow-glyph'.

1 participants
0 comments

Redisplay weirdness... No '^' in front of control chars? 24 years, 6 months

William M. Perry

Does anybody have any idea why control characters would show up as their ASCII counterpart (ie 'L' instead of '^L')? I thought perhaps a display table was not being set up correctly, but that does not appear to be the case. -Bill P.

1 participants
0 comments

Re: XEmacs/GTK does menus... 24 years, 6 months

William M. Perry

karlheg(a)bittersweet.inetarena.com (Karl M. Hegbloom) writes: > >>>>> "William" == William M Perry <wmperry(a)aventail.com> writes: > > >> > Well, is the only reason for motion events while over the toolbar > >> > for tooltips? Those are handled natively by the GTK toolbar. > >> > >> Can you embed images in such tooltips? > > William> Ick! I should hope not. :) > > Ahhhwwww. :( I want a dancing paperclip, Bill! > > Hey, can you do the transparent / shaded XEmacs thing? That would be > pretty neat. I think it just looks for a Gnome specific property on the > root window that holds the pixmap. *shudder* I haven't started any GNOME integration yet... their menus and toolbar specifications suck, and wouldn't be usable in XEmacs. But some of their widgets would be useful. I doubt I'd spend time on the transparency stuff - there are important bugs to fix in either the GTK redisplay or XEmacs itself. :) -Bill P.

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 May 2000