> *Not everyone* gets around to doing updates/upgrades *immediately*!
>
NeXT machines were sold from 1988 to 1993, and it's OS, Next step lingered
on for a while, bits of it apparently ending up in Mac OS X.
https://www.computinghistory.org.uk/det/927/NeXT-Computers/
Sales weren't spectacular, and with the newest machines 30 years old, it's
unlikely any are being updated regularly, so a cautious policy as proposed
sounds perfectly reasonable.
--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/2fbfd24d9cf268289e38f83a09f0bb05.squirrel%40webmail.vybenetworks.com.
Thursday, August 28, 2025
Re: Using a regex to mark a particular form as accepted spelling?
On 2025-08-28 04:06, Maxim Kim wrote:
> syntax match MyPages /\<p\d\+\%(-\d\+\)\=\>/ contains=@NoSpell
My spell-highlight is now much more useful because it's no longer so
visually cluttered. Thanks so much!
-tim
--
--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/aLBEgkbe_bs1VLEK%40thechases.com.
> syntax match MyPages /\<p\d\+\%(-\d\+\)\=\>/ contains=@NoSpell
My spell-highlight is now much more useful because it's no longer so
visually cluttered. Thanks so much!
-tim
--
--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/aLBEgkbe_bs1VLEK%40thechases.com.
Re: Using a regex to mark a particular form as accepted spelling?
Try
syntax match MyPages /\<p\d\+\%(-\d\+\)\=\>/ contains=@NoSpell
This would work for an existing buffer, to (auto)apply it, let's assume you're in filetype=text
augroup NoSpellPages
au!
au Filetype text syntax match MyPages /\<p\d\+\%(-\d\+\)\=\>/ contains=@NoSpell
augroup END
au!
au Filetype text syntax match MyPages /\<p\d\+\%(-\d\+\)\=\>/ contains=@NoSpell
augroup END
On Thursday, August 28, 2025 at 11:29:47 AM UTC+10 Tim Chase wrote:
Taking some notes, I have a lot of page-references of the form "p12",
"p35-36", etc. With 'spell' set, it highlights them as misspelled
words. However, I can formulate a regex that would identify these:
/\<p\d\+\%(-\d\+\)\=\>/
Is there a way to convey this information to vim so that they get
ignored for spellcheck purposes?
I know there's some highlight-group aspect that might be usable,
contains=@NoSpell
as detailed at `:help spell-syntax`, so I think I have the relevant
pieces, but am just failing to put them together in the right way
(writing syntax files is not my forte)
What do I need to do to assemble these so spell-checking ignores my
page-number ranges?
Thanks,
-tim
--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/9c827a6a-778d-4c86-856f-d115aba83bddn%40googlegroups.com.
Wednesday, August 27, 2025
Re: Anybody using NextStep?
Not everyone gets around to doing updates/upgrades immediately!
I concur by supporting this more disciplined (gradual) approach (mentionned below by Charles Campbell) of blocking out the code using #ifdef, then allowing the resultant "handicapped" code into the "wild" for at least 6 months.
After 6 months, any newer release is likely to have been installed and tested by those who have a critical vested interest in ensuring continuity of their preferred tools, especially if they know their OS (a.k.a. NextStep) is being gradually abandoned by upstream tool providers like Vim/GVim or others.
If the OS providers themselves consider the tool critical enough to their own internal processes, or as part of the User-expected toolset deployed with their OS, I am sure that they will make their voices be heard and speak up!
On 2025-08-26 15:59, Christian Brabandt wrote:
Charles, On Mo, 25 Aug 2025, Charles Campbell wrote:I think it would be a Good Idea to have a procedure for this sort of thing, and to publish it in the Vim Manual someplace. *1 announce that something is being considered for deprecation (comments accepted) *2 deprecate by surrounding the relevant code with #ifdef blocks and await any screams of protest. With this approach you'll get notified if anyone is using the feature/support and they can reverse it by putting a #define SOMETHING in vim.h. *3 release vim with the #ifdef SOMETHING blocks *4 next release remove the SOMETHING blocks At any point until the last one reversal of the change is easy. *2 is likely to get protestations amongst those who pay attention to the vim/vimdev groups. *3 will get protestations from those who are using the deprecated feature. Finally, *4 will remove the feature/support.Thanks, that makes a lot of sense. Yes I need to document this, it's been on my list for a while already. Thanks, Christian
Using a regex to mark a particular form as accepted spelling?
Taking some notes, I have a lot of page-references of the form "p12",
"p35-36", etc. With 'spell' set, it highlights them as misspelled
words. However, I can formulate a regex that would identify these:
/\<p\d\+\%(-\d\+\)\=\>/
Is there a way to convey this information to vim so that they get
ignored for spellcheck purposes?
I know there's some highlight-group aspect that might be usable,
contains=@NoSpell
as detailed at `:help spell-syntax`, so I think I have the relevant
pieces, but am just failing to put them together in the right way
(writing syntax files is not my forte)
What do I need to do to assemble these so spell-checking ignores my
page-number ranges?
Thanks,
-tim
--
--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/aK-xAQaL2k5pM-cL%40thechases.com.
"p35-36", etc. With 'spell' set, it highlights them as misspelled
words. However, I can formulate a regex that would identify these:
/\<p\d\+\%(-\d\+\)\=\>/
Is there a way to convey this information to vim so that they get
ignored for spellcheck purposes?
I know there's some highlight-group aspect that might be usable,
contains=@NoSpell
as detailed at `:help spell-syntax`, so I think I have the relevant
pieces, but am just failing to put them together in the right way
(writing syntax files is not my forte)
What do I need to do to assemble these so spell-checking ignores my
page-number ranges?
Thanks,
-tim
--
--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/aK-xAQaL2k5pM-cL%40thechases.com.
Tuesday, August 26, 2025
Text props/virtual text
Is it possible in Vim to have multiline virtual text?
Like `virtual_lines` (?) in nvim?
The only issue related to this I found Issue #10842
And that was closed completely disallowing newlines in the virtual text.
However it looks like it IS possible to have multiline text by allowing that to wrap...
The idea is to have LSP messages or git comments (github) displayed through multiple lines. For example for code reviews with comments displayed...
Sincerely,
Andrew
Sent by
from my Android device. --
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/35e244f1.1756254577039%40imap.mtc.md.
Like `virtual_lines` (?) in nvim?
The only issue related to this I found Issue #10842
And that was closed completely disallowing newlines in the virtual text.
However it looks like it IS possible to have multiline text by allowing that to wrap...
The idea is to have LSP messages or git comments (github) displayed through multiple lines. For example for code reviews with comments displayed...
Sincerely,
Andrew
Sent by
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/35e244f1.1756254577039%40imap.mtc.md.
Re: Anybody using NextStep?
Charles,
On Mo, 25 Aug 2025, Charles Campbell wrote:
> I think it would be a Good Idea to have a procedure for this sort of thing,
> and to publish it in the Vim Manual someplace.
>
> *1 announce that something is being considered for deprecation (comments
> accepted)
> *2 deprecate by surrounding the relevant code with #ifdef blocks and await
> any screams of protest. With this approach you'll get notified if anyone is
> using the feature/support and they can reverse it by putting a #define
> SOMETHING in vim.h.
> *3 release vim with the #ifdef SOMETHING blocks
> *4 next release remove the SOMETHING blocks
>
> At any point until the last one reversal of the change is easy. *2 is likely
> to get protestations amongst those who pay attention to the vim/vimdev
> groups. *3 will get protestations from those who are using the deprecated
> feature. Finally, *4 will remove the feature/support.
Thanks, that makes a lot of sense. Yes I need to document this, it's
been on my list for a while already.
Thanks,
Christian
--
Canada Post doesn't really charge 32 cents for a stamp. It's 2 cents
for postage and 30 cents for storage.
-- Gerald Regan, Cabinet Minister, 12/31/83 Financial Post
--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/aK4SPucmbMA0zO0m%40256bit.org.
On Mo, 25 Aug 2025, Charles Campbell wrote:
> I think it would be a Good Idea to have a procedure for this sort of thing,
> and to publish it in the Vim Manual someplace.
>
> *1 announce that something is being considered for deprecation (comments
> accepted)
> *2 deprecate by surrounding the relevant code with #ifdef blocks and await
> any screams of protest. With this approach you'll get notified if anyone is
> using the feature/support and they can reverse it by putting a #define
> SOMETHING in vim.h.
> *3 release vim with the #ifdef SOMETHING blocks
> *4 next release remove the SOMETHING blocks
>
> At any point until the last one reversal of the change is easy. *2 is likely
> to get protestations amongst those who pay attention to the vim/vimdev
> groups. *3 will get protestations from those who are using the deprecated
> feature. Finally, *4 will remove the feature/support.
Thanks, that makes a lot of sense. Yes I need to document this, it's
been on my list for a while already.
Thanks,
Christian
--
Canada Post doesn't really charge 32 cents for a stamp. It's 2 cents
for postage and 30 cents for storage.
-- Gerald Regan, Cabinet Minister, 12/31/83 Financial Post
--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/aK4SPucmbMA0zO0m%40256bit.org.
Subscribe to:
Posts (Atom)