On 07.12.15 13:34, Paolo Bolzoni wrote:
> On Fri, Dec 4, 2015 at 7:05 PM, Erik Christiansen
> wrote:
> > The more structured approach also simplifies matters if it is decided to
> > place the source code under version control, but not anything generated.
> > (YMMV. And
On Sun, 6 Dec 2015, Paolo Bolzoni wrote:
>This is a good point indeed, I guess it is time to learn cmake or
>something similar to make this step easy, as manually written Makefile
>s do not really make easy multidirectory projects. Do you know a good
Not really on topic for this group, but the
On Fri, Dec 4, 2015 at 7:05 PM, Erik Christiansen
wrote:
> The more structured approach also simplifies matters if it is decided to
> place the source code under version control, but not anything generated.
> (YMMV. And version the compiler in that case ;)
This is a good
On 04.12.15 13:55, Paolo Bolzoni wrote:
> I am aware that is exactly what I asked, but I was wondering if there
> is a easy way to tell vim to ignore any filename ending by .o
The suggested glob ignore methods are simpler alternatives to explicitly
listing the filename extensions to be included,
Hi,
2015-12-4(Fri) 14:48:23 UTC+9 h_east:
> Hi Paolo,
>
> 2015-12-4(Fri) 13:55:27 UTC+9 Paolo Bolzoni:
> > Dear list,
> >
> > I use vim to write C++ code and often I start the program using a
> > command line like
> > $ vcpp classX.*
> > (vcpp is an alias for vim -u ~/.vim/vcpp/vimrc where the
Hi Paolo,
2015-12-4(Fri) 13:55:27 UTC+9 Paolo Bolzoni:
> Dear list,
>
> I use vim to write C++ code and often I start the program using a
> command line like
> $ vcpp classX.*
> (vcpp is an alias for vim -u ~/.vim/vcpp/vimrc where the C++ settings are)
>
> So vim opens the files with
On 2015-12-04, Paolo Bolzoni wrote:
> Dear list,
>
> I use vim to write C++ code and often I start the program using a
> command line like
> $ vcpp classX.*
> (vcpp is an alias for vim -u ~/.vim/vcpp/vimrc where the C++ settings are)
>
> So vim opens the files with definitions and headers.