April 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: [Success] 21.0 "Pygmy" XEmacs Lucid (beta37) on i586-pc-linux 27 years

Greg Klanderman

>>>>> "Larry" == Larry Ayers <layers(a)marktwain.net> writes: Larry> Larry> Patched from b36, egcs 1.02, libc5.4.44. Had to change some X Larry> resources from Emacs to XEmacs (background, foreground, and menu Larry> colors). Can you please explain? You should not have to switch to `XEmacs' resources; `Emacs' should still work, unless you already had some `XEmacs' resources. greg

2 participants
1 comments

Re: [Patch] Warnings in 21.0b37 27 years

Andreas Jaeger

>>>>> Hrvoje Niksic writes: Hrovje> "Kirill M. Katsnelson" <kkm(a)kis.ru> writes: >> Some time ago, Andreas Jaeger wrote... >> |+ >> | +++ src/specifier.c Sun Apr 26 14:45:24 1998 >> | >> | -/* #### The purpose of this is to check for inheritance loops >> | - in specifiers that can inherit from other specifiers, but it's >> | - not yet implemented. >> | - >> | - #### Look into this for 19.14. */ >> | -static Lisp_Object_dynarr current_specifiers; >> | - >> |- >> >> May we please have that in? It maybe a good idea to comment the >> declaration, not remove it. Comments about still unimplemented >> feature should not be removed, until we have strong evidence that >> this feature is not needed. Hrovje> I agree with Kirill. We should probably add an appropriate smiley Hrovje> near "Look into this for 19.14". I've misread this and thought it meant that it had been in 19.14 :-(. Ok, but what smiley should we add instead of removing the code? Andreas O-S-< -- Andreas Jaeger aj(a)arthur.rhein-neckar.de jaeger(a)informatik.uni-kl.de for pgp-key finger ajaeger(a)alma.student.uni-kl.de

1 participants
0 comments

bug in w3 27 years

Andy Piper

If I try and start w3 I get this failure: Signaling: (wrong-type-argument number-char-or-marker-p nil) +(nil 12) font-spatial-to-canonical("+12pt") css-expand-length("+12pt" t) css-expand-value(height "+12pt") css-parse-args(235 254) css-parse("file:/usr/gnu/lib/xemacs/packages/etc/w3/stylesheet" nil nil) w3-find-default-stylesheets() w3-refresh-stylesheets() w3-do-setup() #<compiled-function nil "...(68)" [w3-setup-done w3-do-setup w3-track-last-buffer bufferp w3-last-buffer buffer-name switch-to-buffer message "Reusing buffer. To reload, type %s." substitute-command-keys "\\[w3-reload-document]" w3-default-homepage call-interactively w3-fetch error "Invalid setting for w3-default-homepage: %S" string-match ".*:.*" "file:"] 4 ("/usr/gnu/lib/xemacs/packages/lisp/w3/w3.elc" . 29615) nil>() call-interactively(w3) command-execute(w3 t) execute-extended-command(nil) call-interactively(execute-extended-command) This is of course under cygwin so I guess font handling is not going to be the same - but some fix to at least let w3 run would be nice. andy

1 participants
0 comments

Package request 27 years

Andy Piper

Can JDE be made a package? (Java Development Environment) andy

1 participants
0 comments

Re: [PATCH] msw / toolbar cleanup 27 years

Andy Piper

