067adc1ff2
runtime(doc): add back bars for the '' mark
...
this was erroneously changed in commit
85cd509885#17857
Signed-off-by: zeertzjq <zeertzjq@outlook.com >
Signed-off-by: Christian Brabandt <cb@256bit.org >
2025-08-06 13:41:05 +02:00
85cd509885
runtime(doc): Use correct option-name tags
...
closes : #17857
Signed-off-by: Hirohito Higashi <h.east.727@gmail.com >
Signed-off-by: Christian Brabandt <cb@256bit.org >
2025-08-06 12:44:36 +02:00
df68419ba0
runtime(doc): clarify the use of change marks when writing a buffer
...
related: #17008
Signed-off-by: Christian Brabandt <cb@256bit.org >
2025-04-03 12:35:51 +02:00
d32bf0a067
patch 9.1.0942: a few typos were found
...
Problem: a few typos were found
Solution: fix them (zeertzjq)
closes : #16232
Signed-off-by: zeertzjq <zeertzjq@outlook.com >
Signed-off-by: Christian Brabandt <cb@256bit.org >
2024-12-17 20:55:13 +01:00
9c3330de28
runtime(doc): fix some small errors
...
Signed-off-by: Christian Brabandt <cb@256bit.org >
2024-12-17 20:24:24 +01:00
0a4e57f44a
runtime(doc): fix a few minor errors from the last doc updates
...
1) move the section at :h inclusive-motion-selection-exclusive a few
lines below, so that it doesn't live in between the 2 exceptions.
2) remove the tag :h :!-range. It's not accurate (because it is actually
a filter) and this command is already described at :h :range!
Signed-off-by: Christian Brabandt <cb@256bit.org >
2024-12-16 10:20:51 +01:00
ed89206efe
runtime(doc): add a note about inclusive motions and exclusive selection
...
related: #16202
Signed-off-by: Christian Brabandt <cb@256bit.org >
2024-12-14 20:23:39 +01:00
fd4e47e06b
runtime(doc): clarify the effect of 'startofline' option
...
fixes : #15794
Signed-off-by: Christian Brabandt <cb@256bit.org >
2024-10-06 18:02:45 +02:00
89872f58a9
runtime(doc): update formatting and syntax
...
closes : #15800
Signed-off-by: Milly <milly.ca@gmail.com >
Signed-off-by: Christian Brabandt <cb@256bit.org >
2024-10-05 17:16:18 +02:00
f8702aeb8f
patch 9.1.0699: "dvgo" is not always an inclusive motion
...
Problem: "dvgo" is not always an inclusive motion
(Iain King-Speir)
Solution: initialize the inclusive flag to false
fixes : #15580
closes : #15582
Signed-off-by: Christian Brabandt <cb@256bit.org >
2024-08-28 20:39:24 +02:00
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
c25a7084e9
patch 9.1.0573: ex: no implicit print for single addresses
...
Problem: ex: no implicit print for single addresses
Solution: explicitly print even during single addresses,
as requested by POSIX (Mohamed Akram)
See the POSIX behaviour here:
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/ex.html#tag_20_40_13_03
Section 6b
closes : #15230
Signed-off-by: Mohamed Akram <mohd.akram@outlook.com >
Signed-off-by: Christian Brabandt <cb@256bit.org >
2024-07-12 20:18:54 +02:00
ad4d7f446d
patch 9.1.0007: can select empty inner text blocks
...
Problem: can select empty inner text blocks
(laurentalacoque)
Solution: make selecting empty inner text blocks an error
textobjects: Make selecting inner empty blocks an error
fixes : #13514
closes : #13523
Signed-off-by: Christian Brabandt <cb@256bit.org >
2024-01-04 22:11:33 +01:00
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
65672ae118
runtime(doc): clarify behaviour of ]m and ]M motions
...
In particular remove the sentence, that a missing '{'
(for ]m) or '}' (for ]M) after the cursor is an error, since
currently this is not treated as an error.
fixes : #13777
Signed-off-by: Christian Brabandt <cb@256bit.org >
2023-12-27 18:55:53 +01:00
02902b547b
runtime(doc): text-objects: document how escaped delimiters are handled
...
Signed-off-by: Christian Brabandt <cb@256bit.org >
2023-09-29 00:10:04 +02:00
a7aba6ca50
runtime(doc): format jumplist examples more consistently ( #13137 )
...
Signed-off-by: Christian Brabandt <cb@256bit.org >
2023-09-21 07:22:57 +01:00
87018255e3
patch 9.0.1921: not possible to use the jumplist like a stack
...
Problem: not possible to use the jumplist like a stack
Solution: Add the 'jumpoptions' setting to make the jumplist
a stack.
Add an option for using jumplist like tag stack
related: #7738
closes : #13134
ported from NeoVim:
- https://neovim.io/doc/user/motion.html#jumplist-stack
- neovim/neovim@39094b3
- neovim/neovim#11530
- https://vi.stackexchange.com/questions/18344/how-to-change-jumplist-behavior
Based on the feedback in the previous PR, it looks like many people like
this option.
Signed-off-by: Christian Brabandt <cb@256bit.org >
Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com >
Co-authored-by: butwerenotthereyet <58348703+butwerenotthereyet@users.noreply.github.com >
2023-09-20 20:25:17 +02:00
346ac1429c
runtime(doc): add help tag describing object-selection
...
closes : #13114
Signed-off-by: Christian Brabandt <cb@256bit.org >
2023-09-18 20:12:22 +02:00
654bdbbd32
patch 9.0.1761: g<kEnd> behaves different from g<end>
...
Problem: g<kEnd> behaves different from g<end>
Solution: Make g<kEnd> behave like g<End>
closes : #12861
Signed-off-by: Christian Brabandt <cb@256bit.org >
Co-authored-by: zeertzjq <zeertzjq@outlook.com >
2023-08-20 18:24:20 +02:00
b5f6fe9ca2
patch 9.0.1753: can't move to last non-blank char
...
Problem: can't move to last non-blank char
Solution: Make g<end> behave like that
Make it possible to move to last non-blank char on a line
We can distinguish between g0 and g^ to move to the very first character
and the first non-blank char.
And while we can move to the last screen char, we cannot go to the last
non-blank screen char.
Since I think g$ is the more widely used and known movement command (and
g<end> is synonymous to it) change the behaviour of g<end> to move to
last non-screen char instead and don't have this be the same command as
the g$ command anymore.
If you want to keep the old behaviour, you can use:
```
nnoremap g<end> g$
```
Add a test to verify the behaviour.
closes : #12593
Signed-off-by: Christian Brabandt <cb@256bit.org >
2023-08-19 15:55:35 +02:00
9fbdbb814f
Update runtime files
2022-09-27 17:30:34 +01:00
887748742d
patch 9.0.0222: no good reason why text objects are only in larger builds
...
Problem: No good reason why text objects are only in larger builds.
Solution: Graduate +textobjects.
2022-08-16 20:24:29 +01:00
e1f3fd1d02
Update runtime files
2022-08-15 18:51:32 +01:00
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
75ab590f85
Update runtime files
2022-04-18 15:36:40 +01:00
a0f659c76e
patch 8.2.4719: ">" marker sometimes not displayed in the jumplist
...
Problem: ">" marker sometimes not displayed in the jumplist.
Solution: If the buffer no longer exists show "-invalid-". (Christian
Brabandt, closes #10131 , closes #10100 )
2022-04-09 13:35:00 +01:00
cbaff5e06e
Update runtime files
2022-04-08 17:45:08 +01:00
c51cf03298
Update runtime files.
2022-02-26 12:25:45 +00:00
a4d131d110
Update runtime files
2021-12-27 21:33:07 +00:00
0e6adf8a29
Update runtime files
2021-12-16 14:41:10 +00:00
739f13a55b
patch 8.2.3795: too many #ifdefs
...
Problem: Too many #ifdefs.
Solution: Graduate the jumplist feature.
2021-12-13 13:12:53 +00:00
4700398e38
Update runtime files
2021-12-05 21:54:04 +00:00
4d8f476176
Update runtime files
2021-06-27 15:18:56 +02:00
2346a63784
Update runtime files
2021-06-13 19:02:49 +02:00
dad4473f02
Update runtime files.
2021-03-31 20:07:33 +02:00
cb80aa2d53
Update runtime files.
2020-10-26 21:12:46 +01:00
207f009326
Update runtime files.
2020-08-30 17:20:20 +02:00
98056533b9
Vim 8.2 release
2019-12-12 14:18:35 +01:00
09c6f265b2
Update runtime files.
2019-11-17 15:55:14 +01:00
5ef1c6a483
Update runtime files
2019-11-10 22:09:11 +01:00
1ff14ba24c
Update runtime files.
2019-11-02 14:09:23 +01:00
8b530c1ff9
patch 8.1.2231: not easy to move to the middle of a text line
...
Problem: Not easy to move to the middle of a text line.
Solution: Add the gM command. (Yasuhiro Matsumoto, closes #2070 )
2019-10-28 02:13:05 +01:00
61da1bfa6c
Update runtime files.
2019-06-06 12:14:49 +02:00
68e6560b84
Update runtime files.
2019-05-26 21:33:31 +02:00
a6c27c47dd
Update runtime files
2019-05-09 19:16:22 +02:00
25c9c680ec
patch 8.1.1280: remarks about functionality not in Vi clutters the help
...
Problem: Remarks about functionality not in Vi clutters the help.
Solution: Move all info about what is new in Vim or already existed in Vi to
vi_diff.txt. Remove {not in Vi} remarks. (closes #4268 ) Add
"noet" to the help files modeline. Also include many other help
file improvements.
2019-05-05 18:13:34 +02:00
26967617a3
Update runtime files.
2019-03-17 17:13:16 +01:00
c8c8849267
Update runtime files.
2018-12-27 23:59:26 +01:00
f0d58efc9d
Update runtime files.
2018-11-16 16:13:44 +01:00
