May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

John Jones

>>>>> Andy Piper writes: > If I do package-get-update-all what happens? Do packages I haven't > installed get updated? I see lots of packages being installed - > but when I consult the package installation directory I specified > and configure time, I can't find any of them, is this where they > are supposed to go? It is only supposed to update the packages you have, and decides which to update based on package-get-base. Currently, it may end up installing packages you do not have if they are required by packages you do have. I think that should be changed since sometimes package A is officially required by package B, but there are no real problems in running B without A. John Jones jj(a)asu.edu

2 participants
1 comments

[FAIL] 21.0 "Russian White-pre4" XEmacs Lucid (beta39) on i386-pc-cygwin32 27 years

Andy Piper

Well, success with the patch that I will post shortly, failure otherwise. andy > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /development/build/xemacs-20/Installation: > (Output from most recent run of ./configure) uname -a: CYGWIN32_NT ARMAGEDON 4.0 19.1 i586 unknown ./configure '--site-includes=/usr/local/include' '--package-path=/usr/gnu/lib/xemacs/packages' '--prefix=/usr/gnu' XEmacs 21.0-b39 "Russian White-pre4" configured for `i386-pc-cygwin32'. Where should the build process find the source code? /development/build/xemacs-20 What installation prefix should install use? /usr/gnu 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 Additional header files: /usr/local/include Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for GIF image conversion. Compiling in support for JPEG image conversion. Compiling in support for PNG image conversion. Compiling in support for TIFF image conversion. Compiling in support for GNU DBM. 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: --------------------------------------------------------- > /development/build/xemacs-20/beta.err does not exist!

1 participants
0 comments

b39 pre4 27 years

Andy Piper

event-msw.c is totally broken in pre4 (i.e. does not compile at all) due to the dnd changes. andy

1 participants
0 comments

[OK] 21.0 "Repartida" XEmacs Lucid (beta38) on i686-pc-linux 27 years

Tetsuya HOYANO

with fresh tar balls, works fine so far... --HOYANO Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnulibc1/pgcc-2.91.24/specs gcc version pgcc-2.91.24 19980418 (gcc2 ss-980401 experimental) > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /home2/beta/xemacs-21.0-b38/Installation: > (Output from most recent run of ./configure)

1 participants
0 comments

RE: More package questions 27 years

Ian MacKinnon

I tried this yesterday, by doing M-x load-file package-get.el then M-x package-get-update-all and all the packages I had were updated This is on cygwin on NT --- Ian -----Original Message----- From: Andy Piper [mailto:andyp＠parallax.co.uk] Sent: Wednesday, May 06, 1998 9:36 AM To: xemacs-beta(a)xemacs.org Subject: More package questions If I do package-get-update-all what happens? Do packages I haven't installed get updated? I see lots of packages being installed - but when I consult the package installation directory I specified and configure time, I can't find any of them, is this where they are supposed to go? andy

1 participants
0 comments

More package questions 27 years

Andy Piper

If I do package-get-update-all what happens? Do packages I haven't installed get updated? I see lots of packages being installed - but when I consult the package installation directory I specified and configure time, I can't find any of them, is this where they are supposed to go? andy

1 participants
0 comments

Re: [FAILURE] Russian White-pre2 27 years

SL Baur

Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes: > As of right now, the CVS tree seems to be out of sync; dragdrop.[ch] > seem to be missing. At least, I couldn't figure out how to CVS to > cough them up. Correct. Russian White-pre2 is cursed. I'll be updating it to pre3 shortly. Other than the missing files it looks pretty good from the testing I've been doing on it. > They were added in an Oliver Graf patch that apparently appeared on > xemacs-patches a few hours before I subscribed. > Still, this system is a _big_ improvement over the huge number of > patches, most of which I don't care about, flowing through XEmacs beta. Cool. > I've also set procmail to filter all reports generated by build-report > into a separate bin. It's not clear to me whether it makes sense to > make a separate list for build reports, but this is working well for > me, as the typical reply to a build report includes all of the text > leading up to the auto-generated report. The list for taking build reports should be up. I am uncertain as well that it is The Right Thing to do. Even if it may be tedious at times, the build reports often times contain information other people are looking for and ask questions about. If nothing else, they contain ideas about how to configure XEmacs. Whatever people feel comfortable with.

1 participants
0 comments

[FAILURE] Russian White-pre2 27 years

Stephen J. Turnbull

As of right now, the CVS tree seems to be out of sync; dragdrop.[ch] seem to be missing. At least, I couldn't figure out how to CVS to cough them up. They were added in an Oliver Graf patch that apparently appeared on xemacs-patches a few hours before I subscribed. Still, this system is a _big_ improvement over the huge number of patches, most of which I don't care about, flowing through XEmacs beta. I've also set procmail to filter all reports generated by build-report into a separate bin. It's not clear to me whether it makes sense to make a separate list for build reports, but this is working well for me, as the typical reply to a build report includes all of the text leading up to the auto-generated report.

1 participants
0 comments

Re: DND for XEmacs 21 27 years

Jonathan Harris

Oliver, thanks for sending me your patch. > By the way: how does windos handle a drag (i.e. when is a press a drag)? It's up to the application to initiate a drag operation. The win32 user interface guidlines recommend that the application should initiate a drag operation when the user clicks and holds the left-button (with or without modifiers) within selected text. Most applications also initiate a drag when the right button (button3 in XEmacs) is used in the same way. On dropping text, the text should be copied if the Ctrl modifier is held down and should be moved if Ctrl isn't down. Mod and Shift are ignored. Some applications display a popup menu when text is dropped with the right button: the menu offers the user the choice of copying or moving the text. We probably don't need to bother with this and can just treat a right-button like a left-button. The button and modifier state is ignored for file drops. Because the state of the Ctrl modifier is examined at _drop_ time, but affects whether the _dragged_ text should be deleted, dragging is a two-stage operation and needs both a start-drag and a stop-drag function. I imagine that you're aiming for the lisp-level dispatch functions to be independant of the dnd system in use. Does the desired mswindows behaviour that I've described sound consistent with that goal? Actually, dnd for text uses a different and more complicated win32 API than dnd for files. I don't plan to implement dnd for _text_ for XEmacs 21.0. This means that for XEmacs 21.0, the mswindows code won't be able to initiate drags and will only have to handle file drops. Jonathan. -- Jonathan Harris | jhar(a)tardis.ed.ac.uk London, England | Jonathan-Harris(a)psion.com

2 participants
3 comments

Re: DND for XEmacs 21 27 years

Oliver Graf

"Kirill M. Katsnelson" <kkm(a)kis.ru> writes: > Some time ago, Oliver Graf wrote... > |+ > | Ah, we're on our own... > | Do you know Xdnd (the protocol used by KDE)? It only uses MIME data in > | drags. If you drag some files, the mime type url/* is used, where * is some > | action verb (i.e. move or copy). > > I think I got your point: you are asking about a protocol, right? Nope. This was just to explain the different ways to do the same thing... > [some dnd protocol description] This was Xdnd I think. Or am I wrong? The low-level protocols have a low priotity on my todo (well, thats why they are called low-level ;-). First think I do is the abstraction of the drop, after this the abstraction of the drag follows, then I will look after other protocols. My test bed is the OffiX protocol (which is easy but also simple -- and I have control over it -- and it's is already in XEmacs), and it seems that the mswindows code will follow in my footsteps (as the maintainer told me for file drops only). After this I will see what will follow (Xdnd, Xde, CDE, Motif, etc.). Regards, Oliver.

3 participants
3 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 1998