May 2000 - XEmacs-Beta - XEmacs Mailing List Archives

[FAILURE] CVS @ 10/05/2000 12:12 24 years

Daniel Pittman

Building from CVS for the latest XEmacs failed on my Debian machine. Attached is a log of the build process and the stack trace I chased down. I hope this is enough to work out what went wrong. If it's not, let me know... Daniel -- The cost of error on an internetwork of scientists is bandwidth. -- Hettinga's First Law of Internet Error

1 participants
0 comments

21.2 b33 Update for MinGW32 24 years

Craig Lanning

Amazingly enough, it didn't take much to get mingw32 to work again! Below is a patch to make mingw32 work for me in Cygwin v1.1.0. Andy, you may want to pay special attention to the places in nt.c where I disabled the checks for __MINGW32__. I'm still not sure how different v1.0.0 is from v1.1.0. If there are no comments, I will submit a formal patch with ChangeLog entries. Craig ------------------ / > uname -a CYGWIN_98-4.10 CRAIG 1.1.0(0.17/3/2) 2000-03-01 00:15:19 i586 unknown Index: nt/inc/sys/socket.h =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/nt/inc/sys/socket.h,v retrieving revision 1.3 diff -u -r1.3 socket.h --- socket.h 1998/05/06 09:46:20 1.3 +++ socket.h 2000/05/10 02:39:29 ＠＠ -22,7 +22,7 ＠＠ #endif /* 0 */ /* avoid duplicate definition of timeval */ -#ifdef HAVE_TIMEVAL +#if defined(HAVE_TIMEVAL) && !defined(__MINGW32__) #define timeval ws_timeval #endif Index: src/nt.c =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/src/nt.c,v retrieving revision 1.17.2.18 diff -u -r1.17.2.18 nt.c --- nt.c 2000/05/07 12:56:43 1.17.2.18 +++ nt.c 2000/05/10 02:39:34 ＠＠ -2072,7 +2072,7 ＠＠ return TRUE; } -#ifndef __MINGW32__ +#if 1 /* !defined(__MINGW32__) */ /* Return pointer to section header for section containing the given relative virtual address. */ static IMAGE_SECTION_HEADER * ＠＠ -2143,7 +2143,7 ＠＠ start with a DOS program stub. Note that 16-bit Windows executables use the OS/2 1.x format. */ -#ifdef __MINGW32__ +#if 0 /* defined( __MINGW32__ ) */ /* mingw32 doesn't have enough headers to detect cygwin apps, just do what we can. */ FILHDR * exe_header; Index: src/syscommctrl.h =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/src/Attic/syscommctrl.h,v retrieving revision 1.1.2.2 diff -u -r1.1.2.2 syscommctrl.h --- syscommctrl.h 2000/05/07 12:56:45 1.1.2.2 +++ syscommctrl.h 2000/05/10 02:39:35 ＠＠ -54,6 +54,9 ＠＠ #ifndef TCS_VERTICAL #define TCS_VERTICAL 0x0080 #endif +#ifndef PBS_SMOOTH +#define PBS_SMOOTH 0x01 +#endif #ifndef ICC_BAR_CLASSES #define ICC_BAR_CLASSES 4 Index: src/syswindows.h =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/src/Attic/syswindows.h,v retrieving revision 1.1.2.2 diff -u -r1.1.2.2 syswindows.h --- syswindows.h 2000/05/07 12:56:45 1.1.2.2 +++ syswindows.h 2000/05/10 02:39:36 ＠＠ -90,9 +90,6 ＠＠ #ifndef WM_MOUSEWHEEL #define WM_MOUSEWHEEL 0x20A #endif -#ifndef PBS_SMOOTH -#define PBS_SMOOTH 0x01 -#endif #ifndef VK_APPS #define VK_APPS 0x5D #endif Index: src/s/mingw32.h =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/src/s/Attic/mingw32.h,v retrieving revision 1.1.2.8 diff -u -r1.1.2.8 mingw32.h --- mingw32.h 2000/05/03 14:47:22 1.1.2.8 +++ mingw32.h 2000/05/10 02:39:38 ＠＠ -229,6 +229,7 ＠＠ #undef HAVE_SYS_WAIT_H #undef HAVE_TERMIOS #undef SYSV_SYSTEM_DIR +#undef CLASH_DETECTION /* We now have emulation for some signals */ #define HAVE_SIGHOLD

