August 1999 - XEmacs-Beta - XEmacs Mailing List Archives

HTML Documentation Available [comments, please] 26 years

Matt Curtin

I think I'm finished with the HTML conversions of the documentation. http://www.cis.ohio-state.edu/~cmcurtin/xemacs-doc/ -- Matt Curtin cmcurtin(a)interhack.net http://www.interhack.net/people/cmcurtin/

1 participants
0 comments

The `a b' syntax bug fixed 26 years

Hrvoje Niksic

While I was away, someone fixed the infamous bug where typing `a b' and pressing M-f jumped to the beginning of `a' instead of to the beginning of `b'. Thanks!

1 participants
0 comments

Re: xemacs source code HOWTO ? 26 years

Hrvoje Niksic

Stef Epardaud <stef(a)lunatech.com> writes: > and so i got into the source code, and, as i haven't done C for > quite a while, and Java brainwashed me quite well, Note that XEmacs is not a very easy piece of C code. It's a good idea to hone your C skills on something smaller before embarking on the XEmacs journey. Having said that, I'll also say that most of XEmacs is very nicely written and that, once you find your way around the code, it is not hard to read. I've also found XEmacs very modular, even when that modularity is not visible to the outside. It is quite possible to change (fix or improve) one part of it without understanding or knowing about the other parts. > is there such a HOWTO, to introduce new programers, or did everyone > that ever participated to emacs/xemacs just read the code and > understood the whole project guidelines in a second and started > coding the minute after ? It takes a few months.

1 participants
0 comments

Re: Viva la muerte! 26 years

Hrvoje Niksic

Chris Woods <cjwoods(a)mediaone.net> writes: > Hrvoje Niksic wrote: > > > > Has anyone tried to compile and run XEmacs with and without aliasing > > and with and without union type to see if it works? > > Yes. I compiled with -O6 -mpentium. Other than that, I didn't change > anything. Everything compiled fine and runs great: You tried both it with and without union type, I assume?

3 participants
2 comments

Re: pcl-cvs fork in the road 26 years

Jan Vroonhof

Charles G Waldman <cgw(a)fnal.gov> writes: > Any suggestions as to which one? I don't see any package where it > seems like a natural fit. Either fsf-compat or xemacs-base > I'm also not overwhelmingly convinced of its general usefulness. Especially not given that XEmacs has add-minor-mode. Jan

1 participants
0 comments

RFC: MULE coding system docs and modeline indicators 26 years

Stephen J. Turnbull

I've just completed drafting a revision of the Lispref | Mule documentation aimed at making the coding system documentation more useful. The structure is still pretty bad (I've mostly just added descriptions of various coding systems), and I would appreciate suggestions on improving the organization. Also, a while back somebody (Hrvoje? welcome back!) suggested rationalizing the coding system modeline indicators. Before I start on that, I want to check that (1) nobody else has worked on it, and (2) that using the FSF scheme is the way to go. It seems to me that *very* short and cryptic is the way to go, so I'm thinking about adding (a) balloon help giving full name of the coding system plus (b) the "about the coding system" help function(s) from the Mule menu to the modeline. (a) seems pretty uncontroversial; for (b) should the functions be duplicate, moved, or don't do this? I'm also working on fixing the functions in mule-base/mule-diag.el. Again, if anybody's done anything in that direction, let me know. The current description functions come in a verbose but very incomplete form and a uninterpretably terse but complete form. I don't see any use for the latter; I think that should be verbose, too. Comments? -- 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 two straight lines for? "Free software rules."

1 participants
0 comments

Re: xemacs source code HOWTO ? 26 years

William M. Perry

Martin Buchholz <martin(a)xemacs.org> writes: > >>>>> "William" == William M Perry <wmperry(a)aventail.com> writes: > > William> Kyle Jones <kyle_jones(a)wonderworks.com> writes: > >> Hrvoje Niksic writes: > >> > 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. :-) > >> > >> Ha ha, that was me. Let me qualify that. I like the accessor > >> macros. The flow-of-control macros, LIST_LOOP, DEVICE_LOOP, etc. > >> struck me as being a bit over the top. Sort of Common Lisp-ish, > >> and I'm no CL fan. The pointer XFOO macros are evil, but necessary. > > William> Quick, what does FROB do? :) > > FROB is generally function-local, so it's not so important to understand. No, but I love FROB... I get people griping at work about my psychotic use of the preprocessor. One guy spent 5 days trying to hunt down a type definition for a function pointer that we use all over the place, and it was buried in some macros... he sends my code through the preprocessor now when he wants to find things. :) > Also, I removed most of the FROB macros from the code in 21.2 Yes, but there are still 19 left. :)

1 participants
0 comments

Re: xemacs source code HOWTO ? 26 years

William M. Perry

Kyle Jones <kyle_jones(a)wonderworks.com> writes: > Hrvoje Niksic writes: > > 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. :-) > > Ha ha, that was me. Let me qualify that. I like the accessor > macros. The flow-of-control macros, LIST_LOOP, DEVICE_LOOP, etc. > struck me as being a bit over the top. Sort of Common Lisp-ish, > and I'm no CL fan. The pointer XFOO macros are evil, but necessary. Quick, what does FROB do? :) -Bill P.

2 participants
1 comments

PRIVATE: "auto-save.el" no longer optional 26 years

Greg.Jumper＠Sun.COM

Full_Name: Greg Jumper OS: Solaris 8 alpha Version: 21.1.6 mule: no severity: Aggravating Submission from: (NULL) (192.9.25.22) With the advent of the package system in XEmacs 21.1, the file auto-save.el moved from the "packages" subdirectory of the old lisp hierarchy to the core lisp directory, where it is now loaded as part of the default XEmacs build process; unlike past versions, you get auto-save.el whether you want it or not. I don't particularly like/want the added auto-save.el functionality, so I tried (unload-feature 'auto-save) which "succeeds". Unfortunately, any subsequent attempt to edit a file fails with an error about "make-auto-save-file-name" being undefined, as the feature unload does not restore the definitions from "files.el" (which I gather should occur if files.el "provide"d a feature?). Thanks, Greg --=-=-=--

1 participants
0 comments

Re: pcl-cvs fork in the road 26 years

Jan Vroonhof

Charles G Waldman <cgw(a)fnal.gov> writes: > adding the non-bundled file "easy-mmode.el", If this is generally useful it should probably not be in a pcl-cvs packages but in a more low level package. > So my question is, should I submit the patches to fix bugs in the > R-2_0-Beta_2 version that we ship, or should I submit patches to sync > our pcl-cvs package with Stefan Monnier's 2.9.6 substantially reworked > 2.9.6 version? Staying close the main author is always better. Usual marking of changes with ;; XEmacs and contributing back rules apply. Jan

2 participants
1 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 August 1999