November 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Neal D. Becker

[...] Loading auto-save.el...*** Error in XEmacs initialization (file-error "Creating directory" "Permission denied" "//.autosave") *** Backtrace really-early-error-handler((file-error "Creating directory" "Permission denied" "//.autosave")) make-directory-internal("//.autosave") (if (not parents) (make-directory-internal dir) (let (... create-list) (while ... ...) (while create-list ... ...))) ) (if handler (funcall handler (quote make-directory) dir parents) (if (not parents) (make-directory-internal dir) (let ... ... ...))) ) # bind (handler) (let ((handler ...)) (if handler (funcall handler ... dir parents) (if ... ... ...))) ) # bind (parents dir) make-directory("//.autosave") (if (file-directory-p dir) nil (setq dir (directory-file-name dir)) (make-directory dir) (set-file-modes dir 448)) [...] Not sure why - I put a symlink from /usr/local/lib/xemacs -> (automounted remote /usr/local/lib/xemacs) Why is it trying to make //.autosave????

1 participants
0 comments

alphaev56-unknown-linux not recognized! 26 years

Neal D. Becker

checking host system type... alphaev56-unknown-linux [...] Invalid configuration 'alphaev56-unknown-linux': machine 'alphaev56-unknown' not recognized

1 participants
0 comments

Re: hm--html-menus, new version 26 years

SL Baur

Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes in xemacs-beta(a)xemacs.org: ... > (4) There is a mechanism for excluding "uninteresting" files (test > scaffolding, whatnot) from the binary packages, I believe. As of the latest revision, everything must be explicitly mentioned to get installed. > But I'm not sure how it's supposed to work. I think that what > happens is that the contents of the ELCS make variable get > included, and so do EXTRA_SOURCES. Everything mentioned in ELCS gets bytecompiled and installed. Everything mentioned in EXTRA_SOURCES gets copied directly into the binary distribution. There are various methods of installing data files in etc/. The best and most comprehensive example of this is the Gnus installation. > This would allow exclusion of specifically FSF-only files. Even > if not, I don't think it's a big deal. Yup.

1 participants
0 comments

Re: FSF Emacs 20.1 syntax parsing engine? 26 years

Hrvoje Niksic

David C Worenklein <dcw(a)gcm.com> writes: > Supposedly RMS spruced up the syntax parsing engine. Are we in the > process of synching with it? We are not (and that's a shame). To me it looks that synching that code shouldn't be too hard, but comments in our version say otherwise, at least for some functions. Quoting the comment preceding Fforward_comment: /* #### between FSF 19.23 and 19.28 there are some changes to the logic in this function (and minor changes to find_start_of_comment(), above, which is part of Fforward_comment() in FSF). Attempts to port that logic made this function break, so I'm leaving it out. If anyone ever complains about this function not working properly, take a look at those changes. --ben */ -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Don't hit a man when he's down -- kick him; it's easier.

1 participants
0 comments

Re: hm--html-menus, new version 26 years

Jareth Hein

>>>>> "Heiko" == Heiko Muenkel <muenkel(a)tnt.uni-hannover.de> writes: Heiko> Hi, next week I'd like to announce a new version of my Heiko> hm--html-menus package. I've changed some things, like the Heiko> places were special files will be searched - they are now Heiko> searched in package specific etc directories and no longer in Heiko> the main etc directory. Because of the new packaging system of Heiko> the XEmacs I've some questions: Heiko> 2. What is the prefered way to provide the new version to the Heiko> XEmacs development team? Should I Heiko> - put the original tar file on ftp.xemacs.org ? Heiko> - build a XEmacs package file and put it on ftp.xemacs.org ? Heiko> - put it in the CVS tree and check it in (no idea, if I've the Heiko> permissions to do that)? Heiko> - send patches[1] (diffs against the CVS tree)? If you (or anyone else!) would like to be the CVS maintainer for a package, please send me e-mail about it, and I will set things up for you to be able to commit to the tree. The less work upon Steve, the better, eh? -- Jareth Hein | jareth(a)camelot.co.jp | ハインジェラス Toolsmith & Program lead | http://www.camelot.co.jp | 開発部チーフ Camelot Software, Ltd. | |（株）キャメロット "It's a sad sign of the times when 'political machine' is redefined to include 'main-line battle tank'" - Ambassador Grossblunder

3 participants
2 comments

FSF Emacs 20.1 syntax parsing engine? 26 years

David C Worenklein

Supposedly RMS spruced up the syntax parsing engine. Are we in the process of synching with it?

1 participants
0 comments

