May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: [COMMENTS?] Re: DND for XEmacs 21 26 years, 6 months

Oliver Graf

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > Oliver Graf <ograf(a)fga.de> writes: > > > associations (as in hm--html-mode, internal-drag-and-drop, idd), or > > should I use a function, where the programmer/user of the mode can > > do whatever he wants (plus a set of standart functions defined in > > dragdrop.el)? > > I would go for a list of functions, running them one by one until the > first one returns t. And if the extent specific funtions don't return > nil, you try the buffer-local functions, etc etc. Yup, this one sounds good to me. Regards, Oliver.

1 participants
0 comments

Re: Mule & Thai 26 years, 6 months

SL Baur

Jeff Miller <jmiller(a)smart.net> writes: > Folks, > Someone where i work is interested in using XEmacs w/Mule to read Thai > encoded files. > I see that thai support was removed from XEmacs around January or so, > apparently it was broken. > I'd like to help him use XEmacs to read his Thai files, but I know > little about coding systems, thai, etc, but I'm willing to try to hack a > bit on it. Cool. > I see Emacs 20.2 apparently has thai support, how close are their > language/thai*.el files to our old ones? How hard is it to port them to > what our mule expects? You'll have to port the CCL stuffs. There might also be some C code changes required. I have no idea how hard this might be. Until certain changes (I have no idea what, unfortunately) are made I cannot help as any attempt to view Thai in XEmacs crashes my X server. :-( > I can't find the old ones that were removed, to do any comparision. If > anyone has them, could they send them, please? I've restored the last versions that were in 20.3 betas before they were removed.

3 participants
2 comments

Re: [COMMENTS?] Re: DND for XEmacs 21 26 years, 6 months

Jan Vroonhof

Oliver Graf <ograf(a)fga.de> writes: > associations (as in hm--html-mode, internal-drag-and-drop, idd), or > should I use a function, where the programmer/user of the mode can > do whatever he wants (plus a set of standart functions defined in > dragdrop.el)? I would go for a list of functions, running them one by one until the first one returns t. And if the extent specific funtions don't return nil, you try the buffer-local functions, etc etc. Jan

1 participants
0 comments

Re: DND for XEmacs 21 26 years, 6 months

Oliver Graf

Jonathan Harris <jhar(a)tardis.ed.ac.uk> writes: > > | The button and modifier state is > > | ignored for file drops. > > > > Not exactly. They may have the same meaning for drop targets which are > > file containers. What does dropping a file on a dired buffer mean? > > But for a filemanager dnd the target app (ie XEmacs) can't pass any > information about the state of the modifiers to the source app (ie the > filemanager), so one can't implement the usual Move/Copy semantics for > even if one wanted to. Or am I missing something. This is a problem of the low-level protocol. If it has no ability to tell the source of the drop if the destination has the data of such a move operation, then the source has a problem (kill it or leave it...). This is for example a problem of OffiX. It throws the data whereever the user releases the button, no matter if there is someone who catchs the stuff. Xdnd on the other hand knows if the destination can handle the drop. Regards, Oliver.

1 participants
0 comments

Re: [OK] 21.0 "Repartida" XEmacs Lucid (beta38) on i586-pc-linux 26 years, 6 months

SL Baur

Glynn Clements <glynn(a)sensei.co.uk> writes: > Larry Ayers wrote: >> consistently fail if png support is enabled. This is the error >> message: >> >> glyphs-eimage.o: In function `png_instantiate': >> glyphs-eimage.o(.text+0x663): undefined reference to `png_set_strip_alpha' >> glyphs-eimage.o(.text+0x676): undefined reference to `png_get_valid' >> glyphs-eimage.o(.text+0x691): undefined reference to `png_set_strip_alpha' >> glyphs-eimage.o(.text+0x6f6): undefined reference to `png_get_bKGD' >> collect2: ld returned 1 exit status >> make[1]: *** [temacs] Error 1 >> make: *** [dump-elcs] Error 2 >> >> Is the newer libpng incompatible with XEmacs? No. It is preferred as it fixes some problems in the beta PNGs. The color problem I was reporting recently was actually due to using a too-old libpng and was fixed by upgrading. > IIRC, you need 0.96 (libpng.so.0.96). There is a problem with 0.89, in > that it calls itself libpng.so.1.0.89, although it's actually older. This looks more like a problem where the wrong libpng is being linked in. Larry, does -L/usr/local/lib appear on the link line?

