| " Statusline (requires Powerline font) | |
| set statusline= | |
| set statusline+=%(%{&buflisted?bufnr('%'):''}\ \ %) | |
| set statusline+=%< " Truncate line here | |
| set statusline+=%f\ " File path, as typed or relative to current directory | |
| set statusline+=%{&modified?'+\ ':''} | |
| set statusline+=%{&readonly?'\ ':''} | |
| set statusline+=%= " Separation point between left and right aligned items | |
| set statusline+=\ %{&filetype!=#''?&filetype:'none'} | |
| set statusline+=%(\ %{(&bomb\|\|&fileencoding!~#'^$\\\|utf-8'?'\ '.&fileencoding.(&bomb?'-bom':''):'') |
While the following structure is not an absolute requirement or enforced by the tools, it is a recommendation based on what the JavaScript and in particular Node community at large have been following by convention.
Beyond a suggested structure, no tooling recommendations, or sub-module structure is outlined here.
lib/ is intended for code that can run as-issrc/ is intended for code that needs to be manipulated before it can be used
| // DayDream was initially created as a dialup BBS for the Amiga computer and operating system. | |
| // Later it was ported to linux. Recently, it was ported also to *bsd and should be compatible | |
| // with most *nix flavors. | |
| // | |
| // DayDream is maintained by Ryan Fantus (https://github.com/ryanfantus) or daydreambbs.com | |
| // | |
| // | |
| // This guide was written step by step following the process on a Linux console. If you find, | |
| // steps you want to skip, that is up to you, but if you follow step-by-step, you will have a | |
| // working DayDream BBS Setup by the end of it. |
I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!
\
I’ll assume you are on Linux or Mac OSX. For Windows, replace ~/.vim/ with $HOME\vimfiles\ and forward slashes with backward slashes.
Vim plugins can be single scripts or collections of specialized scripts that you are supposed to put in “standard” locations under your ~/.vim/ directory. Syntax scripts go into ~/.vim/syntax/, plugin scripts go into ~/.vim/plugin, documentation goes into ~/.vim/doc/ and so on. That design can lead to a messy config where it quickly becomes hard to manage your plugins.
This is not the place to explain the technicalities behind Pathogen but the basic concept is quite straightforward: each plugin lives in its own directory under ~/.vim/bundle/, where each directory simulates the standard structure of your ~/.vim/ directory.