<3.0.3.32.19980424101946.00a9d620(a)exchange.parallax.co.uk> > >At 02:37 PM 4/27/98 +0200, you wrote: >>Andy Piper <andyp(a)parallax.co.uk> writes: >> >>> + dnl check for our special version of select >>> AC_TRY_RUN([#include <fcntl.h> >>> int main() { return (open("/dev/windows", O_RDONLY, 0) > 0)? 0 : 1; }], >>> [AC_DEFINE(HAVE_MSG_SELECT)]) >>> const_is_losing=no >>> with_file_coding=yes >>> + use_minimal_tagbits=yes >>> + use_indexed_lrecord_implementation=yes >> >>Why is this here? I believe it is wrong to unconditionally define >>minimal tagbits and indexed lrecord implementation. > >Temporary fix until we can come up with another (better solution). Defining DATA_SEG_BITS does not apparently cut it. > >andy

1 participants
0 comments

Re: package bootstraping? 27 years

Andy Piper

At 12:50 PM 4/22/98 +0100, Adrian Aichner wrote: >I have experimented some with > >1. Downloading all packages in package-get-base (pgua.el) > >2. Downloading them asynchronously using EFS continuations > (package-get-async.el) This is cool! In case anybody is interested this is what I had to do: package-admin-add-binary-package <xemacs-base> package-admin-add-binary-package <mail-lib> package-admin-add-binary-package <efs> set efs variables to get through our firewall load-file package-get-async.el (There is a bug in this it needs to (provide 'package-get-async)) load-file pgua.el and away it goes. I notice that pgua.el gets packages that I already have installed which seems wrong IMHO. I look forward to the customize interface to packages it will make stuff a whole lot easier. andy

1 participants
0 comments

[Success - almost ] 21.0 "Pygmy" XEmacs Lucid (beta37) on i386- pc-cygwin32 27 years

Ian MacKinnon

Just the File->Open dialog not working as previously discussed ( window height too small) > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /usr/xemacs-21.0-b37/Installation: > (Output from most recent run of ./configure) uname -a: CYGWIN32_NT TECH007 4.0 19.1 i686 unknown ./configure XEmacs 21.0-b37 "Pygmy" configured for `i386-pc-cygwin32'. Where should the build process find the source code? /usr/xemacs-21.0-b37 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/cygwin32.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O2 -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? default What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11R6.3/include Where do we find X Windows libraries? /usr/X11R6.3/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for ncurses. Compiling in File coding support. Compiling in support for OffiX. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. movemail will use "dot-locking" for locking mail spool files. Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. 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: --------------------------------------------------------- > /usr/xemacs-21.0-b37/beta.err does not exist! --- Ian

1 participants
0 comments

package wierdness 27 years

Andy Piper

If I do C-h v late-packages, package-admin-add-binary-package then works, if I don't do this first then adding the binary package fails. If I add a binary package the path is not dynamically added to my load-path, thus I have to stop and restart XEmacs for package-admin-add-binary-package to take effect. This is a bug IMHO, how fixable I don't know. andy

1 participants
0 comments

Re: [PATCH] msw / toolbar cleanup 27 years

Hrvoje Niksic

Andy Piper <andyp(a)parallax.co.uk> writes: > + dnl check for our special version of select > AC_TRY_RUN([#include <fcntl.h> > int main() { return (open("/dev/windows", O_RDONLY, 0) > 0)? 0 : 1; }], > [AC_DEFINE(HAVE_MSG_SELECT)]) > const_is_losing=no > with_file_coding=yes > + use_minimal_tagbits=yes > + use_indexed_lrecord_implementation=yes Why is this here? I believe it is wrong to unconditionally define minimal tagbits and indexed lrecord implementation. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Then... his face does a complete change of expression. It goes from a "Vengeance is mine" expression, to a "What the fuck" blank look.

1 participants
0 comments

Re: Comparison between integer and character is constant nil (?\; and 0) 27 years

Hrvoje Niksic

SL Baur <steve(a)xemacs.org> writes: > More or less. The usual cause of an Ebola notice at the beginning or > end of a buffer is due to use of preceding-char and following-char. > Those functions return integer 0 at the boundary. Since they really > want to return something that cannot be a character, this is O.K. > Kind of yucky, but O.K. Well said -- "kind of yucky, but OK" summarizes it. The funny thing is that this {following,preceding}-char are now actually *safer* than they were in Emacs 19, where they would stop when encountering a ?\0 character! > In general, an Ebola notice of a comparison of a character and > integer 0 when generated from usage of preceding-char and > following-char is not Ebola and is safe usage. Exactly. > Yes. > > It is also _incorrect_ (and Ebola) to do something like (eq ?B (1+ > ?A)). Arithmetic on characters is allowed, but turns the characters > into integers. You would have to do (eq ?B (int-char (1+ ?A))) to > make it work right. (= ?B (1+ ?A)) will work, but it's dirty. Still, it is arguably cleaner than scattering the code with `int-char's. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- aibohphobia (ay' bo fo beeya): n. The fear of palindromes.

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