January 2000 - XEmacs-Beta - XEmacs Mailing List Archives

CVS commit access procedure documented. 24 years, 11 months

Martin Buchholz

I've added a section on being a CVS committer to http://cvs.xemacs.org/#committers. Comments are welcome. Per, you get to beta test these instructions. Your commit access should be working now. You can test your access using a non-commit operation like `diff'. Martin

1 participants
0 comments

Re: "Symbol X has different size in shared object" bug reappears 24 years, 11 months

Daniel Pittman

On Tue, 04 Jan 2000, Martin Buchholz <martin(a)xemacs.org> wrote: >>>>>> "DP" == Daniel Pittman <daniel(a)danann.net> writes: > > DP> This is caused by using mismatched flat and 3D Athena headers when > DP> building. If you use 3D Athena -- and especially if you have > DP> overwritten libXaw.so with a 3D version, make sure that the 3D (or > DP> whatever variant) headers are on your path. > > Shouldn't configure be able to *guarantee* that we don't have > mismatched headers and libraries, at least if we run on the same > system we build on? Hrm. Yes. The detection stuff does have XE_DIE() if we don't get a suitably matching library and header combination _and_ if the Athena widgets were used somewhere. Hmmm. My guess is that Hrvoje uses the flat Xaw and has the Debian `put something 3D in the LD search path as libXaw' lossage. Something like that, anyway. Patch attached reports the Athena library and headers in the Installation file, making this bit of debugging a little less guesswork the next time :) Daniel 2000-01-05 Daniel Pittman <daniel(a)danann.net> * configure.in (Installation): Report which Athena header/library combo is being used. -- Until the pain of remaining the same, hurts more than the pain of change, most people prefer to remain the same. -- Dr. Richard D. Dobbins

1 participants
0 comments

Global-Set-Key on C-Home ..... gets a complaint? 24 years, 11 months

Warren Music

Hi, I am new to emacs, and had .emacs set up to map C-Home to beginning-of-buffer, and C-End to end-of-buffer. It looks like Xemacs sets these up automatically, but I would like to leave the mappings in my .emacs because I would like to use both versions (emacs is just a tad faster but Xemacs has some other things I like). How can I resolve this so I can leave the mappings in my .emacs?

1 participants
0 comments

Re: Merging customize support 24 years, 11 months

Per Abrahamsen

Hrvoje Niksic <hniksic(a)iskon.hr> writes: > You could also have CVS write access and commit your changes > yourself. That would be most convenient. If so, I'll suggest changes on <emacs-custom(a)sunsite.auc.dk>, and if nobody protest, commit them to both Emacs and XEmacs. Who should I mail cvs username and password to?

2 participants
1 comments

"Symbol X has different size in shared object" bug reappears 24 years, 11 months

Hrvoje Niksic

This bug I haven't seen for quite a while has apparently reared it ugly head one more time. This is printed to stderr when I start XEmacs: {mraz}[~/work/emacs/build]$ ./src/xemacs ./src/xemacs: Symbol `toggleClassRec' has different size in shared object, consider re-linking ./src/xemacs: Symbol `labelClassRec' has different size in shared object, consider re-linking I've seen this before, and I managed to fix it by finding a magic combination of 3D Athena headers and libraries with on my system. Its reappearance is likely due to recent Athena detection rewrite in configure, but it might also be the a package upgrade. I'll be happy to provide relevant data. Any ideas?

1 participants
0 comments

`yes-or-no-p-dialog-box' broken. (Was: Re: nextaw lib & Xaw3d headers... broken again) 24 years, 11 months

Karl M. Hegbloom

I have been having the same problem. I've disabled dialog boxes for now. Clicking the buttons in the dialog does nothing; they press, but XEmacs doesn't read it. Closing the dialog via the WM causes XEmacs to crash. I just updated via CVS and have recompiled. If it's still happening, I'll mail a stack trace.

3 participants
4 comments

Re: Merging customize support 24 years, 11 months

Per Abrahamsen

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > How is Emacs 20 intended to cope with these settings, or is that not a > supported configuration. Unsupported, same with XEmacs 21.0. None of this is going to work on emacsen that are actually released ;-) There will be no unbundled customize, at least not from me.

1 participants
0 comments

Re: Merging customize support 24 years, 11 months

Per Abrahamsen

Hrvoje Niksic <hniksic(a)iskon.hr> writes: > After this is approved by the maintainers, that would be Jason > Mastaler <jason(a)xemacs.org>. Ok, I'll wait until I hear from the maintainers ;-)

1 participants
0 comments

vc.el suggestion 24 years, 11 months

Albert Ting

When using CVS, it's hard to tell if a file was locally modified. Looking for the "CVS-" vs "CVS:" on the modeline is not user friendly. Below will highlight the CVS/RCS text on the modeline if the file was locally modified. I'm currently using a defadvice, it would be great if something like this was built into vc.el. Albert (defvar vc-mode-ext (detach-extent (make-extent 0 0 ""))) (set-extent-face vc-mode-ext 'highlight) (defadvice vc-mode-line (after highlight activate) "highlight CVS/RCS tag if file is modified locally" (let* ((str vc-mode) (hdr "^ \$CVS\\|RCS\$") (locked-hdr (concat hdr "-"))) (when (and str ;; initial version may start with nil (string-match hdr str) (not (string-match locked-hdr str))) (let ((substr (substring str 1))) ;; normally modeline displays whatever is in the minor-mode-alist, ;; indexed by mode. The cdr can be either a string or (extent ;; . str) or a list of them. vc-mode is normally set to a string. ;; Change the variable to specify an extent, preceded by a regular ;; space (setq vc-mode (list " " (cons vc-mode-ext substr)))))))

1 participants
0 comments

Re: Tabs' background pixmap 24 years, 11 months

Didier Verna

Hrvoje Niksic wrote: > I noticed that buffer tabs (aka "gutter") don't inherit the background > pixmap of the face they're supposed to be using. This makes them look > very ugly for us that use a background pixmap. This is related to something I planned to investigate on a while ago. The problem is that in XEmacs, the way to specify a background pixmap is hacky: it's done by setting the default face's background pixmap, which plays a particular role. This is semantically incorrect since what you want to do is really use a background pixmap for the /whole/ text area, or even the whole frame. Ideally, you should be able to do that, and to specify, say, another background pixmap for the default face, which would be drawn under the characters, but *only* under them. As a consequence of the current design, there can be no inheritance of the backgrond pixmap between X windows because (AFAIK) the corresponding X window attribute is simply not used. Although I'm not very positive about this, there could be a potential gain of efficiency in redisplay if we used background pixmaps in the X sense (meaning for instance that XClearWindow and stuff would actually redraw the pixmap). I'm not completely sure, however, that there would be a substantial gain compared to clearing the areas manually (by filling them with the pixmap) as it is done now. It would at least save us some GC context switches. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / EPITA / LRDE mailto:didier＠epita.fr /_/ / /_/ / /__ / 14-16 rue Voltaire Tel. +33 (1) 44 08 01 77 94276 Kremlin-Bicêtre cedex Fax. +33 (1) 44 08 01 99

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 January 2000