When trying to load a file that does not have a lexer (without specifying a lexer override via -x), the file fails to load:

$ rich us1.env
unable to read us1.env: no lexer for filename 'us1.env' found

I would like to suggest a fallback to text lexer, perhaps with a warning message, instead of not displaying the file

I was wondering if I could get a little help.. 😬

I'm trying to figure out a semi-generalised way for people to generate nice-looking SVGs showing command-line help output from ewels/rich-click.

One approach that I tried is to set force_terminal=True or color_system="256" on the rich-click console object. This maintains colour through a pipe to rich-click nicely, however it kills the SVGs..

See for example test.svg (doesn't render in GitHub comments). In the browser (Chrome, Safari), this renders with the following warning at the top:

Passing the file through the w3c validator tool gives slightly more detail:

Error Line 45, Column 184: illegal XML character U+1b
…-r1" x="0" y="20" textLength="1946.8">      …

Any ideas on how to either (a) fix this problem or (b) generate the SVGs in a better way?

Thanks in advance!

I've been trying rich --pager as a less pager replacement. I've realized that I can't select words while in that mode, which prevents copy. Is there a way to allow selecting of words? (and ideally some sort of find?)

rich  ~/.emacs.d/config.org
unable to read /home/xircon/.emacs.d/config.org: no lexer for filename 'config.org' found

Org files are just text. Perhaps it should just "have a go" :smile:

On running the following command

ps |rich - -m

I got the following output

┌───────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ PID TTY          TIME CMD                                                                                         │
└───────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
6697 pts/1    00:00:00 bash 6722 pts/1    00:00:36 fish 50260 pts/1    00:00:00 ps 50261 pts/1    00:00:00 rich

So rich-cli is able to inspect the first line (header) correctly, but not the subsequent lines.

Without rich-cli, I got the following output:

$ ps
    PID TTY          TIME CMD
   6697 pts/1    00:00:00 bash
   6722 pts/1    00:00:37 fish
  50453 pts/1    00:00:00 ps

Tested with commands like netstat.

One possible solution could be to allow the users to specify the delimiters.

I am wondering whether this could be a bug, since rich-cli is able to detect the first line.

We will need a --force-terminal switch (plus single letter -f if its free) which forces terminal output. To allow users to pip to a file while allowing ansi codes (for pagers etc).

For example, the mosquitto_sub command can print data received through MQTT. It has a built-in formatting option using the -F flag. But I would like to have a better looking output that would be possible with Rich CLI. What's the best way to use it?

I did the following and it worked so I assumed mosquitto would work too:

echo '{"test":"OK"}' | rich - --json
{
  "test": "OK"
}

I tried the following: mosquitto_sub -h test.mosquitto.org -t "181818/json" | rich - --json but did not get any output. Without | rich - --json I got this: {"test":"OK"}

Hi all,

I can't seem to remedy this. I uninstalled/reinstalled and get the same thing. Any help would be greatly appreciated.

> rich try.csv
unable to read try.csv: no lexer for filename 'try.csv' found

Thanks!!

$ git clone https://github.com/pypa/setuptools
$ rich setuptools/docs/pkg_resources.rst

The last bunch of sections have headers but no content in the output, though content exists in the input.

Hello!

I'm sorry I'm not sure exactly what's going on here, so I'll get to it. Using Zsh:

$ rows=( Package,Version,Latest,Project 'tomli,2.0.0,2.0.1,~/Code/zpy' 'click,8.0.1,8.0.3,~/Code/archbuilder_iosevka' 'pep517,0.11.0,0.12.0,~/Code/archbuilder_iosevka' 'ruamel.yaml,0.17.17,0.17.21,~/Code/archbuilder_iosevka' 'tomli,1.2.1,2.0.1,~/Code/archbuilder_iosevka' )
$ rich --csv - <<<${(F)rows}

$ rows=( 'Package,Version,Latest,Project' 'tomli,2.0.0,2.0.1,~/Code/zpy' 'click,8.0.1,8.0.3,~/Code/archbuilder_iosevka' 'pep517,0.11.0,0.12.0,~/Code/archbuilder_iosevka' 'ruamel.yaml,0.17.17,0.17.21,~/Code/archbuilder_iosevka' 'tomli,1.2.1,2.0.1,~/Code/archbuilder_iosevka' )
$ rich --csv - <<<${(F)rows}

Same result as above

$ rows=( 'tomli,2.0.0,2.0.1,~/Code/zpy' 'click,8.0.1,8.0.3,~/Code/archbuilder_iosevka' 'pep517,0.11.0,0.12.0,~/Code/archbuilder_iosevka' 'ruamel.yaml,0.17.17,0.17.21,~/Code/archbuilder_iosevka' 'tomli,1.2.1,2.0.1,~/Code/archbuilder_iosevka' )
$ rich --csv - <<<${(F)rows}

What determines whether the first row gets treated as a header?

Thanks for any help!

Some --themes are not working on my Windows Terminal (using Windows 11) although they seem to work on WSL on the same machine.

Some of the themes not working include gruvbox-light, dracula, and friendly_grayscale (all taken from the pygments documentation here).

Below you can find a screenshot showing the Windows terminal on the left and WSL on the right, both running rich-cli 1.3.0:

1. I ran rich without specifying a theme;
2. I ran rich with --theme dracula and the Windows terminal renders it with the same styling as if I had invented a random theme name;
3. I ran rich with another theme that both terminals seem to recognise, although the colours don't match 100% (which is fine).

Running python -m rich.palette gives this output:

Bumps certifi from 2021.10.8 to 2022.12.7.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Hi,

Concerning the markdown preview, I see that the titles are centered. I would like to have them on the left instead. How can I achieve this?

Best regards

Since rich-cli pins textual to 0.1.18 it's not possible to install Textual as suggested in the README:

$ pip install --index-url=https://pypi.org/simple "textual[dev]"
Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: textual[dev] in ./.local/lib/python3.7/site-packages (0.1.18)
  WARNING: textual 0.1.18 does not provide the extra 'dev'
Requirement already satisfied: rich<13.0.0,>=12.3.0 in ./.local/lib/python3.7/site-packages (from textual[dev]) (12.6.0)
$ python -m textual
python: No module named textual.__main__; 'textual' is a package and cannot be directly executed

By capitalizing the emoji single-letter option to -J, a collision between JSON and emoji display options is removed.

I also included a test that monkeypatches a private function of the click.decorators module to make it fail noisily when option names are duplicated. Could be useful if CI is implemented for this project.

Fixes #73

The -j option name is listed for both the "Display as JSON" and "Enable emoji code" options in the code and documentation (including the splash screen image in the README). Click's option decorator silently allows one to overwrite the other. As a result, the JSON display option currently has no single-letter option name. To use it, one has to call --json.

Since the JSON option is older than the emoji option, I propose capitalizing the single-letter emoji option to -J. This would be a breaking change. I'll submit a PR for you to consider if this seems like a good approach.