News for hackers. Stuff that matters.
Re:If you love automation, why is your development environme... by npsimons on Wednesday May 08, 2013 @10:10AM (#5674181)
If your team is checking in to the central repository such personal things as config files for development environments, you've got bigger problems. Sure, occasional snippets (such as a .dir-locals.el for style), but whole configs? WTF?
Re:If you love automation, why is your development environme... by jaredmcateer on Wednesday May 08, 2013 @12:14PM (#5675039)
The environment is shared for a consistency, if I'm sshing into the environment to do my work then that means I need the environment updated with my config and that either means that we need to share configs on the vagrant user or setup the environment to provision settings for every user of that environment which sounds unmaintainable. It's easier to just work locally through the share directory.
Re:If you love automation, why is your development environme... by sikhnerd on Wednesday May 08, 2013 @01:30PM (#5675578)
Use can easily do something like this for one-off edits "vim scp://[email protected]//path/to/document" or use netrw for a more robust solution to using your local vim to edit remotly. http://www.drchip.org/astronaut/vim/index.html#NETRW
Re:If you love automation, why is your development environme... by jaredmcateer on Wednesday May 08, 2013 @04:26PM (#5676680)
Or you can just edit within the shared directory between your local machine and the environment.