summaryrefslogtreecommitdiffstats
path: root/src/gui_xim.c
AgeCommit message (Collapse)Author
2024-02-06patch 9.1.0078: GTK3: using wrong style for pre-edit areav9.1.0078lilydjwg
Problem: GTK3: using wrong style for pre-edit area Solution: remove the widget name, adjust css (lilydjwg) closes: #13972 Signed-off-by: lilydjwg <lilydjwg@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2024-01-25patch 9.1.0058: Cannot map Super Keys in GTK UIv9.1.0058Casey Tucker
Problem: Cannot map Super Keys in GTK UI (Casey Tucker) Solution: Enable Super Key mappings in GTK using <D-Key> (Casey Tucker) As a developer who works in both Mac and Linux using the same keyboard, it can be frustrating having to remember different key combinations or having to rely on system utilities to remap keys. This change allows `<D-z>` `<D-x>` `<D-c>` `<D-v>` etc. to be recognized by the `map` commands, along with the `<D-S-...>` shifted variants. ```vimrc if has('gui_gtk') nnoremap <D-z> u nnoremap <D-S-Z> <C-r> vnoremap <D-x> "+d vnoremap <D-c> "+y cnoremap <D-v> <C-R>+ inoremap <D-v> <C-o>"+gP nnoremap <D-v> "+P vnoremap <D-v> "-d"+P nnoremap <D-s> :w<CR> inoremap <D-s> <C-o>:w<CR> nnoremap <D-w> :q<CR> nnoremap <D-q> :qa<CR> nnoremap <D-t> :tabe<CR> nnoremap <D-S-T> :vs#<CR><C-w>T nnoremap <D-a> ggVG vnoremap <D-a> <ESC>ggVG inoremap <D-a> <ESC>ggVG nnoremap <D-f> / nnoremap <D-g> n nnoremap <D-S-G> N vnoremap <D-x> "+x endif ``` closes: #12698 Signed-off-by: Casey Tucker <dctucker@hotmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2024-01-04patch 9.1.0006: is*() and to*() function may be unsafev9.1.0006Keith Thompson
Problem: is*() and to*() function may be unsafe Solution: Add SAFE_* macros and start using those instead (Keith Thompson) Use SAFE_() macros for is*() and to*() functions The standard is*() and to*() functions declared in <ctype.h> have undefined behavior for negative arguments other than EOF. If plain char is signed, passing an unchecked value from argv for from user input to one of these functions has undefined behavior. Solution: Add SAFE_*() macros that cast the argument to unsigned char. Most implementations behave sanely for negative arguments, and most character values in practice are non-negative, but it's still best to avoid undefined behavior. The change from #13347 has been omitted, as this has already been separately fixed in commit ac709e2fc0db6d31abb7da96f743c40956b60c3a (v9.0.2054) fixes: #13332 closes: #13347 Signed-off-by: Keith Thompson <Keith.S.Thompson@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
2023-02-21patch 9.0.1336: functions without arguments are not always declared properlyv9.0.1336Yegappan Lakshmanan
Problem: Functions without arguments are not always declared properly. Solution: Use "(void)" instead of "()". (Yegappan Lakshmanan, closes #12031)
2023-02-20patch 9.0.1330: handling new value of an option has a long "else if" chainv9.0.1330Yegappan Lakshmanan
Problem: Handling new value of an option has a long "else if" chain. Solution: Use a function pointer. (Yegappan Lakshmanan, closes #12015)
2023-01-30patch 9.0.1262: the did_set_string_option function is too longv9.0.1262Yegappan Lakshmanan
Problem: The did_set_string_option function is too long. Solution: Split off functionality to individual functions. (Yegappan Lakshmanan, Lewis Russell, closes #11904)
2023-01-08patch 9.0.1158: code is indented more than necessaryv9.0.1158Yegappan Lakshmanan
Problem: Code is indented more than necessary. Solution: Use an early return where it makes sense. (Yegappan Lakshmanan, closes #11787)
2022-11-24patch 9.0.0934: various code formatting issuesv9.0.0934Bram Moolenaar
Problem: Various code formatting issues. Solution: Improve code formatting.
2022-08-26patch 9.0.0271: using INIT() in non-header filesv9.0.0271zeertzjq
Problem: Using INIT() in non-header files. Solution: Remove INIT(). (closes #10981)
2022-05-26patch 8.2.5020: using 'imstatusfunc' and 'imactivatefunc' breaks 'foldopen'v8.2.5020Milly
Problem: Using 'imstatusfunc' and 'imactivatefunc' breaks 'foldopen'. Solution: Save and restore the KeyTyped flag. (closes #10479)
2022-05-07patch 8.2.4911: the mode #defines are not clearly namedv8.2.4911Bram Moolenaar
Problem: The mode #defines are not clearly named. Solution: Prepend MODE_. Renumber them to put the mapped modes first.
2022-01-08patch 8.2.4038: various code not used when features are disabledv8.2.4038Dominique Pelle
Problem: Various code not used when features are disabled. Solution: Add #ifdefs. (Dominique Pellé, closes #9491)
2022-01-01patch 8.2.3977: error messages are spread outv8.2.3977Bram Moolenaar
Problem: Error messages are spread out. Solution: Move more error messages to errors.h.
2021-12-12patch 8.2.3788: lambda for option that is a function may be freedv8.2.3788Yegappan Lakshmanan
Problem: Lambda for option that is a function may be garbage collected. Solution: Set a reference in the funcref. (Yegappan Lakshmanan, closes #9330)
2021-12-04patch 8.2.3735: cannot use a lambda for 'imactivatefunc'v8.2.3735Yegappan Lakshmanan
Problem: Cannot use a lambda for 'imactivatefunc'. Solution: Add lambda support for 'imactivatefunc' and 'imstatusfunc'. (Yegappan Lakshmanan, closes #9275)
2021-08-02patch 8.2.3274: macro for printf format check can be simplifiedv8.2.3274Bram Moolenaar
Problem: Macro for printf format check can be simplified. Solution: Add ATTRIBUTE_FORMAT_PRINTF(). (Dominique Pellé, issue #8635)
2021-03-18patch 8.2.2622: GTK: error when starting up and -geometry is givenv8.2.2622Bram Moolenaar
Problem: GTK: error when starting up and -geometry is given. (Dominique Pellé) Solution: Use another function to get the monitor if the window has not been created yet. (closes #7978)
2020-07-01patch 8.2.1107: 'imactivatefunc' and 'imstatusfunc' are not used in the GUIv8.2.1107Bram Moolenaar
Problem: 'imactivatefunc' and 'imstatusfunc' are not used in the GUI. Solution: Adjust the #ifdefs. (closes #6367)
2020-06-02patch 8.2.0889: using old style commentsv8.2.0889Bram Moolenaar
Problem: Using old style comments. Solution: Use // comments. (Yegappan Lakshmanan, closes #6190)
2020-06-01patch 8.2.0872: XIM code is mixed with multi-byte codev8.2.0872Bram Moolenaar
Problem: XIM code is mixed with multi-byte code. Solution: Move the XIM code to a separate file. (Yegappan Lakshmanan, closes #6177)