I'd like to use CONNECT method with HTTP (at least with 1.1, and, ideally with 2).

However, I don't think there's a way to unwrap the underlying stream from HTTP response.

Practically, I need an object that implements futures::io::AsyncRead and futures::io::AsyncWrite (from futures 0.3). Similar thing via tokio should work too.

• The first example can have few more chained prompts (It shows the power of enquirer in a few seconds)
• Todo can be moved to the bottom & can be a section (Below Contribution section)
• The 'Related prompts' section can be moved below 'Example Usage'. After the gif, the code should be shown (It is correct for Input prompt)
• The example should be complete. It should match exac

I'll preface this issue by saying i have only used the Web UI so far. Oh, and what a great project!

I am currently having to brute-force my way through when using the web UI to make my theme, which is an indication of a underlying problem: The lack of intention for each shade and accent

Specifically accent1 has no other description than "syntax", and is not showcased at all in the code pr

Please visit the contributing guidelines to learn more on how to translate project's documentation into more languages.

Tons of thank you to everyone for your help and support! ❤️

Description

The use of license keys seems to be configured where it is only going to use the evaluation keys. That may be suitable for most but for those of us with MSDN licenses, or volume licenses with our employer, there is a need to use a customized key for the OS installations.

Right now this is where I find how the keys are managed:

https://github.com/AutomatedLab/AutomatedLab/bl

https://gnunn1.github.io/tilix-web/manual/themes/
https://github.com/storm119/Tilix-Themes

Hey, nice theme.
Would be great to have an option the set the background transparency and the color as well.

See #157. Opening this issue per @pacocoursey’s comment:

Manual selection is a good idea, if you still feel strongly about adding it as a feature please open a new issue.

If the only available .hyperlayout file contains invalid JSON, the "Can't find any hyperlayout preset (.hyperlayout, package.json, ~./hyperlayout)" error is shown - we should check for valid JSON first and show an error for this if necessary.

On OSX when pressing cmd + a the content of the terminal gets selected. When focus is on search field the text in the search field should get selected.