From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.bugs Subject: Re: user has no business toggling overwrite-mode in read-only buffers Date: 20 Apr 2003 00:39:24 +0200 Organization: T-Online Sender: bug-gnu-emacs-bounces+gnu-bug-gnu-emacs=m.gmane.org@gnu.org Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1050791997 5956 80.91.224.249 (19 Apr 2003 22:39:57 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sat, 19 Apr 2003 22:39:57 +0000 (UTC) Original-X-From: bug-gnu-emacs-bounces+gnu-bug-gnu-emacs=m.gmane.org@gnu.org Sun Apr 20 00:39:55 2003 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1970zy-0001Xl-00 for ; Sun, 20 Apr 2003 00:39:55 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 19710L-0007Z2-03 for gnu-bug-gnu-emacs@m.gmane.org; Sat, 19 Apr 2003 18:40:17 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13) id 1970zv-00075r-00 for bug-gnu-emacs@gnu.org; Sat, 19 Apr 2003 18:39:51 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13) id 1970zs-0006zd-00 for bug-gnu-emacs@gnu.org; Sat, 19 Apr 2003 18:39:48 -0400 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 1970zr-0006wm-00 for bug-gnu-emacs@gnu.org; Sat, 19 Apr 2003 18:39:47 -0400 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by fencepost.gnu.org with esmtp (Exim 4.10) id 1970zr-0008V1-00 for gnu-emacs-bug@prep.ai.mit.edu; Sat, 19 Apr 2003 18:39:47 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13) id 1970zp-0006t2-00 for gnu-emacs-bug@prep.ai.mit.edu; Sat, 19 Apr 2003 18:39:46 -0400 Original-Received: from mailout11.sul.t-online.com ([194.25.134.85]) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 1970zc-0006PV-00 for gnu-emacs-bug@prep.ai.mit.edu; Sat, 19 Apr 2003 18:39:32 -0400 Original-Received: from imh00.t-online.com by mailout11.sul.t-online.com with esmtp id 1970zV-0004GR-00; Sun, 20 Apr 2003 00:39:25 +0200 Original-Received: from news.t-online.com by imh00.t-online.com with esmtp id 1970zV-0000B4-00; Sun, 20 Apr 2003 00:39:25 +0200 Original-Received: from news by news.t-online.com with local id 1970zU-0006M2-00; Sun, 20 Apr 2003 00:39:24 +0200 Original-To: gnu-emacs-bug@prep.ai.mit.edu Original-Path: news.t-online.com!not-for-mail Original-Newsgroups: gnu.emacs.bug Original-Lines: 24 Original-X-Trace: news.t-online.com 1050791964 02 23308 QUr2E6sVT9YtSU 030419 22:39:24 Original-X-Complaints-To: abuse@t-online.com X-ID: GbcId0ZZoeZDwbY7eTZB5HMlDS8dgoHY1+OOuzmf+jvR6PYDWfS+ow X-Face: 2FEFf>]>q>2iw=B6,xrUubRI>pR&Ml9=ao@P@i)L:\urd*t9M~y1^:+Y]'C0~{mAl`oQuAl \!3KEIp?*w`|bL5qr,H)LFO6Q=qx~iH4DN;i"; /yuIsqbLLCh/!U#X[S~(5eZ41to5f%E@'ELIi$t^ Vc\LWP@J5p^rst0+('>Er0=^1{]M9!p?&:\z]|;&=NP3AhB!B_bi^]Pfkw User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Bug reports for GNU Emacs, the Swiss army knife of text editors List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: bug-gnu-emacs-bounces+gnu-bug-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.bugs:4842 X-Report-Spam: http://spam.gmane.org/gmane.emacs.bugs:4842 Dan Jacobson writes: > In a new crackdown on excessive freedoms, prime minister Moi > recommends toggling overwrite-mode be outlawed in read-only buffers. > > In an interview, he was quoted as saying "It just doesn't make sense. > Why should we allow kids to toggle it back and fourth if they can't > possibly use it? They might get the wrong impression, that they can > write stuff! Only later will they find out the real deal." I beg to disagree. One might gear up all necessary resources for an onslaught onto a buffer before one finally disabled read-only-ness. So I find toggling over-write mode a perfectly sensible operation even on read-only buffers. However, to make the case of visual feedback, I would tend to gray out a "toggle overwrite-mode" menu item, while still having it work if you ignored the grayout. Of course, this probably would violate all imaginable user interface guidelines... -- David Kastrup, Kriemhildstr. 15, 44793 Bochum