dnkl changed the topic of #foot to: Foot - fast, lightweight and minimalistic Wayland terminal emulator || 1.19.0 || https://codeberg.org/dnkl/foot || channel logs: https://libera.irclog.whitequark.org/foot
baltazar has quit [Ping timeout: 252 seconds]
baltazar has joined #foot
wofA has quit [Remote host closed the connection]
wofA has joined #foot
rrogalski has quit [Quit: Quit: Dog probably tripped over power cord again.]
rrogalski has joined #foot
cbb has joined #foot
cryne5 has joined #foot
cryne has quit [Quit: Bye!]
cryne5 is now known as cryne
cryne7 has joined #foot
cryne7 has quit [Read error: Connection reset by peer]
cryne7 has joined #foot
andrea_ is now known as andrea
chiselfuse has quit [Remote host closed the connection]
chiselfuse has joined #foot
cryne7 has quit [Quit: Bye!]
cryne7 has joined #foot
urosm has joined #foot
urosm has quit [Ping timeout: 252 seconds]
urosm has joined #foot
urosm has quit [Ping timeout: 244 seconds]
urosm has joined #foot
urosm has quit [Ping timeout: 260 seconds]
aljustiet has joined #foot
aljustiet has quit [Quit: aljustiet]
aljustiet has joined #foot
<sewn> why does foot --server occasionally die with "failed to dispatch pending Wayland events: Broken pipe" through out the day?
<dnkl> the compositor is killing the connection
<vyivel> sewn: because the compositor has closed the connection, probably due to a protocol error
boomboxnation has quit [Remote host closed the connection]
boomboxnation has joined #foot
<sewn> arent clients able to print out a protocol error before they die?
urosm has joined #foot
urosm has quit [Ping timeout: 252 seconds]
<aljustiet> Yay, I can know search gentoo wiki directly from the url bar
urosm has joined #foot
<vyivel> sewn: wl_display.error handler does that
<vyivel> there's also wl_display_get_protocol_error() except it doesn't provide the message
cbb has quit [Quit: cbb]
urosm has quit [Ping timeout: 272 seconds]
urosm has joined #foot
urosm has quit [Ping timeout: 252 seconds]
urosm has joined #foot
urosm has quit [Ping timeout: 252 seconds]
urosm has joined #foot
<constxd> hi any any terminal experts there?
<jpp> Ask your question and we'll see!
<constxd> i am wondering how does ioctl() work. or win32 Console API calls. how is it possible that a windows program on a remote machine invoking SetConsoleMode() can, over an SSH connection, cause my local terminal running under linux to change into raw input mode? question applies to TIOCS ioctls as well
urosm has quit [Ping timeout: 252 seconds]
<constxd> surely it isn't just writing some bytes to the pty or it wouldn't be a syscall
<bapt> m
urosm has joined #foot
urosm has quit [Ping timeout: 244 seconds]
urosm has joined #foot
<rockorager> constxd: It doesn't change your local terminal
<rockorager> The terminal is dumb, it moves the cursor and places text on the screen
urosm has quit [Ping timeout: 260 seconds]
urosm has joined #foot
<constxd> rockorager: it must change my local terminal
<rockorager> constxd: why do you say that
<rockorager> If you use bash as your shell, it doesn't reset the terminal mode. from bash, ssh into a machine. make sure you are in bash again. `stty raw`. type and press enter, you will see you are in raw mode
<rockorager> kill ssh from your local machine
<rockorager> in bash, press some keys and you will see you are not in raw mode
<constxd> rockorager: ok so then what is happening
<rockorager> what do you mean
<constxd> foot -> bash -> ssh -> bash -> ./my_prog
<constxd> i am in cooked mode
<constxd> my_prog calles tcsetattr()
<constxd> suddenly i am in raw mode
<rockorager> the remote pty is in raw mode
<constxd> hmm
<constxd> so foot doesn't behave differently at all
<constxd> it always writes to the pty immediately as soon as you press a key. and cooked/raw is purely in the kernel pty layer
aljustiet has quit [Ping timeout: 252 seconds]
<rockorager> yes
<constxd> but what about TIOCGWINSZ surely that requires some action from foot
<rockorager> signals work over ssh
<constxd> is it that foot called TIOCSWINSZ earlier and the kernel remembers the window size
<constxd> like ultimately only foot can know how many lines and columns there really are
<rockorager> or rather, ssh forwards that signal
<rockorager> section 6.7
<rockorager> So ssh locally catches the SIGWINCH, sends that message, and the remote pty changes size
<constxd> ok i think i get it now
<constxd> ty
<rockorager> np
mx08 has quit [Quit: WeeChat 3.8]
mx08 has joined #foot