From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Support "\n" in icomplete-separator Date: Wed, 11 Nov 2020 11:22:32 +0000 Message-ID: References: <20201105235735.oxouuek66ehu5o45@Ergus> <20201106151541.dpgep7borlja25su@Ergus> <837dqv5huk.fsf@gnu.org> <83mtzp2qj0.fsf@gnu.org> <83r1p11369.fsf@gnu.org> Reply-To: Gregory Heytings Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="11924"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Alpine 2.22 (NEB 394 2020-01-19) Cc: Eli Zaretskii , monnier@iro.umontreal.ca, spacibba@aol.com, Andrii Kolomoiets , emacs-devel@gnu.org To: martin rudalics Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Nov 11 12:23:26 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kcoDm-0002xq-1J for ged-emacs-devel@m.gmane-mx.org; Wed, 11 Nov 2020 12:23:26 +0100 Original-Received: from localhost ([::1]:42386 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kcoDl-00034v-4D for ged-emacs-devel@m.gmane-mx.org; Wed, 11 Nov 2020 06:23:25 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49470) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kcoDF-0002d1-Ca for emacs-devel@gnu.org; Wed, 11 Nov 2020 06:22:53 -0500 Original-Received: from mx.sdf.org ([205.166.94.24]:52700) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kcoDC-0007C0-Uj; Wed, 11 Nov 2020 06:22:53 -0500 Original-Received: from sdf.org (IDENT:ghe@faeroes.freeshell.org [205.166.94.9]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 0ABBMZcs029960 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Wed, 11 Nov 2020 11:22:36 GMT Original-Received: (from ghe@localhost) by sdf.org (8.15.2/8.12.8/Submit) id 0ABBN4IH014141; Wed, 11 Nov 2020 11:23:04 GMT In-Reply-To: Received-SPF: pass client-ip=205.166.94.24; envelope-from=ghe@sdf.org; helo=mx.sdf.org X-detected-operating-system: by eggs.gnu.org: First seen = 2020/11/11 04:07:35 X-ACL-Warn: Detected OS = ??? X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:259009 Archived-At: >>> If an application has a truly expandable minibuffer window or a normal >>> window at its hands, it can try to show completions vertically. With >>> the default minibuffer window, it should always behave as if only one >>> line were available. >> >> Why? The default value for max-mini-window-height is 0.25 (at least >> since Emacs 21), which means that in a default 80x24 terminal the >> minibuffer can be 6 lines tall. > > I explained earlier why this is not generally true. Have a look at the > code of 'window--resize-root-window-vertically'. > Yes of course, you are correct, it is not always true that the minibuffer can be expanded to 0.25 * frame-height. I should have said "which means that in a default 80x24 terminal the minibuffer can _normally_ be 6 lines tall." The exceptions are however orthogonal to the request to give applications the control on how the contents of the minibuffer should preferably be displayed: should it preferably start at the beginning of buffer (point-min), or should it preferably start at the beginning of the line on which the cursor is? ATM the latter behavior is the only possibility (except with the code I sent to Andrii yesterday).