all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: Missing frame parameters on tty's
Date: Thu, 03 Dec 2015 13:34:35 +0200	[thread overview]
Message-ID: <83lh9bix4k.fsf@gnu.org> (raw)
In-Reply-To: <20151203111815.GE2136@acm.fritz.box>

> Date: Thu, 3 Dec 2015 11:18:15 +0000
> Cc: emacs-devel@gnu.org
> From: Alan Mackenzie <acm@muc.de>
> 
> > Why single out those two?
> 
> Because they're the two over which a misunderstanding has happened.

Doesn't sound like a compelling reason to me.

> > Especially since it make no sense at all to have them on TTY frames.
> 
> I think it does.  A tty frame's top left corner starts 0 "pixels" from
> the top and from the left of the screen.

And it cannot start at any other point.  What sense does it make to
have frame parameters whose values are known in advance, and cannot be
changed?

> Anyhow, I've been reading the "Window Frame Parameters" chapter in the
> Elisp manual, in particular "Position Parameters".  The description of
> `left' and `top' immediately follow a statement that measurements on a
> TTY are in terms of characters or lines.  This cannot help but give the
> impression `left' and `top' _are_ available on TTYs.  Perhaps if we
> aren't going to give TTYs these parameters, we should amend that manual
> page to say explicitly that TTYs don't have them.

Patches to that effect are welcome.

Thanks.



  reply	other threads:[~2015-12-03 11:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 22:15 Missing frame parameters on tty's Alan Mackenzie
2015-12-02 23:07 ` Juanma Barranquero
2015-12-03  7:34 ` Eli Zaretskii
2015-12-03  8:30   ` Alan Mackenzie
2015-12-03 10:27     ` Eli Zaretskii
2015-12-03 11:18       ` Alan Mackenzie
2015-12-03 11:34         ` Eli Zaretskii [this message]
2016-01-18 16:02           ` Alan Mackenzie
2016-01-18 16:11             ` Eli Zaretskii
2016-01-18 17:03               ` Alan Mackenzie
2016-01-18 17:07                 ` Eli Zaretskii
2016-01-18 17:55                   ` Alan Mackenzie
2016-01-18 18:41                     ` Eli Zaretskii

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=83lh9bix4k.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=acm@muc.de \
    --cc=emacs-devel@gnu.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 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.