tomk3003

I have played around with the debug output of `Devel::Camelcadedb` and found that a saved brakepoint for a module loaded by code is never sent to the debugger on the...

If you want to test this without too much effort, you can use my module `lib::archive` from CPAN. It puts a sub into `@INC` that can load modules from a...

A related Question: with modules loaded from code, the context sensitive actions (CTRL-Q:Quick Doc or CTRL-ALT-B:Goto Implementation) are not possible at the moment. Is this something you'd consider to implement?

We are using a lib::archive TAR file consisting a versioned(!) collection of self written modules (an internal standard library). The developer just adds the line `use lib::archive STD-v1.0.5.tgz;` and thus...

no worries, for our use case I have already added an option to extract to a temporary directory. Then everything works as expected.

I still would like to see an option to not write the metadata to the head of the resulting docx. If I want to include them I can always do...

Yes, then the script could read a config file from the repository and the admin can define what can be run. This would be more secure than letting everyone run...