From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: ! in Dired--what was the outcome? Date: Fri, 15 Oct 2004 10:15:46 +0200 Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Message-ID: References: <87vfdgezro.fsf@jurta.org> <200410130301.i9D31GM02856@raven.dms.auburn.edu> <16751.4154.953643.585450@zarniwoop.ms25.local> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1097828287 9639 80.91.229.6 (15 Oct 2004 08:18:07 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 15 Oct 2004 08:18:07 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 15 10:18:01 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1CINHl-0000J9-00 for ; Fri, 15 Oct 2004 10:18:01 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CINOt-0001Yg-3e for ged-emacs-devel@m.gmane.org; Fri, 15 Oct 2004 04:25:23 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CINN4-0001EX-PL for emacs-devel@gnu.org; Fri, 15 Oct 2004 04:23:30 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CINN3-0001EG-QQ for emacs-devel@gnu.org; Fri, 15 Oct 2004 04:23:30 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CINN3-0001EA-Dx for emacs-devel@gnu.org; Fri, 15 Oct 2004 04:23:29 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CINFc-0003g8-7u for emacs-devel@gnu.org; Fri, 15 Oct 2004 04:15:48 -0400 Original-Received: from localhost ([127.0.0.1] helo=lola.goethe.zz) by fencepost.gnu.org with esmtp (Exim 4.34) id 1CINFb-00013F-PA; Fri, 15 Oct 2004 04:15:48 -0400 Original-To: Reinhard Kotucha In-Reply-To: <16751.4154.953643.585450@zarniwoop.ms25.local> (Reinhard Kotucha's message of "Fri, 15 Oct 2004 01:48:10 +0200") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/21.3.50 (gnu/linux) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 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 Xref: main.gmane.org gmane.emacs.devel:28424 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:28424 Reinhard Kotucha writes: >>>>>> "David" == David Kastrup writes: > > > If you really need {}, you can quote one > > of the two characters, like '{'} or {\}. > > I'd prefer to force people to quote both braces, for example '{}' or This form is useless, as it does not hide the {} pattern. We don't want the command line to start messing with quoting characters if we can avoid it. If you want symmetry, use {''} instead. > \{\}. That's ok. But I don't see why one should _force_ anybody to use that. > Otherwise syntax checkers have to know that there is something > special. Syntax checkers? On ad-hoc entered dired command lines? Are we talking about the same thing still? Ok, brace matching will complain, but that is no catastrophe. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum