May 1999 - XEmacs-Beta - XEmacs Mailing List Archives

[21.0b62] mouse copy and paste on NT4.0 26 years, 1 month

Roger Wimmer

Hi I have built Xemacs 21.0b62 on NT 4.0. All works fine except the mouse binding. I can highlight a region with the left button of the mouse. But if i try to paste the selection with the middle button, nothing appears in the buffer. But I have the following error message in the minibuffer: "Kill ring is empty" When I use C-Insert after highlighting the region, paste with the middle button works fine. How can I change that the highlighted region is in the kill ring? Roger -- Lieber wenige Programme die laufen als viele die abstuerzen! (Ein gluecklicher SUN-user ;-) Aber zuhause hat man ja Zeit zum Basteln.

2 participants
1 comments

[21.1.2] Problems running dumped xemacs on hppa1.1-hp-hpux10.20 26 years, 1 month

Justin Vallon

I'm trying to build 21.1.2 on HP using HP's cc. xemacs gets dumped. However, when src/xemacs is first run (as part of lisp shadows), it hangs, and can't be interrupted, killed, or kill -9'ed. If I run it from gdb (gdb ./xemacs CR run), it works. If I use dde: (Warning) Object file "/var/tmp/vallon/public/xemacs-21.1/xemacs-21.1.2/src/xemacs" has no debug information. Limited debugging will be available. (Warning) end.o has not been linked in. Cannot read from virtual address 7B0394DC of process 0. ...and the debugger is left in an unloaded state. xdb is able to load the executable, and it starts in main (no source code, though due to -O), but "cont" hangs. Neither gdb nor dde are able to attach to the hung xemacs. I found some 21.0 build successes for HPUX 10.20. Are there any later successes? Is the "Should XEmacs use the GNU version of malloc?" ok to be yes, if using the native compiler? Anything else to try? I guess I can try downgrading until it works. Here's Installation: uname -a: HP-UX pearl B.10.20 A 9000/778 2014301313 two-user license ./configure '--compiler' 'cc' '--cflags=-O +Onolimit' '--with-gnu-make' XEmacs 21.1-p2 "20 Minutes to Nikko" configured for `hppa1.1-hp-hpux10.20'. Where should the build process find the source code? /a/vallon/public/xemacs-21.1/xemacs-21.1.2 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/hpux10.h' and `m/hp800.h' What compiler should XEmacs be built with? cc -O +Onolimit 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/contrib/X11R6/include Where do we find X Windows libraries? /usr/dt/lib /usr/lib/X11R6 /usr/contrib/X11R6/lib -------------------------------------------------------------------- WARNING: Compiling without XPM support. WARNING: You should strongly consider installing XPM. WARNING: Otherwise toolbars and other graphics will look suboptimal. WARNING: (a copy may be found in ftp://ftp.xemacs.org/pub/xemacs/aux) -------------------------------------------------------------------- -------------------------------------------------------------------- WARNING: Compiling without PNG image support. 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 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. -Justin vallon(a)mindspring.com

1 participants
0 comments

Re: Major select rationalisation [21.2] 26 years, 1 month

Norbert Koch

Andy Piper <andy(a)xemacs.org> writes: > Well its taken longer than I though but I have finally finished > rationalising select so that the windows behaviour is much more like the X > behaviour. I have generalised much of the code so that there is virtually > no duplication. All the selection converter stuff now works for mswindows. > Next the font-menu .... > > I will apply this to cvs. > * select-msw.c (mswindows_own_selection): new device method to set > the clipboard when we 'own' the selection. > (mswindows_get_foreign_selection): new device method to get the > clipboard. > (mswindows_disown_selection): new device method to delete the > selection when we 'disown' it. > (console_type_create_select_mswindows): new function. Hi, it's possible, I've missed something here, but after applying these changes, I'm no longer able to build XEmacs 21.2 native on NT due to some unresolved symbols: [...] select-msw.obj : error LNK2001: unresolved external symbol _get_local_selection select-msw.obj : error LNK2001: unresolved external symbol _QSTRING emacs.obj : error LNK2001: unresolved external symbol _vars_of_select emacs.obj : error LNK2001: unresolved external symbol _syms_of_select ..\nt\temacs.exe : fatal error LNK1120: 4 unresolved externals NMAKE : fatal error U1077: 'link.exe' : return code '0x460' Stop. I've tried to remove the xselect parts of my makefile, since a makedepend doesn't work, but to no avail. Any leads? TIA, norbert.

2 participants
1 comments

Re: [PATCH] 21.1.2: fix "file has changed on disk" problem on Linux 26 years, 1 month

Jan Vroonhof

Kyle Jones <kyle_jones(a)wonderworks.com> writes: > been done. Under some extant versions of Linux this loses because > the file modtime can be changed when the file is closed. Isn't this a general nfs problem anyway? However, I am getiing a deja vu feeling here. Either we already discussed his a while ago but the change was never made _or_ the behaviour was intentionally changed to be this way. Cannot test the patch here as I am too far away from a test machine now. -- Jan Vroonhof http://www.math.ethz.ch/~vroonhof/ Mathematik, vroonhof ＠ math.ethz.ch HG E16, ETH-Zentrum, Tel: +41-1-6325456/25154 Raemistrasse 101, CH-8092 Zuerich. Fax: +41-1-6321085

3 participants
2 comments

Build failure for CVS 21.2 of 19990531 (with mule) 26 years, 1 month

Daniel Pittman

Hi. Trying to build the latest XEmacs 21.2 from CVS fails for me when --with-mule is used. The same configure sans mule works fine. Suggestions? Daniel System details: * Debian unstable * i586 architecture * kernel 2.2.6 * glibc 2.1.1 final * egcs 2.91.66 (1.1.2) * X11R6, by XFree86 3.3.3.1 Attached is a log of the failed build.

1 participants
0 comments

Re: open parts 26 years, 1 month

SL Baur

Hrvoje Niksic <hniksic(a)srce.hr> writes in xemacs-beta(a)xemacs.org: ... > Both points really boil down to the need of someone shaking the dust > off it. We've discussed this at the symposium, and the general > conclusion was that nobody ;; except Colin Rafferty :-) > knows how external widget support really works. ... and Colin has promised to supply a simple example so that we can more easily test it out. -- I protest the NATO war in Yugoslavia.

1 participants
0 comments

Re: Terminology 26 years, 1 month

SL Baur

Charles G Waldman <cgw(a)fnal.gov> writes in xemacs-beta(a)xemacs.org: > How come it's M-x remove-directory to get rid of a directory, but > M-x delete-file to do the same thing to a file? > Just wondering... It must be to confuse people. All the file functions are named without rhyme or reason. -- I protest the NATO war in Yugoslavia.

1 participants
0 comments

Re: [Wolfram Gloger <wmglo@dent.med.uni-muenchen.de>] more on the emacs-20.3 segfault 26 years, 1 month

SL Baur

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes in xemacs-beta(a)xemacs.org: > That's probably 21.1p2. The reason you don't see it is that on > glibc2.x systems XEmacs uses the system malloc instead of its own doug > lea allocator. The main reason for this is that we don't run into > obscure and hard to debug problems like this. The Doug Lea or "new GNU malloc" is the system malloc when using glibc or Linux libc5; it has not been cloned into the XEmacs core. The so-called "new GNU malloc" in XEmacs is really the old GNU malloc, and the "old GNU malloc" in XEmacs is really the very-old GNU malloc. >> Nevertheless the patch looks fine (I'm just running a mule-enabled >> XEmacs 21.0p2 with it) and should work with glibc 2.0 and 2.1 (I only >> tested with glibc 2.1.1). >> From glancing at the patch in its current incarnation, > it seems awfully glibc specific to me. If I understand it correctly. > It works because the glibc startup code works by calling this hook > somewhere. > Who says the Solaris startup code will do that? All Doug Lea malloc related stuff is guarded by ifdefs and are only enabled if configure detects the presence of it. It should be absolutely safe to apply the patch and it is better than voodoo_free_hook. -- I protest the NATO war in Yugoslavia.

