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: 43996@debbugs.gnu.org
Subject: bug#43996: 26.3; Please document frame parameter `modeline' in the Elisp manual
Date: Thu, 15 Oct 2020 08:18:25 -0700 (PDT)	[thread overview]
Message-ID: <c50e35ab-699d-43b4-8ee3-ee1159630dbd@default> (raw)
In-Reply-To: <87362gymmk.fsf@gnus.org>

> Where did you happen onto the modeline frame parameter?

I see it when I invoke function `frame-parameters'.

I don't have it in any of my code.  It must be coming
from Emacs itself.

> Reading the code, it looks like internal bookkeeping, and is always set
> on the C level from f->wants_modeline, which again is only set to false
> in make_minibuffer_frame.

Thanks for that info.  That corresponds to what I
see.  I cannot add a mode-line to a standalone
minibuffer frame, it seems.  See bug #43997 for a
request to be able to do that.

> So it doesn't look like a frame parameter that can be set by the user,
> if I'm reading the code correctly, and therefore shouldn't be documented.

Can't be set, but can be seen.  And you can
_seemingly_ set it.  You get no error or direct
indication that it doesn't get set, when you try
to set it.  So at the very least, its visibility
and apparent setting can mislead/confuse users.
If it were entirely invisible from Lisp, then,
yes, it wouldn't need to be described/explained.

The fact that you can't really set it should
maybe be doc'd.  Or at least the fact that
non-nil means there is a mode-line (or whatever
it really means), and that a standalone
minibuffer frame can't have a mode-line (but
why not?).





  reply	other threads:[~2020-10-15 15:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-14 21:11 bug#43996: 26.3; Please document frame parameter `modeline' in the Elisp manual Drew Adams
2020-10-15  7:27 ` Lars Ingebrigtsen
2020-10-15 15:18   ` Drew Adams [this message]
2020-10-15 15:46     ` Eli Zaretskii
2020-10-15 13:46 ` Eli Zaretskii
     [not found] <<c681ba8e-b2c4-4db0-826f-520a6e974bb1@default>
     [not found] ` <<83r1pzy53l.fsf@gnu.org>
2020-10-15 15:23   ` Drew Adams
2020-10-15 15:49     ` Eli Zaretskii
2021-09-25 15:25       ` Stefan Kangas
     [not found] ` <<87362gymmk.fsf@gnus.org>
     [not found]   ` <<c50e35ab-699d-43b4-8ee3-ee1159630dbd@default>
     [not found]     ` <<837drrxzit.fsf@gnu.org>
2020-10-15 16:17       ` Drew Adams

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=c50e35ab-699d-43b4-8ee3-ee1159630dbd@default \
    --to=drew.adams@oracle.com \
    --cc=43996@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).