zsh-users
 help / color / mirror / code / Atom feed
From: Grant Taylor <gtaylor@tnetconsulting.net>
To: zsh-users@zsh.org
Subject: Re: Is there a way of getting current xterm buffer?
Date: Wed, 13 Sep 2023 10:14:29 -0500	[thread overview]
Message-ID: <ee1f04c1-5203-7b92-a5d9-6f98c6414413@tnetconsulting.net> (raw)
In-Reply-To: <CAKc7PVDmdYC+7k5gLTabqmm=iSQg0W7oMLN3R=Na4W=Qmaz-8w@mail.gmail.com>

Pre-Script:  As others have said, this probably isn't a Zsh question.

On 9/13/23 2:48 AM, Sebastian Gniazdowski wrote:
> Hi,

Hi,

> Is there a way to somehow read screen-text

I'm not aware of one.

But my ignorance doesn't preclude it from existing.

> I've have had hopes for it when reading xtermctl and promptnl (this 
> function reads cursor position, so I've thought that maybe it could 
> read the character at given position…), but no success at the end.

I'd suggest skimming / reading the XTerm Control Sequences page.

Link - ctlseqs(ms) - XTerm Control Sequences
  - https://www.invisible-island.net/xterm/ctlseqs/ctlseqs.html

N.B. the ctlseqs page is the most complete that I've found for XTerm -- 
which makes sense given the source.  The only other thing beyond that is 
to delve into the manuals for various other terminals.

XTerm should implement everything on it's ctlseqs page.

I've found that most of the control sequences that XTerm and fancier DEC 
terminals support aren't even a glimmer in the eye of most terminal 
emulator programmers.

Finally, I find the idea of allowing programs to read existing text on 
the screen to be a potential security violation.



-- 
Grant. . . .
unix || die



  parent reply	other threads:[~2023-09-13 15:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13  7:48 Sebastian Gniazdowski
2023-09-13  9:16 ` Roman Perepelitsa
2023-09-13 14:35   ` A. Wik
2023-09-13 15:14 ` Grant Taylor [this message]
2023-09-13 15:18   ` Roman Perepelitsa
2023-09-13 16:01     ` Oliver Kiddle
2023-09-13 16:10       ` Roman Perepelitsa
2023-09-13 18:59       ` Grant Taylor
2023-09-19 22:21         ` Sebastian Gniazdowski
2023-09-20  3:05           ` Grant Taylor
2023-09-20 12:28             ` Sebastian Gniazdowski
2023-09-21 18:05               ` Grant Taylor

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=ee1f04c1-5203-7b92-a5d9-6f98c6414413@tnetconsulting.net \
    --to=gtaylor@tnetconsulting.net \
    --cc=zsh-users@zsh.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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).