From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.devel Subject: Re: Shouldn't emacs print long lists with newlines? Date: Thu, 29 Aug 2019 09:46:12 +0200 Message-ID: <5705f993-6baf-e1ac-acd4-652bd785379d@gmx.at> References: <87muglxxns.fsf@web.de> <9535bbe5-cb70-f2be-3d17-010da8a4be1b@gmx.at> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="239380"; mail-complaints-to="usenet@blaine.gmane.org" Cc: Michael Heerdegen , ndame , "emacs-devel@gnu.org" To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Aug 29 09:54:41 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1i3FGS-00106d-Oc for ged-emacs-devel@m.gmane.org; Thu, 29 Aug 2019 09:54:40 +0200 Original-Received: from localhost ([::1]:46618 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i3FGQ-00084S-6X for ged-emacs-devel@m.gmane.org; Thu, 29 Aug 2019 03:54:38 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49364) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i3F8k-00048c-LT for emacs-devel@gnu.org; Thu, 29 Aug 2019 03:46:43 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i3F8h-00020c-Iw for emacs-devel@gnu.org; Thu, 29 Aug 2019 03:46:41 -0400 Original-Received: from mout.gmx.net ([212.227.17.20]:41337) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1i3F8h-0001zn-8u for emacs-devel@gnu.org; Thu, 29 Aug 2019 03:46:39 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1567064774; bh=MTcFxxN9pZ+75P6O6zsO3pb12aqjF5rhKSgEHra51a4=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=VFpipWqOHq/zV5zH/aK15BzSh02o2tuQuoZx5FEIa9dXxbX49oCVOYQ+hQNuTvx0S YgYcy8qYyiCcPYbBEifCJ6XGaGItsQ9+afIiNYEXjrScTrvBI9CGQW2u468rQ7NjhV orvDCpy+N8OyvKoxRQBM65myEucprLwbot888TSY= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from [192.168.1.101] ([46.125.249.63]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Man6U-1hnMwW2eyo-00KOMU; Thu, 29 Aug 2019 09:46:14 +0200 In-Reply-To: Content-Language: de-DE X-Provags-ID: V03:K1:J11Flln6jEGPL06jR61H4RprTpjklYN9tZS3ItkrOOzQKEpWV0q 2HS5w2NiVt+3PQGzUUJy21UsyTfMWBp3h2l0nmsVCWWonR/sbl2LT2Yq6dM9xmcZG7TpIaa kcwKQkn/JxmCOrPCs/aw/3KH8yEvkM8Q7M4qKK8+CJKh3UPT/30W2mJDBisuqSW/d0vM/ps JB4f87gONoLJlOCq/pSsA== X-UI-Out-Filterresults: notjunk:1;V03:K0:tVT7mW9Bm8w=:9va7OIg4VflPC6QARwJJYJ uGueJRT/nsBNbS9EEF1cur0ULd9V1QoC603K8m21rANAm5Syp/2XJk6cn4wK2JyqSn97pyKer 6QCiF1nUPs4YO+nzCnHPymmnPRt6+p4tfFRxwRhgEKJwfnnW/uLQUyX0sPn2UsOIACY2YPSYI m6/+rRIKTE85Pm9MNbXc2Wbi8f0HBXZ9hdmSHW8BZQbmji+vHFppMPxxjqeIIyWI1h0xRb+7p KOUJ3BxbSsMB1xp1zZY0UwvQdUZ4nVIcDgIcXqBxn3CKDbKwXreO+GMeI/iGkhSmayIH+M3q7 Zu9cfW0MFYa/HGCgCxp6mP2Lk+eSS+0FaKEJ5VN+LLyxAp5tQ8tPMWhhJgx6k9bqJb4vG6tqQ hDk+qXcbG7no/XZrnlWJR3HIEKQURlpKQO2yGm0c+vb75PXiVeov1WLkgIDfNgsf3aCdSzZyi P//tMv+4LXhJAUz6RqMXFWTs9JwzF+EXA1CUQ3xUbFbx6XoO73a83BJ4UWWPBgWDi93Tp3diX LSZB6IrSQRrKs7mnr0xMhUsPB+k+xbBIag4UeHT6TrGY41qhlVc/Awva4ggb8WrYYIoPD3/sF 4RD00uJO7XMWAeXpHg/SqjA+OotuWlbQOPEsBfd8gKhjmqp7CT7J6RGP/NzptlCb1rQ/z+V2i 9O03/N1DzN7Fc66c5+jDFAhoo8CF5/P/6sW72RIQ4WOmbdpLiFcg9fJtHT4ac9dhqiaUPN7uZ eWV5Hsh7leTEkcOr+Dirjnf+rFuPeWUrD2pdm3AkVpU77fByUWHjYL4DU+EBuiFnp/KfIf7x X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 212.227.17.20 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:239668 >> Since you can now customize 'resize-mini-frames' this restriction no >> longer applies (at least not as stated here). > > FWIW, resize-mini-frames doesn't work very well for me: > > - at startup it resizes the frame to a one-line frame of maybe 10-20 > chars long, which is oddly short. The length is updated on the fly, > but I find this a bit annoying. Nothing too serious tho. You could try to customize 'fit-frame-to-buffer-sizes' for this. > - I have my minibuffer frame at the bottom of the screen. When it grows > to two or more lines, it correctly moves up. But when it shrinks back > to a single line, it doesn't move back down, so it ends up "near" the > bottom rather than at the bottom. Attaching a frame to the bottom of the screen is more tricky. I'm afraid it wouldn't even help to set the second element of 'fit-frame-to-buffer-margins' to a value that just fits into the display. > The second problem is probably partly linked to the window-manager, but > I've found size-varying windows at the bottom of the screen to be poorly > handled under X11 in general (not only with the window-manager > I'm using), so I think I'd have to move my minibuffer-only frame to the > top of the screen to avoid those problem :-( The solution is to write your own function to (1) resize your frame less noisily and, once you know its size, (2) make sure the minibuffer frame's bottom aligns with the bottom of the workarea where it appears and (3) set 'resize-mini-frames' to that function. >>> , so spreading the output on several >>> lines is not always a good solution. ] > > So this still holds :-( It shouldn't since it negatively impacts the design of solutions for adjustable minibuffer windows. martin