Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
For the rustc completion: You can add descriptions to any completion option by separating the option and it's description with a tab character and the next option with a newline.
I.e. something like this should give properly described options:
printf "%s\t%s\n" box-pointers "some text that describes box-pointers" fat-ptr-transmutes "some description for fat-ptr-transmutes"
(Note that I'm not a rust user, but to me some of these seem rather esoteric, so descriptions seem useful)
Ah okay, it's for generating completion scripts. I thought you had written a helper that is called at runtime. This is kinda neat, but I'd still like it more if we could generate the completions on the user's machine since they then perfectly match the rust version (since that's apparently possible).
What you basically do here is call
I could also take a look, but I'll have to download rust first and my current internet connection won't allow for that, so I'll try to get to it over the weekend.
Not too well I think.
The current version (run the
I guess my next challenge is to find a way to generate completions without heavily relying on
I did run into a strange problem though.
Any ideas? I'm using
Okay, I tested it a bit and played a bit around, and while there's still plenty of micro-optimizations possible (e.g. the recurring
The semantics of
So unless you think there's anything missing, this seems about ready to merge. Okay?