Re: ftdetect for a new SQL dialect

2016-01-10 Thread Nicola
On 2016-01-09 10:24:08 +, Nicola said: Is there a way to have the dialect be loaded directly without requiring the use to set g:sql_type_default? Is pgsql not a good choice as a default for you? Yes, for me it is. But, in the perspective of making my plugin available to a general audien

Re: ftdetect for a new SQL dialect

2016-01-09 Thread Nicola
On 2016-01-08 21:48:22 +, David Fishburn said: So, for example, the default syntax file (sqloracle.vim) links sqlKeyword to sqlSpecial, while I would want to link it to a different highlight group (and, of course, still let the user override the plugin's choice). That shouldn't happen. Th

Re: ftdetect for a new SQL dialect

2016-01-08 Thread David Fishburn
On Wed, Jan 6, 2016 at 9:59 AM, Nicola wrote: > I have defined my own PostgreSQL dialect and I would like to use it with > .pgsql files by default. Currently, I have this in my ftdetect/pgsql.vim: > >au BufNewFile,BufRead *.pgsql setfiletype sql | SQLSetType pgsql > > The problem with this is

ftdetect for a new SQL dialect

2016-01-06 Thread Nicola
I have defined my own PostgreSQL dialect and I would like to use it with .pgsql files by default. Currently, I have this in my ftdetect/pgsql.vim: au BufNewFile,BufRead *.pgsql setfiletype sql | SQLSetType pgsql The problem with this is that it first loads the default syntax files and then th