From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: Feature request : Tab-completion for 'shell-comand' Date: Thu, 6 Mar 2008 09:46:27 -0800 Message-ID: <009601c87fb2$01cce2d0$0600a8c0@us.oracle.com> References: <874pbmjgsy.fsf@gmx.de> <874pbknt3j.fsf@tsuchiya.vaj.namazu.org><87mypccg6r.fsf@jurta.org> <87lk4vpxnk.fsf@catnip.gol.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1204825694 8817 80.91.229.12 (6 Mar 2008 17:48:14 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 6 Mar 2008 17:48:14 +0000 (UTC) Cc: 'Juri Linkov' , 'Michael Albinus' , 'TSUCHIYA Masatoshi' , emacs-devel@gnu.org To: "'Miles Bader'" , "'Stefan Monnier'" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Mar 06 18:48:40 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 1JXKCP-0003I0-0v for ged-emacs-devel@m.gmane.org; Thu, 06 Mar 2008 18:48:09 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JXKBr-0003HR-Gj for ged-emacs-devel@m.gmane.org; Thu, 06 Mar 2008 12:47:35 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JXKBn-0003G3-2l for emacs-devel@gnu.org; Thu, 06 Mar 2008 12:47:31 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JXKBk-0003F1-7a for emacs-devel@gnu.org; Thu, 06 Mar 2008 12:47:30 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JXKBk-0003Eu-0e for emacs-devel@gnu.org; Thu, 06 Mar 2008 12:47:28 -0500 Original-Received: from agminet01.oracle.com ([141.146.126.228]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JXKBg-0007pV-2Y; Thu, 06 Mar 2008 12:47:24 -0500 Original-Received: from agmgw2.us.oracle.com (agmgw2.us.oracle.com [152.68.180.213]) by agminet01.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id m26HlJAd007789; Thu, 6 Mar 2008 11:47:19 -0600 Original-Received: from acsmt350.oracle.com (acsmt350.oracle.com [141.146.40.150]) by agmgw2.us.oracle.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id m26CLD0G016382; Thu, 6 Mar 2008 10:47:18 -0700 Original-Received: from inet-141-146-46-1.oracle.com by acsmt350.oracle.com with ESMTP id 3602388521204825583; Thu, 06 Mar 2008 09:46:23 -0800 Original-Received: from dradamslap1 (/141.144.72.2) by bhmail.oracle.com (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 06 Mar 2008 09:46:23 -0800 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <87lk4vpxnk.fsf@catnip.gol.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Thread-Index: Ach/sBrCH8wv7dOyTJSdMrXjNofEugAAK76g X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE X-detected-kernel: by monty-python.gnu.org: Linux 2.4-2.6 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:91524 Archived-At: > > I think that when the minibuffer is active, we should still output > > a message, only differently (as does minibuffer-message). > > Maybe just using minibuffer-message (and changing it so it uses > > plain "message" when the minibuffer is not active) would do the trick. > > I wish _all_ messages would display ala minibuffer-message when the > user's editing in the minibuffer -- the current behavior (temporarily > ovewriting the minibuffer to show messages) is stupid and annoying, > especially given that many errors one gets are fairly trivial or > transient. > > I made a patch to do this sometime before Emacs 21 was released, and > recall various issues popping up though... I think mainly it was the > somewhat more exotic users of message, like quail completion info etc. I find that it depends, though I can't give you a good fer-instance right now. I'm not sure that a blanket change would be appropriate. One disadvantage to `minibuffer-message' in some contexts is its `minibuffer-message-timeout' delay. That can be inappropriate or annoying in some contexts. And the message appears for only a limited time, even if there is no input event. That's usually TRT, but not always, in my experience. Possibly a single DTRT messaging interface can be devised, but I suspect that some code will continue to need to explicitly DTRT on a case-by-case basis.