thac0/vim
1
0
Fork 0
forked from aniani/vim
Code Activity
20,065 Commits 1 Branch 1,905 Tags
cca3df9275c6f76e3b31ad9b13ced91a44e1855b
Commit Graph

184 Commits

Author SHA1 Message Date
h-east
52e7cc26d8 runtime(doc): tweak documentation style a bit 
closes: #15371

Signed-off-by: h-east <h.east.727@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
 2024-07-28 17:03:29 +02:00
Christian Brabandt
22105fd1fe patch 9.1.0589: vi: d{motion} and cw work differently than expected 
Problem:  vi: d{motion} and cw command work differently than expected
Solution: add new cpo-z flag to make the behaviour configurable

There are two special vi compatible behaviours (or should I say bugs?):

1): cw behaves differently than dw. That is, because cw is special cased
    by Vim and is effectively aliased to ce.
    POSIX behaviour is documented here:
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/vi.html#tag_20_152_13_81

2): d{motion} may make the whole delete operation linewise, if the start
    and end of the motion are on different lines and there are only
    blanks before the start and after the end of the motion.
    Did not find a related POSIX link that requires this behaviour.

Both behaviours can be considered inconsistent, but we cannot easily
change it, because it would be a backward incompatible change and also
incompatible to how classic vi behaved.

So let's add the new cpo flag "z", which when not included fixes both
behaviours and make them more consistent to what users would expect.

This has been requested several times:
https://groups.google.com/d/msg/vim_use/aaBqT6ECkA4/ALf4odKzEDgJ
https://groups.google.com/d/msg/vim_dev/Dpn3xtUF16I/T6JcOPKN6usJ
http://www.reddit.com/r/vim/comments/26nut8/why_does_cw_work_like_ce/
https://groups.google.com/d/msg/vim_use/vunNWLFWfQg/MmJh_ZGaAgAJ
https://github.com/vim/vim/issues/4390

So in summary, if you want to have the w motion work more consistent,
remove the 'z' from the cpo settings.

related: #4390
closes: #15263

Signed-off-by: Christian Brabandt <cb@256bit.org>
 2024-07-15 20:51:11 +02:00
Christian Brabandt
ecd642af43 runtime(doc): clarify, that register 1-9 will always be shifted 
related: #15077

Signed-off-by: Christian Brabandt <cb@256bit.org>
 2024-06-23 20:24:52 +02:00
Christian Brabandt
946f61c405 runtime(doc): clarify when text properties are cleared 
related: #15030

Signed-off-by: Christian Brabandt <cb@256bit.org>
 2024-06-17 13:17:58 +02:00
Christian Brabandt
5cf5301e28 runtime(doc): clarify temporary file clean up 
related: #14770

Co-authored-by: Enno <Konfekt@users.noreply.github.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
 2024-05-18 10:15:04 +02:00
h-east
53753f6a49 runtime(doc): Fix typos in help documents 
closes: #14720

Co-authored-by: Christian Clason <c.clason@uni-graz.at>
Signed-off-by: h-east <h.east.727@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
 2024-05-05 18:42:31 +02:00
Yegappan Lakshmanan
f01493c550 patch 9.1.0329: String interpolation fails for Dict type 
Problem:  String interpolation fails for Dict type
Solution: Support Dict data type properly, also support :put =Dict
          (without having to convert it to string() first)
          (Yegappan Lakshmanan)

fixes: #14529
closes: #14541

Signed-off-by: Yegappan Lakshmanan <yegappan@yahoo.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
 2024-04-14 23:21:02 +02:00
Christian Brabandt
b4ddc6c11e patch 9.1.0000: Vim 9.1 release 
Problem:  Need a new release
Solution: Release Vim 9.1

Signed-off-by: Christian Brabandt <cb@256bit.org>
 2024-01-02 16:51:11 +01:00