1 participants
0 comments

RE: 21.2.32 (CVS updated 4/19) crashes spontaneously 24 years

Michael Hill

>>>>> "Michael" == Michael Harnois <mdharnois(a)home.com> writes: On Sat, 06 May 2000 16:24:50 +0100, Andy Piper said: >> I can't reproduce. Michael> Hmmm. Then where did this infant who's interrupting your Michael> hacking time come from? Andy's in the UK, so it could be cloning.

2 participants
1 comments

Re: wrong-type-argument hash-table-p nil 24 years

Michael Harnois

On Tue, 09 May 2000 12:23:32 +0100, Andy Piper <andy(a)xemacs.org> said: > This should also fix most of the other problems people have been > seeing. Not mine, unfortunately, unless the patch didn't get committed ... I updated about fifteen minutes ago. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois(a)home.com aa0bt(a)aa0bt.ampr.org The atheist staring from the attic window is often nearer to God than the believer caught up in his own false image of God. -- Martin Buber

1 participants
0 comments

Re: ftp.xemacs.org and www.xemacs.org 24 years

John S Jacobs Anderson

on 5/9/00 1:48 PM, Björn Torkelsson at torkel(a)hpc2n.umu.se wrote: > Are anybody maintaining www.xemacs.org? yes. > It still lists 2.1.9 as the latest > stable release, and 2.2.29 as the development release. These are behind, and will be updated shortly. Thanks for pointing out the problem. > /torkel - complaining too much? No, a little thump is good every now and then... john, aka jacobs(a)xemacs.org

1 participants
0 comments

Re: new subject: proper X session management 24 years

Hamish Macdonald

>>>>> On 09 May 2000 21:14:08 +0900, >>>>> In message <200005091210.VAA14133(a)uct010.urawa.cabletv.ne.jp>, >>>>> IKEYAMA Tomonori <tomonori(a)suiyokai.org> wrote: IKEYAMA> Kondara, a Japanese GNU/Linux distribution, has its own version of IKEYAMA> XEmacs which supports XSMP and XDND. Attached patch is extracted from IKEYAMA> ftp://ftp.kondara.org/pub/Kondara/SRPMS/SRPMS/xemacs-21.1.9-1k9.nosrc.rpm. IKEYAMA> I don't understand this code. Does it fit your plan? The session management code looks like the sort of thing I was planning on doing. If the XEmacs developers are willing to have this code incorporated into XEmacs, I can work on that, making any API changes as necessary. I'll skip the DnD stuff and just incorporate the session management side. I suppose I should correspond with: Akira Higuchi <a(a)kondara.org> Regards, Hamish.

1 participants
0 comments

Another cscope mode for xemacs 24 years

Darryl Okahata

