May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Proposal: XEmacs startup, Microsoft, and kernels 26 years, 6 months

William M. Perry

"Kirill M. Katsnelson" <kkm(a)kis.ru> writes: > Some time ago, Lonhyn T. Jasinskyj wrote... > |+ > | I believe that this effort would win many converts from the FSF Emacs > | crowd. We can begin with the more popular and freely available > | operating systems like GNU Hurd and then move on based on that > | experience. I will begin writing letters on impressive government > | letterhead to Microsoft explaining our noble effort and demanding > | source code to Windows 98 and NT. They have no choice but to comply > | since they are already running scared because of the severe legal > | action that the US government has arrayed against them. > > There's a simpler approach. Just sign a non-disclosure agreement, pay > $250,000, ans NT source code is all yours. Getting Windows 95 source > is rewarded $5 and a can of beer, but no one needs this crap anyways. Uhhhh... last I checked the NT source license was $1 million. :) Ever _READ_ any of that stuff. Yick[1]. :) -Bill P. [1] Not kidding! I just perused it briefly once, compuserve has a source license :)

1 participants
0 comments

Re: [Q] Should `string' accept integers? 26 years, 6 months

SL Baur

Hrvoje Niksic <hniksic(a)srce.hr> writes: > When I created the `string' function, I made it accept integers (via > CHECK_CHAR_COERCE_INT) out of inertia. > Today it crossed my mind that `string' is a new function and there is > no compatibility code actually depending on it accepting integers. > Should we make new functions behave logically, i.e. accept only > characters where characters are expected? I lean toward this. I would say no. > Another question: do we care about FSF compatibility? FSF also has > `string', and they certainly accept integers. We care where it otherwise hurts. If it's going to accept integers the DOC string needs to be corrected.

1 participants
0 comments

[PATCH] Scrollbar visible and placement specifiers 26 years, 6 months

Kirill M. Katsnelson

ChangeLog entry for src/ 1998-05-09 Kirill M. Katsnelson <kkm(a)kis.ru> * This change adds four scrollbar specifiers: {horizontal,vertical}-scrollbar-visible-p and scrollbar-on-{top,left}-p. Spare parts supplied by Didier Verna <verna(a)inf.enst.fr> * frameslots.h: Added slots for the four specifier caching. * frame.h: FRAME_SCROLLBAR_{WIDTH,HEIGHT} count for scrollbar visible specifiers. Removed old resource-only controlled scrollbar_on_* ints. * frame-x.c (x_layout_widgets): Removed (to x-scrollbar.el) initialization of old style scrollbar placement from resources. * frame-tty.c (tty_init_frame_1): Removed initialization of old style scrollbar placement. * frame-msw.c (mswindows_init_frame_1): Removed random initialization of scrollbar sizes to 15 pixel. * redisplay-msw.c (mswindows_redisplay_deadbox_maybe): Use scrollbar placement specifiers cached values from window, instead of the old per-frame values. (mswindows_output_vertical_divider): Ditto. * redisplay-x.c (x_output_vertical_divider): Ditto. * redisplay-output.c (redisplay_clear_bottom_of_window): Ditto. * scrollbar.c (update_scrollbar_instance): Ditto. (specifier_vars_of_scrollbar): Declared the four specifiers. * window.h (struct window): Defined slots for caching the new specifiers. * window.c (mark_window): Mark them. (allocate_window): Initialize them. (struct saved_window): Store them in a cool place. (saved_window_equal): Compare them. (save_window_save): Save them. (Fset_window_configuration): Fetch them back. (window_needs_vertical_divider): Check for scrollbar placement using window cached specs. (window_top_gutter_height): Ditto. (window_bottom_gutter_height): Ditto. (window_left_gutter_width): Ditto. (window_right_gutter_width): Ditto. (window_scrollbar_width): Account for scrollbar visibility specification in window. (window_scrollbar_height): Ditto. ChangeLog entry for lisp/ 1998-05-09 Kirill M. Katsnelson <kkm(a)kis.ru> * x-scrollbar.el (x-init-scrollbar-from-resources): Initialize scrollbar-on-{left,top}-p from *scrollBarPlacement resources. * x-misc.el (x-get-resource-and-maybe-bogosity-check): Removed obsolete comment. * scrollbar.el (scrollbars-visible-p): Use new {vertical,horizontal}-scrollbar-visible-p specifiers.

1 participants
0 comments

[Q] Should `string' accept integers? 26 years, 6 months

