vim does not see lib directory in projects - macvim

Learning Ruby, using MacVim on Mountain Lion.
Installed Command-T (same problem if I used CtrlP) and a file search is not finding the lib directory. That's how I noticed it, but it's not seen anywhere by anything vim related.
If I go to a project directory that contains a lib subdirectory and start vim with 'mvim .', the directory listing does not show lib. If I invoke NerdTree, lib does not show up.
Weird. But from what little I know about Ruby at this point, it seems ruby files are supposed to go under lib so I need to get this working.
Ideas?

Related

Can I use opam to make a package out of a local file and install it?

I'm new to opam and trying to figure out how to use it properly. For a class, I want to set up students with an environment that has some custom packages installed. (The package will consist of some raw .ml files that I got from a colleague at another school; the files are on their github but there's no .opam file that I can see, and as far as I know they're not in any official package release.)
Can I somehow call these local .ml files a package and ask opam to install it? Do the files have to be on github first, and if so can I use my colleague's existing repository as the source? I don't want to make any of this public, since it is not my own work; I just want to configure my local environment so that the code in the files can be included easily as a package. Basically I don't know the best way to proceed so I'm happy for any advice.
You can add a custom opam file in the base directory of the project. See the documentation for how to create that file.
Then you can enter opam pin add . in the base directory and your project will be installed as if it was an opam package. Check opam pin --help for more info (you can also pin to a remote git project for instance).
Note that though the default repository is hosted on github, this is in no way a requirement for opam. Opam is dependent on git but you can absolutely use it with a private git repository. If you want to use your colleague's repository as the source, that is totally doable though it is often preferable to have the opam file at the root of the directory (you can do a PR on their repository or make your own fork of it on github, the site makes it clear you copied the code).
If pinning is not to your taste, you can also create your own repository though this is probably a bit too heavyweight for your needs.
Good luck!

How to install colortheme in NeoVim in Mac OS X?

I just installed NeoVim VimR 0.13.1 from https://github.com/qvacua/vimr/releases
for Mac OSX. I was able to set default options by creating a file at
~/.config/nvim/init.vim
Now I am having a hard time trying use a color theme. For example I am interested with OceanicNext theme from https://github.com/mhartington/oceanic-next
So I downloaded the zip file, unzipped it then it creates a folder called
oceanic-next-master
So I moved this folder to
~/.config/nvim/oceanic-next-master
Added necessary code to the init.vim file
" For Neovim 0.1.3 and 0.1.4
let $NVIM_TUI_ENABLE_TRUE_COLOR=1
" Or if you have Neovim >= 0.1.5
if (has("termguicolors"))
set termguicolors
endif
" Theme
syntax enable
colorscheme OceanicNext
But even restarting the VimR, nothing happens. So I tried renaming the folder name from
~/.config/nvim/oceanic-next-master
to
~/.config/nvim/OceanicNext
Still no luck. So tried to copy the actual OceanicNext.vim file to
~/.config/nvim/OceanicNext.vim
Still didn't work restarting it. So I tried running the command directly
colorscheme OceanicNext
But it give me the following error message
Cannot find color scheme 'OceanicNext'
I also tried install other color scheme from https://github.com/frankier/neovim-colors-solarized-truecolor-only but still wasn't able to make it work.
I also have MacVim installed and just copy and pasting the plugins into the ~/.vim worked, but looks like NeoVim is different? What am I doing wrong?
Thank you.
The nvim documentation on the colorscheme command :help colorscheme
:colo[rscheme] {name}
Load color scheme {name}. This searches 'runtimepath' for the file
"colors/{name}.vim". The first one that is found is loaded. Also
searches all plugins in 'packpath', first below "start" and then under
"opt".
You can put the color scheme file into ~/.config/nvim/colors f older. Where ~ is your user home directory.
Consider you have "nord.vim" colorscheme. The full path to it will be ~/.config/nvim/colors/nord.vim.
Then the :colorscheme nord command will be able to load the theme.
By the way, vim-plug plugin is great for managing vim and neovim plugins and colorschemes. It will install/update/delete plugins including colorschemes for you. Give it a try.
Had to install vim-plug manager from https://github.com/junegunn/vim-plug
by placing the plug.vim file to
~/.config/nvim/autoload
to install the plugins.

Files not showing up in Nitrous.io desktop sync folder

I loaded up the Nitrous.io desktop sync app and then installed the mean.io stack on my box. For some reason I can't get any of the files to sync with my desktop. My keys are working fine, but there are no files syncing. There doesn't seem to be a lot of info in the docs on why this could be happening.
The key thing is mentioned in the Nitrous.io docs in this line:
"...the content within your ~/workspace/ folder will be synced into the newly created Nitrous folder once enabled."
This apparently means ONLY the stuff inside workspace (which is not root, so somewhat confusing) will be synced. So, a key missing step is that if you do anything outside the workspace folder, IT WILL NOT BE SYNCED. This includes installing frameworks or other software via the command line. You have to cd into the ~/workspace folder before installing anything or it won't be synced. Seems like a small thing to miss but it makes a big difference when nothing gets pulled down.
In the command line, type this before you install anything like node, bower, etc.
cd ~/workspace

What is .rds_delta file?

I see a file in the root folder of my Tizen project called .rds_delta that contains what appears to be change commands for something. A Google search reveals nothing. Does anyone know what this file is for and if it should be kept in the Git repository, or should we add this to .gitignore?
.rds_delta file:
#delete
#add
#modify
res/wgt/author-signature.xml
res/wgt/config.xml
res/wgt/signature1.xml
It was a file that inform application installer what is changed in your app between one package build and second one. This is needed to quick application install from SDK.
Some official link: https://developer.tizen.org/development/training/native-application/application-development-process/running-applications
In my opinion it shouldn't be throw into Git repository.

How to install MySQL Connector/C on Mac OS X?

I'm writing an app in C that requires MySQL interaction, so I downloaded the Connector/C archive from the official website, and it contains bin, lib and include folders, but I don't know where to install them.
I could copy the include files into my project folder, but where can I put the lib file so that my compiled binary (and other binaries) can find it?
Thanks in advance!
This is confusing, isn't it.. don't know why they don't make this more clear.
The lib/ files go in /usr/local/lib
The include/ files go in /usr/local/include
The bin/ files go in /usr/local/bin
The /usr/.. directory isn't visible through finder afaik so you have to go at it via commandline. Best of luck
Also, in your Xcode project, make sure you add a Linked Library by going to your Target's settings, General, then adding Linked Library "libmysqlclient.dylib"
Alternatively, to do everything on the commandline by "mv", you could also execute (on cmdline):
defaults write com.apple.finder AppleShowAllFiles TRUE
and
killall Finder
to make the hidden folder /usr (and everything else) visible.
After placing your connector files (like Nektarios explicitly discribed where) and closing all "hidden folder - finder windows", execute on your cmd:
defaults write com.apple.finder AppleShowAllFiles FALSE
and again
killall Finder
to hide what have to be hidden.