April 1998 - XEmacs-Beta - XEmacs Mailing List Archives

[OK] 21.0 "Pygmy" XEmacs Lucid (beta37) on sparc-sun-solaris2.5.1 26 years

Raymond Toy

Built from full tarballs and the most recent set of packages. Looks good so far. I do have a couple of problems, but not related to the build. Another message for that. Ray > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /apps/public/XEmacs/Beta/src/xemacs-21.0-b37/Installation: > (Output from most recent run of ./configure)

1 participants
0 comments

Re: select-window focus problem [was: Re: minor compile.el bug] 26 years

Hrvoje Niksic

greg(a)alphatech.com (Greg Klanderman) writes: > Hrvoje> I want `C-x 5 o' to behave the same regardless of > Hrvoje> focus-follows-mouse. The reason for this is that `C-x 5 o' is an > Hrvoje> interactive command. If I press 3 keystrokes for something to happen, > Hrvoje> I expect it to happen, not to be silently ignored. > > Binding f-f-m to nil within other-frame when called interactively > works. Are there other commands that need this? I can't think of many commands that need this kind of intervention. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- What is mind? No matter. What is matter? Never mind.

1 participants
0 comments

Re: select-window focus problem [was: Re: minor compile.el bug] 26 years

SL Baur

Greg Klanderman <greg(a)alphatech.com> writes: > Steve, could you explain what benefit f-f-m added prior to my patch? Prior to adding the variable and the code controlled by that variable really evil stuff happened. Any new frame command (C-x 5 ...) threw keyboard focus to the new frame regardless of whether the frame was visible (at that time one could end up with keyboard focus on a frame in another virtual desktop) and whether the frame was underneath the mouse. > I don't see how it did anything but allow emacs and window manager > focus to be on different frames. No. The opposite actually. It was intended for emacs to never override the window manager.

1 participants
0 comments

Re: select-window focus problem [was: Re: minor compile.el bug] 26 years

SL Baur

Greg Klanderman <greg(a)alphatech.com> writes: > The right thing with f-f-m true seems for C-x 5 o to physically move > the mouse pointer, a la ediff. Aargh. That's mouse warping. We should *never* warp the mouse. It is strictly under control of the user. Hrvoje> BTW, are you aware that FSF 20.3 sets focus-follows-mouse to t by Hrvoje> default? Maybe we should copy what they do? > Copy the default value, or behavior of C-x 5 o? > What do they do for C-x 5 o? Good question.

1 participants
0 comments

Re: [patch] Fix for image related memory corruption 26 years

SL Baur

P E Jareth Hein <jareth(a)camelot-soft.com> writes: > Okay, I jumped the gun a bit with my last patch. Apply this one > instead and things should work fine. > 1998-04-28 P. E. Jareth Hein <jareth(a)camelot-soft.com> > * glyphs-x.c : slight cleanup and bugfix related to memory > corruption and possible leaks. Also fix a visual problem > with XPM pointers That works for me. Patch applied, thanks.

1 participants
0 comments

b37 FAIL 26 years

Georg Nikodym

