all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Lars Ingebrigtsen <larsi@gnus.org>,
	Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 10670@debbugs.gnu.org
Subject: bug#10670: `fullscreen' frame parameter ill-named
Date: Wed, 20 Jan 2021 19:29:31 +0100	[thread overview]
Message-ID: <0adfd5c9-e194-9b26-24b6-db7636ed0709@gmx.at> (raw)
In-Reply-To: <874kjbo6ts.fsf@gnus.org>

 >> The frame parameter `fullscreen' is ill-named: I think that it should be
 >> renamed to `maximized' with accepted values nil, `vertical',
 >> `horizontal', `both', or `fullscreen'.
 >
 > I think that makes sense, but I'm not sure just how we would deprecate
 > something like that.  We could introduce a `maximized' parameter and use
 > it in preference of `fullscreen', and add some special code to issue a
 > (run-time?) deprecation warning...  but I'm not sure the effort (on our
 > part) and pain (for the users) would be worth it.
 >
 > Anybody got any opinions here?

'maximized' is a WM concept, usually has an API and pretty well defined
semantics there (show a title bar with the corresponding indicator, do
not show the outer borders, cover the entire working area) and has
little or nothing to do with the other values (except that they are
mutually exclusive).  So the proposed renaming would be misguided IMHO.

martin





  reply	other threads:[~2021-01-20 18:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31  1:52 bug#10670: `fullscreen' frame parameter ill-named Stefan Monnier
2021-01-20 17:29 ` Lars Ingebrigtsen
2021-01-20 18:29   ` martin rudalics [this message]
2021-01-20 19:59     ` Stefan Monnier
2021-01-21 14:38       ` Lars Ingebrigtsen
2021-01-21 14:57         ` Stefan Monnier
2021-01-27  4:15           ` Lars Ingebrigtsen

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

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

  git send-email \
    --in-reply-to=0adfd5c9-e194-9b26-24b6-db7636ed0709@gmx.at \
    --to=rudalics@gmx.at \
    --cc=10670@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.