March 2000 - XEmacs-Beta - XEmacs Mailing List Archives

BUILD_MULE vs. BUILD_WITHOUT_MULE 24 years, 8 months

Charles G Waldman

In the XEmacs package sources, file XEmacs.rules has a variable BUILD_MULE. In the ChangeLog there is the following entry: 1999-04-17 Karl M. Hegbloom <psu25682(a)odin.cc.pdx.edu> * Makefile (SUBDIRS): Don't put "mule" in SUBDIRS unless BUILD_MULE=t I comment out BUILD_MULE in the "Developer Configurable" section of XEmacs.rules, as there instructed: # Build Mule? Comment for no Mule #BUILD_MULE=t But guess what, after commenting this and typing Make, I get a ton of errors from building the Mule packages! Well, on further investigation I see this ChangeLog entry: 1999-12-14 Andreas Jaeger <aj(a)suse.de> * Makefile (SUBDIRS): Build for mule unless BUILD_WITHOUT_MULE is set. Why was the new variable BUILD_WITHOUT_MULE introduced, when we already have BUILD_MULE? And why isn't it documented in XEmacs.rules? Whassup wit dat?

1 participants
0 comments

Re: M-up and M-down changed? 24 years, 8 months

Jan Vroonhof

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > But Customize doesn't do a thing for faces, its only real raison > d'etre for me personally, outside of ISO-8859. In fact, using it is > almost certain to give you a butt-ugly screen in Japanese under > XFree86 as distributed by Debian, Turbolinux, and Red Hat, and > probably all the other Linux distros, because the ideographic bitmap > fonts get mixed into lib/X11/fonts/misc, which is scaled by default. > (This is assuming the user is competent to work around Custom's > complete lack of support by setting font sizes for non-ISO-8859 fonts > by hand.) Questions: 1. Does customize "work" with mule now if you just set colors but not family/size etc? 2. Is the ignorance of customize wrt to the Mule font lists when setting the size and/or family the only problem. If the answer to both these questions is yes, then there is at least hope it can be fixed. The problem with 2 is that there currently is no make-face-size which works using frob face property. (There only is make-face-larger). Such a function is needed anyway, but it is not exactly trivial to write. Jan

2 participants
1 comments

Re: should I keep reporting crashes? 24 years, 8 months

Jan Vroonhof

"John A. Turner" <turner(a)blueskystudios.com> writes: > here's another - should I keep reporting these? is it useful or just > annoying? They all look more less identical. I suggest you only post ones that are different to spare you the effort. But please do keep reminding us (say after each beta) that you still have the problem. Then it will get fixed in the end. Unfortunately this is a hard nut to crack so it takes somebody with a good idea and a few hours to fix it. Jan

2 participants
1 comments

Gutters interface change? or bug? 24 years, 8 months

Nick V. Pakoulin

try xemacs -vanilla -eval \ (custom-set-variables '(default-gutter-position (quote top))) What i get is Wrong number of arguments: #<compiled-function (arg) "...(7)" [gutter-buffers-tab update-tab-in-gutter arg] 2>, 0 In 21.2.31 this works. Nick.

2 participants
1 comments

Re: Slider and Accelerator 'anomally' 24 years, 8 months

Jan Vroonhof

Matthew Persico <persicom(a)acedsl.com> writes: > 2) When widgets pop up with buttons, the button text does not have the > underlined accelerators, but rather the text with the accelerator > indicators: > > Anyone else seen this? I will -vanilla in the morning. Yes. Unfortunately Popup acceleerators only work on windows ATM. Jan

1 participants
0 comments

XEmacs 21.2 b32 redisplay problem 24 years, 8 months

Hamish Macdonald

Bah, forgot version information.... In XEmacs 21.2 (beta32) "Kastor & Polydeukes" [Lucid] (sparc-sun-solaris2.7) of Fri Mar 24 2000 on rhea configured using `configure --prefix=/export/users/hamishm/xemacs --site-prefixes=/export/users/hamishm/gnome:/export/users/hamishm' I CVS-upped at about 10:10am EST this morning. I was seeing this problem with a version from the 21st of March also. If I execute the following code in a vanilla xemacs, the message-mode toolbar is incorrectly rendered. "C-l" (recenter) doesn't solve the problem, but getting any X-based refresh to run ("xrefresh", iconifying/uniconifying, hide/expose window fixes the display. It looks like the portion of the toolbar, corresponding to where the gutter/tabs were, is not drawn. (set-specifier default-toolbar nil) (setq mail-user-agent 'message-user-agent) (compose-mail) Here is what it looks like: Regards, Hamish.

1 participants
0 comments

XEmacs 21.2 b32 redisplay problem 24 years, 8 months

Hamish Macdonald

I CVS-upped at about 10:10am EST this morning. I was seeing this problem with a version from the 21st of March also. If I execute the following code in a vanilla xemacs, the message-mode toolbar is incorrectly rendered. "C-l" (recenter) doesn't solve the problem, but getting any X-based refresh to run ("xrefresh", iconifying/uniconifying, hide/expose window fixes the display. It looks like the portion of the toolbar, corresponding to where the gutter/tabs were, is not drawn. (set-specifier default-toolbar nil) (setq mail-user-agent 'message-user-agent) (compose-mail) Here is what it looks like: Regards, Hamish.

1 participants
0 comments

[FAIL] Can't find the DOC file 24 years, 8 months

Norbert Koch

Hi! After updating 21.2 from CVS I get the following error: Loading site-load... Finding pointers to doc strings... Opening doc string file: No such file or directory, ../lib-src/DOC xemacs exiting. make[1]: *** [xemacs] Error 255 make[1]: Leaving directory `/usr/users/nk/archive/xemacs/src' Well, the compiler of course is right, there's no DOC file in my xemacs source tree. norbert. -- Yow! Is my fallout shelter termite proof?

3 participants
2 comments

Re: Accelerator I18N [was: I don't wont the f* underlinings ...] 24 years, 8 months

Hrvoje Niksic

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > >>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)iskon.hr> writes: > > >> By the way, Ben's improvements have made a bunch of work for > >> menubar localizers (who already have localized menus to work > >> with---obviously it doesn't matter for those who will be > >> starting fresh). > > Hrvoje> Yes. Most improvements make a bunch of work for someone. > Hrvoje> Translators should be prepared to deal with a moving > Hrvoje> target. > > Definitely not. Definitely _yes_, or they shouldn't have become translators in the first place. I know because I've worked somewhat on translating programs to Croatian. One's desire to have things translated to his tongue should not reduce the developer's freedom to change the program. > We don't make API changes without discussion beforehand, we should > not make extensive menu changes (other than adding new > functionality) without similar discussion. Assuming we take I18N > halfway seriously. That's your opinion. I say otherwise. By your standards, nothing UI-wise in XEmacs would ever change, because there's always a possibility that _someone_ in _some_ language would misunderstand/misparse _something_. I can't hope to disprove that claim. What I do claim is that _English_ menus are written for people who understand _English_. Croatians, Japanese, Thai, etc. without proper knowledge of English will fail to understand them. Well, that's what translations are for. If that means "fuck I18N" in your book, then you have a pretty weird notion of I18N. Uh, and the Japanese better get used to Internet not being IE and Netscape. It's for their own good. :-)

3 participants
3 comments

Re: A gtk/kde-xemacs... a modest toolbar/menubar proposal... 24 years, 8 months

Per Abrahamsen

Giacomo Boffi <giacomo.boffi(a)polimi.it> writes: > William M. Perry writes: > > > XEmacs can be linked with motif libraries (no opensource) > > > is this relevant to clarify/obfuscate the current issue? > > > > Stallman has granted a special exception for motif. I'm not even > > sure it is that 'official'. Its more of a look-the-other-way. > > Plus there is LessTif. Now that the harmony project is dead, there > > is no equivalent for Qt. > > the situation of motif on, e.g., a HP box to me looks similar to the > situation of Qt on, say a Corel distribution, or whatever ships those > libs with their distributions --- or someone please explain the > differences As wmperry wrote, RMS hasn't granted a "special exception", official or not, and there are no GPL compatible Qt replacement. These factors might be significant, or they might not be. Both may be legal. Both may be illegal. The legal situation is muddy enough that we will not know without a court ruling.

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