April 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Re: How about a new XEmacs logo? 24 years, 7 months

Michael Harnois

On 05 Apr 2000 14:45:10 +0200, Hrvoje Niksic <hniksic(a)iskon.hr> said: > I'm sure almost everyone agrees with that. There's no question > about preserving capitalization. I'm not as free to speak for everyone as Hrvoje <g> but I agree with preserving the capitalization as it is. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois(a)home.com aa0bt(a)aa0bt.ampr.org Sed quis custodiet ipsos custodes? -- Juvenal

1 participants
0 comments

Initial Frames (was Re: How about a new XEmacs logo?) 24 years, 7 months

Brady Montz

Ben Wing <ben(a)666.com> writes: > Frame mapping ... > part of the scheme might want to be delayed until version 22.) The basic idea > is that the initial frame is not created before the > initialization file is run, but instead a banner frame is created containing > the XEmacs logo, a button that allows the user to cancel > the execution of the init file and an area where messages that are output in > the process of running this file are displayed. This ... > > Ben Wing I completely agree. I hate having my initial window waiting for me to click on it for it to warp to its final destination. -- Brady Montz bradym(a)bluejet.com

1 participants
0 comments

Re: How about a new XEmacs logo? 24 years, 7 months

Hrvoje Niksic

Larry Ayers <layers(a)marktwain.net> writes: > On Wed, Apr 05, 2000 at 10:44:13AM +0200, Giacomo Boffi wrote: > > Sandra Wambold writes: > > > I think the case of "XEmacs" should be preserved in any new logo. > > > > i think that _all_ uppercase is ok, and that 2 capitals letters on > > the left give an unpleasant unbalanced feel > > I hope the capitalization of the first two letters is retained, it > gives the editor's name a distinctive look. I'm sure almost everyone agrees with that. There's no question about preserving capitalization.

1 participants
0 comments

Re: How about a new XEmacs logo? 24 years, 7 months

Jan Vroonhof

"John A. Turner" <turner(a)blueskystudios.com> writes: > agree completely, in case anyone's keeping count > > aren't there more important things to do? Yep. Painting GPL highcolor icons for example. jan

1 participants
0 comments

Re: Mode line offset from mouse pointer 24 years, 7 months

Jan Vroonhof

Kyle Jones <kyle_jones(a)wonderworks.com> writes: > > Hmm, this means we've broken something. Top-left is definitely > supposed to be 0,0. It looks like we lost some position adjustments in that function (probably the result of Andy reverting the "gutters are counted in window" experiment" and forgetting this one). I'll try making a patch that reverts to the 21.1 version and see whether that works. Jan

1 participants
0 comments

Re: crash when using W3 24 years, 7 months

Jan Vroonhof

Hrvoje Niksic <hniksic(a)iskon.hr> writes: > > ... what happens when the buffer gets killed during the loop? > > You lose. I didn't really pay much attention to that case, > considering it highly extreme and even contrived. Well lisp is allowed to be evil and extreme unfortunately. > How do we get in the situation where after-change-functions kill the > buffer? Can that really be intentional? In this case it is was not the after-change-functions themselves. It is the fact that we process events during after change functions. It is normal to delete buffers in process sentinels. Maybe we should disallow killing the buffer in an after-change-function (and enforce this somehow) and inhibit all event processing? Jan

2 participants
1 comments

Re: crash when using W3 24 years, 7 months

Jan Vroonhof

