From 4ad4ddf0c9a745713f6205abfaac375ac8998389 Mon Sep 17 00:00:00 2001 From: Simon Michael Date: Wed, 17 Jul 2024 08:42:37 +0100 Subject: [PATCH] ;examples: hledger.conf updates --- hledger.conf.sample | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/hledger.conf.sample b/hledger.conf.sample index aee00b359..727818626 100644 --- a/hledger.conf.sample +++ b/hledger.conf.sample @@ -6,8 +6,8 @@ # If you use a config file, be careful about what you put in it. # It changes hledger's behaviour, so it's easy to confuse yourself, # disrupt reports, or break scripts/applications which use hledger. -# If a command is not working as expected, add --debug to troubleshoot. -# To avoid using any config file, run hledger with -n/--no-conf. +# If a command is not working as expected, run with --debug to troubleshoot. +# To avoid using any config file, you can run hledger with -n/--no-conf. # # You can also choose a config file with --conf, or add a shebang line (eg # #!/usr/bin/env -S hledger --conf) to config files and run them like scripts.