1 participants
0 comments

Re: [Wolfram Gloger <wmglo@dent.med.uni-muenchen.de>] more on the emacs-20.3 segfault 26 years, 1 month

SL Baur

Andreas Jaeger <aj(a)arthur.rhein-neckar.de> writes in xemacs-beta(a)xemacs.org: ... > I did send the patch for discussion and further testing and thought > the information in it might become relevant. Looking at Wolfram's > analysis of the situation, XEmacs should segfault the same way as > FSF-Emacs does --- but AFAIK it doesn't. It did, but I worked around it, I believe. Check out voodoo_free_hook in emacs.c ... Also, look through your old glibc email archives. I emailed you about this in March of 1998. 1998-03-29 SL Baur <steve(a)altair.xemacs.org> * emacs.c (voodoo_free_hook): ELF libraries built with newer versions of GCC do horrible things in dumped binaries after exit() is called. (Fkill_emacs): Use it. > Either the analysis is wrong, we're just lucky with XEmacs or XEmacs > is just better;-). The patch looks O.K. and Wolfram's analysis is correct. I no longer have access to the machine where XEmacs crashed 100% of the time at exit due to a double free, but hopefully I can duplicate it on a different machine and verify that this fixes the problem without voodoo_free_hook and turning off free at exit(3) time. -- I protest the NATO war in Yugoslavia.

1 participants
0 comments

Inserting a string extent with a glyph in a buffer 26 years, 1 month

Oscar Figueiredo

When I do the following in 21.2 Demeter, (setq mystr " ") " " (setq myext (make-extent 1 1 mystr)) #<extent [1, 1) 0x873a124 in string " "> (set-extent-property myext 'duplicable t) t (set-extent-begin-glyph myext (make-glyph (vector 'jpeg :data jpegdata))) #<glyph (buffer) #<image-specifier global=(((x) . [jpeg :data "ÿØÿà

2 participants
1 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 May 1999