unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 53478-done@debbugs.gnu.org
Subject: bug#53478: 26.3; Document text-terminal (non)support of pixel-relevant features
Date: Sun, 23 Jan 2022 18:53:42 +0200	[thread overview]
Message-ID: <83ee4yl7ft.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB54888B73DE23381FC11A3265F35D9@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Sun, 23 Jan 2022 16:25:12 +0000)

> From: Drew Adams <drew.adams@oracle.com>
> Date: Sun, 23 Jan 2022 16:25:12 +0000
> 
> I tried to help with this user question:
> 
> https://emacs.stackexchange.com/q/70231/105
> 
> I'm no expert on this.  I guessed that Emacs in terminal mode can't
> support most pixel-level operations.

That question has nothing to do with pixel-level operations.  It asks
about functions like x-display-pixel-width that are not available in a
build --without-x.

> I wanted to point the user to the Emacs manual about this.  I tried to
> find info about it with `i' using keyword `terminal' (even with
> substring matching for completions).  I found nothing.  Likewise, with
> keyword `pixel'.

I see no reason to say in the manual anything about this that we don't
already do.  Every place that talks about pixels either says it's
relevant to graphical displays, or discusses stiff that is only
relevant to GUI.  The doc string of x-display-pixel-width, for
example, says:

  Return the width in pixels of the X display TERMINAL.
                                    ^^^^^^^^^
So I don't think we should do anything here, and I'm closing this bug
report.





      reply	other threads:[~2022-01-23 16:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-23 16:25 bug#53478: 26.3; Document text-terminal (non)support of pixel-relevant features Drew Adams
2022-01-23 16:53 ` Eli Zaretskii [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=83ee4yl7ft.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=53478-done@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /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).