[vim/vim] ctrl-c in insert mode in *.sql files wouldn't issue exit of the insert mode (Issue #12248)

6 views
Skip to first unread message

dm

unread,
Apr 11, 2023, 9:23:54 AM4/11/23
to vim/vim, Subscribed

Steps to reproduce

  1. gvim --clean
  2. :set filetype=sql
  3. enter insert mode
  4. press ctrl-c

Expected behaviour

exit insert mode like it happens for other filetypes

Version of Vim

VIM - Vi IMproved 9.0 (2022 Jun 28, compiled Jun 28 2022 13:09:53) MS-Windows 32-bit GUI version with OLE support Compiled by appveyor@APPVYR-WIN

Environment

OS: Windows 10 64 bit
terminal: not applied
$term: not applied
shell: not applied

Logs and stack traces

No response

—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/12248@github.com>

Christian Brabandt

unread,
Apr 11, 2023, 9:50:47 AM4/11/23
to vim/vim, Subscribed

cc @dfishburn

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/12248/1503392532@github.com>

Bram Moolenaar

unread,
Apr 15, 2023, 4:18:08 PM4/15/23
to vim/vim, Subscribed

The choice of CTRL-C as the default completly key was unfortunate. We can't change it now without upsetting users who have gotten used to it. You can change it by setting a variable, see ":help sql-completion-static".

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/12248/1509952344@github.com>

David Fishburn

unread,
Apr 15, 2023, 4:53:05 PM4/15/23
to vim...@googlegroups.com, reply+ACY5DGDDXDDBX25JKD...@reply.github.com, vim/vim, Subscribed
> The choice of CTRL-C as the default complete key was unfortunate. We can't change it now without upsetting users who have gotten used to it. You can change it by setting a variable, see ":help sql-completion-static".

Agreed Bram.

So many of the keys are already taken in Vim for various functions, I chose this as primarily a Windows user, which worked just fine.

But as you point out, I made it as an option to be overridden by the user.

:help sql-completion-static".

The use of "<C-C>" can be user chosen by using the following in your |.vimrc|
as it may not work properly on all platforms: >
    let g:ftplugin_sql_omni_key = '<C-C>'

David



--
--
You received this message from the "vim_dev" 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

---
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/vim/vim/issues/12248/1509952344%40github.com.

vim-dev ML

unread,
Apr 15, 2023, 4:53:25 PM4/15/23
to vim/vim, vim-dev ML, Your activity

> The choice of CTRL-C as the default complete key was unfortunate. We
can't change it now without upsetting users who have gotten used to it. You
can change it by setting a variable, see ":help sql-completion-static".

Agreed Bram.

So many of the keys are already taken in Vim for various functions, I chose
this as primarily a Windows user, which worked just fine.

But as you point out, I made it as an option to be overridden by the user.

:help sql-completion-static".

The use of "<C-C>" can be user chosen by using the following in your
|.vimrc|
as it may not work properly on all platforms: >
let g:ftplugin_sql_omni_key = '<C-C>'

David



On Sat, Apr 15, 2023 at 4:18 PM Bram Moolenaar ***@***.***>

wrote:

> The choice of CTRL-C as the default completly key was unfortunate. We
> can't change it now without upsetting users who have gotten used to it. You
> can change it by setting a variable, see ":help sql-completion-static".
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/vim/vim/issues/12248#issuecomment-1509952344>.
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>

>
> --
> --
> You received this message from the "vim_dev" 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
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ***@***.***

> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_dev/vim/vim/issues/12248/1509952344%40github.com
> <https://groups.google.com/d/msgid/vim_dev/vim/vim/issues/12248/1509952344%40github.com?utm_medium=email&utm_source=footer>
> .
>

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/12248/1509964002@github.com>

Christian Brabandt

unread,
Apr 16, 2023, 3:26:36 AM4/16/23
to vim/vim, vim-dev ML, Comment

Closed #12248 as not planned.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you commented.Message ID: <vim/vim/issue/12248/issue_event/9015942725@github.com>

Christian Brabandt

unread,
Apr 16, 2023, 3:26:37 AM4/16/23
to vim/vim, vim-dev ML, Comment

closing then.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you commented.Message ID: <vim/vim/issues/12248/1510140412@github.com>

Reply all
Reply to author
Forward
0 new messages