;doc: manuals: whitespace cleanup

Remove a bunch of trailing whitespace with M-x whitespace-cleanup.
Except for examples showing hledger output, which might be tested
with shelltest some day, so stripping that whitespace might be problematic.

[ci skip]
This commit is contained in:
Simon Michael 2020-02-08 12:08:47 -08:00
parent 98d0cc9c17
commit 4d94a5273b
6 changed files with 217 additions and 219 deletions

View File

@ -1479,4 +1479,3 @@ Also, any transaction that has been changed by transaction modifier rules will h
- `modified:` - this transaction was modified - `modified:` - this transaction was modified
- `_modified:` - a hidden tag not appearing in the comment; this transaction was modified "just now". - `_modified:` - a hidden tag not appearing in the comment; this transaction was modified "just now".

View File

@ -1584,17 +1584,17 @@ Here are some issues you might encounter when you run hledger
[mail list](http://list.hledger.org) or [mail list](http://list.hledger.org) or
[bug tracker](http://bugs.hledger.org)): [bug tracker](http://bugs.hledger.org)):
**Successfully installed, but "No command 'hledger' found"** **Successfully installed, but "No command 'hledger' found"**\
stack and cabal install binaries into a special directory, which stack and cabal install binaries into a special directory, which
should be added to your PATH environment variable. Eg on unix-like should be added to your PATH environment variable. Eg on unix-like
systems, that is ~/.local/bin and ~/.cabal/bin respectively. systems, that is ~/.local/bin and ~/.cabal/bin respectively.
**I set a custom LEDGER_FILE, but hledger is still using the default file** **I set a custom LEDGER_FILE, but hledger is still using the default file**\
`LEDGER_FILE` should be a real environment variable, not just a shell variable. `LEDGER_FILE` should be a real environment variable, not just a shell variable.
The command `env | grep LEDGER_FILE` should show it. The command `env | grep LEDGER_FILE` should show it.
You may need to use `export`. Here's an [explanation](http://stackoverflow.com/a/7411509). You may need to use `export`. Here's an [explanation](http://stackoverflow.com/a/7411509).
**"Illegal byte sequence" or "Invalid or incomplete multibyte or wide character" errors** **"Illegal byte sequence" or "Invalid or incomplete multibyte or wide character" errors**\
In order to handle non-ascii letters and symbols (like £), hledger needs In order to handle non-ascii letters and symbols (like £), hledger needs
an appropriate locale. This is usually configured system-wide; you can an appropriate locale. This is usually configured system-wide; you can
also configure it temporarily. The locale may need to be one that also configure it temporarily. The locale may need to be one that
@ -1638,4 +1638,3 @@ $ LANG=fr_FR.utf8 hledger -f my.journal print
Note some platforms allow variant locale spellings, but not all (ubuntu Note some platforms allow variant locale spellings, but not all (ubuntu
accepts `fr_FR.UTF8`, mac osx requires exactly `fr_FR.UTF-8`). accepts `fr_FR.UTF8`, mac osx requires exactly `fr_FR.UTF-8`).