From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: New text property: `inhibit-read-only' Date: Sun, 16 Nov 2014 23:30:14 -0500 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1416198658 6849 80.91.229.3 (17 Nov 2014 04:30:58 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 17 Nov 2014 04:30:58 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 17 05:30:51 2014 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 1XqDxj-0001LT-2C for ged-emacs-devel@m.gmane.org; Mon, 17 Nov 2014 05:30:51 +0100 Original-Received: from localhost ([::1]:46050 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XqDxi-00006f-Lv for ged-emacs-devel@m.gmane.org; Sun, 16 Nov 2014 23:30:50 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59324) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XqDxG-00006Q-Tt for emacs-devel@gnu.org; Sun, 16 Nov 2014 23:30:30 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XqDx9-0004TS-Dn for emacs-devel@gnu.org; Sun, 16 Nov 2014 23:30:22 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:18878) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XqDx9-0004TN-9e for emacs-devel@gnu.org; Sun, 16 Nov 2014 23:30:15 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AsUIAGA2ZVSnWBqE/2dsb2JhbABbgw6KYssMBAICgRwXAQEBAQEBfIQDAQEDAVYoCws0EhQYDVKIHQnRBAELIJEbFoQ1BYwLk1qHBI4vhBofgnsBAQE X-IPAS-Result: AsUIAGA2ZVSnWBqE/2dsb2JhbABbgw6KYssMBAICgRwXAQEBAQEBfIQDAQEDAVYoCws0EhQYDVKIHQnRBAELIJEbFoQ1BYwLk1qHBI4vhBofgnsBAQE X-IronPort-AV: E=Sophos;i="5.07,380,1413259200"; d="scan'208";a="97156676" Original-Received: from 167-88-26-132.cpe.teksavvy.com (HELO pastel.home) ([167.88.26.132]) by ironport2-out.teksavvy.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 16 Nov 2014 23:30:14 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 77E7A880A; Sun, 16 Nov 2014 23:30:14 -0500 (EST) In-Reply-To: (Lars Magne Ingebrigtsen's message of "Sun, 16 Nov 2014 23:45:30 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.181 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:177388 Archived-At: > As previously discussed (like a year or two ago), we have certain modes > that basically have read-only buffers, but that need certain bits to be > writable. Right, like Custom buffers. > eww is one of them -- we need to write things into search fields and the > like. > So I've just implemented an `inhibit-read-only' text property and pushed > it. What is different that the solution used in Custom buffers can't be used or doesn't work well in eww? Stefan