Be afraid, be very afraid.... Are we going to have to audit the whole code for stuff like this? :-( > I think that whole code should be audited for race conditions.... And its clients.. Index: process.c =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/src/process.c,v retrieving revision 1.39.2.12 diff -u -u -r1.39.2.12 process.c --- process.c 2000/02/21 23:06:59 1.39.2.12 +++ process.c 2000/03/18 01:19:03 ＠＠ -921,12 +921,16 ＠＠ buffer_insert_raw_string (buf, chars, nbytes); #endif - Fset_marker (p->mark, make_int (BUF_PT (buf)), p->buffer); + /* buffer_insert_raw_string_1 can call lisp code! */ - MARK_MODELINE_CHANGED; + if (BUFFER_LIVE_P(buf)) + { + Fset_marker (p->mark, make_int (BUF_PT (buf)), p->buffer); + + MARK_MODELINE_CHANGED; - /* If the restriction isn't what it should be, set it. */ - if (old_begv != BUF_BEGV (buf) || old_zv != BUF_ZV (buf)) + /* If the restriction isn't what it should be, set it. */ + if (old_begv != BUF_BEGV (buf) || old_zv != BUF_ZV (buf)) { Fwiden(p->buffer); old_begv = bufpos_clip_to_bounds (BUF_BEG (buf), ＠＠ -939,14 +943,15 ＠＠ p->buffer); } - /* Handling the process output should not deactivate the mark. */ - zmacs_region_stays = old_zmacs_region_stays; - buf->read_only = old_read_only; - old_point = bufpos_clip_to_bounds (BUF_BEGV (buf), - old_point, - BUF_ZV (buf)); - BUF_SET_PT (buf, old_point); - + /* Handling the process output should not deactivate the mark. */ + zmacs_region_stays = old_zmacs_region_stays; + buf->read_only = old_read_only; + old_point = bufpos_clip_to_bounds (BUF_BEGV (buf), + old_point, + BUF_ZV (buf)); + BUF_SET_PT (buf, old_point); + } + UNGCPRO; } return nchars;

2 participants
1 comments

Re: [edit-utils] Handling Japanese man page 24 years, 7 months

Hrvoje Niksic

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > Yoshiki> Why? It might become a little bit slower for large > Yoshiki> English man page because of regexp search, but other > Yoshiki> than that it does no harm. I can't imagine a situation > Yoshiki> where > > Speed is no issue here, man pages just can't get that big. Speed is definitely an issue with large English man pages. First, nroff takes a while to process them, and Emacs takes time to clean them. This is less dire on newer machines, but man pages really do get that big (try `man zshall' on a slower computer.) Unfortunately, I have no useful input for Japanese stuff, I just wanted to point out that the speed problem for man pages is real. > Yoshiki> I'm reluctant to do the same thing for Chinese and > Yoshiki> Korean characters as I don't know how they localize man > Yoshiki> pages. > > ...why not give these other guys a chance of fixing the same problem > _without_ needing to read the code? With the defcustom, _they_ can > decide for themselves even if they don't grok elisp. Ideally, XEmacs should just do the right thing, either by hardcoding the stuff or by guessing it. We should generally be careful about introducing new user-options.

3 participants
4 comments

[BUG] vc C-x v = broken 24 years, 7 months

Kirill 'Big K' Katsnelson

When vc is loaded and I press C-x v = in a buffer which is under source control (cvs), I get WTA stringp, t Big K

2 participants
1 comments

Re: psgml dtds 24 years, 7 months

Jerry James

On Tue, 04 Apr 2000 at 23:58:56 +1000, "Peter B. West" <pbwest(a)netscape.net> wrote: > When I write a text xml file and a dtd for it, as in the JAXP tutorial, > any attempt to indent the buffer text leads to the following problem. [snip] > The difficulty is that my DOCTYPE is a SYSTEM followed by the local > filename of the dtd. In the call to `sgml-setup-doctype' the pubid is > `nil'. `sgml-canonize-pubid' however, makes no provision for a `nil' > pubid. This one is my fault. Does the following patch solve the problem? --- psgml-parse.el~ Fri Mar 31 11:34:30 2000 +++ psgml-parse.el Tue Apr 4 17:40:39 2000 ＠＠ -3535,8 +3535,9 ＠＠ (cond (external ;; James addition - set the sgml-declaration (let ((decl - (sgml-catalog-lookup sgml-catalog-files nil 'dtddecl - (sgml-canonize-pubid (car external))))) + (and (car external) + (sgml-catalog-lookup sgml-catalog-files nil 'dtddecl + (sgml-canonize-pubid (car external)))))) (if decl (setq sgml-declaration decl))) (sgml-push-to-entity (sgml-make-entity docname 'dtd external)) (sgml-check-dtd-subset) If so, I'll send it to xemacs-patches. Thanks, -- Jerry James Email: james(a)eecs.ukans.edu WWW: http://www.eecs.ukans.edu/~james/

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