From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: John Yates Newsgroups: gmane.emacs.help Subject: Re: [External] : Re: Is there a way to avoid clobbering minibuffer by messages? Date: Thu, 30 Mar 2023 16:08:33 -0400 Message-ID: References: <3f004ca9-1f71-2c5b-17f1-e154f209e6d3@gmail.com> <83ilei62o6.fsf@gnu.org> <8d94bd37-d657-cf14-c0cb-372cde983ee0@gmail.com> <837cuy5y2m.fsf@gnu.org> <83fs9m42pc.fsf@gnu.org> <83a5zu3z7a.fsf@gnu.org> <835yai3xhh.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="35743"; mail-complaints-to="usenet@ciao.gmane.io" Cc: help-gnu-emacs@gnu.org To: Eli Zaretskii Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Thu Mar 30 22:09:16 2023 Return-path: Envelope-to: geh-help-gnu-emacs@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 1phyaC-00096Z-CY for geh-help-gnu-emacs@m.gmane-mx.org; Thu, 30 Mar 2023 22:09:16 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1phyZm-0000GP-Sw; Thu, 30 Mar 2023 16:08:50 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1phyZl-0000G8-Jv for help-gnu-emacs@gnu.org; Thu, 30 Mar 2023 16:08:49 -0400 Original-Received: from mail-ed1-f42.google.com ([209.85.208.42]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1phyZk-000488-4l; Thu, 30 Mar 2023 16:08:49 -0400 Original-Received: by mail-ed1-f42.google.com with SMTP id r11so81217987edd.5; Thu, 30 Mar 2023 13:08:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680206926; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=X8ZKUD4/FKHx/NtQACBMR235Yi3vC6AnPqYWoGHTbZ0=; b=Fx1pChEMLjBjggzWob2MKUe5Y7Ci470A6l0aOkoFdzJYITuzrqIHSuqiVaZbmW3WG0 n8EZAnO5OGaJsrPIwNQQ3TV+1VMeESect0IZIfyA1/h5x7RxD4fuAW8Tzlt3B4fC1xEr p+X9LedQMkXhWFyaGqYm0bEpWvtwhGjpszGy5lLpzthFrzjMfJ1h3BrIyO+qAk0feyJ8 seAoQmCpkI6BrS8ljjBsnVTMnWFFYBFwcx/1id/qlctkuoGnF7aQgS/mAigHRK2JvPUH vOHF5SvEnZCzUuLy8PyUhyN8P9Xc6uPAGvVhwlS0EPV5FL6h0pXOsmn8n6KK9R6jz3sN h5MA== X-Gm-Message-State: AAQBX9cX6KnpDpehNWjUxVNXdtHB+5o7b8IkL7PdRAleffSG2aKHnKTb lzTrvKeVqWArGQVeGa/IjJX72Vk/kfWcEf5NadTv4l8U X-Google-Smtp-Source: AKy350Y+ce9lVukrYFNXtgY0Mz5uXdW4h04jL2cKdoD/nviQOVIzvrkMtz5SVnYYoIQnFebYFSwW818hpoNY4zi9Yvk= X-Received: by 2002:a17:906:37c8:b0:934:b5d6:14d0 with SMTP id o8-20020a17090637c800b00934b5d614d0mr13032588ejc.2.1680206925730; Thu, 30 Mar 2023 13:08:45 -0700 (PDT) In-Reply-To: <835yai3xhh.fsf@gnu.org> Received-SPF: pass client-ip=209.85.208.42; envelope-from=john.yates.sheets@gmail.com; helo=mail-ed1-f42.google.com X-Spam_score_int: -13 X-Spam_score: -1.4 X-Spam_bar: - X-Spam_report: (-1.4 / 5.0 requ) BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.help:143169 Archived-At: On Thu, Mar 30, 2023 at 2:28=E2=80=AFPM Eli Zaretskii wrote: > > Split how? The Emacs display engine doesn't support column-wise > display that you are describing, it can only do that if the > mini-window is split into two side-by-side windows, but that will run > afoul of many assumptions everywhere that there's at most only one > min-window per frame. It was only an idea based on observing that on my high res screens the full width minibuffer seems overly generous. Hence my imagining side-by-side windows. Honestly, I do not have any real appreciation for the implications of "only one min-window per frame" assumptions. My thinking was that the two side-by-side windows would be children of a single full- width internal window which would in turn be a per-frame singleton. This per-frame internal min-window would contain the per-frame mini-buffer input window and the per-frame echo area output window.