4 ms·
Edit: it's GTK that provides multithreading functionality, not VTE itself. VTE based terminals are actually multithreaded globally, so you only ever have one p
by paavoova 8y ago
Edit: it's GTK that provides multithreading functionality, not VTE itself.
VTE based terminals are actually multithreaded globally, so you only ever have one process regardless of number of tabs/windows open.
But I agree, VTE is something I avoid ever since the scrollback fiasco. (For the uninitiated: the library wrote all scrollback to disk, which is not something end-users might expect security wise. Scrollback is encrypted now, but it appears you still cannot disable writing to disk, as e.g. the output of dmesg, consisting of 62210 bytes of output on my machine, causes 5-digits of bytes to be written each time on any VTE-based terminal I've tried even with "infinite" scrollback disabled. And none appear to honor TMPDIR).
- voltagex_ 8y agoI wish I understood it enough to throw it into GDB - it looks like it uses O_TMPFILE, but I don't think that quite gives you what you want. https://github.com/GNOME/vte/blob/65d67f6f814df4f4ab800898bb7f4b1bc9f135b0/src/vteutils.cc#L50 https://github.com/GNOME/vte/blob/65d67f6f814df4f4ab800898bb...
- paavoova 8y agoThe O_TMPFILE flag is just an anonymous file as far as I understand. From that source file, VTE uses glib, particularly g_get_tmp_dir() and g_file_open_tmp() (which uses the latter), which claims to honor TMPDIR according to the docs: https://developer.gnome.org/glib/stable/glib-Miscellaneous-Utility-Functions.html#g-get-tmp-dir https://developer.gnome.org/glib/stable/glib-Miscellaneous-U... Perhaps a terminal emulator is unable to read variables exported in .bashrc, as the terminal is started prior to executing the shell.