2 participants
1 comments

[COMMENTS?] Re: DND for XEmacs 21 26 years, 6 months

Oliver Graf

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > Oliver Graf <ograf(a)fga.de> writes: > > > * do the some for the mode > > Is this needed? Can the mode not simply set the buffer-local value? Sure. I just read through all the topics I mentioned (extents, buffer-locals, etc.) and it is as you say. One thing I'm currently thinking about is the following: Should the dragdrop-drop-rules (or whatever it is called: -hook, -function) which is set in extents, buffers, etc. to get the thing to do something appropiate with the dropped data be some predefined list of source/dest/action associations (as in hm--html-mode, internal-drag-and-drop, idd), or should I use a function, where the programmer/user of the mode can do whatever he wants (plus a set of standart functions defined in dragdrop.el)? Personally I think that the function would be the better way, because the extents and buffer-locals still give you full control what to do depending on the source (and perhaps the destination -- but this is difficult if the source is outside of XEmacs). Any comments? Regards, Oliver.

1 participants
0 comments

[OK] 21.0 "Repartida" XEmacs Lucid (beta38) on i586-pc-linux 26 years, 6 months

Larry Ayers

Tried again with the site-includes and site-libraries switches added, and the newer libpng.so.2.1 is now correctly detected (it lives in /usr/local/lib, while the older version is in /usr/lib). Works fine. > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /usr/local/src/xemacs-21.0-b38/Installation: > (Output from most recent run of ./configure) uname -a: Linux liatris 2.0.33 #1 Sun Apr 19 16:35:48 CDT 1998 i586 unknown ./configure '--prefix=/usr/local/xemacs-beta' '--site-includes=/usr/local/include' '--site-libraries=/usr/local/lib' '--with-site-lisp' '--package-path=/usr/local/xemacs-beta/lib/xemacs/packages' '--cflags=-O6 -mpentium -fno-exceptions -fno-peep-spills -fno-risc' '--with-toolbars=no' '--gung-ho' '--with-xpm' '--with-jpeg' '--with-pop' '--with-gif=no' '--with-tiff=no' '--verbose' XEmacs 21.0-b38 "Repartida" configured for `i586-pc-linux'. Where should the build process find the source code? /usr/local/src/xemacs-21.0-b38 What installation prefix should install use? /usr/local/xemacs-beta What operating system and machine description files should XEmacs use? `s/linux.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -O6 -mpentium -fno-exceptions -fno-peep-spills -fno-risc Should XEmacs use the GNU version of malloc? yes (Using Doug Lea's new malloc from the Linux C Library.) 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/X11/include Where do we find X Windows libraries? /usr/X11/lib Additional header files: /usr/local/include Additional libraries: /usr/local/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for JPEG image conversion. Compiling in support for PNG image conversion. Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in support for OffiX. 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. Using POP for mail access 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: --------------------------------------------------------- > Contents of /usr/local/src/xemacs-21.0-b38/beta.err > keeping lines matching > "^--\[\[\|\]\]$\|make\[\|error\|warn\|pure.*$space\|size$\|hides\b\|strange\|shadowings\|^Compilation\|not\s-+found" > and then deleting lines matching > "confl.*with.*auto-inlining\|/usr/local/src/xemacs-21\.0-b38/lisp/[^ ]+ hides " Purespace usage: 773292 of 1507600 (51% -- 717k wasted). XEmacs: Pure size adjusted, Don't Panic! I will restart the `make' make[1]: [xemacs] Error 1 (ignored) Purespace usage: 773292 of 773292 (100%). /usr/local/xemacs-beta/lib/xemacs/site-lisp/time-stamp hides /usr/local/xemacs-beta/lib/xemacs/packages/lisp/xemacs-base/time-stamp /usr/local/xemacs-beta/lib/xemacs/packages/lisp/efs/passwd hides /usr/local/xemacs-beta/lib/xemacs/packages/lisp/xemacs-base/passwd /usr/local/xemacs-beta/lib/xemacs/packages/lisp/efs/auto-save hides /usr/local/src/xemacs-21.0-b36/lisp/auto-save 3 Emacs Lisp load-path shadowings were foundCleaning out of date .elcs in directory `lisp'...

