telnet_event_t::ttype_t(3)

πŸ“¦
version 0.23 Β· 2 versions
, in epel 10, fedora 43, fedora 44

πŸ’– NAME πŸ’–

telnet_event_t::ttype_t β€” bestie, this is the TTYPE event struct, the lil' glow-up that tells you what terminal type the other side is rocking πŸ–₯️✨

It lives in the telnet_event_t family, so if you're staring at a telnet_event_t and the _type says TTYPE, this is the vibe you're looking at. Periodt.


🌸 SYNOPSIS 🌸

#include <libtelnet.h>

πŸŽ€ Data Fields πŸŽ€

enum telnet_event_type_t _type
unsigned char cmd
const char * name

πŸ¦‹ DESCRIPTION πŸ¦‹

✨ Detailed Description ✨

TTYPE event. That's the whole vibe. It's the event that fires when the terminal-type negotiation is happening β€” you know, the whole "hey what terminal are you" / "bestie I'm xterm-256color" conversation. 🫢


πŸ‘‘ Field Documentation πŸ‘‘

πŸ’… enum telnet_event_type_t telnet_event_t::ttype_t::_type

alias for type β€” it's the same thing, just chiller about it. no cap. πŸͺž

🌈 unsigned char telnet_event_t::ttype_t::cmd

TELNET_TTYPE_IS or TELNET_TTYPE_SEND β€” literally those two, nothing else. One of them is the ask, one of them is the answer. iykyk. πŸ’«

πŸ“ const char* telnet_event_t::ttype_t::name

terminal type name (IS only) β€” so when the cmd is the IS one, this is where the actual terminal name lives. If it's the SEND one, this field is not the moment, bestie. πŸ™ˆ


🧚 Author 🧚

Generated automatically by Doxygen for My Project from the source code. not a human girlie writing this at 3am, a robot did it πŸ’€πŸ€–


okay that's the whole page, tysm for reading πŸŽ€ β€” this was telnet_event_t::ttype_t from the Library Functions Manual, brought to you by My Project, generated by Doxygen, and yes the footer really is just My Project telnet_event_t::ttype_t(3) and that's iconic in its own quiet way. stay hydrated, read your manpages, mwah πŸ’–βœ¨

πŸ“¦ where this page comes from