Toby Inkster

That would break backwards compatibility with versions of Type::Params before `compile_named` was introduced. Back then the only way to do named parameters was: ```perl my $check = compile( slurpy Dict[...

If the old API is this: ```perl foo( $hashref, %options ) ``` Then this part seems wrong: ```perl { # legacy goto_next => \&goto_next, head => [Str], #

I'd suggest doing something like: ```perl signature_for table_generator => ( named => [ cell_span => Maybe [ Enum[ DISPLAY_CELL_SPANS ] ] ... ); my $cell_span = $args->cell_span // DISPLAY_CELL_SPAN_MULTI; ```

@UziTech I've been using this plugin with PulsarEdit for a few days and it seems okay so far.

I cheated: ```shell cp -r ~/.atom ~/.pulsar cp -r ~/.config/Atom ~/.config/Pulsar ```

JSON::Excess

Yeah, it's not really the same kind of thing. I just want to be able to run an external script each time I visit a page on a certain domain....

I don't have much of a preference at what stage it runs. I'm just looking for once per page load.

Actually, `onHistoryStateUpdated` might be nice, as there are an increasing number of websites which use Javascript to replace the page content then update the address bar and history with a...

Yeah true. I can't imagine many people would want dozens of external programs running for each navigation event.