Could you please add a short description for the key chord definitions as well? It's not too clear what a user is supposed to write for all the special keys (e.g. there's numpad_5, there's esc and not escape, etc.) or whether we are supposed to separate parts with + or -. Also, the JSON schema helps a bit but this information should really be documented!

The parsing code can be found

What's going wrong?

I discovered this default behavior of PM2 by trial and error:

1. -out logs and -err logs will default to output in ~/.pm2/logs, unless and only unless they are [rerouted](http://pm2.keymetrics.io/docs/usage/lo

From COMMUNITY-ROLES.md:

Specifically: once a repository collaborator has merged at least 10 PRs (see https://github.com/tldr-pages/tldr/commits?committer=<username>) and submitted at least 5 non-trivial reviews to PRs (see https://github.com/tldr-pages/tldr/pulls?q=reviewed-by:<username>), which can overlap with t

Hi, I've found the following cheatsheet :

In the README you explain that there must be an edit button in the page and a github button to access the sheet but as you can see it doesn't appear here.

Thx ;)

Using ripgrep 11.0.2 I ran into a hang using ripgrep from GNU Emacs via helm-rg on Windows. Window creates a stdin and ripgrep detects that stdin exists and waits for data, making it look like ripgrep is hung. I was able to easily work around the issue once I saw that I could explicitly specify the directory to search. Having this in the doc may save others confusion. Also having the note about .g

I would like to map my "meson.build" files to python syntax.
I've tried the following without success:

• -m=build:python
• -m=meson.build:python

Summary of the new feature/enhancement

Tee-Object currently invariably uses the default character encoding when teeing to a file (-Path aka -Filepath, -LiteralPath), which in PS Core is BOM-less UTF-8

However, sometimes you need a specific character encoding, and Tee-Object currently offers no way to specify a different encoding.

Proposed technical implementation details

View the release notes for guidance on migrating => https://github.com/urfave/cli/releases/tag/v2.0.0

When an error boundary's getDerivedStateFromError handler is called, React will print out a warning to the console like so:

The above error occurred in the <Example> component:
    in Example
    in ErrorBoundary
    in App

React will try to recreate this component tree from scratch using the error boundary you provided.

Because of this log output, it means that when the er

The syntax files is written in yaml-format and specify how to highlight
languages.

Should be 'are written'.

It would also be very helpful to add info about how the syntax YAML files should be named. I have no clue after reading the docs. .YAML ?

As discussed in this bat issue, the behavior of fd's -X flag is different from the behavior of fd | xargs. My initial impression upon reading the docs was that -X's behavior would be equivalent to piping to xargs, and I was surprised when that wasn't the case.

Shell session for reference:

$ for i in a b c d; do echo $i > $i.t

Please fix documentation inaccuracies with respect to required fields.

DefinitelyTyped/DefinitelyTyped#36708 (comment)

According to this document type, name and message are always required.
This is very inaccurate as type might be skipped which causes the default prompt to be used.

It looks like there is only a master branch for this repo at this time. This has caused any commits to affect PRs which now show large numbers of conflicts. Would it be possible to get a development branch or other instructions as to how PRs should be made to avoid this situation going forward?

The log view currently serves to only tail a containers logs (including last 10 by default).

This issue tracks the implementation of a more fully featured container log pager (navigation, search, etc.)

I think it would be a good idea to mention the tee command, probably somewhere in the "Cat, Less, Tail and Head" chapter

Thanks a ton for any helpful feedback

I need help with getting best quality GIFs.

I am not used to CSS syntax so it would be amazing if you add a lot of example config.yml files. Also, try adding config.yml files for the GIFs you are displaying in your README.md. They look fantastic. I have spent hours trying to get perfect GIF but no luck.

I don't know what value to give for shadow

I've tested it in a dir with such structure:

.
├── a      // dir
├── b      // dir
│  └── a   // file
├── c      // dir
│  └── a   // dir
└── d      // dir

I ran exa --tree --git-ignore with different versions of .gitignore. There are 2 problems

exa doesn't exclude directories if there's a backslash at the end of the line.

IMO this one is the most annoying. [`git

I am reporting:

• a bug or unexpected behavio

When using git cz, one option for a type to select is "improvement", but this fails the enum check

husky > commit-msg hook failed (add --no-verify to bypass)
git exited with error code 1
kris@Kriss-MacBook-Pro cent-admin % git cz
cz-cli@4.0.3, cz-conventional-changelog@3.0.1

? Select the type of change that you're committing: 
  revert:      Reverts a previous commit 
  feat:

It's a minor request, but would be nice to have a URI always pointing for the latest stable version, thus people could use it for installing q in automated scripts. Something like:

https://github.com/harelba/packages-for-q/raw/master/deb/q-text-as-data_latest_all.deb

For anyone who'd like to contribute and don't know where to start - it might be a good idea to add more unit tests for any uncovered part

If you'd like contribute, please leave a comment here, specifying the areas (functions/files/packages), which you are going to cover

I think the work you've done on this is amazing. Seems like a great project, but your README is a bit bloated and hard to decipher. Might I suggest you condense it down into a set of readable chunks and maybe link off to the wiki for the more detailed bits.

Its only my opinion, but I find that answering the following questions, in order, helps to simplify docs.

• who? - who wrote the p

Inexplicably, part of the conemu website is written in Russian. Scroll down and note how much of the text is not english.

https://conemu.github.io/en/TabletPC.html

It would be helpful to get the original english docs back. I was trying to figure out how to disable zoom gestures on my touch pad, which happens by accident all the time, but all the docs are non-english.

idk what happened to the readme but i had to go look at an old commit were the documentation is in it. I dont like the website and it isnt convienent. also its very slow. issue #117 mentioned parallel threading. Why was this issue closed. its not fixed and its still an issue. Threading isnt difficult if its high level enough. it should be an argument along with what the deley should be to spawn a

I have this method:

@hug.get('/documents/list')
def llista():
    """Returns whole list of documents"""
    docs = [lib.Doc(doc).HeaderstoJSON for doc in glob.iglob('./*.md')]
    return {'documents': docs}

and http://localhost:8000 returns me:

"documentation": {
        "handlers": {
            "/documents/list": {
                "GET": {
                    "usa

It looks like a great tool, is it possible to translate the documentation to English?

Describe the bug

There is no documentation about how to mark a choice as pre-selected in a multiselect. It works to set selected: true in the choice, however @types/prompts doesn't know about it and neither does any of the documentation.

Expected behavior

The docs as well as the types should help to figure out how to do this.

System

• OS: macOS
• Terminal: iTerm