bb010g
bb010g
LLVM's build cycle has a undeclared phony dependency on ~~Git's `git` (or not? currently building to check) & an undeclared dependency on~~ Python 3 (of the form `python${major}${minor}`). Here's a...
So, I've been looking at redoing my nvim config to potentially switch back from [Doom Emacs](https://github.com/hlissner/doom-emacs), and targets.vim caught my eye once again. The recent #217 seems to have made...
Here's a draft mapping from the asyncomplete option set to deoplete: ```vim deoplete#custom#var('tmux-complete', 'splitmode', 'words') " (Currently a default of v:false for deoplete) deoplete#custom#var('tmux-complete', 'filter-prefix', v:true) deoplete#custom#var('tmux-complete', 'show_incomplete', v:true) "...
For comparison: - denite: https://github.com/Shougo/denite.nvim/blob/609c85797a5f6acc2e2357cf56e7f6c78c561145/rplugin/python3/denite/filter/matcher/cpsm.py - Deoplete: https://github.com/Shougo/deoplete.nvim/blob/bbec852adee45a1500fa817a3c17889dc328cad0/rplugin/python3/deoplete/filter/matcher_cpsm.py They're pretty similar, aside from `matcher_fruzzy` instead of `matcher/fruzzy`. :)
The convention for unstable packages is to use the last modification date as `version`. Niv should assist in setting this by recording it when updating in a property like `date`....
This ensures proper support for `plugin_spec.as` in plugins specified in `plugin_spec.requires`.
In the documentation for [`server::Multipart::foreach_iterator`](https://docs.rs/multipart/0.13.1/multipart/server/struct.Multipart.html#method.foreach_entry), you use an internal iterator due to Rust's iterators not supporting elements that borrow from the iterator. There is a [streaming-iterator](https://crates.io/crates/streaming-iterator) crate with a [`StreamingIterator`](https://docs.rs/streaming-iterator/0.1.2/streaming_iterator/trait.StreamingIterator.html)...
The Cheats dialog only allows for two levels of nesting, seen in [the hardcoded v. checks in frontend/cheat.py](https://github.com/mupen64plus/mupen64plus-ui-python/blob/2c1ec337a5f547ca6f147248e655750a25697465/src/m64py/frontend/cheat.py#L57L80). If arbitrary levels of nesting were supported, that would be great.
These allow `nix-shell --pure --show-trace --keep-going --run 'cargo build --release'` from a clean checkout to succeed. ## Don't assume LLVM & Clang share the same lib dir Also, don't assume...
Also, users can supply a function for `network.evalConfig` instead of just a path, if desired.