From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.help Subject: RE: Method to hide minibuffer Date: Tue, 28 May 2019 10:33:57 -0700 (PDT) Message-ID: References: <20190528073932.GA31104@tuxteam.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="208797"; mail-complaints-to="usenet@blaine.gmane.org" To: tomas@tuxteam.de, help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue May 28 19:39:18 2019 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hVg4C-000sCY-KG for geh-help-gnu-emacs@m.gmane.org; Tue, 28 May 2019 19:39:16 +0200 Original-Received: from localhost ([127.0.0.1]:40222 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hVg4B-0001cF-DN for geh-help-gnu-emacs@m.gmane.org; Tue, 28 May 2019 13:39:15 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:42818) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hVfzI-0006Mj-Nq for help-gnu-emacs@gnu.org; Tue, 28 May 2019 13:34:13 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hVfzH-0006yL-Co for help-gnu-emacs@gnu.org; Tue, 28 May 2019 13:34:12 -0400 Original-Received: from userp2130.oracle.com ([156.151.31.86]:49520) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hVfzH-0006wm-3H for help-gnu-emacs@gnu.org; Tue, 28 May 2019 13:34:11 -0400 Original-Received: from pps.filterd (userp2130.oracle.com [127.0.0.1]) by userp2130.oracle.com (8.16.0.27/8.16.0.27) with SMTP id x4SHTEWJ023708; Tue, 28 May 2019 17:34:07 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=mime-version : message-id : date : from : sender : to : subject : references : in-reply-to : content-type : content-transfer-encoding; s=corp-2018-07-02; bh=JN/U13c6FnthQvaLYtuVUEIE61VDddbZSH9DE54KAfc=; b=owkv4XNxgO2a5Z4+NZTc4hjkQcMtrvqjzYFVmy6feFgmc6CVYjnACirc16rvkwazzjlq +h+MK2mfFC8aplt5Ck94EkIEaQ1V08MGasmYLnHpuR7Q4kvKy/JTAmGGHUnBm/Cpfe7W 8ye98a5oXYWKummsBcJf4LS1uXvx9vjIWJ8Cy1a1BfuuRkl/Sz7mdJ8U6Ts+/bf1wYBn M9bvekUUm5Bvv3d6plQJ2MSWm4U7cqGJ4sa6R3nFRcxrPlursADdcFTppTCFI/KJTNsx 6hSdwlecUkblADK9AZPgL7qg4mBiMGHgE+1TS/Ne/5z9xXF//OPlYGn/M4I6+jkDf+Iy mQ== Original-Received: from userp3030.oracle.com (userp3030.oracle.com [156.151.31.80]) by userp2130.oracle.com with ESMTP id 2spw4tct53-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 28 May 2019 17:34:07 +0000 Original-Received: from pps.filterd (userp3030.oracle.com [127.0.0.1]) by userp3030.oracle.com (8.16.0.27/8.16.0.27) with SMTP id x4SHXKwE047690; Tue, 28 May 2019 17:34:07 GMT Original-Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by userp3030.oracle.com with ESMTP id 2ss1fn0bak-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 28 May 2019 17:34:06 +0000 Original-Received: from abhmp0018.oracle.com (abhmp0018.oracle.com [141.146.116.24]) by userv0121.oracle.com (8.14.4/8.13.8) with ESMTP id x4SHXwuD011318; Tue, 28 May 2019 17:34:00 GMT In-Reply-To: <20190528073932.GA31104@tuxteam.de> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9.1 (1003210) [OL 16.0.4849.0 (x86)] X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9271 signatures=668687 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=961 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1905280111 X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9271 signatures=668687 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=995 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1905280111 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic] X-Received-From: 156.151.31.86 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:120678 Archived-At: > you can confine it to a frame you don't show: >=20 > https://stackoverflow.com/questions/5079466/hide-emacs-echo-area-during-i= nactivity Yes, it's possible to do things like use a separate minibuffer frame, and then make that frame invisible or transparent (alpha) or lowered in the stacking order - and then bring it back normally when you are prompted for minibuffer input. But you _really_ do NOT want to do that, OP. One good reason is that the same real estate is used for the echo area: messages to you. And messages to you include prompts for non-minibuffer input. Consider just these two uses of the echo area, for instance: Isearch (it does NOT use the minibuffer, even though that's not obvious) and prompts to read input other than minibuffer input. The latter includes prompts when reading a character, such as is done by `y-or-n-p' and `query-replace*'. Any user interaction that makes use of the echo area will be lost (not seen) if you hide that screen real estate.