Skip to content

Key bindings for DEC VT-320 terminal#38

Open
sblendorio wants to merge 6 commits intotaviso:mainfrom
sblendorio:main
Open

Key bindings for DEC VT-320 terminal#38
sblendorio wants to merge 6 commits intotaviso:mainfrom
sblendorio:main

Conversation

@sblendorio
Copy link

No description provided.

@taviso
Copy link
Owner

taviso commented May 27, 2022

Thanks, this is fun! I wonder if I can just automate it though, if TERM=vt320, can I just send those strings in main() and it will work?

@taviso
Copy link
Owner

taviso commented May 27, 2022

Untested, but I'm thinking of something like this in main()?

if (strcmp(getenv("TERM"), "vt320") == 0) {
      setenv("TERM, "vt100", 1);
      fwrite(""\eP1;1;1|33/1b5b363b357e\e\\", xx, 1, stdout);
}

@sblendorio
Copy link
Author

I did it in this new commit. I used printf() because fwrite() - also with fflush() - did not write anything on the terminal.

@taviso
Copy link
Owner

taviso commented May 28, 2022

The patch looks good to me! I copied your note to the wiki too:

https://github.com/taviso/123elf/wiki/Terminals

I've noticed there is a built-in keymap called "vtxxx", but I don't know what it does, I just want to check that isn't better than vt100 for some terminals before overwriting it!

@sblendorio
Copy link
Author

sblendorio commented May 30, 2022

Do you think it's possibile to control PF3 and PF4 keys through your patch?
Both original VT100 and VT320 got PF3 and PF4, while F20 and F19 are absent on VT100

@sblendorio
Copy link
Author

"vtxxx" is a binary file labeled as "PDP-11 UNIX/RT ldp", never heard about that...

image

Hard to find infos about that format

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants