August 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Bad entry in package index 24 years, 8 months

Kevin Oberman

There seems to be a bad entry in the new package index. I suspect that hm--html-menus is a typo. In any case, the tarball is not found. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman(a)es.net Phone: +1 510 486-8634

1 participants
0 comments

Re: xemacs source code HOWTO ? 24 years, 8 months

Hrvoje Niksic

Kyle Jones <kyle_jones(a)wonderworks.com> writes: > Well, I like the macros. I remember someone calling ***'s use of macros "pathological". I wonder who that might be. :-) But then again, I also thought they were pathological until I became one with the code. I still hate them when I am one with the GDB.

2 participants
1 comments

<ndbm.h> missing 24 years, 8 months

Hrvoje Niksic

database.c won't compile because <ndbm.h> is missing. On my system (Debian potato), <ndbm.h> is in fact <db1/ndbm.h>. As a kludge, I've modified my copy of database.c, but I'm sure it's not the right fix. I understand too little of what's going on in database.c to provide a good fix, though.

1 participants
0 comments

Re: xemacs source code HOWTO ? 24 years, 8 months

Hrvoje Niksic

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > Kyle Jones <kyle_jones(a)wonderworks.com> writes: > > > Well, I like the macros. A few of the mods I've made would have > > been a lot harder without them. It's just another form of modularity. > > It would be nice to have something like 'macroexpand' for C code > though. Have you tried `C-c C-e' in C mode?

1 participants
0 comments

[Crash!] 21.2b19 24 years, 8 months

Erik Arneson

I'm not really sure what caused the crash. I had several windows open and I believe I was quitting GNUS while composing an e-mail in VM. Suddenly my hard drive light went bonkers and my computer got very nonresponsive, then kablooie! XEmacs was gone! uname -a: Linux inanna 2.2.10 #3 Fri Jun 25 17:08:28 PDT 1999 i686 unknown Lisp backtrace follows: resize-subwindow(#<image-instance (widget) on #<x-device on ":0.0" 0x20dd> (#<face default "default face">)Buffers 789x23 on #<x-frame > 0x0x8c81d68 0x56e63> 789 nil) # bind (inst frame-or-buffer) update-tab-in-gutter(#<buffer "(XEmacs) Presentation">) select-window(#<window on "(XEmacs) Presentation" 0x56e61>) # bind (window tallest-window first-window b horiz-predicate) bbdb-pop-up-bbdb-buffer(#<compiled-function (w) "...(15)" [b window-buffer w major-mode vm-mode] 2>) # bind (offer-to-create) bbdb/vm-pop-up-bbdb-buffer(nil) # (unwind-protect ...) # bind (offer-to-create) bbdb/vm-update-record() run-hooks(bbdb/vm-update-record) # (unwind-protect ...) # (unwind-protect ...) # bind (vm-sr-clip vm-sr-min vm-sr-max) # (unwind-protect ...) # bind (hook-variable message) vm-run-message-hook([[#<marker at 1 in (XEmacs) 0x8c63034> #<marker at 56 in (XEmacs) 0x8c6304c> #<marker at 2116 in (XEmacs) 0x8c631cc> #<marker at 2335 in (XEmacs) 0x8c631fc> #<marker at 2562 in (XEmacs) 0x8c63214> #<marker at 2563 in (XEmacs) 0x8c632bc>] ["6" " 6" nil #<marker at 601 in (XEmacs) Summary 0x8c16054> #<marker at 680 in (XEmacs) Summary 0x8c1603c> <<>> <-- From_ 855 #<buffer "(XEmacs)"> 0 (<37C1FA53\.EB080F08(a)wlv\.iipo\.gtegsc\.com>) nil nil nil nil nil nil #<extent (601, 680) H 0x8e77458 in buffer (XEmacs) Summary>] [t nil nil nil nil nil nil nil nil] [nil "Tuesday" "24" "August" "1999" "01:50:11" "GMT" "Allen M. Cohen" "amc(a)wlv.iipo.gtegsc.com" "<37C1FA53.EB080F08(a)wlv.iipo.gtegsc.com>" "4" "EFS problem with XEmacs 21.1.4" "^From:" "xemacs(a)xemacs.org" "xemacs(a)xemacs.org" "8" "1999082401:50:11" "EFS problem with XEmacs 21.1.4" (number mark "N Allen M. Cohen 24.08.99 01:50 4 " thread-indent "EFS problem with XEmacs 21.1.4\n") nil nil] [nil <v> nil nil nil]] vm-select-message-hook) # (unwind-protect ...) # (unwind-protect ...) # bind (vm-sbe-buffer) vm-preview-current-message() # (unwind-protect ...) # bind (point message-pointer message-list mp) vm-follow-summary-cursor() # bind (arg) vm-scroll-forward(nil) # bind (command-debug-status) call-interactively(vm-scroll-forward) # (condition-case ... . error) # (catch top-level ...) gdb /usr/local/bin/xemacs core `where': #0 0x403e7111 in __kill () #1 0x8075129 in fatal_error_signal () #2 <signal handler called> #3 0x4003e800 in _init () #4 0x40241e63 in XtSetValues () #5 0x813060a in x_resize_subwindow () #6 0x80cc82c in Fresize_subwindow () #7 0x807aeea in Ffuncall () #8 0x805b1fe in execute_optimized_program () #9 0x805aea6 in funcall_compiled_function () #10 0x807b017 in Ffuncall () #11 0x807b8f3 in run_hook_with_args_in_buffer () #12 0x807b943 in run_hook_with_args () #13 0x807b9c3 in va_run_hook_with_args () #14 0x8058789 in Frecord_buffer () #15 0x813d041 in Fselect_window () #16 0x807afe0 in Ffuncall () #17 0x805b1fe in execute_optimized_program () #18 0x805aea6 in funcall_compiled_function () #19 0x807b017 in Ffuncall () #20 0x805b1fe in execute_optimized_program () #21 0x805aea6 in funcall_compiled_function () #22 0x807b017 in Ffuncall () #23 0x805b1fe in execute_optimized_program () #24 0x805aea6 in funcall_compiled_function () #25 0x807b017 in Ffuncall () #26 0x807b8f3 in run_hook_with_args_in_buffer () #27 0x807b943 in run_hook_with_args () #28 0x807b69c in Frun_hooks () #29 0x807afe0 in Ffuncall () #30 0x805b1fe in execute_optimized_program () #31 0x805aea6 in funcall_compiled_function () #32 0x807b017 in Ffuncall () #33 0x805b1fe in execute_optimized_program () #34 0x805aea6 in funcall_compiled_function () #35 0x807b017 in Ffuncall () #36 0x805b1fe in execute_optimized_program () #37 0x805aea6 in funcall_compiled_function () #38 0x807b017 in Ffuncall () #39 0x805b1fe in execute_optimized_program () #40 0x805aea6 in funcall_compiled_function () #41 0x807b017 in Ffuncall () #42 0x805edec in Fcall_interactively () #43 0x807a002 in Fcommand_execute () #44 0x80a6c74 in execute_command_event () #45 0x80a70f4 in Fdispatch_event () #46 0x80646d9 in Fcommand_loop_1 () #47 0x806455e in command_loop_1 () #48 0x8078d88 in condition_case_1 () #49 0x80641cc in command_loop_3 () #50 0x80641e8 in command_loop_2 () #51 0x8078ad9 in internal_catch () #52 0x806432c in initial_command_loop () #53 0x8075fa2 in xemacs_21_2_b19_i686_pc_linux () #54 0x80766c3 in main () #55 0x403e0cb3 in __libc_start_main (main=0x80765c4 <main>, argc=1, argv=0xbffffc34, init=0x804ea24 <_init>, fini=0x81518b4 <_fini>, rtld_fini=0x4000a350 <_dl_fini>, stack_end=0xbffffc2c) at ../sysdeps/generic/libc-start.c:78 -- # Erik Arneson erik(a)starseed.com Webring Software Engineer # # Yahoo! Inc. PGP ID: 1024/6EE28A05 (541) 482-3000x105 # # "There's such a fine line between stupid and clever." Spinal Tap #

