You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For people with large libraries it's very hard to pinpoint which entries have problems when program output is longer than the screen buffer and and you can't see past a certain point. I'm currently using the old school "> logfile.txt" added to the end of the command to dump the program output so I can review or pinpoint any problems, but doing this hides it from the command line and I have no way to know for sure when the program has completed (mine takes a couple hours) except by periodically opening up the text file to see the current status or using a separate app to view live updates of the log file, both of which are annoyingly tedious....
The text was updated successfully, but these errors were encountered:
paegan69
changed the title
Feature request: logfile output
[Feature request] logfile output
May 2, 2020
For people with large libraries it's very hard to pinpoint which entries have problems when program output is longer than the screen buffer and and you can't see past a certain point. I'm currently using the old school "> logfile.txt" added to the end of the command to dump the program output so I can review or pinpoint any problems, but doing this hides it from the command line and I have no way to know for sure when the program has completed (mine takes a couple hours) except by periodically opening up the text file to see the current status or using a separate app to view live updates of the log file, both of which are annoyingly tedious....
The text was updated successfully, but these errors were encountered: