blacklight/aerc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Document collecting log output

Browse source 
Redirecting stdout writes log output to that file, but this wasn't
easily discoverable.

v2 removes changes to aerc-tutorial; I was also on the fence about that,
and agree that it isn't on-topic for the tutorial.

Addresses https://todo.sr.ht/~sircmpwn/aerc2/180
This commit is contained in:
Lyle Hanson 2019-06-12 11:20:49 -05:00 committed by Drew DeVault
parent fd0265d917
commit 0b14d92baf
2 changed files with 12 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -23,6 +23,10 @@ Then compile aerc:
On its first run, aerc will copy the default config files to `~/.config/aerc`
and show the account configuration wizard.
If you redirect stdout to a file, logging output will be written to that file:
$ aerc > log
## Resources
[Send patches](https://git-send-email.io) and questions to

8
doc/aerc.1.scd
View file

@ -132,6 +132,14 @@ message list, the message in the message viewer, etc).
*close*
Closes the terminal.
# LOGGING
Aerc does not log by default, but collecting log output can be useful for
troubleshooting and reporting issues. Redirecting stdout when invoking aerc will
write log messages to that file:
$ aerc > log
# SEE ALSO
*aerc-config*(5) *aerc-imap*(5) *aerc-smtp*(5) *aerc-tutorial*(7)