Thank you so much for creating bat! Very happy with the app.

I'm customizing things a bit and my BAT_OPTS is breaking --list-themes. It's paging one theme at a time and the theme names are not shown. That makes it unusable, unfortunately. Maybe we should ignore --paging=always (or perhaps all config) when running that command?

`BAT_OPTS="--theme=TwoDark --paging=always --pager='less -j3

• Gitea version (or commit ref): 1.13 (Codeberg), 1.15 (try.gitea.io)
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes https://try.gitea.io/30repos (feel free to join this org as admin)

Description

The paging of repos is broken in the user dashboard with (n)*15 repos, n >= 2.
So wi

Describe the bug

gh run view --log throws a regex parsing error if the Actions job name contains a ++ character sequence.
It appears to be interpreted as a regex, without escaping.

Version: gh version 1.10.3 (2021-05-21)
OS: MacOS Catalina 10.15.7

Steps to reproduce the behavior

1. Create an Actions workflow with a job whose name contains ++, e.g. `Pre-check: C++ test

Is your feature request related to a problem? Please describe.
In our project we use git describe all the time for issue tracking. I implemented a custom command that sort of does what I want but I'm interested if you have ever thought about informational only prompts. I.e. not 'input' or 'menu', just outputting the result of something like git describe. There may be other use cases for infor

Is your feature request related to a problem? Please describe.: No.

URL clickable also in description in github Desktop like the title

How will it benefit Desktop and its users?

Save times to not copy/paste

Ref #94. It might be better for the output to say something like

added: foo (binary file)

than the current

Binary files /dev/null and b/foo differ

This is a reminder for me or a task if anyone wants :P

Basically, The last two questions aren't really regex's questions.

To do:

• Move said questions to correct place.
• Add new regex questions (Python related!)?
• Maybe add a new ## Regex section, as it is a valuable skill