BlaBlubbBlog

Silo is a "mesh and field I/O library and scientific database" which VisIt uses to read in data. As such it is an interesting thing for my data, especially for adaptive mesh refinement (AMR) data. I am torn between two options. Option one: Invent my own file format that does what I want and nothing more, though that will require me to write a plugin for VisIt to actually read the data then. Option two: Produce files that VisIt can read directly but hence enforcing a bunch of dependencies on my code.

In either case it is going to be a pain, so to estimate one side of the pain I was going to play around with Silo a bit. But I keep on not finding the sources, so once and for all (until they change the web site) here is the link: Silo.

Soon. Indeed, indeed:

...is a very useful thing. But it can drive me mad. Especially if it is not doing the same thing in different places. I am used to the standard tab completion of Bash, namely it completes as far as it is unique, then stops and shows after another tab (actually, two) a list of options. Vim, in its standard configuration, does something else, it completes to one of the possibles matches. And then every next tab completes to the next option. I guess it does make sense, as showing a list of options is not really that nice. But anyhow, I drives me mad, so here is how to change the behaviour (in your ~/.vimrc) to what I like:

set wildmode=longest,list