HackerTrans
TopNewTrendsCommentsPastAskShowJobs

maxjohan

no profile record

comments

maxjohan
·7 miesięcy temu·discuss
Thanks for the notice! Embarrassing rookie mistake ;)
maxjohan
·7 miesięcy temu·discuss
These methods would fetch Sway error messages, but nothing else, no? This is not about Sway messages.
maxjohan
·7 miesięcy temu·discuss
Thanks for the input! Sounds promising. I've to admit, 'script' doesn't say anything to me yet. I've to look into it.

About the logs, yes, I have yet to dive into that. The _everything_ part makes it very tedious, so I had hoped for another solution :)
maxjohan
·7 miesięcy temu·discuss
Thanks for your reply! I've thought about that as well. Haven't tried it though. Two thoughts about it:

1. Running graphical from within tmux feels unsafe (?). Introducing another layer can't be the way to go. BUT this comes from a position of limited knowledge, so I might stand corrected on this one. Also, doing it once for debugging won't do any harm.

2. I'm pretty sure the errors are not printed by Sway itself, but some other OS module. Errors that Sway cause for other modules won't be included in the Sway log. So the problem remains, no?
maxjohan
·7 miesięcy temu·discuss
Is there a way to read from present tty?

In practice: I boot into tty and manually start the graphical session (Wayland/Sway). I occasionally get (non-Sway) warnings when I return to tty (eg close the window manager). But the output is always scuffed, so I can't read the whole log. The lines get printed on top of each other or something.

Is there a way to read everything from tty, from within the tty?

Neither of the methods below work, because the warnings/errors aren't produced by Sway itself, but some other OS module/component.

$ sway |& tee /tmp/sway.log

$ tail -f /tmp/sway.log