1 participants
0 comments

Re: DND for XEmacs 21 26 years, 6 months

Jan Vroonhof

Oliver Graf <ograf(a)fga.de> writes: > * do the some for the mode Is this needed? Can the mode not simply set the buffer-local value? Jan

1 participants
0 comments

Re: [Failure] Don't do this at home... 26 years, 6 months

Gunnar Evermann

Ok, I need some advice from the Sun-experts among you! I tried to track down the workshop/XPM/GC-related problems some more. So my plan was the following: I start xemacs under dbx and stop imediately in main. I use ldp to print the object, which gets corrupted later on (using the address from the coredump) -- cool, this is "auto-autoloads.el". Now I'd like to find out wheter there still is some pointer to this string, so I thought (after having browsed through the internals manual): let's do a GC and see if something changes: I call Fgarbage_collect() and... the machine locks up completly! I still could move the mouse but nothing else worked: no ^c, the desktop didn't react, telnet from the outside didn't work anymore. Oh, btw this is our main compute serve -- oops! frustrated users from all over the place converge right here and look at me accusingly... I decide to reboot the machine, type STOP-A, one of our part-time Sysadmin mentions sync and types it at the ok prompt -- sync starts doing its thing, times out -- kernel panics -- reboot doesn't work -- Ah shit! luckily another reboot brought the machine up cleanly. Now I have two questions: - what's evil about calling Fgarbage_collect right at the start of XEmacs -- I had anticipated that this might fail and kill xemacs, but - what the f**k is going on here, a dbx-session killing off the whole machine??? (fed up with debugging for today) Gunnar

1 participants
0 comments

[OK] 21.0 "Repartida" XEmacs on Windows 95/Cygwin32 26 years, 6 months

David Bush

I apologize if this is a duplicate, but our mail system was not working well yesterday, and I have not seen my post come back. The build of b38 patched up from b37 on a Cygwin/Windows 95 system went without any problems using the simple configuration below. Toolbars ar now working with the new version of comctl32.dll. Thanks to Andy Piper for pointing that out. I have seen some strange behavior that I have not seen mentioned anywhere: 1. If I highlight something using the mouse and then popup the XEmacs Command menu with buttoin three the Cut and Copy menu entries are greyed out. Cut and Copy does work from the toolbar. IF I copy something using the toolbar, the Paste entry is stipp greyed out in the XEmacs Command menu. 2. The scroll bar slider does not move down. If I move down in the buffer and then touch the slider with button 1, the buffer moves back to the top. 3. If I modify a buffer and then select Exit from the File menu, I get a message in the minibuffer: Symbol's function definition is void: popup-dialog-box 4. Maybe this is a feature since I am comparing against 20.3 on Solaris, but with HOME defined and a .emacs in that directory I get a new entry on the menu bar "Load .emacs". If I select it it disappears, but it does reappear on occasion if I visit a file and tehen delete the buffer. So far I have not been able to narrow this one down further. One other comment could be added for Cygwin users - the installation process uses /bin/pwd. If /bin is a separate directory and not a link to the Cygwin bin directory, then wd should be copied into /bin. uname -a: CYGWIN32_95 DBUSH 4.0 19.1 i586 unknown ./configure '--with-xpm' '--site-prefixes=/usr/local' XEmacs 21.0-b38 "Repartida" configured for `i386-pc-cygwin32'. Where should the build process find the source code? /develop/xemacs-21.0-b38 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? msw Additional prefixes: /usr/local Compiling in support for XPM images. Compiling in File coding support. 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: ---------------------------------------------------------

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 1998