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: buffer name completion is case-sensitive now Date: Sun, 08 Jun 2008 21:28:41 +0300 Message-ID: References: <002201c8c986$68802b90$0200a8c0@us.oracle.com> <002501c8c98f$d66552d0$0200a8c0@us.oracle.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1212949737 6512 80.91.229.12 (8 Jun 2008 18:28:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 8 Jun 2008 18:28:57 +0000 (UTC) Cc: emacs-devel@gnu.org, rileyrgdev@googlemail.com, jpw@pobox.com To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jun 08 20:29:39 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1K5Pe6-00036d-16 for ged-emacs-devel@m.gmane.org; Sun, 08 Jun 2008 20:29:38 +0200 Original-Received: from localhost ([127.0.0.1]:60648 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K5PdI-0005xb-PW for ged-emacs-devel@m.gmane.org; Sun, 08 Jun 2008 14:28:48 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K5PdE-0005xG-SX for emacs-devel@gnu.org; Sun, 08 Jun 2008 14:28:44 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K5PdE-0005wx-Dt for emacs-devel@gnu.org; Sun, 08 Jun 2008 14:28:44 -0400 Original-Received: from [199.232.76.173] (port=58358 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K5PdE-0005ws-74 for emacs-devel@gnu.org; Sun, 08 Jun 2008 14:28:44 -0400 Original-Received: from mtaout3.012.net.il ([84.95.2.7]:28910) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K5PdD-0006P4-VV for emacs-devel@gnu.org; Sun, 08 Jun 2008 14:28:44 -0400 Original-Received: from HOME-C4E4A596F7 ([80.230.28.131]) by i_mtaout3.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0K2500JYHQOR6581@i_mtaout3.012.net.il> for emacs-devel@gnu.org; Sun, 08 Jun 2008 21:43:40 +0300 (IDT) In-reply-to: <002501c8c98f$d66552d0$0200a8c0@us.oracle.com> X-012-Sender: halo1@inter.net.il X-detected-kernel: by monty-python.gnu.org: Solaris 9.1 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: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:98707 Archived-At: > From: "Drew Adams" > Date: Sun, 8 Jun 2008 10:48:18 -0700 > Cc: 'Richard G Riley' , > 'Emacs-Devel' > > > With the introduction of `read-file-name-completion-ignore-case' > > there's less need to have an MS-Windows specific > > default value of `completion-ignore-case'. > > Irrelevant. This is about completion of _buffer_ names, not file names. Try > completing `*m' to *Messages* now - doesn't work. > > No one is questioning what `read-file-name' should do; this is about > `completing-read' with buffer names. Buffer-name completion was case-insensitive on Windows because there was no mechanism to request case-insensitive file-name completion except making _all_ completions case-insensitive. Now there _is_ a way to request that for file names only. I'm not saying that I'm necessarily in favor of the change, I'm just explaining what John was saying, because it's not ``irrelevant''. > > Are there any other examples > > where case sensitivity is problematic? > > Dunno what you mean. > > Are you proposing to also change the traditional behavior for other kinds of > completion? I certainly hope other such changes won't be made. > > Or are you asking if the same improper behavior occurs now for more than just > buffer names? I've only noticed it wrt buffer names. > > Please revert this "experimental" change. Please at least explain why you think buffer-name completion should be case-insensitive, on Windows or elsewhere. Otherwise, this is not a rational discussion, and will lead nowhere.