April 2001 - XEmacs-Beta - XEmacs Mailing List Archives

Steve Youngs

Hello People. I've just uploaded a new Dired package to the 'Pre-Releases' directory on ftp.xemacs.org. The maintainer is looking for feedback, especially from Windows users. Please take the time to grab this package, do some testing (including Dired's interaction with EFS), and report the results back to Michael Sperber <sperber(a)informatik.uni-tuebingen.de>. Michael wants to hear about, not only the bad news, but also the good. Getting The New Dired: ===================== 1) Tools -> Packages -> Add Download Site -> Pre-Releases 2) Tools -> Packages -> List and Install 3) select dired (mouse-2 or RET) 4) Packages -> Install/Remove Selected 5) Re-Start XEmacs. If that method gives you problems (it may do for Windows users), simply download: <ftp://ftp.xemacs.org/pub/xemacs/beta/experimental/packages/dired-1.10-pkg...> and unpack it to <emacs-roots>/lib/xemacs/xemacs-packages/ Don't forget that most open source developers do not have R & D departments with huge budgets. Having good software is worth spending a couple of minutes to send an email to the maintainers telling of success/failure. And obviously, the more details you can give the better. Thanks very much to you all for you help with this. -- |---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---| | XEmacs - It's not just an editor. | | It's a way of life. | |------------------------------------<youngs(a)xemacs.org>---|

2 participants
1 comments

New Package for inclusion into XEmacs: Build 23 years

Adrian Aichner

I have talked about this so long. Now is the time to let it see the harsh light of day (it actually night here, so it shouldn't be too bad). My CVS repository for build is also available if Steve Youngs wants to put in on cvs.xemacs.org as a whole (it's only 110 Kbytes). I'd actually prefer that. It's currently a comm package but that's negociably, of course. For others to test and give me feedback, here is a source kit for the package and the overview page of the included documentation. For those who don't want to hack on it, but would like to try it, here is the familiar binary distribution package: M-x build will get you started and will bring up a harmless widget-based interface. Best regards, Adrian File: build.info, Node: Build Overview, Next: Build Installation, Prev: Top, Up: (dir) Build Overview ************** `build' supports the building process of the `XEmacs' editor from its sources. The build process consists of following steps: 1. Download source code from FTP server or CVS repository. 2. Configure any attributes of the build process, of the resulting XEmacs executable, and of the XEmacs environment. 3. Start the make process to build XEmacs, install it, and run the regression tests. 4. Report on the success or failure of the build, using build-report. The `build' command generates a widget-based interface to configure and build XEmacs either using GNU Tools (`configure', `make') or Microsoft Tools (`nmake' with command-line options (<= 21.2-b32) or `config.inc' configuration file (> 21.2-b32)). -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

5 participants
21 comments

ediff lossage w/RH7.1 23 years

Neal D. Becker

Just installed RH7.1 with Value: "21.1 (patch 14) \"Cuyahoga Valley\" XEmacs Lucid" Now ediff is broken. Attempting an ediff gives: Can't diff remote file /tmp/.... Of course I'm asking to diff local files.

2 participants
2 comments

how to set font for C++ code ... 23 years

Shuguang Wei

1 .How to set font colour for C++ code? for example: using different colors for key words, comments... 2. how can I set the .emacs file that let it knows the file is C++ file? please send answer to shuguang01(a)yahoo.com Thank you very much. Shuguang

2 participants
1 comments

[from ben wing] Please cc me if you want my attention. Thanks. 23 years

Ben Wing

Hi, sorry to broadcast, but I keep coming across old mails where someone is asking me a question, but I don't see it because my name isn't in the header. I am on most of the xemacs lists, but that does *not* mean I necessarily read them -- there's just too much traffic for me to keep up with, so I end up not reading many of the lists most of the time, or reading them only sporadically. I filter my mail, which means I *always* see mail with my name in the headers. So if you want to make sure I see a message, put my name in a cc. Likewise, *do not* trim my name out of a header in an ongoing discussion. btw XEmacs people seem in general to be overzealous header trimmers. can i request that people stop this? thanks. -- ben I'm sometimes slow in getting around to reading my mail, so if you want to reach me faster, call 520-661-6661. See http://www.666.com/ben/chronic-pain/ for the hell I've been through.

1 participants
0 comments

None 23 years

Latchezar M. Dimitrov

Hi, As I promised I tried the suggestion bellow and yes it (make check) works -- xemacs-21.4.1 and xemacs-21.5.0 on Solaris 8 on Sun w/s. Now I can check the installation (and sleep better :-) Thanks. But I still have the problem with XEmacs not beeing able to customize (you caled it broken button or something) I need to be able to use 'customize'. Also both 21.5.0 and 21.4.1 treat fonts differently from 21.1.14 - I do not know why. But I am missing a lot nice fonts that 21.1.14 uses and the others cannot. Both 21.5.0 and 21.4.1 cannot (do not) open any images as images, i.e. open them as (binary) files. Because of that I have to keep 21.1.14. I compiled all of them with the same configure parameters and use the same (literally) configuration even the same packages except for xemacs/libxemacs-21.x.x/lisp/. Thanks Latchezar > From: "Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > Date: Thu, 29 Mar 2001 13:20:57 +0900 > To: "Latchezar M. Dimitrov" <lmdimi(a)mthcsc.wfu.edu> > Subject: Re: probs "Urania" on sparc-sun-solaris2.8 > > >>>>> "lmd" == Latchezar M Dimitrov <lmdimi(a)mthcsc.wfu.edu> writes: > > lmd> Would you or "the path guru" please tell how to do it now? > > cd $path_to_XEmacs_sources > > if [ -d xemacs-packages ] ; then rmdir -f xemacs-packages ; fi > if [ -L xemacs-packages ] ; then rm -f xemacs-packages ; fi > if [ -e xemacs-packages ] ; then exit(1) ; fi # should not happen!! > ln -s /usr/scratch/XEmacs/lib/xemacs/xemacs-packages xemacs-packages > > if [ -d mule-packages ] ; then rmdir -f mule-packages ; fi > if [ -L mule-packages ] ; then rm -f mule-packages ; fi > if [ -e mule-packages ] ; then exit(1) ; fi # should not happen!! > ln -s /usr/scratch/Mule/lib/mule/mule-packages mule-packages > > make check # should pass all tests now, unless the paths guru has > # changed the code that checks for "in-place" packages > > > -- > University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN > Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 > _________________ _________________ _________________ _________________ > What are those straight lines for? "XEmacs rules." Latchezar (Lucho) Dimitrov Wake Forest University, Winston-Salem, NC home: (336) 794-2094 grad.lab: (336) 758-4954 mailto:dimil01g＠wfu.edu or http://www.wfu.edu/~dimil01g/ lmdimi(a)mthcsc.wfu.edu lmdimi(a)pilot.mthcsc.wfu.edu ... Type fast, think slow. ... "Hippocratic Oath For Software Engineers"

4 participants
5 comments

Re: 21.4.0 segfault on debain 2.2r2 with athena widgets 23 years

Jan Vroonhof

Doug Alcorn <doug(a)lathi.net> writes: > > Use --with-widgets=athena --with-athena=3d to get support for Xaw3d, > > You nailed it. Thanks. Note that we have quite a bit of code in the configure script to catch this kind of stuff. Could you try figuring out what's going wrong there? Jan

5 participants
5 comments

Re: More Debian/Athena Progress Bar was Re: 21.4.0 segfault 23 years

A.J. Rossini

>>>>> "MH" == Michael Hill <mikehill(a)hgeng.com> writes: MH> Building then with athena=next I get the neXtaw widgets and am MH> able to reproduce the crash (described below) that I get on my MH> Debian sid (unstable) machine. Also attached are the MH> Installation and C backtrace from the crash on both machines. MH> The neXtaw crash: MH> In the shell window where I've started XEmacs, I get a bunch MH> of these messages while the progress bar's being drawn: MH> xemacs: X Error of failed request: BadGC (invalid GC MH> parameter) Major opcode of failed request: 66 (X_PolySegment) MH> Resource id in failed request: 0x1000022 Serial number of MH> failed request: 6121 Current serial number in output stream: MH> 6121 MH> ...but no crash. Then next time the file dialog opens (also MH> noticed for some other toolbar/menubar picks), crash. No lisp MH> backtrace. (Poor-quality) Conjecture -- since you are running sid/unstable, do you recall the warning that the Xaw3d package is no longer an Xaw replacement? Could this be related? (I.e. syncing of the Xaw libs). best, -tony -- A.J. Rossini Rsrch. Asst. Prof. of Biostatistics UW Biostat/Center for AIDS Research rossini(a)u.washington.edu FHCRC/SCHARP/HIV Vaccine Trials Net rossini(a)scharp.org -------- (friday is unknown) -------- FHCRC: M--W : 206-667-7025 (fax=4812)|Voicemail is pretty sketchy CFAR: ?? : 206-731-3647 (fax=3694)|Email is far better than phone UW: Th : 206-543-1044 (fax=3286)|Change last 4 digits of phone to FAX

2 participants
1 comments

21.4.0 segfault on debain 2.2r2 with athena widgets 23 years

Doug Alcorn

OK, first I tried to build 21.4.0 --with-gtk and --with-gnome. That build fine (and quickly too). It ran OK. The only problem was that all the widgets didn't work. The buffer tabs were blank or non-existant and the customize buffer buttons didn't work. So I thought I would go back to athena. I did a "make realclean" and reconfigured. The build progressed fine. When I run xemacs, it segfaults before it finished coming up. Immediately upon starting it complains: /usr/local/bin/xemacs-21.4.0: Symbol `toggleClassRec' has different size in shared object, consider re-linking /usr/local/bin/xemacs-21.4.0: Symbol `labelClassRec' has different size in shared object, consider re-linking Warning: Representation size 4 must match superclass's to override value Then when it tries to popup the progress bar, it segfaults. Here's the beginning of the backtrace: Program received signal SIGSEGV, Segmentation fault. 0x401a945f in XTextWidth () from /usr/X11R6/lib/libX11.so.6 (gdb) where #0 0x401a945f in XTextWidth () from /usr/X11R6/lib/libX11.so.6 #1 0x8191cc9 in MaxLabel (gw=0x871b7a8, wid=0xbfffbc4c, hgt=0xbfffbc4e, w0=0xbfffbc50, w1=0xbfffbc52) at xlwgauge.c:967 #2 0x819087d in GaugeResize (w=0x871b7a8) at xlwgauge.c:327 #3 0x40029b95 in XawFormDoLayout () from /usr/X11R6/lib/Xaw3d/libXaw.so.6 #4 0x40138ceb in XtInitializeWidgetClass () from /usr/X11R6/lib/libXt.so.6 #5 0x40138cb9 in XtInitializeWidgetClass () from /usr/X11R6/lib/libXt.so.6 #6 0x401391bc in XtInitializeWidgetClass () from /usr/X11R6/lib/libXt.so.6 #7 0x40139685 in _XtCreateWidget () from /usr/X11R6/lib/libXt.so.6 #8 0x40139785 in XtCreateManagedWidget () from /usr/X11R6/lib/libXt.so.6 #9 0x818b2f5 in xaw_create_progress (instance=0x871b320) at lwlib-Xaw.c:828 #10 0x8189399 in instantiate_widget_instance (instance=0x871b320) at lwlib.c:941 #11 0x81895ce in lw_make_widget (id=65538, parent=0x871b1a0, pop_up_p=0 '\000') at lwlib.c:389 #12 0x8189d70 in lw_create_widget (type=0x81b8e29 "progress", name=0x84c6708 "Progress", id=65538, val=0x84ba720, parent=0x871b1a0, pop_up_p=0, pre_activate_cb=0, selection_cb=0x80c6870 <popup_selection_callback>, post_activate_cb=0) at lwlib.c:993 #13 0x81730b1 in x_widget_instantiate (image_instance=141665168, instantiator=141664736, pointer_fg=136289276, pointer_bg=136289276, dest_mask=111, domain=141664104, type=0x81b8e29 "progress", wv=0x84ba720) at glyphs-x.c:2539 There's actually 128 levels of this backtrace. If I need to include them all I can. I don't get a core file for some reason. I got this by just running xemacs with gdb. -- (__) Doug Alcorn (mailto:doug＠lathi.net http://www.lathi.net) oo / PGP 02B3 1E26 BCF2 9AAF 93F1 61D7 450C B264 3E63 D543 |_/ If you're a capitalist and you have the best goods and they're free, you don't have to proselytize, you just have to wait.

7 participants
15 comments

Problems with fontification in ruby mode 23 years

Norbert Koch

Hi! font-lock doesn't seem to work in ruby buffers. I've attached the file ruby-mode.el which is part of the ruby distribution. When I open a source file, I see Fontifying f.rb... aborted.aborted. in the message buffer. Also, the warning (1) (warning/warning) Error caught in `font-lock-pre-idle-hook': (malformed-list ?\') come up in tons. I don't know left from right with font-locking, so I can't figure out the problem to say nothing of its solution (might be some differences between emacs and xemacs, though). Any takers? TIA, norbert.

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 April 2001