From xemacs-m  Sat Jan 11 01:18:12 1997
Received: from altair.xemacs.org (steve@xemacs.miranova.com [206.190.83.19])
          by xemacs.org (8.8.4/8.8.4) with ESMTP
	  id BAA26643 for <xemacs-beta@xemacs.org>; Sat, 11 Jan 1997 01:18:11 -0600 (CST)
Received: (from steve@localhost)
          by altair.xemacs.org (8.8.4/8.8.4)
	  id XAA19375; Fri, 10 Jan 1997 23:28:09 -0800
Sender: steve@xemacs.org
To: xemacs-beta@xemacs.org
Subject: Deletion of read-only extents (was Re: scrollbars)
References: <9701080035.AA12973@euler.alphatech.com> <kigafql5608.fsf@jagor.srce.hr> <x220bwlhpl.fsf@lemcbed.lem.uni-karlsruhe.de> <kigu3osmvl0.fsf@jagor.srce.hr> <x2sp4cxtob.fsf@lemcbed.lem.uni-karlsruhe.de> <m29164c72h.fsf@altair.xemacs.org> <x2vi97uv6m.fsf@lemcbed.lem.uni-karlsruhe.de>
X-Url: http://www.miranova.com/%7Esteve/
Mail-Copies-To: never
X-Face: #!T9!#9s-3o8)*uHlX{Ug[xW7E7Wr!*L46-OxqMu\xz23v|R9q}lH?cRS{rCNe^'[`^sr5"
 f8*@r4ipO6Jl!:Ccq<xoV[Qz2u8<8-+Vwf2gzJ44lf_/y9OaQ`@#Q65{U4/TC)i2`~/M&QI$X>p:9I
 OSS'2{-)-4wBnVeg0S\O4Al@)uC[pD|+
X-Attribution: sb
From: Steven L Baur <steve@miranova.com>
In-Reply-To: Jens Lautenbacher's message of 09 Jan 1997 09:09:05 +0100
Mime-Version: 1.0 (generated by tm-edit 7.100)
Content-Type: text/plain; charset=US-ASCII
Date: 10 Jan 1997 23:28:06 -0800
Message-ID: <m2loa0u0vt.fsf_-_@altair.xemacs.org>
Lines: 39
X-Mailer: Red Gnus v0.80/XEmacs 20.0

Jens Lautenbacher writes:

> Steven L Baur <steve@miranova.com> writes:
>> 
Jens> Conclusion: It's not only atomic that is broken, it's also
Jens> read-only (I know one can argue about that point).

Relayed Ben Wing comment:
It's no wonder there's brokenness in atomic extents they weren't
really finished.

>> I thought I fixed the read-only brokenness.  Sigh.

> Oh yessss! There is some progress made! :-) I tried this actually on
> 19.14. Just did the same with 19.15 and the read-only thingie works
> now! (on killing it chokes with "peculiar error
> (text-read-only...)")

Ben brought to my attention that I made the wrong `fix' on this (a
lisp patch to kill-region and a proper `fix' would be to fix the C
routine in extents.c that does this checking.  Except that the 19.14
behavior is a deliberate feature.

So, in time honored XEmacs tradition, I'm taking an opinion poll for
consensus. :-)

Do you consider the 19.14 ability to kill read-only extents a
feature you must have, may sometimes need, or don't need at all?

I've already received a number of complaints about the way this works,
and I'm in favor of ditching the feature.  So if you like it, now is
the time to speak up. 

> The other bugs are still there :-(
-- 
steve@miranova.com baur
Unsolicited commercial e-mail will be billed at $250/message.
"That Bill Clinton.  He probably doesn't know how to log on to the
Internet."  -- Rush Limbaugh, noted Computer Expert