Re: adding an entry to the standard menus 26 years

Jan Vroonhof

Per Abrahamsen <abraham(a)dina.kvl.dk> writes: > For obvious reasons, easymenu is more important on Emacs than on > XEmacs. I think it is equally important on both Emacsen. For instance would we have the autosizing environment menus in auctex.el if FSF Emacs did not implement the moderen style menu defs with :menu-filter etc? > I think what one reasonable can expect of Emacs programmers, > is that they try to coordinate changes in the API with the XEmacs > people. Not that they actually implement them themselves. It would also have been nice if the FSF version of easymenu.el actually acknowledges that it is basically implementing compatability with the XEmacs API that way people trying to extent it would have a look there first. Anyway 'easymenu-add-menu-item' is there now and seems quite easy to implement at least at first glance. Jan

2 participants
1 comments

Re: adding an entry to the standard menus 26 years

Hrvoje Niksic

Per Abrahamsen <abraham(a)dina.kvl.dk> writes: > Hrvoje Niksic <hniksic(a)srce.hr> writes: > > > Per Abrahamsen <abraham(a)dina.kvl.dk> writes: > > > > > Inge did propose the new functions on the xemacs-beta list. I don't > > > think he received any (useful) feedback. > > > > He did, but most of it boiled down to noone being moved enough to > > implement them. > > That's not what I consider useful. What would be useful would be > comments about the API. Was it implementable in XEmacs? Did it > suck? Those are not useful questions. Yes, it was implementable and no, it didn't suck, but I, for one, didn't find much value in those enhancements. Definitely not useful enough value to give a shot at implementing them. > > Inge didn't care about implementing them, so they didn't get done. > > For obvious reasons, easymenu is more important on Emacs than on > XEmacs. I think what one reasonable can expect of Emacs > programmers, is that they try to coordinate changes in the API with > the XEmacs people. Not that they actually implement them > themselves. Just like FSF Emacs, XEmacs is a volunteer project. If noone cares to code something up, it won't get done. But you know that. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- What is mind? No matter. What is matter? Never mind.

2 participants
1 comments

Re: Fix for several pdb.el problems 26 years

Wolfgang Weitz

Dear xemacs maintainers, Charles G Waldman sent me (and you) yesterday a patch fixing some bugs in pdb.el (XEmacs debugging support for Python). Please apply this patch to your old version of pdb.el (a patched version is available from ftp://ftp.aifb.uni-karlsruhe.de/pub/wwe/pdb.el). Thanks, Wolfgang -- Wolfgang Weitz Institut AIFB, Uni Karlsruhe (TH) weitz(a)aifb.uni-karlsruhe.de SAAC Raum 242, Tel: 0721/608-4063 PGP key fingerprt D7 C0 E3 77 39 82 0E 53 81 93 27 C7 5D 23 2D E8 On Tue, 17 Nov 1998, Charles G Waldman wrote: > I've finally got pdb working inside XEmacs on Windows. (Hooray!) The > problems were in the gud-pdb-marker-filter. In fact, it had errors > which kept the thing from working correctly on Unix, also. The regexp > was way too strict - it wouldn't match directories with a '-' in the > name, such as 'site-packages'. I've now got it working on Windows as > well as fixed some of the annoying bugs on Unix. I've also changed it > to use a completing read when reading the initial pdb command line. [...] > Wolfgang, if you approve of these changes, please send a note to > xemacs-beta(a)xemacs.org. [...]

1 participants
0 comments

Forthcoming contributions to XEmacs 26 years

Martin Buchholz

XEmacs development has been quiet for a while while Steve is elsewhere, and I have been lurking while doing some performance hacking for 21.2. That work is mostly done now, and I have the usual Martin mega-patch to integrate into 21.2. I was expecting Steve to be around for this, but he is still away. Anyways, we need to make changes to the CVS tree, both for my changes to 21.2, and to get 21.0 out the door. Hopefully, Steve will be back soon, but if not, we'll have to get the job done without him. I am personally lacking many of the skills of a good maintainer, including complete or partial ignorance of PGP, CVS, Windows and the new package system. But if no one else is willing to take on the job of releasemeister, I'll probably reluctantly try to do it for a while before I go to Japan. I haven't volunteered for this before because the releasemeister does not really have the time to have a personal development project on the side. By the way, there have been mail problems at xemacs.org, and so I haven't received all of the email addressed to martin(a)xemacs.org. Hopefully those problems are fixed now. XEmacs is a classic example of a project that needs some maintainer leadership right now. Perhaps we should advertise, say on Linux Weekly News? Martin

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 November 1998