1 participants
0 comments

Re: web site access mechanisms (was _real_ long subject) 24 years, 8 months

Michael Sperber

>>>>> "Jan" == Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: Jan> Thus you need to CVS checkout the file on the web server. Either Jan> you do this manually and then it isn't much different from using Jan> ftp to update the site or you have the webserver do this Jan> periodically. The last solution is harder, but has the advantage Jan> that not everybody needs access to the Web server. The best way is to check out a copy for the web server on every commit. The CVS manual describes how to do it. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: C-x C-f foo.jpg in XEmacs 21.1.3/21.2.19 24 years, 8 months

Hrvoje Niksic

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > Kyle Jones <kyle_jones(a)wonderworks.com> writes: > > > The automatic image display goop was removed from format-alist > > because it broke the world. Before 21.2 is released, someone > > should put this stuff on auto-mode-alist. > > Alternatively the processing of format-alist should be moved from > insert-file-contents to find-file. That would be wrong. format-alist is *designed* to encode/decode formats at a low level, i.e. in insert-file-contents.

1 participants
0 comments

Re: bad change to buffer-string 24 years, 8 months

Hrvoje Niksic

wmperry(a)aventail.com (William M. Perry) writes: > You used to be able to do (buffer-string nil nil somebuffer) to get > the entire string out of a buffer. With XEmacs 21.2, it has been > changed to just take a 'buffer' arguent, but it is _supposed_ to be > backwards compatible and take 'buffer old-end old-buffer' arguments. > > But if you pass in nil for 'buffer', it thinks you want the new way > and 'nil' means current-buffer. This broke the content-id (cid) url > handling in Emacs/W3 + pGnus. Ah, how I sometimes hate myself. After the FSF change to `buffer-string', I wowed not to make the same change. Then the time has softened me, so I hacked it in anyway, but I just _knew_ I'd break something. I'll send a patch soonish. Thanks for the code.

1 participants
0 comments

Re: web site access mechanisms (was _real_ long subject) 24 years, 8 months

Jan Vroonhof

john s jacobs anderson <jacobs(a)azstarnet.com> writes: > I do think a Minister of Information-Dissemination type position is a > good idea. That is, a person _ultimately_ (but not necessarily > _personally_) responsible for the FAQ, coordinating the documentation > versions and formats, announcing releases to Freshmeat and the > newsgroups, evangelism and proselytizing, etc., etc. I agree. It used to be that the "XEmacs maintainer" (currently Steve) was responsible for that (as well as deciding which apaches to apply). We shifted the patches burden, it seems like a good idea to this with the PR too. > Of course, if you've got access, feel free to do it yourself, also. Send > me a note and let me know, or at least modify the comments in the page > header. (Add another <META type="author"> tag.) This is basically what CVS is all about. > We've already got the submission/confirmation part (mail > webmaster(a)xemacs.org stuff, I (or somebody else) posts it, we tell you > it's posted). The only advantage to CVS would be (1) maintaining a > local 'source' tree for the web site and (2) making sure two people > weren't editing the file at the same time. No (by default CVS doesn't even do (2), although it can). The main advantage is keeping track of changes. This already a huge advantage when working alone and it is a must-have when working with others. > Is that worth the effort, or is there something I'm missing? Setting up and using CVS is fairly simple. There is just two points to keep in mind 1. Due to a design error in CVS moving/renaming files is harder than it should (not impossible just less convenient then it should be). 2. The perfect solution would a web-server (a mod_cvs for apache) than can serve directly out of CVS. However this currently impossible. Thus you need to CVS checkout the file on the web server. Either you do this manually and then it isn't much different from using ftp to update the site or you have the webserver do this periodically. The last solution is harder, but has the advantage that not everybody needs access to the Web server. The manual solution would look something like (after initial setup) # Send your changes to the repository cvs commit # (optional) # Tell the CVS server that the state as now is ready for release cvs tag public # Tell the webserver to get the changes from CVS ssh www.xemacs.org cvs update In "automatic mode" the last line would be done by a cron script on www.xemacs.org. > > > Jan> [2] Note: That is maintenance, _not_ design. I think we are > > Jan> disciplined enough to keep a make minor (but possibly crucial > > Jan> information wise) changes in accordance with your style > > Jan> guides if you are on that round the world trip. > > I don't know if I'm on 'that round the world trip', What was trying to say (in a humorous way, but it failed) that we should plan for the contingency of you (or anyone else) being unavailable (such as after you won the lottery and when on a round the world trip). Thats why I brought up CVS because it means that others have access to the master copy of the website and in case of "automatic" updates that access to CVS is sufficient to update the website. It also means that people should have the discipline to not do this until absolutely necessary. > CVS-guru's: Can the CVS system check to make sure a particular feature > exists in a file before it's accepted for check-in? That is, if an > Author: type field is defined, can check-ins of files lacking that > field be blocked? Yes. Like I wrote before; There is no need to rush this. Maybe you should talk a bit with other projects that have their website under CVS. Jan

1 participants
0 comments

Re: Suggested addition to README.packages 24 years, 8 months

Jan Vroonhof

Robert Pluim <rpluim(a)bigfoot.com> writes: > > That is OK with me, but _first_ the provide info needs to be up to > > date. > > What needs to be done here? I can look at it if no-one else is > volunteering. Hmm. I just looked at the package index again and it seems that the situation is already a lot better (Thanks Steve). I suggest that you write the documentation change as a patch (please update also the info file if you can) and submit it to xemacs-patches (I'll apply it then). After that (if you have time) it would be nice if you could make sure that each provides line has the following in it 1. A list of all features provided by the package (more or less done now). 2. A list of all minor and major modes provided by the package (this is used by some magic in the mode setting code to provide tips for what packages to install). Jan

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 August 1999