when i run serve like:

serve -l tcp://localhost:8888

i get this debug output:

   ┌───────────────────────────────────────────────────┐
   │                                                   │
   │   Serving!                                        │
   │                                                   │
   │   - Local:            http://127.0.0.1:8888       │
   │   - On 

The docs recommend using rewrites instead of routes but AFAIK it's not possible to use methods in the rewrite config.

I tried it with now dev and it stoped with this error:

Error! Invalid rewrites property: [0] should NOT have additional properties

I'm guessing this feature has not been implemented and if that's the case please consider this a feature request.

Issue summary

I found that "completionEscape: false" is needed in my use case to avoid escape of open parenthesis. E.g. python style autocomplete will include open parens of function name, such as "sorted(".

However completionEscape is not a documented option. I only found it referenced in bug jcubic/jquery.terminal#321 (comment)

Expected

Most command examples currently shown do the operation way worse than what I'd expect thunar would do (and afair, does). Here's an attempt at fixing the most obvious differences.

-cp readme.txt documents
+cp --verbose --no-clobber --no-dereference --target-directory='documents' -- 'readme.txt'

stop right click and duplicate file

A core feature of the duplicate command is

Summary

The documentation "activate_announcer_on_command_failure" is not helpful for users as it misses information a

Additional examples should be developed to demonstrate a wider breadth of py_cui supported features.

Does crudini have support for reading the whole content (sections, keys) in one read with --format sh?

The documentation suggests I have to iterate over all sections in order to do that. That is inefficient and time consuming because the ini file is read (opened, closed) for each iteration...

What was the confusing thing is the world came down to a simple lack of documentation and understanding of how something worked.

When using {@@} in description and message, you CAN'T use ROOT values. You MUST supply a children section for the languages. The improvement would be to allow multi-nested values along with root values in the @@

Related with this pull request #17

Micro::Case::Result#data
Micro::Case::Result#[]
Micro::Case::Result#values
Micro::Case::Result#values_at