As you may know, I cannot run with file-coding. Now, I cannot link without it: Undefined first referenced symbol in file lrecord_coding_system glyphs-eimage.o convert_to_external_format glyphs-eimage.o ld: fatal: Symbol referencing errors. No output written to temacs Installation file attached. P.S. For those that are curious, I almost have a 64 bit XEmacs. The temacs dumps core in image_instatiate, which I suspect is due XEmacs not working anymore without XPM... I'm gonna build a 64bit XPM lib and test that hypothesis... uname -a: SunOS verve 5.7 on998-gate:04/27/98 sun4u sparc SUNW,Ultra-30 ../configure '--extra-verbose' '--compiler=/opcom/on998-tools/SUNWspro/SC5.x/bin/cc' '--with-gcc=no' '--with-gnu-make' '--cflags=-g -xarch=v8plusa' '--site-includes=/ot/misc_includes' '--site-libraries=/ot/misc_libs_dynamic /ot/misc_libs_static' '--dynamic=yes' '--srcdir=/import/verve/georgn/xemacs/xemacs-21.0-b37' '--const-is-losing=no' '--prefix=/ot/XEmacs_common' '--exec-prefix=/ot/XEmacs/21.0' '--with-x' '--with-menubars=lucid' '--with-scrollbars=motif' '--with-dialogs=motif' '--with-cde' '--with-xpm' '--with-xface' '--with-tooltalk' '--with-workshop' '--with-database=dbm' '--with-sound=native' '--debug=yes' '--error-checking=all' '--memory-usage-stats' '--use-union-type' '--rel-alloc' '--gung-ho' '--with-mule=no' '--package-path=/import/verve/georgn/xemacs/site-packages::/import/verve/georgn/xemacs/xemacs-21.0/packages' '--infopath=/import/verve/georgn/xemacs/xemacs-21.0/packages/info:/ot/lib/info:/ot/gnu_shared/info' XEmacs 21.0-b37 "Pygmy" configured for `sparc-sun-solaris2.7'. Where should the build process find the source code? /import/verve/georgn/xemacs/xemacs-21.0-b37 What installation prefix should install use? /ot/XEmacs_common What operating system and machine description files should XEmacs use? `s/sol2.h' and `m/sparc.h' What compiler should XEmacs be built with? /opcom/on998-tools/SUNWspro/SC5.x/bin/cc -g -xarch=v8plusa 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 /usr/openwin/include Where do we find X Windows libraries? /usr/dt/lib /usr/openwin/lib Additional header files: /ot/misc_includes Additional libraries: /ot/misc_libs_dynamic /ot/misc_libs_static Runtime library search path: /ot/misc_libs_dynamic:/usr/ccs/lib:/usr/dt/lib:/usr/openwin/lib:/opt/SUNWdt/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for X-Face message headers. Compiling in support for JPEG image conversion. Compiling in support for PNG image conversion. Compiling in native sound support. Compiling in support for DBM. Compiling in support for CDE. Compiling in support for ToolTalk. Compiling in support for OffiX. Compiling in support for Sun WorkShop. Compiling in support for proper session-management. Using Lucid menubars. Using Motif scrollbars. Using Motif dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Using the union type for Lisp_Objects. 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: ---------------------------------------------------------

1 participants
0 comments

Re: stupid question... 26 years

Jens Lautenbacher

SL Baur <steve(a)xemacs.org> writes: > Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes: > > >>>>>> "Jens" == Jens Lautenbacher <jens(a)tellux.de> writes: > Jens> Sorry if this is a faq or plain stupid, but I simply seem to > Jens> be unable to get an xemacs-21 beta working... > > > I'm not all that surprised; the install process is in flux, big-time > > right now, especially with respect to packages. > > Hopefully things will be slowing down now. The mechanics of it all > are working quite well based on the testing I've been doing of it. > > Jens> After a long time I want to again work a bit with xemacs, > Jens> and so I decided to get a new package enabled xemacs-21. I > Jens> downloadded the cvs xemacs-20 and xemacs-packages. > > CVS'ing packages is the hard way. Download the `binary' tarballs from > the FTP site for a first installation. Figure out where your packages > should be ($prefix/lib/xemacs/packages, $prefix/lib/xemacs/mule-packages) > and untar the packages you want there. OK, with Stephen's help I got it going.... My problem was that I didn't realize that under the package hirarchy there's only one etc, lisp and info dir allowed... I was under the impression that a link to the cvs tree of xemacs-packages from (refix)/lib/xemacs/packages would be enough... It was a bit stupid to realize how to install of the compiled lisp from the cvs tree there without doing too much work by hand, but a make bindist with the directory redirected to the packages dir helped... I simply ditched the tar files after that :-) Maybe it would help to have the information somewhere HOW the packages tree is supposed to look (or is it somewhere?). Or something in the cvs tree for those people who want to go that way. jtl

