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

When I try to fork a repo and add a new remote, it doesn't add a new remote to my current repository.

gh version 1.4.0 (2020-12-17)

Expected vs actual behavior

I expect to see a fork remote added to my repository, but nothing is added.

Logs

❯ gh repo fork --clone=false --remote=true $(git remote get-url up)
- Forking someorg/somerepo...

Is your feature request related to a problem? Please describe.
I'm using a lot of markdown emoji in my commits message, but in lazygui, the emoji are not parsed.

Describe the solution you'd like
Replace all markdown emoji by it's Unicode equivalent in commits list.

EDIT:
I have found this file that can be useful

https://answers.netlify.com/t/map-dictionary-fields/5241 has problem faced and solution found.

I'm making a files collection for hugo configuration files, and to edit the taxonomies field requires users to be able to define keys and values, resulting in something like:

[taxonomies]
featured = "featured"
topic = "topics"
tag = "tags"
team = "team"

I originally thought the cod

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