FYI, I've been working on yet another cscope minor mode. This one's specific to XEmacs. Although I'd call this an alpha release, it has a number of nice features (e.g., searches are done in the background). If you'd like an idea of what it can do, I've appended a copy of the (minimal) usage instructions to the end of this message. You can get a copy at: ftp://ftp.sonic.net/pub/users/darrylo/cscope/cscope-xemacs-0.80.tar.gz This being an alpha release, there's no README file; see the comments at the beginning of xcscope.el for installation instructions, etc.. Please send any comments and complaints to me. -- Darryl Okahata darrylo(a)soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. =============================================================================== ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; ;; ***** USING THIS MODULE ***** ;; ;; * Basic usage: ;; ;; If all of your C/C++/lex/yacc source files are in the same ;; directory, you can just start using this module. If your files are ;; spread out over multiple directories, see "Advanced usage", below. ;; ;; Just edit a source file, and use the pull-down or pop-up (button 3) ;; menus to select one of: ;; ;; Find symbol ;; Find global definition ;; Find called functions ;; Find functions calling a function ;; Find text string ;; Find egrep pattern ;; Find a file ;; Find files #including a file ;; ;; The cscope database will be automatically created in the same ;; directory as the source files (assuming that you've never used ;; cscope before), and a buffer will pop-up displaying the results. ;; You can then use button 2 (the middle button) on the mouse to edit ;; the selected file, or you can move the text cursor over a selection ;; and press [Enter]. ;; ;; Hopefully, the interface should be fairly intuitive. ;; ;; ;; * Locating the cscope databases: ;; ;; This module will first use the variable, `cscope-database-regexps', ;; to search for a suitable database directory. If a database ;; location cannot be found using this variable, then the current ;; directory is searched, then the parent, then the parent's parent, ;; etc. until a cscope database directory is found, or the root ;; directory is reached. If the root directory is reached, the ;; current directory will be used. ;; ;; A cscope database directory is one in which EITHER a cscope ;; database file (e.g., "cscope.out") OR a cscope file list (e.g., ;; "cscope.files") exists. If only "cscope.files" exists, the ;; corresponding "cscope.out" will be automatically created by cscope ;; when a search is done. ;; ;; Note that the variable, `cscope-database-regexps', is generally not ;; needed, as the normal hierarchical database search is sufficient ;; for placing and/or locating the cscope databases. However, there ;; may be cases where it makes sense to place the cscope databases ;; away from where the source files are kept; in this case, this ;; variable is used to determine the mapping. One use for this ;; variable is when you want to share the database file with other ;; users; in this case, the database may be located in a directory ;; separate from the source files. ;; ;; ;; * Keybindings: ;; ;; All keybindings use the "C-c s" prefix, but are usable only while ;; editing a source file, or in the cscope results buffer: ;; ;; C-c s s Find symbol. ;; C-c s d Find global definition. ;; C-c s g Find global definition (alternate binding). ;; C-c s c Find functions calling a function. ;; C-c s C Find called functions (list functions called ;; from a function). ;; C-c s t Find text string. ;; C-c s e Find egrep pattern. ;; C-c s f Find a file. ;; C-c s i Find files #including a file. ;; ;; These pertain to cscope database maintanance: ;; ;; C-c s L Create list of files to index. ;; C-c s I Create list and index. ;; C-c s E Edit list of files to index. ;; C-c s W Locate this buffer's cscope directory ;; ("W" --> "where"). ;; C-c s S Locate this buffer's cscope directory. ;; (alternate binding: "S" --> "show"). ;; C-c s T Locate this buffer's cscope directory. ;; (alternate binding: "T" --> "tell"). ;; C-c s D Dired this buffer's directory. ;; ;; ;; * Advanced usage: ;; ;; If the source files are spread out over multiple directories, ;; you've got a few choices: ;; ;; [ NOTE: you will need to have the script, "cscope-indexer", ;; properly installed in order for the following to work. ] ;; ;; 1. If all of the directories exist below a common directory ;; (without any extraneous, unrelated subdirectories), you can tell ;; this module to place the cscope database into the top-level, ;; common directory. This assumes that you do not have any cscope ;; databases in any of the subdirectories. If you do, you should ;; delete them; otherwise, they will take precedence over the ;; top-level database. ;; ;; If you do have cscope databases in any subdirectory, the ;; following instructions may not work right. ;; ;; It's pretty easy to tell this module to use a top-level, common ;; directory: ;; ;; a. Make sure that the menu pick, "Cscope/Index recursively", is ;; checked (the default value). ;; ;; b. Select the menu pick, "Cscope/Create list and index", and ;; specify the top-level directory. This will run the script, ;; "cscope-indexer", in the background, so you can do other ;; things if indexing takes a long time. A list of files to ;; index will be created in "cscope.files", and the cscope ;; database will be created in "cscope.out". ;; ;; Once this has been done, you can then use the menu picks ;; (described in "Basic usage", above) to search for symbols. ;; ;; Note, however, that, if you add or delete source files, you'll ;; have to either rebuild the database using the above procedure, ;; or edit the file, "cscope.files" to add/delete the names of the ;; source files. To edit this file, you can use the menu pick, ;; "Cscope/Edit list of files to index". ;; ;; ;; 2. If most of the files exist below a common directory, but a few ;; are outside, you can use the menu pick, "Cscope/Create list of ;; files to index", and specify the top-level directory. Make sure ;; that "Cscope/Index recursively", is checked before you do so, ;; though. You can then edit the list of files to index using the ;; menu pick, "Cscope/Edit list of files to index". Just edit the ;; list to include any additional source files not already listed. ;; ;; Once you've created, edited, and saved the list, you can then ;; use the menu picks described under "Basic usage", above, to ;; search for symbols. The first time you search, you will have to ;; wait a while for cscope to fully index the source files, though. ;; If you have a lot of source files, you may want to manually run ;; cscope to build the database: ;; ;; cd top-level-directory # or whereever ;; rm -f cscope.out # not always necessary ;; cscope -b ;; ;; ;; 3. If the source files are scattered in many different, unrelated ;; places, you'll have to manually create cscope.files and put a ;; list of all pathnames into it. Then build the database using: ;; ;; cd some-directory # whereever cscope.files exists ;; rm -f cscope.out # not always necessary ;; cscope -b ;; ;; Next, read the documentation for the variable, ;; "cscope-database-regexps", and set it appropriately, such that ;; the above-created cscope database will be referenced when you ;; edit a related source file. ;; ;; Once this has been done, you can then use the menu picks ;; described under "Basic usage", above, to search for symbols. ;; ;; ;; * Interesting configuration variables: ;; ;; "cscope-truncate-lines" ;; This is the value of `truncate-lines' to use in cscope ;; buffers; the default is the current setting of ;; `truncate-lines'. This variable exists because it can be ;; easier to read cscope buffers with truncated lines, while ;; other buffers do not have truncated lines. ;; ;; "cscope-use-relative-paths" ;; If non-nil, use relative paths when creating the list of files ;; to index. The path is relative to the directory in which the ;; cscope database will be created. If nil, absolute paths will ;; be used. Absolute paths are good if you plan on moving the ;; database to some other directory (if you do so, you'll ;; probably also have to modify `cscope-database-regexps'). ;; Absolute paths may also be good if you share the database file ;; with other users (you'll probably want to specify some ;; automounted network path for this). ;; ;; "cscope-index-recursively" ;; If non-nil, index files in the current directory and all ;; subdirectories. If nil, only files in the current directory ;; are indexed. This variable is only used when creating the ;; list of files to index, or when creating the list of files and ;; the corresponding cscope database. ;; ;; "cscope-name-line-width" ;; The width of the combined "function name:line number" field in ;; the cscope results buffer. If negative, the field is ;; left-justified. ;; ;; "cscope-do-not-update-database" ;; If non-nil, never check and/or update the cscope database when ;; searching. Beware of setting this to non-nil, as this will ;; disable automatic database creation, updating, and ;; maintenance. ;; ;; "cscope-database-regexps" ;; List to force directory-to-cscope-database mappings. ;; This is a list of `(REGEXP DIRECTORY OPTIONS)' triplets, where: ;; ;; REGEXP is a regular expression matched against the current ;; buffer's current directory. The current buffer is typically ;; some source file, and you're probably searching for some ;; symbol in or related to this file. Basically, this regexp is ;; used to relate the current directory to a cscope database. ;; ;; DIRECTORY is the name of the corresponding directory ;; containing (or will contain, if creating) the cscope database ;; files. ;; ;; OPTIONS is a string listing any additional options (e.g., ;; "-d") to pass to the cscope executable. Normally, this ;; string is empty. ;; ;; All of the above are strings. ;; ;; This variable is generally not used, as the normal ;; hierarchical database search is sufficient for placing and/or ;; locating the cscope databases. However, there may be cases ;; where it makes sense to place the cscope databases away from ;; where the source files are kept; in this case, this variable ;; is used to determine the mapping. ;; ;; This module searches for the cscope databases by first using ;; this variable; if a database location cannot be found using ;; this variable, then the current directory is searched, then ;; the parent, then the parent's parent, until a cscope database ;; directory is found, or the root directory is reached. If the ;; root directory is reached, the current directory will be used. ;; ;; A cscope database directory is one in which EITHER a cscope ;; database file (e.g., "cscope.out") OR a cscope file list ;; (e.g., "cscope.files") exists. ;; ;; ;; * Other notes: ;; ;; 1. The script, "cscope-indexer", uses a sed command to determine ;; what is and is not a C/C++/lex/yacc source file. It's idea of a ;; source file may not correspond to yours. ;; ;; 2. This module is called, "xcscope", because someone else has ;; already written a "cscope.el" (although it's quite old). ;;

