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: feature/icomplete-vertical Date: Mon, 05 Oct 2020 11:02:17 +0000 Message-ID: References: <20200912133311.6ujtgczj6wyclufy@Ergus> <20200920130435.heye7bk73pm252km@Ergus> <83sgbczj0i.fsf@gnu.org> <83lfh4zfml.fsf@gnu.org> <838sd4z6lz.fsf@gnu.org> <20201001164804.mqqyxtet4ttweuyv@Ergus> <83blhhdy3w.fsf@gnu.org> <87d01xghmt.fsf@gmail.com> <83sgatc8er.fsf@gnu.org> <83mu11c78j.fsf@gnu.org> <87tuv9eygk.fsf@gmail.com> 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="20676"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Alpine 2.22 (NEB 394 2020-01-19) Cc: Eli Zaretskii , spacibba@aol.com, juri@linkov.net, casouri@gmail.com, emacs-devel@gnu.org To: =?ISO-8859-15?Q?Jo=E3o_T=E1vora?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Oct 05 13:04:11 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 1kPOHq-0005GG-EN for ged-emacs-devel@m.gmane-mx.org; Mon, 05 Oct 2020 13:04:10 +0200 Original-Received: from localhost ([::1]:52298 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kPOHp-0003pI-FD for ged-emacs-devel@m.gmane-mx.org; Mon, 05 Oct 2020 07:04:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42894) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kPOGK-0002ob-IY for emacs-devel@gnu.org; Mon, 05 Oct 2020 07:02:37 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:60910) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kPOGE-00038K-9y; Mon, 05 Oct 2020 07:02:36 -0400 Original-Received: from sdf.org (IDENT:ghe@otaku.sdf.org [205.166.94.8]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 095B2K1H023514 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Mon, 5 Oct 2020 11:02:20 GMT Original-Received: (from ghe@localhost) by sdf.org (8.15.2/8.12.8/Submit) id 095B2ebu014637; Mon, 5 Oct 2020 11:02:40 GMT In-Reply-To: <87tuv9eygk.fsf@gmail.com> 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/10/05 06:53:34 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:257104 Archived-At: >> If an application wants to fit the buffer in the window, or display >> some hint about truncation, it's the application's business to do these >> things. > > I guess you can argue that, but this implies there are ways to predict > truncation (since being notified of it seems to be what you're opposed > to). > > So how is the application to know if its n lines, of lengths L = {l1, > ..., li, ..., ln}, it wants to display (not necessarily by buffer > insertion) in the mini-window need truncation and starting in which > line? Does it need to perform calculations with max-mini-window-height? > If so, is there a "canonical" way to perform these calculations that > accounts for fontsizes, frame widths, etc? To be clear, I find this > information useful for other domais, notably designing the way the Eldoc > should show information in the echo area. > This is feasible, but IMHO very (and needlessly) difficult. Basically you need to work with pixel dimensions, and recalculate everything manually: first calculate the (maximal) size of the miniwindow (given the user preferences, in particular max-mini-window-height), then calculate the size of its contents with window-text-pixel-size. You should add one character (or line) at at time, and recalculate the new size each time.