From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Inhibiting read-only Date: Thu, 20 Jun 2013 20:45:02 +0300 Message-ID: <83wqpooew1.fsf@gnu.org> References: <838v24pyhl.fsf@gnu.org> <8338scpvcn.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1371750372 504 80.91.229.3 (20 Jun 2013 17:46:12 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 20 Jun 2013 17:46:12 +0000 (UTC) Cc: monnier@IRO.UMontreal.CA, cloos@jhcloos.com, emacs-devel@gnu.org To: Lars Magne Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jun 20 19:46:12 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Upivt-0000d2-B0 for ged-emacs-devel@m.gmane.org; Thu, 20 Jun 2013 19:46:05 +0200 Original-Received: from localhost ([::1]:35273 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Upivs-0002ku-Vb for ged-emacs-devel@m.gmane.org; Thu, 20 Jun 2013 13:46:04 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57681) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Upive-0002Xa-0Z for emacs-devel@gnu.org; Thu, 20 Jun 2013 13:45:53 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UpivX-0001hM-W3 for emacs-devel@gnu.org; Thu, 20 Jun 2013 13:45:49 -0400 Original-Received: from mtaout23.012.net.il ([80.179.55.175]:57590) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UpivX-0001gz-OD for emacs-devel@gnu.org; Thu, 20 Jun 2013 13:45:43 -0400 Original-Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0MOP00B00D8ILM00@a-mtaout23.012.net.il> for emacs-devel@gnu.org; Thu, 20 Jun 2013 20:44:52 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MOP00BJHDASC880@a-mtaout23.012.net.il>; Thu, 20 Jun 2013 20:44:52 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.175 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:160761 Archived-At: > From: Lars Magne Ingebrigtsen > Cc: monnier@IRO.UMontreal.CA, cloos@jhcloos.com, emacs-devel@gnu.org > Date: Thu, 20 Jun 2013 19:09:39 +0200 > > Eli Zaretskii writes: > > > I don't see why the former would be a problem. If you really want it > > to work, you can bind it to a command that removes the read-only > > properties. > > Sure. But why would we? A read-only buffer is a simple and > understandable interface that gives us this already. But the read-only buffer doesn't fit your bill, it requires that you develop a non-trivial infrastructure we currently lack. Isn't it better to use existing features instead? > > As for the latter, can you elaborate about the annoyance, since > > read-only is in yank-excluded-properties? > > Oh, is that a new thing? AFAIR, it's very old. > Having to re-apply properties to ensure that we still are read-only > after inserting text (modulo stickiness) is pretty annoying. I don't see the annoyance. Can you elaborate the difficulties you envision? > Being able to use a read-only buffer, but have some text be modifiable, > seems like a simple, obvious and symmetrical thing to do. But marking the entire buffer read-only and then using text properties to inhibit that for some portions of the text sounds wrong to me. Especially when we already have facilities for making only part of the text read-only.