3 ms·
I emailed the author of GNU Screen about the lack of proper documentation about the logging to a file feature: http://www.zoobab.com/screenrc http://www.zoobab
by zoobab 1y ago
I emailed the author of GNU Screen about the lack of proper documentation about the logging to a file feature:
http://www.zoobab.com/screenrc http://www.zoobab.com/screenrc
GNU need a better issue tracking system :-)
- CelestialMystic 1y agoThere was a Q&A with the author of Tmux. He was complaining about the lack of documentation ~16 years ago. https://undeadly.org/cgi?action=article&sid=20090712190402 https://undeadly.org/cgi?action=article&sid=20090712190402
- anthk 1y agoTmux has been in OBSD base side several releases and documented since the first one.
- CelestialMystic 1y agoI know. I suggest you read the Q&A I posted.
- deleted 1y ago[deleted]
- amszmidt 1y agoIt is documented in detail in the GNU screen manual, https://www.gnu.org/software/screen/manual/screen.html#Log https://www.gnu.org/software/screen/manual/screen.html#Log
- Avamander 1y ago> GNU need a better issue tracking system :-) This is a problem with quite a few older projects, that issues get buried in the endless depths of unindexed mailing lists, if at all. People bemoan Discord (rightfully) for making info like this unaccessible, but IRC (that some projects still use) is basically twice as bad. I really wish these projects would migrate to Gitea/Forgejo/Codeberg, GitLab or GitHub or anything like that, just to bring these things together and provide vital discoverability.