Skip to content

Commit 7005c1c

Browse files
author
Jorengarenar
committed
Configuration
1 parent 175f149 commit 7005c1c

File tree

3 files changed

+339
-156
lines changed

3 files changed

+339
-156
lines changed

README.md

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,18 @@ git clone git://github.com/Jorengarenar/vim-SQL-UPPER.git
2323
## Usage
2424

2525
When you type an SQL keyword in an SQL file, it will be automatically uppercased
26-
after you finish writting it. Words in comments and strings will be ignored.
26+
after you finish writting it.
2727

28-
---
28+
Words in comments and strings will be ignored.
2929

30-
Based on: [vim-uppercase-sql](https://github.com/alcesleo/vim-uppercase-sql)
30+
## Configuration
31+
32+
There is one variable, `g:SQL_UPPER`. Default value is `1`
33+
| Value | Description |
34+
|:------:|:------------|
35+
| 1 | Keywords from Wikipedia's list of [SQL reserved word](https://en.wikipedia.org/w/index.php?title=SQL_reserved_words&oldid=1016896932) marked as in SQL:2016 |
36+
| 2 | All keywords from Wikipedia's list of [SQL reserved word](https://en.wikipedia.org/w/index.php?title=SQL_reserved_words&oldid=1016896932) |
37+
| 5 | Keywords returned by `syntaxcomplete#OmniSyntaxList()` function |
38+
| 10 | Keywords from Drupal's [List of SQL reserved words](https://www.drupal.org/docs/develop/coding-standards/list-of-sql-reserved-words) |
39+
| `list` | You can provide your own list of keywords, e.g. `let g:SQL_UPPER = [ "select", "from" ]` |
40+
| * | Everything else disables auto-uppering |

0 commit comments

Comments
 (0)