From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Shouldn't emacs print long lists with newlines? Date: Wed, 28 Aug 2019 13:23:53 -0400 Message-ID: References: <87muglxxns.fsf@web.de> <9535bbe5-cb70-f2be-3d17-010da8a4be1b@gmx.at> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="194391"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: Michael Heerdegen , ndame , "emacs-devel@gnu.org" To: martin rudalics Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Aug 28 19:25:16 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 1i31h1-000oHp-QK for ged-emacs-devel@m.gmane.org; Wed, 28 Aug 2019 19:25:12 +0200 Original-Received: from localhost ([::1]:39166 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i31h0-0005DF-FQ for ged-emacs-devel@m.gmane.org; Wed, 28 Aug 2019 13:25:10 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49887) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i31fz-0004z7-Pl for emacs-devel@gnu.org; Wed, 28 Aug 2019 13:24:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i31fy-0001co-8S for emacs-devel@gnu.org; Wed, 28 Aug 2019 13:24:07 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:29791) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1i31fy-0001bg-1U for emacs-devel@gnu.org; Wed, 28 Aug 2019 13:24:06 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id CB13B100EA1; Wed, 28 Aug 2019 13:24:03 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 8140C100B00; Wed, 28 Aug 2019 13:24:02 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1567013042; bh=tHvvTy0SAb/W7dwOP0mjDi/VRrlEFPVZW0JjKotZTfE=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=LxdtmIWaW7SdSWQaSVyCkkl8hZkSh9fWmGgwbD40YCvmNQyhSFTSOiPf5vNqXt7rb nHctbG5SfMlCV+gVV0XaPYwx9vzxCz/UJ6JlaYfLXsyv318eDaj4b4ed92qWdVGkzW SjyB1kkmLcLmAisL12eeIk+btMK3HHZXuOl7XMXTSNwXlINS9GlLO0UIkvJkFMo52H ewOFoM/okdjqJza5RXcWHycU4fuwbGDzNTOPeHTLE7SlbSJ/VrkGvyXMZocLFJEVQP JAAs87/pteiTt7UBSASUJnbPAac4rqSPAn692FCC2hrPvoy37fF8mOnzMHMdkzENpS 6VpTeP3us6RPQ== Original-Received: from alfajor (modemcable157.163-203-24.mc.videotron.ca [24.203.163.157]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 53894120298; Wed, 28 Aug 2019 13:24:02 -0400 (EDT) In-Reply-To: <9535bbe5-cb70-f2be-3d17-010da8a4be1b@gmx.at> (martin rudalics's message of "Wed, 7 Aug 2019 14:04:33 +0200") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 132.204.25.50 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:239647 Archived-At: >> [ My minibuffer is exactly 1-line tall (and it's a separate frame, so >> Emacs is not allowed to grow it) > 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. - 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. 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 :-( >> , so spreading the output on several >> lines is not always a good solution. ] So this still holds :-( Stefan