http://jsfiddle.net/ht16273t/

As the above Fiddle demonstrates, moving rows between grids doesn't seem to update each grid's pagination. This leads to pages not being added in the destination (and the row seemingly being lost) and all kind of oddness in the source. I'd think this could be resolved with a reloadGrid on each but the ondrop event, according to the documentation, doesn't pass the s

Hello.
I've come across what (to me) seems to be a problem with the FILENAME and FILENUM variables.

# mlr --version
Miller v5.6.2

# cat /tmp/csv1
A,B,C
_2GB,255,2
_4GB,120,4
_6GB,50,6
_10GB,10,10

# cat /tmp/csv2
FIRST,SECOND,THIRD,FOURTH
1,2,3,4
5,6,7,8
9,10,11,12
13,14,15,16

# mlr --icsv cat then put 'print FILENAME'   /tmp/csv1 /tmp/csv2
/tmp/csv1
A=_2GB,B=255,C=2
/

I'm sorry for raising a whole issue on this, I'd have put it in a chat group but I couldn't find one

Jsmn is a world fastest JSON parser/tokenizer.

isn't grammatically correct

its either

Jsmn is the world's fastest JSON parser/tokenizer.

or

Jsmn is one of the world's fastest JSON parsers/tokenizers.

(this is the description in the github top part)
![githubthingy](https:/

Add the ability to provide a custom document id (aka key) to set using a new command specific option --key. This feature also bumps the major version to 2.0.0.

Requires updating README.md, CHANGELOG.md, and adding new specific tests for this case as well.

It appears that both the rgb and rgba value definitions are incorrect.

https://github.com/mdn/data/blob/a2e2d7adb53f7906985b50e30dc3c6fd9c200652/css/syntaxes.json#L531
rgb( <percentage>{3} [ / <alpha-value> ]? ) | rgb( <number>{3} [ / <alpha-value> ]? ) | rgb( <percentage>#{3} , <alpha-value>? ) | rgb( <number>#{3} , <alpha-value>? )

From https://drafts.csswg.org/css-color/#rgb-functions:

The readme stated for the timestamp the following syntax:

{
  "operation": "timestamp",
  "timestamp[0]": {
    "inputFormat": "Mon Jan _2 15:04:05 -0700 2006",
    "outputFormat": "2006-01-02T15:04:05-0700"
  },
  "nowTimestamp": {
    "inputFormat": "$now",
    "outputFormat": "2006-01-02T15:04:05-0700"
  },
  "epochTimestamp": {
    "inputFormat": "2006-01-02T15:04:05-0700"

If the data field is missing when cloning a template, the current error message is very confusing. There should be an clear, explicit error message when data is undefined.

const data = undefined;
dna.clone('book', data);  //should immediately throw an error

I’d like to recommend an updated list of data we should collect for plugins and how we should collect it.

1. Collect the target NPM name:
   • process.argv[2], the first argument passed to the script.
2. Collect entry data from NPM:
   • https://registry.npmjs.org/${ name }/latest:
     • Collect author, the primary author.
     • Collect dependencies, all/plugin dependencies.
     • Coll

What should it be called?

• "Array traversal operator": This is what we've always(?) called it
• "Projection operator": I thought about this earlier and it makes some sense. It's very similar to a projection (in the sense that it changes a stream of data); the only difference is that the output can be any value (not only an object).

How do we specify the semantics

There are three