diff options
| author | Canop <cano.petrole@gmail.com> | 2021-08-10 15:52:17 +0200 |
|---|---|---|
| committer | Canop <cano.petrole@gmail.com> | 2021-08-10 15:52:17 +0200 |
| commit | 35be7733cee3223bec0c69ab1c693da3a0b7d371 (patch) | |
| tree | 036d69cc81f2f433e58cafc9ba2945e1b97beb13 /website/docs | |
| parent | 42f65262169b68472d690b5a9234b8ef22488018 (diff) | |
change community page: explain I need comments
Diffstat (limited to 'website/docs')
| -rw-r--r-- | website/docs/community.md | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/website/docs/community.md b/website/docs/community.md index 51c20f9..c4d86b8 100644 --- a/website/docs/community.md +++ b/website/docs/community.md @@ -21,7 +21,11 @@ We use [GitHub's issue manager](https://github.com/Canop/broot/issues). Before posting a new issue, check your problem hasn't already been raised and in case of doubt **please come first discuss it on the chat**. -## Log +# Your wishes + +[Issues](https://github.com/Canop/broot/issues) is also where I test new ideas. If you're interested in the directions broot takes, **please come and vote on issues**, or maybe comment. This would help me prioritize developments: if nobody's interested in a feature I'm not sure I want, I'll do something else. + +# Log When something looks like a bug, especially keyboard problems, we need both to know the exact configuration (OS, terminal program, mainly) and to have the log. The log can be obtained this way: @@ -30,7 +34,7 @@ When something looks like a bug, especially keyboard problems, we need both to k 3. quit broot 4. go to the chat (or the GitHub issue if you already made one) and paste the content of the `broot.log` file -## Benchmark +# Benchmark To get a precise idea of the time taken by operations in real broot use, it's often a good idea to run them with `--cmd`. |