The maintained version now lives at Hypervisor Host Based CephFS pass through with VirtioFS, part of scyto/homelab-docs.
Questions or troubleshooting? Continue the conversation here — a Q&A discussion where replies thread properly, answers can be marked, and everything is searchable. The 22 comments below stay exactly where they are as an archive.
FOREWORDS
I don't mean the snippet at the bottom of this gist to be a generic plug-n-play solution to your search needs. It is very likely to not work for you or even break things, and it certainly is not as extensively tested and genericised as your regular third-party plugin.
My goal, here and in most of my posts, is to show how Vim's features can be leveraged to build your own high-level, low-maintenance, workflows without systematically jumping on the plugins bandwagon or twisting Vim's arm.
| version: '2' | |
| services: | |
| plex: | |
| image: linuxserver/plex | |
| container_name: plex | |
| volumes: | |
| - /path/to/plex/config:/config | |
| - /path/to/plex/Movies:/data/movies | |
| - /path/to/plex/Shows:/data/tvshows | |
| - /path/to/plex/transcode:/data/transcode |
- 13" Macbook Pro 3.3 GHz i7 (late 2016)
- Microsoft Surface Book (2016)
- Dell up3216q 32" monitor
The driver situation with Apple Bluetooth wireless keyboards and Windows 10 is horrible, even with the latest BootCamp drivers. Fortunately, a workaround is available, if you're patient.
- Turn on the keyboard.
- Press and hold
Command + wuntil the keyboard light begins blinking, indicating the keyboard is ready to pair. - Use Windows Bluetooth settings to pair the keyboard, entering the same code (e.g.
123456 Enter) on both internal and external keyboards.
Pairing the keyboard is very trial and error. 9/10 times, Windows will complain that the keyboard is not available for pairing. Just keep trying.
| console.log(`%c ________________________________________ | |
| < mooooooooooooooooooooooooooooooooooooo > | |
| ---------------------------------------- | |
| \\ ^__^ | |
| \\ (oo)\\_______ | |
| (__)\\ )\\/\\ | |
| ||----w | | |
| || ||`, "font-family:monospace") |
| // Composition Example | |
| // http://codepen.io/ericelliott/pen/XXzadQ?editors=001 | |
| // https://gist.github.com/ericelliott/fed0fd7a0d3388b06402 | |
| const distortion = { distortion: 1 }; | |
| const volume = { volume: 1 }; | |
| const cabinet = { cabinet: 'maple' }; | |
| const lowCut = { lowCut: 1 }; | |
| const inputLevel = { inputLevel: 1 }; |
| /System/Library/Frameworks/ScreenSaver.framework/Resources/ScreenSaverEngine.app/Contents/MacOS/ScreenSaverEngine -background |
The goal of this is to have an easily-scannable reference for the most common syntax idioms in JavaScript and Rust so that programmers most comfortable with JavaScript can quickly get through the syntax differences and feel like they could read and write basic Rust programs.
What do you think? Does this meet its goal? If not, why not?
JavaScript:
Sometimes you want to have a subdirectory on the master branch be the root directory of a repository’s gh-pages branch. This is useful for things like sites developed with Yeoman, or if you have a Jekyll site contained in the master branch alongside the rest of your code.
For the sake of this example, let’s pretend the subfolder containing your site is named dist.
Remove the dist directory from the project’s .gitignore file (it’s ignored by default by Yeoman).