1 participants
0 comments

Re: reproducible (with my setup) crash in beta 33 24 years

Dmitry Yaitskov

Andy Piper <andy(a)xemacs.org> wrote: > Fixed Not on my system, unfortunately. The behavior has changed in that now just after sending the message XEmacs freezes. Killing it shows the following: LUCY:/usr/local/src/xemacs-21.2$src/xemacs.exe & [1] 1532 LUCY:/usr/local/src/xemacs-21.2$kill 1532 Lisp backtrace follows:/usr/local/src/xemacs-21.2 $ # bind (inhibit-quit) # (condition-case ... . error) # (catch top-level ...) [1]+ Terminated src/xemacs.exe LUCY:/usr/local/src/xemacs-21.2$ (I've cvs updated this morning - May 9, around 11:00 EST.) > At 09:36 AM 5/6/00 -0400, Dmitry Yaitskov wrote: > >Andy Piper <andy.piper(a)bea.com> wrote: > > > >> This should fix. I still need reproducible cases for the others, but I've > >> only had 2 hours sleep so I'm off to bed .... > >> > >> andy > >> > >> 2000-05-05 Andy Piper <andy(a)xemacs.org> > >> > >> * window.c (window_unmap_subwindows_cache_mapper): remove the dead > >> instance from the frame cache also since GC may catch up too late > >> to make frame deletion sane. > >> > >> > >> > >> -------------------------------------------------------------- > >> Dr Andy Piper > >> Principal Consultant, BEA Systems Ltd > > > >FWIW, with this change I still get the crash (on my system, it is > >consistent) after sending a mail from gnus. The XEmacs screen goes > >blank and apparently it is the scratch buffer (instead of the usual > >group), switching to the group buffer still shows a blank screen, > >buffer list shows up but selecting anything from it freezes XEmacs. > > > >(This is under cygwin) > > > >-- > >Cheers, > >-Dima. > > > > > > > -------------------------------------------------------------- > Dr Andy Piper > Principal Consultant, BEA Systems Ltd -- Cheers, -Dima.

1 participants
0 comments

Re: utility function for converting lists of objects to array of objects? 24 years

Hrvoje Niksic

Craig Lanning <lanning(a)scra.org> writes: > William M. Perry writes: > > Is there any magic utility function that I'm missing to convert a list of > > strings into a char **array with a length, or anything like that? > > In lisp you could use coerce, e.g. > > (coerce '("foo" "bar" "baz") 'array) => > ["foo" "bar" "baz"] That's of little use to William, as he needs a `char **' array, not a Lisp vector.

1 participants
0 comments

new subject: proper X session management 24 years

Hamish Macdonald

Now that GNOME ships with a (mostly-working) session manager, I'm thinking an interesting project might be to extend XEmacs to take advantage of those session manager capabilities What do you folks think?

2 participants
1 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 2000