slaesvuo/hledger
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

;doc: csv: more cleanup

Browse Source
This commit is contained in:
Simon Michael 2023-01-11 14:43:27 -10:00
parent 59e31e5a42
commit 8f9c35200f
1 changed files with 19 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
hledger/hledger.m4.md
View File

@ -3392,20 +3392,29 @@ Try using sed, or a more permissive CSV parser like [python's csv lib](https://d
### File Extension ### File Extension
To help hledger identify the format and show the right error messages, To help hledger choose the CSV file reader and show the right error messages
CSV/SSV/TSV files should normally be named with a `.csv`, `.ssv` or `.tsv` (and choose the right field separator character by default),
filename extension. Or, the file path should be prefixed with `csv:`, `ssv:` or `tsv:`. it's best if CSV/SSV/TSV files are named with a `.csv`, `.ssv` or `.tsv`
filename extension.
(More about this at [Data formats](#data-formats).)
When reading files with the "wrong" extension, you can ensure the CSV reader
(and the default field separator) by prefixing the file path with `csv:`, `ssv:` or `tsv:`:
Eg: Eg:
```shell ```shell
$ hledger -f foo.ssv print $ hledger -f ssv:foo.dat print
```
or:
```
$ cat foo | hledger -f ssv:- foo
``` ```
You can override the file extension with a [separator](#separator) rule if needed. You can also override the default field separator with a [separator](#separator) rule if needed.
See also: [Input files](#input-files) in the hledger manual.
### Reading CSV from standard input
You'll need the file format prefix when reading CSV from stdin also, since hledger assumes journal format by default.
Eg:
```
$ cat foo.dat | hledger -f ssv:- print
```
### Reading multiple CSV files ### Reading multiple CSV files