[BUG] "corr" subcommand output in stderr ?
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.2k
- Forks
- 96
- PR merge metrics
- No merged PRs in 30d
Description
Hi there,
Thanks for developping csvtk, this is a great tool !
Version of csvtk : v0.37.0
Minimal example :
echo -e "col1\tcol2\n0.1\t0.2\n0.3\t0.4" | tsvtk corr | cut -f3
# Output : col1 col2 1.0000
# Expected : 1.00000 (have to use "|&" to cut third column)
Thanks again !
Best,
Felix.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the minimal tsvtk corr | cut -f3 example from the issue and inspect the corr subcommand entry point in the csvtk repository. Trace where headers and correlation values are written, then verify the command produces the expected single correlation value for the documented input without requiring an alternate pipe.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, data
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100