April 1998 - XEmacs-Beta - XEmacs Mailing List Archives

[SUCCESS] 21.0 "Pygmy-pre1" XEmacs Lucid (beta37) on i586-pc-linux 26 years

Robin S. Socha

Works smoothly... > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /usr/src/SOURCES/XEmacs/xemacs-20.0/Installation: > (Output from most recent run of ./configure)

1 participants
0 comments

Majordomo sucks? 26 years

Kirill M. Katsnelson

I got back my last message in 1 hour 45 minutes... Is this unbeatable? Kirill

1 participants
0 comments

[PATCH] cygwin reversed .exe sections under egcs 26 years

Andy Piper

Not as much requested as Kirill's process patch but getting close ... andy Thu Apr 23 19:38:19 1998 Andy Piper <andyp(a)parallax.co.uk> * unexcw.c: cope with the reversed executable sections written by binutils-2.9 ld and egcs.

1 participants
0 comments

[Success] 21.0 "Pygmy-pre1" XEmacs Lucid (beta37) on i586-pc-linux 26 years

Karl M. Hegbloom

When I try to close the editor, with `C-x C-c', it doesn't close. I have to push `C-g', and then `C-x C-c' a second time to make it close. Has anyone else seen this? It doesn't happen with `-vanilla'. > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /usr/local/src/XEmacs/xemacs-21-b37/Installation: > (Output from most recent run of ./configure)

1 participants
0 comments

[Success] 21.0 "Pygmy-pre1" XEmacs Lucid (beta37) on i386-pc-cyg win32 26 years

Michael Hill

With Andy's patch. 'make install' succeeds this time. The toolbar buttons are horizontally squished into the left third of the window. Selecting file handling commands from toolbar or menubar still fails with 'Window height 1 too small (after splitting)', the same as b36 (20 April build report). When I run Debug On Error, the backtrace still comes up in the file dialog box. On Monday I neglected to mention then that the dialog box is split, with the scratch message in the top half, and the backtrace in the bottom half. Today the only difference is that the phantom toolbar in the dialog box is gone. Mike > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /binary/xemacs-21.0-b36/Installation: > (Output from most recent run of ./configure) uname -a: CYGWIN32_NT DILBERT 4.0 19.1 i686 unknown ./configure '--gung-ho' XEmacs 21.0-b37 "Pygmy-pre1" configured for `i386-pc-cygwin32'. Where should the build process find the source code? /binary/xemacs-21.0-b36 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: --------------------------------------------------------- > /binary/xemacs-21.0-b36/beta.err does not exist!

1 participants
0 comments

[Success] 21.0 "Pygmy-pre1" XEmacs Lucid (beta37) on i586-pc-linux 26 years

Kai Haberzettl

No problems. > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /usr/src/packages/xemacs/xemacs-21.0-b35/Installation: > (Output from most recent run of ./configure)

1 participants
0 comments

Re: dlopen in SunOS 26 years

William M. Perry

"Amir J. Katz" <amir(a)ndsoft.com> writes: > Pardon my ignorance, but here are 2 silly questions: > > 1. When dlopen and friends are available, what are they used for in xemacs? > With mule-less xemacs, the only library I see is liblw. The rest > of the objects are linked in. They are used to dynamically load C-level lisp primitives into a running XEmacs. Check out the xemacs-20/modules/ directory. > 2. Assuming that I do choose to use dlopen, can it be done on SunOS? > dlopen works just fine on good old SunOS. It should work fine. -Bill P.

1 participants
0 comments

Re: [PATCH] Some toolbar fixes. 26 years

Andy Piper

The bottom of the images is now cut off by about 1 pixel. I guess if the annoying top margin wasn't there would pan out ok, but I couldn't get rid of the top margin.... andy

2 participants
3 comments

Re: objectives for 21.0? 26 years

Didier Verna

Marcus Thiessel <thiessel(a)hpbbse.bbn.hp.com> writes: > The current beta appears to be slow concerning pulldown menus > (compared to the 20.4 release). This is even true if I increase the > optimize level. 'makes me remember a thread concerning the fact that menu filters should be invoked when the menu is about to be entered and not only when traversing the cascade button (CF. the time it takes to build the fonts menu). Is there news about it ? -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C214 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 80 72 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

1 participants
0 comments

Re: Buffer local additions for font-lock? 26 years

Raymond Toy

Christoph Wedler <wedler(a)fmi.uni-passau.de> writes: > >>>>>"RT" == Raymond Toy <toy(a)rtp.ericsson.se> writes: > > RT> What I would like is some way of adding additional items to the > RT> font-lock-keywords. Why? I want to have file-local entries like > RT> typedefs that get font-locked appropriately. You know, things like > RT> size_t, ptr_diff_t, and whatever other type I might have should get > RT> highlighted. > > FSFmacs-20.2's font-lock has `c-font-lock-extra-types' (same for C++). > Use the corresponding entries with the form (eval . FORM), see > `font-lock-keywords'. > > RT> I supposed I could just append the new patterns to > RT> font-lock-keywords, but that requires eval in the file-local > RT> variables section. Uncool, perhaps. > > If there is such a variable, it should be a 'risky-local-variable since > you can include any code. > > RT> Maybe a buffer-local variable, say, font-lock-local, that contains > RT> additional patterns to be matched. Would probably need to modify > RT> font-lock a bit so that it knows about this variable. > > The concept of `font-lock-fontify-region-function' in FSFmacs-20.2 is > more general. Based on this comment and the comment of others, it seems that FSFmacs-20.2 has what I want. Unfortunately, as soon as XEmacs had tty support, I blew away my copy of FSFmacs and never looked back.... Well, except for OS/2 and now NT, but NT will have XEmacs, so I'm going to blow away emacs there too. Just need an OS/2 version now (doable with the XFree86 OS/2?). :-) Ray

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