1 participants
0 comments

Re: select-window focus problem [was: Re: minor compile.el bug] 26 years

Greg Klanderman

>> What'd it do prior to my patch? I assume it threw emacs focus, but >> not the window manager focus. Checking.... yup. I assume that's not >> what you want? Or is it? Hrvoje> Hrvoje> It's not what I want. Hrvoje> Hrvoje> I want `C-x 5 o' to behave the same regardless of Hrvoje> focus-follows-mouse. The reason for this is that `C-x 5 o' is an Hrvoje> interactive command. If I press 3 keystrokes for something to happen, Hrvoje> I expect it to happen, not to be silently ignored. Binding f-f-m to nil within other-frame when called interactively works. Are there other commands that need this? Hrvoje> BTW, are you aware that FSF 20.3 sets focus-follows-mouse to t by Hrvoje> default? Maybe we should copy what they do? >> >> Copy the default value, or behavior of C-x 5 o? Hrvoje> Hrvoje> The former, sounds good Hrvoje> and maybe the latter. I'm not sure what `C-x 5 o' does Hrvoje> under FSF with focus-follows-mouse set to t, but I'm fairly certain it Hrvoje> is not ignored. could someone check?

1 participants
0 comments

Re: select-window focus problem [was: Re: minor compile.el bug] 26 years

Greg Klanderman

>>>>> "Peter" == Peter Ware <ware(a)nowlab.cis.ohio-state.edu> writes: Peter> Peter> Make sure you read the X stuff on input focus! Can you be more specific? I don't know a lot about X. Peter> It is perfectly Peter> reasonable for the user to be using focus-follows-mouse window manager Peter> policy but for an application to shift the focus to another of its Peter> windows (aka ^X-5-o should work). I'm convinced of this and think I know the right solution. Peter> Then think about what the emacs Peter> variable focus-follows-mouse is supposed to do. Peter> Peter> My window manager policy is focus follows mouse (I hate click to Peter> focus) and I have focus-follows-mouse set to nil -- it all works the Peter> way it is supposed to. Try setting (setq special-display-buffer-names '(("*compilation*" . ((name . "Compile"))) ("*grep*" . ((name . "Grep"))))) and doing a compile or grep. Or maybe you want to have focus switched to the compile frame? With f-f-m true, prior to my patch, you get the same behavior, but the WM focus remains on the original frame. Peter> I remember much discussion about this a year Peter> or two ago. I wouldn't mind seeing that. I do vaguely recall it, I had just joined the list and was rather overwhelmed with other stuff. Steve, could you explain what benefit f-f-m added prior to my patch? I don't see how it did anything but allow emacs and window manager focus to be on different frames. greg

1 participants
0 comments

Re: [crash] Internal emacs bug. 26 years

Jason R Mastaler

My XEmacs crashed as well shortly after viewing Karl's message. This is the first XEmacs crash I've had since v19.13 :-( No core dump, just the following in my console window. I've been using libpng-1.0.1 for a while now. xemacs-beta: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 88 (X_FreeColors) Value in failed request: 0x2401523a Serial number of failed request: 710774 Current serial number in output stream: 710774 xemacs-beta: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 136 () Minor opcode of failed request: 107 Serial number of failed request: 710775 Current serial number in output stream: 710774 xemacs-beta: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 248 () Minor opcode of failed request: 0 Serial number of failed request: 710776 Current serial number in output stream: 710774 xemacs-beta: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 240 () Minor opcode of failed request: 0 Serial number of failed request: 710777 Current serial number in output stream: 710774 xemacs-beta: Fatal I/O Error 14 (Bad address) on display connection ":0.0" after 710774 requests (710777 known processed) with 2 events remaining.

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