On Tuesday, September 11, 2012 6:29:35 PM UTC+1, 葛布林 wrote:
> On Tue, Sep 11, 2012 at 3:32 PM, William Robertson
> <[email protected]> wrote:
>
>
>
>
> I didn't touch the quoting rules - they are still the original. I'll have a
> look but I doubt I can improve on them.
>
>
>
> I assigned VARCHAR and CHAR to the TODO highlighting group so that you can
> easily replace them with the standard VARCHAR2, or if it's code you can't
> change at least you can prepare for unintended side effects. In 20 years of
> PL/SQL development I have seen a valid use for CHAR once, and that was in
> 2000.
>
>
>
>
> btw did you use all of the .vim files I posted, or just plsql.vim?
>
>
>
> William
>
> PS I think this group likes you to bottom-post, newsgroup-style, rather than
> at the top email-style.
>
>
>
> e... I am using Gmail, and when I click the "Reply", it automatically build a
> top-style...
>
> I noticed the mark of " worked well when there were multiple lines. It is in
> the sqlStringComment group which has a type of "region" behind. ( I do not
> know how to call this. I know nothing about VimL...) Maybe it would help.
>
>
>
> I agree with you that CHAR will cause more problems than VARCHAR2. Alas, I
> have to deal with trunks of legacy codes... I appreciate the idea to
> highlight such types. This would remind me add a "trim" to have a try when
> unintended things happen.
>
>
> I used all of your vim files except the _vimrc and _gvimrc. Your vimrc files
> conflicted with my menu.vim and something else. It was hard for me to debug
> so I simply removed them. Your colorscheme was hard coded at the plsql.vim
> along with a tab = 3 spaces so that luckily it worked well even without your
> vimrc files.
>
Interesting - the quoting issue goes away if you set filetype=sqloracle. My
plsql.vim just sources that so I can't think any reason for it to have its own
parsing rules for quoted text. It seems fixed if you comment out the following
lines:
syn match plsqlCharLiteral "'[^']'"
syn match plsqlStringLiteral "'\([^']\|''\)*'"
syn match plsqlStringError "'.*$"
I can't see a colourscheme defined in my plsql.vim or sqloracle.vim, although
I'd be interested to hear how you get on with katia.vim and
gfn=Consolas:h8:cANSI. The colourscheme is PL/SQL-friendly, though should also
be OK with Perl, shellscript etc (although I haven't quite worked out why Korn
shell "[[" comes up red - trying to fix that...)
I'd also be interested to hear whet you think of my subtle tab character
highlighting - it's set up in plsql.vim but activated in _gvimrc or an ftplugin
script, with
let c_show_tabs = 1
In fact I also have an ftplugin/plsql.vim containing:
if exists("b:did_plsql_ftplugin")
finish
endif
let b:did_plsql_ftplugin = 1
setlocal textwidth=160 " 80 character lines
setlocal expandtab smarttab
setlocal ts=3 sw=3 autoindent
colorscheme katia
let c_show_tabs = 1
let c_space_errors = 1
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
