Christopher J. 'CJ' Wright

Yes I think this is fixed now?

I think so, I think this was the same weird starting character that I was running into before. I did not run the test though, so reopening.

I think we can pull that out of the import maps in `libcfgraph`. For example in https://raw.githubusercontent.com/regro/libcfgraph/master/import_maps/mp.json if you search for `mpl_toolkits` you'll see the artifacts that support it that...

We could, I thought it would be more robust to allow 3rd parties to provide it if they wanted to. How do you want to implement that, do you want...

xref: https://github.com/ericdill/depfinder/pull/49

I think xraylib and diffpy use an approximation from: D. Waasmaier, A. Kirfel, Acta Cryst. (1995). A51, 416-413 http://dx.doi.org/10.1107/S0108767394013292 Obtained from: https://github.com/diffpy/libdiffpy/blob/e6da708d28dc258c0787a2ccb95ae693e96ad38c/src/diffpy/srreal/scatteringfactordata.cpp

Also there is [xraylib](https://github.com/tschoonj/xraylib) which does have high energy x-ray tables

Would a reasonable syntax look like: ``` python history tag ['tag1', 'tag2'] history search 'tag1' ```

Sorry maybe they're should be a second clause to that command (the proposed syntax were mostly there to help try to explain the request, less as a specific syntax proposal)

I think that the search support is key, that way we can find the history we are looking for, rather than hoping to find the right uid.