• Dynamic variable naming.
• Internal variables.
• Turn the non-functions into functions.
  • This is so tests can be written.
  • It also shows a working use case for the task.
• Add a CONTRIBUTING.md.
• Look into side effects of using shopt and set.
• /dev/tcp
• Convert to pdf
  • Add a cover.
  • Add references.
• Write some

Localization of readme.md

Translate and add localization of readme.md

Translations:

• Russian (@magauran completed via #203)
• Simplified Chinese (@hiby90hou completed via #214)
• Traditional Chinese (zh-TW) (Taiwan) (@MindyTai completed via #222)
• French (@pgrimaud via PR #251)
• Polish (@P1X3L0V4 via PR #301)
• Spanish (@Tamh via PR #378)
• Korean

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

From what I understand acme.sh seems to have at least two different run modes that seem to be:

• the first run mode expects some environment variables to be set and writes config files, but does not read config files
• the second run mode reads config files - but it is not clear if it ignores environment variables.

This is a strange behaviour for a shell script and leads t

Since GitBook is no longer maintained, a lot of projects started their migration to newer solutions. One of the most popular ones is Docusaurus.

What do think about building Spaceship's website using this tool?

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

low priority issue , it is not a real issue to debug this error , and install bc afterwards , but nevertheless , this is not a native linux command . you should add some warning in , maybe in run.sh for all the diarizations recipe , or in the script itself.

https://github.com/kaldi-asr/kaldi/blob/3e77220b3297831c3a370169580b880461897682/egs/callhome_diarization/v1/diarization/extract_ivecto

Correct the terminology used in code and documentation so that it is consistent with HTTPie and web standards. Examples:

• body parameter -> data field
• operator -> separator

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