K.Takata
955652f6df runtime(doc): Update change.txt (#13725) 
Fix-up and clarify commit  e06f2b498c

Signed-off-by: Ken Takata <kentkt@csc.jp>
Signed-off-by: Christian Brabandt <cb@256bit.org>
 2023-12-19 20:15:47 +01:00
Christian Brabandt
e06f2b498c runtime(doc): fix typo in change.txt 
Signed-off-by: Christian Brabandt <cb@256bit.org>
 2023-12-08 21:22:38 +01:00
Roy Orbitson
2103a56eab runtime(doc): remove non-existent parameter in shift-command (#13626) 
The variant with the {count} parameter is explained in the next item.

Signed-off-by: Christian Brabandt <cb@256bit.org>
 2023-12-05 15:44:33 +01:00
Christian Brabandt
ac63787734 patch 9.0.2108: [security]: overflow with count for :s command 
Problem:  [security]: overflow with count for :s command
Solution: Abort the :s command if the count is too large

If the count after the :s command is larger than what fits into a
(signed) long variable, abort with e_value_too_large.

Adds a test with INT_MAX as count and verify it correctly fails.

It seems the return value on Windows using mingw compiler wraps around,
so the initial test using :s/./b/9999999999999999999999999990 doesn't
fail there, since the count is wrapping around several times and finally
is no longer larger than 2147483647. So let's just use 2147483647 in the
test, which hopefully will always cause a failure

Signed-off-by: Christian Brabandt <cb@256bit.org>
 2023-11-16 22:04:37 +01:00
Christian Brabandt
476733f3d0 patch 9.0.1915: r_CTRL-C works differently in visual mode 
Problem:  r_CTRL-C works differently in visual mode
Solution: Make r_CTRL-C behave consistent in visual mode
          in terminal and Windows GUI

in visual mode, r CTRL-C behaves strange in Unix like environments. It
seems to end visual mode, but still is waiting for few more chars,
however it never seems to replace it by any characters and eventually
just returns back into normal mode.

In contrast in Windows GUI mode, r_CTRL-C replaces in the selected area
all characters by a literal CTRL-C.

Not sure why it behaves like this. It seems in the Windows GUI, got_int
is not set and therefore behaves as if any other normal character has
been pressed.

So remove the special casing of what happens when got_int is set and
make it always behave like in Windows GUI mode. Add a test to verify it
always behaves like replacing in the selected area each selected
character by a literal CTRL-C.

closes: #13091
closes: #13112

Signed-off-by: Christian Brabandt <cb@256bit.org>
 2023-09-19 20:45:07 +02:00
Bram Moolenaar
71badf9547 Update runtime files 2023-04-22 22:40:14 +01:00
Bram Moolenaar
dd60c365cd Update runtime files 2023-02-27 15:49:53 +00:00
Bram Moolenaar
938ae280c7 Update runtime files. 2023-02-20 20:44:55 +00:00
Bram Moolenaar
b59ae59a58 Update runtime files 2022-11-23 23:46:31 +00:00
Bram Moolenaar
9712ff1288 Update runtime files 2022-09-18 13:04:22 +01:00
Bram Moolenaar
2ecbe53f45 Update runtime files 2022-07-29 21:36:21 +01:00
Bram Moolenaar
eb49041875 release version 9.0 
Problem:    About time to release Vim 9.0.
Solution:   Update the version number everywhere.
 2022-06-28 13:44:46 +01:00
Bram Moolenaar
cfa8f9a3f2 Update runtime files 2022-06-03 21:59:47 +01:00
Bram Moolenaar
d899e51120 Update runtime files 2022-05-07 21:54:03 +01:00
Bram Moolenaar
2bf875f881 patch 8.2.4907: some users do not want a line comment always inserted 
Problem:    Some users do not want a line comment always inserted.
Solution:   Add the '/' flag to 'formatoptions' to not repeat the comment
            leader after a statement when using "o".
 2022-05-07 14:54:11 +01:00
Shougo Matsushita
509142ab7a patch 8.2.4881: "P" in Visual mode still changes some registers 
Problem:    "P" in Visual mode still changes some registers.
Solution:   Make "P" in Visual mode not change any register. (Shougo
            Matsushita, closes #10349)
 2022-05-06 11:45:09 +01:00
Bram Moolenaar
75ab590f85 Update runtime files 2022-04-18 15:36:40 +01:00
Bram Moolenaar
1588bc8ebe Update runtime files 2022-03-08 21:35:07 +00:00
Bram Moolenaar
c51cf03298 Update runtime files. 2022-02-26 12:25:45 +00:00
Bram Moolenaar
a2baa73d1d Update runtime files. 2022-02-04 16:09:54 +00:00
Bram Moolenaar
f10911e5db Update runtime files 2022-01-29 22:20:48 +00:00
Bram Moolenaar
04fb916684 Update runtime files 2021-12-30 20:24:12 +00:00
Bram Moolenaar
a4d131d110 Update runtime files 2021-12-27 21:33:07 +00:00
Bram Moolenaar
2286304cdb Update runtime files 2021-10-16 15:23:36 +01:00
Bram Moolenaar
4d8f476176 Update runtime files 2021-06-27 15:18:56 +02:00
Bram Moolenaar
2346a63784 Update runtime files 2021-06-13 19:02:49 +02:00
Christian Brabandt
544a38e44d patch 8.2.2971: cannot yank a block without trailing spaces 
Problem:    Cannot yank a block without trailing spaces.
Solution:   Add the "zy" command. (Christian Brabandt, closes #8292)
 2021-06-10 19:39:11 +02:00
Christian Brabandt
2fa9384ca1 patch 8.2.2914: cannot paste a block without adding padding 
Problem:    Cannot paste a block without adding padding.
Solution:   Add "zp" and "zP" which paste without adding padding. (Christian
            Brabandt, closes #8289)
 2021-05-30 22:17:25 +02:00
Bram Moolenaar
c8cdf0f80b Update runtime files. 2021-03-13 13:28:13 +01:00
Bram Moolenaar
e0e3917554 Update runtime files. 2021-01-25 21:14:57 +01:00
Bram Moolenaar
4466ad6baa Update runtime files 2020-11-21 13:16:30 +01:00
Bram Moolenaar
3132cddd20 Update runtime files 2020-11-05 20:41:49 +01:00
Bram Moolenaar
55e29611d2 patch 8.2.1933: cannot sort using locale ordering 
Problem:    Cannot sort using locale ordering.
Solution:   Add a flag for :sort and sort() to use the locale. (Dominique
            Pellé, closes #7237)
 2020-11-01 13:57:44 +01:00
Bram Moolenaar
207f009326 Update runtime files. 2020-08-30 17:20:20 +02:00
Bram Moolenaar
2547aa930b Update runtime files. 2020-07-26 17:00:44 +02:00
Bram Moolenaar
acc2240640 Update runtime files 2020-06-07 21:07:18 +02:00
Bram Moolenaar
e52702f003 patch 8.2.0901: formatting CJK text isn't optimal 
Problem:    Formatting CJK text isn't optimal.
Solution:   Properly break CJK lines. (closes #3875)
 2020-06-04 18:22:13 +02:00
Bram Moolenaar
7ceefb35c8 Update runtime files 2020-05-01 16:07:38 +02:00
Bram Moolenaar
2c7f8c574f Update runtime files 2020-04-20 19:52:53 +02:00
Bram Moolenaar
d1caa941d8 Update runtime files 2020-04-10 22:10:56 +02:00
Bram Moolenaar
ebdf3c964a Update runtime files. 2020-02-15 21:41:42 +01:00
Bram Moolenaar
6f345a1458 patch 8.2.0017: OS/2 and MS-DOS are still mentioned 
Problem:    OS/2 and MS-DOS are still mentioned, even though support was
            removed long ago.
Solution:   Update documentation. (Yegappan Lakshmanan, closes #5368)
 2019-12-17 21:27:18 +01:00