unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "43997@debbugs.gnu.org" <43997@debbugs.gnu.org>
Subject: bug#43997: [External] : Re: bug#43997: 26.3; Be able to have a mode-line for a standalone minibuffer frame
Date: Sun, 6 Jun 2021 15:35:06 +0000	[thread overview]
Message-ID: <SA2PR10MB44748BD15551A8E61370AEB0F3399@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87im2rs248.fsf@gnus.org>

> > Be able to have a mode-line for a standalone minibuffer frame.
> 
> I'm not sure I understand the utility of this -- putting a mode line on
> a standalone minibuffer frame doesn't seem very useful.  Can you explain
> why you'd like to see this?

Be able to use that mode-line for whatever info one
wants.  In particular, info that's relevant to the
current state of the minibuffer.  (And no, things
like `minibuffer-message' are no substitute.)

There are plenty of (standard, predefined) frame
parameters that this or that user might never use
or see used.  I don't show the fringe or the tool
bar, for example, and innumerable users don't show
the menu-bar.  

Why should users of a standalone minibuffer frame
not be able to use this potential information area?

You don't use a standalone minibuffer frame, I
assume.  Perhaps you don't understand the utility
of that either.  Why not take the word of someone
who does use it and does understand its utility?
Letting it be able to show a mode-line would
increase its utility.





      reply	other threads:[~2021-06-06 15:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-14 21:19 bug#43997: 26.3; Be able to have a mode-line for a standalone minibuffer frame Drew Adams
2020-10-15 13:47 ` Eli Zaretskii
2021-06-06 10:45 ` Lars Ingebrigtsen
2021-06-06 15:35   ` Drew Adams [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=SA2PR10MB44748BD15551A8E61370AEB0F3399@SA2PR10MB4474.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=43997@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).