May 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Doing away with Installation.el 24 years, 11 months

Hrvoje Niksic

Adrian Aichner <aichner(a)ecf.teradyne.com> writes: > sorry to hear my patch is causing grief. I will try looking into > this tonight. Please don't get me wrong -- I don't blame you for breaking Unix build -- that's why we have CVS to test these things out before they make it to a release. > Is it OK if I do a possible patch against 21.2-b13? Please patch against the latest CVS sources; I've done more work on this since the message you responded to, including removal of `Installation.el'.

1 participants
0 comments

Re: Doing away with Installation.el 24 years, 11 months

Adrian Aichner

>>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes: Hrvoje, sorry to hear my patch is causing grief. I will try looking into this tonight. Is it OK if I do a possible patch against 21.2-b13? Regards, Adrian Hrvoje> As explained in my previous message, Installation.el can safely go Hrvoje> away by simply inserting the appropriate code elsewhere. Here is an Hrvoje> implementation of that idea. Hrvoje> NT people, could you please make `xemacs.mak' not generate Hrvoje> Installation.el? Hrvoje> top-level ChangeLog: Hrvoje> 1999-05-03 Hrvoje Niksic <hniksic(a)srce.hr> Hrvoje> * configure.in (xemacs_betaname): Don't generate Installation.el. Hrvoje> * Makefile.in.in (top_distclean): Don't remove Installation.el. Hrvoje> lisp/ChangeLog: Hrvoje> 1999-05-03 Hrvoje Niksic <hniksic(a)srce.hr> Hrvoje> * dumped-lisp.el (preloaded-file-list): Don't load Hrvoje> Installation.el. Hrvoje> * loadup.el (Installation-string): Define it here. Hrvoje> --- configure.in.orig Mon May 3 17:17:55 1999 Hrvoje> +++ configure.in Mon May 3 17:17:58 1999 Hrvoje> ＠＠ -4119,11 +4119,6 ＠＠ Hrvoje> dnl echo "The above configure report is appended to \"Installation\" file." Hrvoje> echo "" Hrvoje> -dnl Generate Installation.el Hrvoje> -echo '(setq Installation-string "' > Installation.el Hrvoje> -sed 's/"/\\"/g' Installation >> Installation.el Hrvoje> -echo '")' >> Installation.el Hrvoje> - Hrvoje> dnl ----------------------------------- Hrvoje> dnl Now generate config.h and Makefiles Hrvoje> dnl ----------------------------------- Hrvoje> --- lisp/dumped-lisp.el.orig Mon May 3 17:18:41 1999 Hrvoje> +++ lisp/dumped-lisp.el Mon May 3 17:18:43 1999 Hrvoje> ＠＠ -2,7 +2,6 ＠＠ Hrvoje> (assemble-list Hrvoje> "backquote" ; needed for defsubst etc. Hrvoje> "bytecomp-runtime" ; define defsubst Hrvoje> - "Installation.el" Hrvoje> "find-paths" Hrvoje> "packages" ; Bootstrap run-time lisp environment Hrvoje> "setup-paths" Hrvoje> --- lisp/loadup.el.orig Mon May 3 17:12:06 1999 Hrvoje> +++ lisp/loadup.el Mon May 3 17:15:47 1999 Hrvoje> ＠＠ -145,6 +145,11 ＠＠ Hrvoje> ;;; for the sake of the next call to precompute-menubar-bindings. Hrvoje> ;(setq define-key-rebound-commands nil) Hrvoje> +(defvar Installation-string Hrvoje> + (with-temp-buffer Hrvoje> + (insert-file-contents "../Installation") Hrvoje> + (buffer-string)) Hrvoje> + "Description of XEmacs installation.") Hrvoje> ;; Note: all compiled Lisp files loaded above this point Hrvoje> ;; must be among the ones parsed by make-docfile -- 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

How do I stop Backspace invoking help. 24 years, 11 months

Dan Glastonbury

Is it possible to make backspace not invoke C-h and not break either functionality?! When I want to use xemacs without a window, backspace invokes help which is annoying, 'cos I tend to bash on backspace quite a bit. So I tried adding (keyboard-translate ?\C-h ?\C-?) and backspace now deletes backwards. Yaa! But C-h doesn't invoke help anymore. Boo :(. What do I have to get this sorted out for tty emacsen, this problem doesn't exist for in a windowed frame (ie. non-tty). PS: I tried stty erase ^? in a shell before xemacs -nw, but backspace still invoked help. tia Dan -- Dan Glastonbury <Dan.Glastonbury at maptek.com.au> "Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe." -- Albert Einstein

2 participants
1 comments

keywordp 24 years, 11 months

Hrvoje Niksic

I wonder if `keywordp' should be changed to be a bit more intelligent. Currently, we have this: (keywordp (intern ":foo" [0])) => t I think the above should evaluate to nil. The code that performs the self-quoting stunts required for keywords actually checks that the symbols are interned to the global obarray. This is by design, so that the code that uses obarrays as hash-tables doesn't get tripped by having a key begin with a colon. Opinions?

3 participants
2 comments

XEmacs 21 crash 24 years, 11 months

Ben Moore

This bug report will be sent to the XEmacs Development Team, not to your local site managers!! Please write in English, because the XEmacs maintainers do not have translators to read other languages for them. In XEmacs 21.0 "20 minutes to Nikko" [Lucid] (sparc-sun-solaris2.5.1) of Fri Apr 9 1999 on brabham configured using `configure --prefix=/app_share/xemacs/21.0.67 --with-jpeg=no' Please describe exactly what actions triggered the bug and the precise symptoms of the bug: I was editing a gnats PR from within xemacs when the crash happened. It was about the 10th consecutive one I had done, ie there were no problems with the prior ones. No core file was produced since I have disabled this. Here is the info I have: uname -a: SunOS brabham 5.5.1 Generic_103640-24 sun4m sparc SUNW,SPARCstation-20 ./configure '--prefix=/app_share/xemacs/21.0.67' '--with-jpeg=no' XEmacs 21.0-b67 "20 minutes to Nikko" configured for `sparc-sun-solaris2.5.1'. Where should the build process find the source code? /app_share/xemacs/src/xemacs-21.0.67 What installation prefix should install use? /app_share/xemacs/21.0.67 What operating system and machine description files should XEmacs use? `s/sol2.h' and `m/sparc.h' What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes 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/dt/include /app/links/include Where do we find X Windows libraries? /usr/dt/lib /app/links/lib Runtime library search path: /usr/ccs/lib:/usr/dt/lib:/app/links/lib Compiling in support for XAUTH. Compiling in support for XPM images. -------------------------------------------------------------------- WARNING: Compiling without PNG image support. Reason: PNG library version and header file don't match! WARNING: You should strongly consider installing the PNG libraries. WARNING: Otherwise certain images and glyphs may not display. WARNING: (a copy may be found in ftp://ftp.xemacs.org/pub/xemacs/aux) -------------------------------------------------------------------- Compiling in support for (builtin) GIF image handling. Compiling in support for X-Face message headers. Compiling in native sound support. Compiling in support for DBM. Compiling in support for CDE. Compiling in support for ToolTalk. Compiling in EXPERIMENTAL support for Drag'n'Drop ( CDE ). Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. 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: --------------------------------------------------------- ulu~: Fatal error: assertion failed, file lstream.h, line 33, RECORD_TYPEP (_obj, lrecord_lstream) || MARKED_RECORD_P (_obj) Fatal error (6). Your files have been auto-saved. Use `M-x recover-session' to recover them. 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 /app_share/xemacs/21.0.67/bin/xemacs 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: process-send-region(#<process " *file-pr--125871145" pid 8092 state:exit> 1 3794) # bind (process-environment proc) # (unwind-protect ...) # bind (buf inbuf proc-name proc-action proc-send-buffer args filep outfile sentinel proctype pr) gnats::start-background("bondi/17154" file gnats::handle-file-pr) gnats::file-pr-background() # (unwind-protect ...) # bind (buf result pr event process) gnats::handle-check-pr(#<process " *check-pr--116856671" pid 8090 state:exit> "finished\n") # (condition-case ... . error) # bind (inhibit-quit) # (unwind-protect ...) # (condition-case ... . error) # (catch top-level ...) Recent keystrokes: Recent messages (most recent first): irrelevant since crash occurred

1 participants
0 comments

Re: cvs access for XEmacs 21.2.* 24 years, 11 months

Hrvoje Niksic

tor(a)spacetec.no (Tor Arntsen) writes: > On May 2, 21:36, Hrvoje Niksic wrote: > >This is quite strange -- it is customary for the unstable code to be > >HEAD, with the stable releases tagged as branches, so I hope it will > >be changed in the future. > > What practice to use varies wildly. By "customary" I meant "in use in other free software projects", at least those I know of. GNOME, for instance.

1 participants
0 comments

Re: cvs access for XEmacs 21.2.* 24 years, 11 months

Tor Arntsen

On May 2, 21:36, Hrvoje Niksic wrote: >This is quite strange -- it is customary for the unstable code to be >HEAD, with the stable releases tagged as branches, so I hope it will >be changed in the future. What practice to use varies wildly. I have worked with main trunk as the stable, branch as stable, as well as main and branches as development and special branch as stable (staged development). I wouldn't say one approach is that much better than any other, it all depends. It can all be good. In general I slightly prefer the branch-as- stable approach though, but as I said it all depends (on a lot of things). - Tor

1 participants
0 comments

inconsistency in iso-acc.el 24 years, 11 months

Tudor Hulubei

Hi, The following 3 lines should be added to iso-acc.el in the "latin-2" mapping in order to fix an inconsistency in the way characters with a cedilla under them are inserted. The affected characters are the romanian "s" and "t" (with a cedilla). Currently, these characters can be inserted by prefixing them with a backquote, even though they should be prefixed with a comma, just like the french "c" with a cedilla is. (?, (?S . ?\252) (?T . ?\336) (?s . ?\272) (?t . ?\376) (?\ . ?,)) I would suggest leaving the backquote based sequences in place, for those people who already got used to them. Tudor

1 participants
0 comments

Re: cvs access for XEmacs 21.2.* 24 years, 11 months

Tor Arntsen

On May 2, 20:41, Petr Konecny wrote: >are the 21.2 releases of XEmacs available through cvs ? > >The announcements indicate they are. I was able to get only 21.0.67 >though. update -r release-21-2 should give you 21.2 (use cvs status -v <file> to find what branches are available) - Tor

1 participants
0 comments

Re: cvs access for XEmacs 21.2.* 24 years, 11 months

Hrvoje Niksic

Petr Konecny <pekon(a)informatics.muni.cz> writes: > are the 21.2 releases of XEmacs available through cvs ? Yes, but you have to use the `-r release-21-2' flag when checking out. For instance: cvs checkout -r release-21-2 This is quite strange -- it is customary for the unstable code to be HEAD, with the stable releases tagged as branches, so I hope it will be changed in the future.

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 1999