bugGNU Screen - Bugs: bug #23859, //debug window


bug #23859: //debug window

Submitted by:  Micah Cowan <micahcowan>
Submitted on:  Tue 15 Jul 2008 06:32:55 PM UTC  
Category:  Feature Request Severity:  2 - Minor
Priority:  3 - Low Status:  Need Discussion
Privacy:  Public Assigned to:  None
Open/Closed:  Open Release:  None
Fixed Release:  None Planned Release:  Later
Work Required:  2 - Weeks

Add a New Comment(Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


Fri 08 Aug 2008 08:29:35 PM UTC, comment #2:

Hi Jason,

I don't believe the debugging output shows info on input translations, but I could be wrong.

I'd like this option to be an "always available" type of thing, though, so that I can help people figure out (e.g.) why their end key isn't working; that sort of thing.

And yes, ttyrec (perhaps in combination with my program, Teseq (http://www.gnu.org/software/teseq/)) is useful for debugging such things; but teaching users how to set that up and then understand the contents is tedious; it's easier if screen has built-in tools for that sort of thing.


Micah Cowan <micahcowan>
Fri 08 Aug 2008 08:16:05 PM UTC, comment #1:

Hi Micah,

Are you sure you want a dedicated debug window? Screen can provide debugging output: you must recompile with -DDEBUG. Debugging will then be on by default. You can turn it off by pressing CTRL-A then entering the command:
:debug off
The manpage mentions that there's also a ":debug on" command, but doesn't make it clear to me when the command will succeed and when it won't.

I've never looked at the debugging output, so I don't know if it shows info on input translations. Does it?

Another idea: Would ttyrec or one of its competitors[1] meet your needs, perhaps if you started one copy of the recorder outside your screen session and another copy inside your screen session? I presume all of those tools capture raw characters including escape codes.

Jason Spiro <jasonspiro4 at gmail.com>
^ [1]. http://0xcc.net/ttyrec/index.html.en#links

Tue 15 Jul 2008 06:32:55 PM UTC, original submission:

A display window for investigating screen behavior.

Not sure of what all could go here; but for instance it could be used to watch input translations. For instance, to see what the "home" key is producing, the user could type "home", and see output like:

\EOH -- kh -> \E[1~

which signifies that screen recognizes \EOH as the display terminal's kh termcap value, and translates it to \E[1~ for the applications running in screen. If the display terminal's termcap was misconfigured, so that it did not specify \EOH for the kh capability, then it might look like:

Untranslated: \EOH

Untranslated text would be detected by characters that follow an escape character "quickly". If one rapidly typed the home key followed by "abc", this would produce

Untranslated: \EOHabc

Micah Cowan <micahcowan>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by micahcowan (Submitted the item)

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.




    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2008-07-15 micahcowan Priority5 - Normal => 3 - Low

    Back to the top

    Powered by Savane 3.4