[opensource] Development Environment For C++

Paul Betts bettsp at cse.ohio-state.edu
Wed Oct 25 10:56:06 EDT 2006


Yeah, it's a bit hacky, but the idea is that you have all the files you
need in one directory, then you set up some links for the particular
machine you're on. 

On Tue, 2006-10-24 at 21:07 -0400, Marc Uhrich wrote:
> Hey Paul,
> Thanks for the response, I finally found some time to sit down and
> look at it.  I'm using OS X here and for some reason the pathing is
> not right using your scripts.  At any rate, when I do your svn command
> to pull down your vimrc directory, it places it at ~/.vim/vimrc/ .
> So, the soft link points to the directory ~/.vim/vimrc instead of the
> configuration file ~/.vim/vimrc/vimrc.  In addition, the monico true
> type font is then located at ~/.vim/vimrc/MONACO.ttf.  It doesn't
> really look like it matters too much, except for the additional path.
> (to be honest, I haven't read much about configuring vim so I don't
> know what to expect as far as the path is concerned)
> 
> When I try to move the path back one directory ~/.vim/  <--
> ~/.vim/vimrc/...I get this error
> Error detected while processing /Users/Marc/.vim/plugin/a.vim:
> 
> I tried to google this error, but it didn't really come up with much.
> Anyway, I have it working but I don't understand why it gets angry
> when I move the path back, as everything seems to still be pointing to
> the right place.
> 
> Thanks again,
> Marc
> 
> 
> -----Original Message-----
> From: Paul Betts [mailto:bettsp at cse.ohio-state.edu]
> Sent: Thu 10/19/2006 3:20 PM
> To: Marc Uhrich
> Subject: Re: [opensource] Development Environment For C++
> 
> I use gVim and make; of course, this needs some clarification because
> to
> get vim to be more awesome, you need a bit of trickery.  The best way
> to
> get trickery is by stealing someone else's trickery, so I present to
> you
> all, my .vimrc. Run the following commands to set it up (This clears
> your previous .vimrc though!):
> 
> rm -rf ~/.vim ; mkdir ~/.vim
> cd ~/.vim && svn co svn://paulbetts.org/vimrc
> ln -s ~/.vim/vimrc .vimrc
> touch ~/.vimrc_local
> mkdir -p .fonts && cp ~/.vim/MONACO.ttf ~/.fonts
> fc-cache
> 
> Some notes:
> C-h/j/k/l  (For you VS'ers, that's Ctrl-h/j/k/l): Move left/down/etc..
> between split windows
> C-Tab: Move to the next ctag (:tn)
> C-S-Tab: Move to the previous ctag (:tp)
> Space (Normal mode): Search for something
> F9: Scramblify!
> ,w: Write
> ,m: DostoUnix'ify
> 
> Learn how to use ctags, it blows Intellisense out of the water.
> 
> --
> Paul Betts <bettsp at cse.ohio-state.edu>
> 
> 
> On Thu, 2006-10-19 at 15:01 -0400, Marc Uhrich wrote:
> > Hello Everyone,
> >
> > I've been programming in C# using Visual Studio (or monodevelop) for
> > the last couple of years, and would like to get back into
> programming
> > in C++.  However, I've become extremely accustomed to Visual Studios
> > "Intellisense" that automatically populates/provides the names of
> > available methods and properties for objects. I've been poking
> around
> > at different cross-platform development environments but haven't
> found
> > one that really makes me feel at home.  Because there are more
> > development environments than adults playing MMORPGs in their
> parent's
> > basements, I feel a little overwhelmed in the search. 
> > 
> >
> > As sort of a fun experiment, I'd love to hear what everyone uses as
> > their development environment and their favorite features about it.
> > Responses like "suck it up and use vi" are also acceptable if that's
> > the right answer.  I know that sometimes easy and powerful are at
> > opposite ends of the spectrum.
> >
> > Thanks,
> >
> > Marc Uhrich
> >
> > Systems Engineer @ OSU Graduate School
> >
> > 247 University Hall, 230 N Oval Mall
> >
> > Columbus, Ohio  43210
> >
> > (614) 292-6998
> >
> > 
> >
> >
> > _______________________________________________
> > Opensource mailing list
> > Opensource at cse.ohio-state.edu
> > http://mail.cse.ohio-state.edu/mailman/listinfo/opensource
> 
> 
> 
> 
> 



More information about the Opensource mailing list