Using vim for postgres development
Jan. 1st, 2019 06:59 pmI've written a wiki article about configuring vim for postgres development.
https://wiki.postgresql.org/wiki/Configuring_vim_for_postgres_development
I actually started to restore my vim configuration (I've lost it some time ago) and found out that these information is scattered along the web. And it is better to keep it in one place.
I've described in the article all options and plugins that I used for pg development.
If you have your own vim experience and know some tools that can be used to make development and following codestyle more easy, please add them there.
PS. I've already written about it to the mailing list. Just want to write about it in the blog too...
https://wiki.postgresql.org/wiki/Configuring_vim_for_postgres_development
I actually started to restore my vim configuration (I've lost it some time ago) and found out that these information is scattered along the web. And it is better to keep it in one place.
I've described in the article all options and plugins that I used for pg development.
If you have your own vim experience and know some tools that can be used to make development and following codestyle more easy, please add them there.
PS. I've already written about it to the mailing list. Just want to write about it in the blog too...
no subject
Date: 2019-01-02 06:58 am (UTC)(recursive make considered harmful, but postgres use it anyway).
no subject
Date: 2019-01-02 08:07 am (UTC)If you tell me more about it, I will add it to wiki article...
no subject
Date: 2019-01-02 02:15 pm (UTC):help quickfix
in the vim command line.
How I now do it:
I start make from the shell prompt,. wait until it fails, then look to the last line reading "Leaving directory ..." in the make output. Then change to this directory, run vim without arguments and type :make
Thus I get erroneous file open and cursor posititoned at the first error/warning.
no subject
Date: 2019-01-02 02:46 pm (UTC)If you don't set errorformat for something less useful than default one.
I just have old errorformat line in my .vimrc. When I've deleted it and resorted to use compiled in one (which is more terrifying than badly written perl one-liner) it started to work.