Hrvoje Niksic

When I created the `string' function, I made it accept integers (via CHECK_CHAR_COERCE_INT) out of inertia. Today it crossed my mind that `string' is a new function and there is no compatibility code actually depending on it accepting integers. Should we make new functions behave logically, i.e. accept only characters where characters are expected? I lean toward this. Another question: do we care about FSF compatibility? FSF also has `string', and they certainly accept integers. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Try to use "ad nauseam" at least once per flame. It doesn't mean anything; but it gives that polished feel to your postings.

1 participants
0 comments

Re: [DOC-BUG] string-rectangle not described in info 26 years, 6 months

Hrvoje Niksic

chr(a)mediascience.no (Christian Nybř) writes: > The command `string-rectangle' is not mentioned in Info. > Shouldn't it be? > > $/usr/local/src/xemacs-20/info> grep string-rectangle * > $/usr/local/src/xemacs-20/info> Maybe the info documentation on rectangles needs updating. > BTW, is this the right place to report /documentation bugs/, as long > as they persist in the current beta tree? Yes. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- "Manic depression is cool... your body can make its own drugs."

1 participants
0 comments

Re: Startup speed: Still too many stats? 26 years, 6 months

Hrvoje Niksic

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > Hrvoje Niksic <hniksic(a)srce.hr> writes: > > > Michael, what was your opinion about the optimization we discussed, > > which would forbid directories ending with `.el' or `.elc'? I think > > it would be worth implementing it, especially for non-Unix systems, > > where a stat is extremely costly. > > I thought this was taken care of by limiting the recursion depth? So did I, but this appears not to be the case. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Jone's law: The man who smiles when things go wrong has thought of someone to blame it on.

1 participants
0 comments

Re: Proposal: XEmacs startup, Microsoft, and kernels 26 years, 6 months

SL Baur

Lonhyn T Jasinskyj <lonhyn(a)nas.nasa.gov> writes: > Cool, well if we all chip in about $1000 then we might be able to > get source officially. It would be worth it just for the pathetic > humor disguised as operating system code. I can think of many better things to do with $250,000.

1 participants
0 comments

Re: [PATCH] Changes to man/xemacs-faq.texi 26 years, 6 months

SL Baur

Michael Sperber <sperber(a)informatik.uni-tuebingen.de> writes: > He told me he either wants people, when using "GNU Emacs", to also > call XEmacs "GNU XEmacs". I actually wouldn't mind "GNU XEmacs" if XEmacs tarballs were available on prep. They aren't and I find "GNU XEmacs" highly annoying.

1 participants
0 comments

Re: Announcements ? 26 years, 6 months

SL Baur

Andy Piper <andyp(a)parallax.co.uk> writes: > At 11:34 PM 5/7/98 -0700, SL Baur wrote: >> There will be beta39 (9-May-1998) and beta40 (16-May-1998) then we move > Is this a record for the number of beta releases? Probably. I am told XEmacs 19.12 reached a higher beta number, but if you add in the recent midweek snapshots ...

2 participants
1 comments

Bug(?) in multi-key handling 26 years, 6 months

Paul Foley

I'm not sure what's going on here...I just discovered that I'm unable to type "ø" (oslash) using "multi-key o /" -- it works fine in 20.3 (but my 20.3 isn't MULE-enabled, if that's got something to do with it) Also, multi-key a " results in ä, but multi-key " a does nothing. These things are all defined in x-compose.el[c], and (lookup-key compose-map "o/"), (lookup-key compose-map "/o"), etc., all return the right thing, but the vast majority of composed keys don't work for me. A quick grep through the source for "Multi_key", "multi-key" and "compose" doesn't turn up anything helpful (I think. Some hint that maybe XIM is to blame?) [In fact, I just tried binding another key to compose-map, and everything works fine] -- Paul Foley <mycroft(a)actrix.gen.nz> --- PGP-encrypted mail preferred PGP key ID 0x1CA3386D available from keyservers fingerprint = 4A 76 83 D8 99 BC ED 33 C5 02 81 C9 BF 7A 91 E8

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