Sure, but it would get wonky with data like this:
London, 12, 13.5
New York, 17, 12.2
Paris, 9, 16.7
Even if you removed the spaces between column values, the space in New York would presumably throw it off.
You’re right and I already changed it. The data this was made for was just numbers without spaces (for plotting) so I never had any problems. As an example, this should be more robust, of course.
2 Likes
I have being getting to know MVV’s and realise now we could easily merge two lists, of equal number, into key=value pairs because we have access to the filters list of titles and or a MVV, or even two MVV’s and merge them. If we parametise the = and default to outputting a compound title like [[key=value with spaces]] we can divide and use these later.
- If the joiner was
:we could build entries for a data dictionary - further features may be able to cope with adding numeric indices when only one list were available
1=a 2=r - Similarly we could use
|to generate title links eg[[key|value as title]]
However I pause to ask if this in the merging of two sets maybe its time for some other set (or title list) manipulation operators.
Post Script:
One strong contender to use this is to take a given list and save it, then transform each member of that list to create a new value for each item, then merge them to create a list of items “=” their transformed item. This combined list can be stored and reused many times.
- The output of such lists could be used to drive the creation of tiddlers, the setting of variables, the provision of parameters or setting multiple fields to preset values.
Post Script
Using an LLM I generated a new filter operator as demonstrated here which is working
-
[list.1[]zipjoin[2ndlist],[=]]typically one may then+ [format:titlelist[]join[ ]]to save it as a list.
However I think this should also either accept input titles as “list one” or be provided two MMV lists as parameters. Note how its parameter is a list variable name, not the <2ndlist> or (2ndlist)