Amjad Ben Hedhili

Oh, I guess it was Color Highlighter ``` This list shows how much time each plugin has taken to respond to each event: _wrapped_on_load: PackageDev.plugins_.syntaxtest_dev: 0.000s total, mean: 0.000s, max:...

You're right, I didn't notice that, I updated the issue.

I don't want the User to interact with the `arg1` input handler, arg1 value is provided already, I want SM's behaviour of calling `Arg1InputHandler` and resolving it directly with the...

Default.sublime-commands: ```json [ { "caption": "Checkout uriparsing", "command": "checkout_branch", "args": { "branch": "refs/remotes/upstream/uriparsing", }, }, ] ``` ST:  SM: 

it requires more hacks to make it work with arbitrary input: ```py import functools import sublime import sublime_plugin class SomeCommand(sublime_plugin.TextCommand): def run(self, edit, arg1, arg2): print(arg1, arg2) def input(self, args):...

Hi, Thanks for your help ! That still produces larger output than gimp Original:  157B GIMP:  103B nimPNG:  134B

I think it's not related to compression. When opening the 3 images in https://www.nayuki.io/page/png-file-chunk-inspector, it shows that gimp only includes `IHDR`, `IDAT` and `IEND` chunks. while nimPNG also includes `PLTE`...

The first code produces 111B (better), gimp produces 103B. The second one produces a corrupt file.

I get that when testing.

There was the string overload, then the openarray overload was added in 6901a8cb13d19a3d251911af240c5f2a54809eba (https://github.com/nim-lang/Nim/pull/646), Ig the author wasn't aware that `string` is compatible with `openArray[char]`.