summaryrefslogtreecommitdiff
path: root/src/mbyte.c
Commit message (Collapse)AuthorAgeFilesLines
...
* patch 8.1.0779: argument for message functions is inconsistentv8.1.0779Bram Moolenaar2019-01-191-2/+2
| | | | | Problem: Argument for message functions is inconsistent. Solution: Make first argument to msg() "char *".
* patch 8.1.0745: compiler warnings for signed/unsigned stringv8.1.0745Bram Moolenaar2019-01-141-1/+1
| | | | | Problem: Compiler warnings for signed/unsigned string. Solution: Remove type casts. (John Marriott)
* patch 8.1.0743: giving error messages is not flexiblev8.1.0743Bram Moolenaar2019-01-131-10/+10
| | | | | | | | Problem: Giving error messages is not flexible. Solution: Add semsg(). Change argument from "char_u *" to "char *", also for msg() and get rid of most MSG macros. (Ozaki Kiichi, closes #3302) Also make emsg() accept a "char *" argument. Get rid of an enormous number of type casts.
* patch 8.1.0443: unnecessary static function prototypesv8.1.0443Bram Moolenaar2018-09-301-9/+0
| | | | | Problem: Unnecessary static function prototypes. Solution: Remove unnecessary prototypes.
* patch 8.1.0377: xdiff doesn't use the Vim memory allocation functionsv8.1.0377Bram Moolenaar2018-09-131-1/+1
| | | | | | Problem: Xdiff doesn't use the Vim memory allocation functions. Solution: Change the xdl_ defines. Check for out-of-memory. Rename "ignored" to "vim_ignored".
* patch 8.1.0368: GTK code has too many #ifdefs and GTK 2.10 building failsv8.1.0368Bram Moolenaar2018-09-111-20/+0
| | | | | | Problem: GTK code has too many #ifdefs and building fails with GTK 2.10. Solution: Always use gtk_widget_get_window() and define it for older GTK versions. (Ken Takata, closes #3421)
* patch 8.1.0301: GTK: input method popup displayed on wrong screen.v8.1.0301Bram Moolenaar2018-08-191-7/+9
| | | | | Problem: GTK: Input method popup displayed on wrong screen. Solution: Add the screen position offset. (Ken Takata, closes #3268)
* patch 8.1.0233: "safe" argument of call_vim_function() is always FALSEv8.1.0233Bram Moolenaar2018-08-011-2/+2
| | | | | Problem: "safe" argument of call_vim_function() is always FALSE. Solution: Remove the argument.
* patch 8.1.0182: Unicode standard was updatedv8.1.0182Bram Moolenaar2018-07-141-23/+48
| | | | | Problem: Unicode standard was updated. Solution: Include the changes. (Christian Brabandt)
* patch 8.1.0055: complete test has wrong order of argumentsv8.1.0055Bram Moolenaar2018-06-131-1/+1
| | | | | | Problem: Complete test has wrong order of arguments. Wrong type for sentinel variable. Solution: Swap arguments, use VAR_UNKNOWN. (Ozaki Kiichi)
* patch 8.1.0053: first argument of 'completefunc' has inconsistent typev8.1.0053Bram Moolenaar2018-06-121-5/+4
| | | | | | | Problem: The first argument given to 'completefunc' can be Number or String, depending on the value. Solution: Avoid guessing the type of an argument, use typval_T in the callers of call_vim_function(). (Ozaki Kiichi, closes #2993)
* patch 8.0.1849: compiler warning for unused arguments, missing prototypev8.0.1849Bram Moolenaar2018-05-171-1/+1
| | | | | Problem: compiler warning for unused arguments and missing prototype Solution: Add UNUSED. Add static.
* patch 8.0.1677: no compiler warning for wrong format in vim_snprintf()v8.0.1677Bram Moolenaar2018-04-081-2/+2
| | | | | Problem: No compiler warning for wrong format in vim_snprintf(). Solution: Add printf attribute for gcc. Fix reported problems.
* patch 8.0.1564: too many #ifdefsv8.0.1564Bram Moolenaar2018-03-041-12/+7
| | | | | | Problem: Too many #ifdefs. Solution: Graduate the +autocmd feature. Takes away 450 #ifdefs and increases code size of tiny Vim by only 40 Kbyte.
* patch 8.0.1550: various small problems in source filesv8.0.1550Bram Moolenaar2018-02-271-1/+0
| | | | | Problem: Various small problems in source files. Solution: Fix the problems.
* patch 8.0.1496: clearing a pointer takes two linesv8.0.1496Bram Moolenaar2018-02-101-2/+1
| | | | | | Problem: Clearing a pointer takes two lines. Solution: Add VIM_CLEAR() and replace vim_clear(). (Hirohito Higashi, closes #2629)
* patch 8.0.1433: illegal memory access after undov8.0.1433Bram Moolenaar2018-01-271-1/+5
| | | | | | Problem: Illegal memory access after undo. (Dominique Pelle) Solution: Avoid the column becomes negative. (Christian Brabandt, closes #2533)
* patch 8.0.1350: cannot build with +eval and -multi_bytev8.0.1350Bram Moolenaar2017-11-271-2/+2
| | | | | | Problem: Cannot build with +eval and -multi_byte. Solution: Adjust #ifdefs. (John Marriott) Always include the multi_byte feature when an input method feature is enabled.
* patch 8.0.1344: using 'imactivatefunc' in the GUI does not workv8.0.1344Bram Moolenaar2017-11-261-9/+16
| | | | | Problem: Using 'imactivatefunc' in the GUI does not work. Solution: Do not use 'imactivatefunc' and 'imstatusfunc' in the GUI.
* patch 8.0.1342: cannot build with Motif and multi-bytev8.0.1342Bram Moolenaar2017-11-251-1/+1
| | | | | Problem: Cannot build with Motif and multi-byte. (Mohamed Boughaba) Solution: Use the right input method status flag. (closes #2374)
* patch 8.0.1340: MS-Windows: cannot build GUI without IMEv8.0.1340Bram Moolenaar2017-11-251-1/+8
| | | | | Problem: MS-Windows: cannot build GUI without IME. Solution: Define im_get_status() and im_set_active() when IME is not used.
* patch 8.0.1338: USE_IM_CONTROL is confusing and incompletev8.0.1338Bram Moolenaar2017-11-251-82/+89
| | | | | Problem: USE_IM_CONTROL is confusing and incomplete. Solution: Just use FEAT_MBYTE. Call 'imactivatefunc' also without GUI.
* patch 8.0.1337: typo in #ifdefv8.0.1337Bram Moolenaar2017-11-251-1/+1
| | | | | Problem: Typo in #ifdef. Solution: Fix the #if line.
* patch 8.0.1336: cannot use imactivatefunc() unless compiled with +ximv8.0.1336Bram Moolenaar2017-11-251-10/+62
| | | | | | Problem: Cannot use imactivatefunc() unless compiled with +xim. Solution: Allow using imactivatefunc() when not compiled with +xim. (Yasuhiro Matsumoto, closes #2349)
* patch 8.0.1236: Mac features are confusingv8.0.1236Bram Moolenaar2017-10-281-13/+13
| | | | | | Problem: Mac features are confusing. Solution: Make feature names more consistent, add "osxdarwin". Rename feature flags, cleanup Mac code. (Kazunobu Kuriyama, closes #2178)
* patch 8.0.1203: terminal window mistreats composing charactersv8.0.1203Bram Moolenaar2017-10-151-0/+2
| | | | | | Problem: Terminal window mistreats composing characters. Solution: Count composing characters with the base character. (Ozaki Kiichi, closes #2195)
* patch 8.0.1152: encoding of error message wrong in Cygwin terminalv8.0.1152Bram Moolenaar2017-09-261-30/+50
| | | | | Problem: Encoding of error message wrong in Cygwin terminal. Solution: Get locale from environment variables. (Ken Takata)
* patch 8.0.1099: warnings for GDK callsv8.0.1099Bram Moolenaar2017-09-131-0/+74
| | | | | | Problem: Warnings for GDK calls. Solution: Use other calls for GTK 3 and fix a few problems. (Kazunobu Kuriyama)
* patch 8.0.1084: GTK build has compiler warningsv8.0.1084Bram Moolenaar2017-09-091-2/+1
| | | | | | Problem: GTK build has compiler warnings. (Christian Brabandt) Solution: Get screen size with a different function. (Ken Takata, Yasuhiro Matsumoto)
* patch 8.0.1060: when imstyle is one, mapping <Left> breaks preeditingv8.0.1060Bram Moolenaar2017-09-051-1/+5
| | | | | | Problem: When imstyle is one, mapping <Left> breaks preediting. Solution: Pass though preediting key-events. (Yasuhiro Matsumoto, closes #2064, closes #2063)
* patch 8.0.1026: GTK on-the-spot input has problemsv8.0.1026Bram Moolenaar2017-08-301-102/+238
| | | | | | Problem: GTK on-the-spot input has problems. (Gerd Wachsmuth) Solution: Support over-the-spot. (Yukihiro Nakadaira, Ketn Takata, closes #1215)
* patch 8.0.1014: old compiler doesn't know uint32_tv8.0.1014Bram Moolenaar2017-08-301-2/+2
| | | | | | Problem: Old compiler doesn't know uint32_t. Warning for using NULL instead of NUL. Solution: Use UINT32_T. Use NUL instead of NULL.
* patch 8.0.0985: libvterm has its own idea of character widthv8.0.0985Bram Moolenaar2017-08-221-0/+22
| | | | | | Problem: Libvterm has its own idea of character width. Solution: Use the Vim functions for character width and composing to avoid a mismatch. (idea by Yasuhiro Matsumoto)
* patch 8.0.0652: unicode information is outdatedv8.0.0652Bram Moolenaar2017-06-221-49/+112
| | | | | Problem: Unicode information is outdated. Solution: Update to Unicode 10. (Christian Brabandt)
* patch 8.0.0620: checking for HAVE_GTK_MULTIHEAD is not neededv8.0.0620Bram Moolenaar2017-06-051-11/+2
| | | | | | Problem: Since we only support GTK versions that have it, the ckeck for HAVE_GTK_MULTIHEAD is no longer needed. Solution: Remove HAVE_GTK_MULTIHEAD. (Kazunobu Kuriyama)
* patch 8.0.0452: some macros are in lower casev8.0.0452Bram Moolenaar2017-03-121-1/+1
| | | | | Problem: Some macros are in lower case. Solution: Make a few more macros upper case.
* patch 8.0.0451: some macros are in lower casev8.0.0451Bram Moolenaar2017-03-121-2/+1
| | | | | | Problem: Some macros are in lower case. Solution: Make a few more macros upper case. Avoid lower case macros use an argument twice.
* patch 8.0.0252: not properly recognizing word characters between 128 and 255v8.0.0252Bram Moolenaar2017-01-281-2/+8
| | | | | | | Problem: Characters below 256 that are not one byte are not always recognized as word characters. Solution: Make vim_iswordc() and vim_iswordp() work the same way. Add a test for this. (Ozaki Kiichi)
* patch 8.0.0175: setting language on MS-Windows does not always workv8.0.0175Bram Moolenaar2017-01-121-42/+1
| | | | | | Problem: Setting language in gvim on MS-Windows does not work when libintl.dll is dynamically linked with msvcrt.dll. Solution: Use putenv() from libintl as well. (Ken Takata, closes #1082)
* patch 8.0.0123v8.0.0123Bram Moolenaar2016-12-031-1/+1
| | | | | Problem: Modern Sun compilers define "__sun" instead of "sun". Solution: Use __sun. (closes #1296)
* patch 7.4.2293v7.4.2293Bram Moolenaar2016-08-291-1/+1
| | | | | Problem: Modelines in source code are inconsistant. Solution: Use the same line in most files. Add 'noet'. (Naruhiko Nishino)
* patch 7.4.2028v7.4.2028Bram Moolenaar2016-07-111-1/+1
| | | | | Problem: cppcheck warns for using index before limits check. Solution: Swap the expressions. (Dominique Pelle)
* patch 7.4.2019v7.4.2019Bram Moolenaar2016-07-101-0/+3
| | | | | Problem: When ignoring case utf_fold() may consume a lot of time. Solution: Optimize for ASCII.
* patch 7.4.1960v7.4.1960Bram Moolenaar2016-06-261-14/+130
| | | | | Problem: Unicode standard 9 was released. Solution: Update the character property tables. (Christian Brabandt)
* patch 7.4.1697v7.4.1697Bram Moolenaar2016-04-021-295/+302
| | | | | | | Problem: Display problems when the 'ambiwidth' and 'emoji' options are not set properly or the terminal doesn't behave as expected. Solution: After drawing an ambiguous width character always position the cursor.
* patch 7.4.1642v7.4.1642Bram Moolenaar2016-03-241-58/+0
| | | | | | Problem: Handling emoji characters as full width has problems with backwards compatibility. Solution: Only put characters in the 1f000 range in the emoji table.
* patch 7.4.1630v7.4.1630Bram Moolenaar2016-03-211-0/+6
| | | | | Problem: Unicode table for double width is outdated. Solution: Update to the latest Unicode standard.
* patch 7.4.1629v7.4.1629Bram Moolenaar2016-03-211-144/+203
| | | | | | | | Problem: Handling emoji characters as full width has problems with backwards compatibility. Solution: Remove ambiguous and double width characters from the emoji table. Use a separate table for the character class. (partly by Yasuhiro Matsumoto)
* patch 7.4.1620v7.4.1620Bram Moolenaar2016-03-201-144/+147
| | | | | Problem: Emoji characters are not considered as a kind of word character. Solution: Give emoji characters a word class number. (Yasuhiro Matsumoto)
* patch 7.4.1604v7.4.1604Bram Moolenaar2016-03-191-5/+144
| | | | | | | Problem: Although emoji characters are ambiguous width, best is to treat them as full width. Solution: Update the Unicode character tables. Add the 'emoji' options. (Yasuhiro Matsumoto)