On Sat, 29 Apr 2023 12:37:19 -0700
Stan Brown <the_stan_brown@fastmail.fm> wrote:
> Some time after that, I'm not sure when but certainly by the release of
> Windows 10, it became possible to disable SFNs for any particular disk
> partition. And sometime after that, "LFNs only" became the default. But
> your disk is obviously set to create SFNs from longer filenames.
I donno if something changed in Windows 11, but it doesn't seem like
"LFN only" is the default anymore. I didn't change any setting (didnt
even know about them) and I get the same behavior Mike describes. It's
just that I never had multiple files where one's extension is a
substring of the other's, so I havent faced this issue.
--
Enan
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/20230501095806.00000459%40gmail.com.
Sunday, April 30, 2023
Saturday, April 29, 2023
Re: surprising glob() result on Windows
On 04/29/2023 3:37 PM, Stan Brown wrote:
>
>
> Stan Brown
> Tehachapi, CA, USA
> https://BrownMath.com
>
> On 2023-04-29 08:28, Mike wrote:
>> On 04/29/2023 10:51 AM, Mike wrote:
>>> On 04/28/2023 9:32 PM, Mike wrote:
>>>> Briefly, I have a case where glob("*.ext") returns more files than I
>>>> expect.
>>>>
>>>> To give an example, in a directory of your choice create two files
>>>> named "test.any" and "zest.anyother". The important detail is that
>>>> the second filename's extension be prefixed by the first filename's
>>>> extension.
>>>>
>>>> Then launch Vim in that directory and run the command
>>>> :echo glob("*.any")
>>>> Both files are returned, not just "test.any".
>>>>
>>>> I see this on Windows running vim 9.0.1240 with normal features built
>>>> with Visual C. On the other hand, Vim on my linux box returns only
>>>> "test.any", as I would expect, so I don't think this a feature. :)
>>>
>>> I've since rebuilt Vim to include patches up to 1494 and still see the
>>> same results on my Windows 10 system. I thought that patches 1400 and
>>> 1458 might help but they did not.
>>
>> More potatoes for the stew.
>>
>> Create 5 files: test.a, test.ab, test.abc, test.abcd and test.abcde.
>> Then, using gvim -u NONE -U NONE --noplugin or gvim --clean:
>> glob("*.a") returns test.a
>> glob("*.ab") returns test.ab
>> glob("*.abc") returns test.abc, test.abcd and test.abcde
>> glob("*.abcd") returns test.abcd
>>
>> So the problem occurs when the glob pattern has a 3-character extension.
>
> Mike, I saw someone answered this, but maybe their answer didn't reach you?
If you're referring to Brams' answer, it did. However, his link
primarily referenced FAT-based systems, not NTFS, and so the light-bulb
remained off.
>
> Short version: Windows is doing what it's supposed to, and so is Vim.
>
> The original MS-DOS and MS-Windows file system, in the 1980s, allowed up
> to 8 characters, and then optionally a dot (period, full stop) plus up
> to 3 characters. Even if the file was created with lower-case characters
> in its name, Windows would change those characters to upper case. We can
> call these "8.3 filenames" for short.
>
> Around the turn of the millennium (in Windows XP, if I recall
> correctly), Windows added so-called long filenames (LFNs), which could
> be longer than 8.3 and could contain lower-case.
>
> Rather than start with a completely new file system (which would then
> make floppy disks and other interchangeable media unreadable on the
> previous generation of computers, Microsoft gave any filename that
> exceeded 8.3 _two_ entries in the directory: one for the actual
> filename, and one for an 8.3 "short filename" (SFN). If the new file's
> name fit within 8.3, then it would get only that one entry, an SFN, in
> the directory. Thus _every_ file had an SFN, but not every file had an
> LFN. The graphical interface (called File Explorer, Windows Explorer, or
> Explorer) would show an LFN if one existed, otherwise the SFN.
>
> Some time after that, I'm not sure when but certainly by the release of
> Windows 10, it became possible to disable SFNs for any particular disk
> partition. And sometime after that, "LFNs only" became the default. But
> your disk is obviously set to create SFNs from longer filenames.
Thank you, now I understand.
Motivated by your answer, I've looked-up the NTFS article on wikipedia-
https://en.wikipedia.org/wiki/NTFS
and it says that short filenames are implemented as "hard links". I,
unthinkingly, did not realize this.
>
> Your test.a, test.ab, and test.abc all fit in the 8.3 paradigm, and
> therefore they have only SFNs. Your test.abcd exceeds 8.3, so when you
> created it Windows set up an SFN for it. How is the SFN formed? Windows
> ignores any characters beyond the 6.3 limits (6.3, not 8.3), and for the
> 7th and 8th characters before the dot it adds ~1. Therefore your
> test.abcd has two names, test.abcd and test~1.abc (probably ~1, but it
> might be ~ and some other number). test.abcde is probably test~2.abc.
> When you glob *.abc, the SFN name test~1.abc is caught in that net. But
> since Windows prefers to show an LFN when one exists, you see them as
> test.abcd and test.abcde.
>
> None of the SFN/LFN business exists on Linux, and since glob() is a
> Linux thing in origin it doesn't seem unreasonable to me that it doesn't
> handle this.
>
> If you really need to have more than three characters after the dot in
> filenames, then the simplest thing would be for you to create a wrapper
> function that calls glob and then in its return filters out anything
> that doesn't match the input expression.
>
Actually, I discovered this not because of glob() but because ":packadd"
was sourcing two files- one named pack.vim and the other named
pack.vim9, and both defined global-scope functions with the same name.
When I looked at the vim source code it appeared that it relied on glob
and so I chose to post the issue using glob as it seemed more fundamental.
Again, thanks for taking the time to provide a detailed answer.
-mike
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/u2kdv1%24l82%241%40ciao.gmane.io.
>
>
> Stan Brown
> Tehachapi, CA, USA
> https://BrownMath.com
>
> On 2023-04-29 08:28, Mike wrote:
>> On 04/29/2023 10:51 AM, Mike wrote:
>>> On 04/28/2023 9:32 PM, Mike wrote:
>>>> Briefly, I have a case where glob("*.ext") returns more files than I
>>>> expect.
>>>>
>>>> To give an example, in a directory of your choice create two files
>>>> named "test.any" and "zest.anyother". The important detail is that
>>>> the second filename's extension be prefixed by the first filename's
>>>> extension.
>>>>
>>>> Then launch Vim in that directory and run the command
>>>> :echo glob("*.any")
>>>> Both files are returned, not just "test.any".
>>>>
>>>> I see this on Windows running vim 9.0.1240 with normal features built
>>>> with Visual C. On the other hand, Vim on my linux box returns only
>>>> "test.any", as I would expect, so I don't think this a feature. :)
>>>
>>> I've since rebuilt Vim to include patches up to 1494 and still see the
>>> same results on my Windows 10 system. I thought that patches 1400 and
>>> 1458 might help but they did not.
>>
>> More potatoes for the stew.
>>
>> Create 5 files: test.a, test.ab, test.abc, test.abcd and test.abcde.
>> Then, using gvim -u NONE -U NONE --noplugin or gvim --clean:
>> glob("*.a") returns test.a
>> glob("*.ab") returns test.ab
>> glob("*.abc") returns test.abc, test.abcd and test.abcde
>> glob("*.abcd") returns test.abcd
>>
>> So the problem occurs when the glob pattern has a 3-character extension.
>
> Mike, I saw someone answered this, but maybe their answer didn't reach you?
If you're referring to Brams' answer, it did. However, his link
primarily referenced FAT-based systems, not NTFS, and so the light-bulb
remained off.
>
> Short version: Windows is doing what it's supposed to, and so is Vim.
>
> The original MS-DOS and MS-Windows file system, in the 1980s, allowed up
> to 8 characters, and then optionally a dot (period, full stop) plus up
> to 3 characters. Even if the file was created with lower-case characters
> in its name, Windows would change those characters to upper case. We can
> call these "8.3 filenames" for short.
>
> Around the turn of the millennium (in Windows XP, if I recall
> correctly), Windows added so-called long filenames (LFNs), which could
> be longer than 8.3 and could contain lower-case.
>
> Rather than start with a completely new file system (which would then
> make floppy disks and other interchangeable media unreadable on the
> previous generation of computers, Microsoft gave any filename that
> exceeded 8.3 _two_ entries in the directory: one for the actual
> filename, and one for an 8.3 "short filename" (SFN). If the new file's
> name fit within 8.3, then it would get only that one entry, an SFN, in
> the directory. Thus _every_ file had an SFN, but not every file had an
> LFN. The graphical interface (called File Explorer, Windows Explorer, or
> Explorer) would show an LFN if one existed, otherwise the SFN.
>
> Some time after that, I'm not sure when but certainly by the release of
> Windows 10, it became possible to disable SFNs for any particular disk
> partition. And sometime after that, "LFNs only" became the default. But
> your disk is obviously set to create SFNs from longer filenames.
Thank you, now I understand.
Motivated by your answer, I've looked-up the NTFS article on wikipedia-
https://en.wikipedia.org/wiki/NTFS
and it says that short filenames are implemented as "hard links". I,
unthinkingly, did not realize this.
>
> Your test.a, test.ab, and test.abc all fit in the 8.3 paradigm, and
> therefore they have only SFNs. Your test.abcd exceeds 8.3, so when you
> created it Windows set up an SFN for it. How is the SFN formed? Windows
> ignores any characters beyond the 6.3 limits (6.3, not 8.3), and for the
> 7th and 8th characters before the dot it adds ~1. Therefore your
> test.abcd has two names, test.abcd and test~1.abc (probably ~1, but it
> might be ~ and some other number). test.abcde is probably test~2.abc.
> When you glob *.abc, the SFN name test~1.abc is caught in that net. But
> since Windows prefers to show an LFN when one exists, you see them as
> test.abcd and test.abcde.
>
> None of the SFN/LFN business exists on Linux, and since glob() is a
> Linux thing in origin it doesn't seem unreasonable to me that it doesn't
> handle this.
>
> If you really need to have more than three characters after the dot in
> filenames, then the simplest thing would be for you to create a wrapper
> function that calls glob and then in its return filters out anything
> that doesn't match the input expression.
>
Actually, I discovered this not because of glob() but because ":packadd"
was sourcing two files- one named pack.vim and the other named
pack.vim9, and both defined global-scope functions with the same name.
When I looked at the vim source code it appeared that it relied on glob
and so I chose to post the issue using glob as it seemed more fundamental.
Again, thanks for taking the time to provide a detailed answer.
-mike
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/u2kdv1%24l82%241%40ciao.gmane.io.
Bug? E216: No such group or event: filetypedetect BufReadPost msg in 14_XxdBack:
Vim Users,
Posting this here based on the request at https://github.com/vim/vim/blob/master/CONTRIBUTING.md :
-- Posting this here based on the request at https://github.com/vim/vim/blob/master/CONTRIBUTING.md :
"If you are not 100% sure that your problem is a Vim issue, please first discuss this on the Vim user maillist."
Running:
VIM - Vi IMproved 9.0 (2022 Jun 28, compiled Jun 28 2022 13:09:53)
MS-Windows 32-bit GUI version with OLE support
Running:
VIM - Vi IMproved 9.0 (2022 Jun 28, compiled Jun 28 2022 13:09:53)
MS-Windows 32-bit GUI version with OLE support
(the one downloadable from https://www.vim.org/download.php)
... I noticed a message when clicking Convert Back after Convert to HEX:
Error detected while processing functions <SNR>14_XxdBack:
line 9:
E216: No such group or event: filetypedetect BufReadPost
...this message cleared when I pressed Enter.
I found this message went away with this patch:
--- menu.vim 2023-04-29 16:47:05.708417500 -0600
+++ menu.vim.bak 2022-06-28 07:08:36.000000000 -0600
@@ -599,10 +599,8 @@
s:XxdFind()
exe ':%!' .. g:xxdprogram .. ' -r'
endif
- if exists('did_load_filetypes')
- set ft=
- doautocmd filetypedetect BufReadPost
- endif
+ set ft=
+ doautocmd filetypedetect BufReadPost
&mod = mod
enddef
Is there a better solution? Should I file this as a bug?
--
Blog | LinkedIn | Twitter | Facebook
... I noticed a message when clicking Convert Back after Convert to HEX:
Error detected while processing functions <SNR>14_XxdBack:
line 9:
E216: No such group or event: filetypedetect BufReadPost
...this message cleared when I pressed Enter.
I found this message went away with this patch:
--- menu.vim 2023-04-29 16:47:05.708417500 -0600
+++ menu.vim.bak 2022-06-28 07:08:36.000000000 -0600
@@ -599,10 +599,8 @@
s:XxdFind()
exe ':%!' .. g:xxdprogram .. ' -r'
endif
- if exists('did_load_filetypes')
- set ft=
- doautocmd filetypedetect BufReadPost
- endif
+ set ft=
+ doautocmd filetypedetect BufReadPost
&mod = mod
enddef
Is there a better solution? Should I file this as a bug?
--
Blog | LinkedIn | Twitter | Facebook
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/CAPXzgB2qrdX%3Dwy3_yfpDUj3-oRBy5ThTKNF0EQEoGpsgse7XXw%40mail.gmail.com.
Re: surprising glob() result on Windows
Stan Brown
Tehachapi, CA, USA
https://BrownMath.com
On 2023-04-29 08:28, Mike wrote:
> On 04/29/2023 10:51 AM, Mike wrote:
>> On 04/28/2023 9:32 PM, Mike wrote:
>>> Briefly, I have a case where glob("*.ext") returns more files than I
>>> expect.
>>>
>>> To give an example, in a directory of your choice create two files
>>> named "test.any" and "zest.anyother". The important detail is that
>>> the second filename's extension be prefixed by the first filename's
>>> extension.
>>>
>>> Then launch Vim in that directory and run the command
>>> :echo glob("*.any")
>>> Both files are returned, not just "test.any".
>>>
>>> I see this on Windows running vim 9.0.1240 with normal features built
>>> with Visual C. On the other hand, Vim on my linux box returns only
>>> "test.any", as I would expect, so I don't think this a feature. :)
>>
>> I've since rebuilt Vim to include patches up to 1494 and still see the
>> same results on my Windows 10 system. I thought that patches 1400 and
>> 1458 might help but they did not.
>
> More potatoes for the stew.
>
> Create 5 files: test.a, test.ab, test.abc, test.abcd and test.abcde.
> Then, using gvim -u NONE -U NONE --noplugin or gvim --clean:
> glob("*.a") returns test.a
> glob("*.ab") returns test.ab
> glob("*.abc") returns test.abc, test.abcd and test.abcde
> glob("*.abcd") returns test.abcd
>
> So the problem occurs when the glob pattern has a 3-character extension.
Mike, I saw someone answered this, but maybe their answer didn't reach you?
Short version: Windows is doing what it's supposed to, and so is Vim.
The original MS-DOS and MS-Windows file system, in the 1980s, allowed up
to 8 characters, and then optionally a dot (period, full stop) plus up
to 3 characters. Even if the file was created with lower-case characters
in its name, Windows would change those characters to upper case. We can
call these "8.3 filenames" for short.
Around the turn of the millennium (in Windows XP, if I recall
correctly), Windows added so-called long filenames (LFNs), which could
be longer than 8.3 and could contain lower-case.
Rather than start with a completely new file system (which would then
make floppy disks and other interchangeable media unreadable on the
previous generation of computers, Microsoft gave any filename that
exceeded 8.3 _two_ entries in the directory: one for the actual
filename, and one for an 8.3 "short filename" (SFN). If the new file's
name fit within 8.3, then it would get only that one entry, an SFN, in
the directory. Thus _every_ file had an SFN, but not every file had an
LFN. The graphical interface (called File Explorer, Windows Explorer, or
Explorer) would show an LFN if one existed, otherwise the SFN.
Some time after that, I'm not sure when but certainly by the release of
Windows 10, it became possible to disable SFNs for any particular disk
partition. And sometime after that, "LFNs only" became the default. But
your disk is obviously set to create SFNs from longer filenames.
Your test.a, test.ab, and test.abc all fit in the 8.3 paradigm, and
therefore they have only SFNs. Your test.abcd exceeds 8.3, so when you
created it Windows set up an SFN for it. How is the SFN formed? Windows
ignores any characters beyond the 6.3 limits (6.3, not 8.3), and for the
7th and 8th characters before the dot it adds ~1. Therefore your
test.abcd has two names, test.abcd and test~1.abc (probably ~1, but it
might be ~ and some other number). test.abcde is probably test~2.abc.
When you glob *.abc, the SFN name test~1.abc is caught in that net. But
since Windows prefers to show an LFN when one exists, you see them as
test.abcd and test.abcde.
None of the SFN/LFN business exists on Linux, and since glob() is a
Linux thing in origin it doesn't seem unreasonable to me that it doesn't
handle this.
If you really need to have more than three characters after the dot in
filenames, then the simplest thing would be for you to create a wrapper
function that calls glob and then in its return filters out anything
that doesn't match the input expression.
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/2b0898b6-90f3-0fe8-077e-8761a263c0ca%40fastmail.fm.
Tehachapi, CA, USA
https://BrownMath.com
On 2023-04-29 08:28, Mike wrote:
> On 04/29/2023 10:51 AM, Mike wrote:
>> On 04/28/2023 9:32 PM, Mike wrote:
>>> Briefly, I have a case where glob("*.ext") returns more files than I
>>> expect.
>>>
>>> To give an example, in a directory of your choice create two files
>>> named "test.any" and "zest.anyother". The important detail is that
>>> the second filename's extension be prefixed by the first filename's
>>> extension.
>>>
>>> Then launch Vim in that directory and run the command
>>> :echo glob("*.any")
>>> Both files are returned, not just "test.any".
>>>
>>> I see this on Windows running vim 9.0.1240 with normal features built
>>> with Visual C. On the other hand, Vim on my linux box returns only
>>> "test.any", as I would expect, so I don't think this a feature. :)
>>
>> I've since rebuilt Vim to include patches up to 1494 and still see the
>> same results on my Windows 10 system. I thought that patches 1400 and
>> 1458 might help but they did not.
>
> More potatoes for the stew.
>
> Create 5 files: test.a, test.ab, test.abc, test.abcd and test.abcde.
> Then, using gvim -u NONE -U NONE --noplugin or gvim --clean:
> glob("*.a") returns test.a
> glob("*.ab") returns test.ab
> glob("*.abc") returns test.abc, test.abcd and test.abcde
> glob("*.abcd") returns test.abcd
>
> So the problem occurs when the glob pattern has a 3-character extension.
Mike, I saw someone answered this, but maybe their answer didn't reach you?
Short version: Windows is doing what it's supposed to, and so is Vim.
The original MS-DOS and MS-Windows file system, in the 1980s, allowed up
to 8 characters, and then optionally a dot (period, full stop) plus up
to 3 characters. Even if the file was created with lower-case characters
in its name, Windows would change those characters to upper case. We can
call these "8.3 filenames" for short.
Around the turn of the millennium (in Windows XP, if I recall
correctly), Windows added so-called long filenames (LFNs), which could
be longer than 8.3 and could contain lower-case.
Rather than start with a completely new file system (which would then
make floppy disks and other interchangeable media unreadable on the
previous generation of computers, Microsoft gave any filename that
exceeded 8.3 _two_ entries in the directory: one for the actual
filename, and one for an 8.3 "short filename" (SFN). If the new file's
name fit within 8.3, then it would get only that one entry, an SFN, in
the directory. Thus _every_ file had an SFN, but not every file had an
LFN. The graphical interface (called File Explorer, Windows Explorer, or
Explorer) would show an LFN if one existed, otherwise the SFN.
Some time after that, I'm not sure when but certainly by the release of
Windows 10, it became possible to disable SFNs for any particular disk
partition. And sometime after that, "LFNs only" became the default. But
your disk is obviously set to create SFNs from longer filenames.
Your test.a, test.ab, and test.abc all fit in the 8.3 paradigm, and
therefore they have only SFNs. Your test.abcd exceeds 8.3, so when you
created it Windows set up an SFN for it. How is the SFN formed? Windows
ignores any characters beyond the 6.3 limits (6.3, not 8.3), and for the
7th and 8th characters before the dot it adds ~1. Therefore your
test.abcd has two names, test.abcd and test~1.abc (probably ~1, but it
might be ~ and some other number). test.abcde is probably test~2.abc.
When you glob *.abc, the SFN name test~1.abc is caught in that net. But
since Windows prefers to show an LFN when one exists, you see them as
test.abcd and test.abcde.
None of the SFN/LFN business exists on Linux, and since glob() is a
Linux thing in origin it doesn't seem unreasonable to me that it doesn't
handle this.
If you really need to have more than three characters after the dot in
filenames, then the simplest thing would be for you to create a wrapper
function that calls glob and then in its return filters out anything
that doesn't match the input expression.
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/2b0898b6-90f3-0fe8-077e-8761a263c0ca%40fastmail.fm.
Re: surprising glob() result on Windows
On 04/29/2023 10:51 AM, Mike wrote:
> On 04/28/2023 9:32 PM, Mike wrote:
>> Briefly, I have a case where glob("*.ext") returns more files than I
>> expect.
>>
>> To give an example, in a directory of your choice create two files
>> named "test.any" and "zest.anyother". The important detail is that
>> the second filename's extension be prefixed by the first filename's
>> extension.
>>
>> Then launch Vim in that directory and run the command
>> :echo glob("*.any")
>> Both files are returned, not just "test.any".
>>
>> I see this on Windows running vim 9.0.1240 with normal features built
>> with Visual C. On the other hand, Vim on my linux box returns only
>> "test.any", as I would expect, so I don't think this a feature. :)
>
> I've since rebuilt Vim to include patches up to 1494 and still see the
> same results on my Windows 10 system. I thought that patches 1400 and
> 1458 might help but they did not.
More potatoes for the stew.
Create 5 files: test.a, test.ab, test.abc, test.abcd and test.abcde.
Then, using gvim -u NONE -U NONE --noplugin or gvim --clean:
glob("*.a") returns test.a
glob("*.ab") returns test.ab
glob("*.abc") returns test.abc, test.abcd and test.abcde
glob("*.abcd") returns test.abcd
So the problem occurs when the glob pattern has a 3-character extension.
>
>>
>> Any comments?
>>
>> -mike
>>
>>
>
>
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/u2jd28%2417r6%241%40ciao.gmane.io.
> On 04/28/2023 9:32 PM, Mike wrote:
>> Briefly, I have a case where glob("*.ext") returns more files than I
>> expect.
>>
>> To give an example, in a directory of your choice create two files
>> named "test.any" and "zest.anyother". The important detail is that
>> the second filename's extension be prefixed by the first filename's
>> extension.
>>
>> Then launch Vim in that directory and run the command
>> :echo glob("*.any")
>> Both files are returned, not just "test.any".
>>
>> I see this on Windows running vim 9.0.1240 with normal features built
>> with Visual C. On the other hand, Vim on my linux box returns only
>> "test.any", as I would expect, so I don't think this a feature. :)
>
> I've since rebuilt Vim to include patches up to 1494 and still see the
> same results on my Windows 10 system. I thought that patches 1400 and
> 1458 might help but they did not.
More potatoes for the stew.
Create 5 files: test.a, test.ab, test.abc, test.abcd and test.abcde.
Then, using gvim -u NONE -U NONE --noplugin or gvim --clean:
glob("*.a") returns test.a
glob("*.ab") returns test.ab
glob("*.abc") returns test.abc, test.abcd and test.abcde
glob("*.abcd") returns test.abcd
So the problem occurs when the glob pattern has a 3-character extension.
>
>>
>> Any comments?
>>
>> -mike
>>
>>
>
>
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/u2jd28%2417r6%241%40ciao.gmane.io.
Re: surprising glob() result on Windows
On 04/28/2023 9:32 PM, Mike wrote:
> Briefly, I have a case where glob("*.ext") returns more files than I
> expect.
>
> To give an example, in a directory of your choice create two files named
> "test.any" and "zest.anyother". The important detail is that the second
> filename's extension be prefixed by the first filename's extension.
>
> Then launch Vim in that directory and run the command
> :echo glob("*.any")
> Both files are returned, not just "test.any".
>
> I see this on Windows running vim 9.0.1240 with normal features built
> with Visual C. On the other hand, Vim on my linux box returns only
> "test.any", as I would expect, so I don't think this a feature. :)
I've since rebuilt Vim to include patches up to 1494 and still see the
same results on my Windows 10 system. I thought that patches 1400 and
1458 might help but they did not.
>
> Any comments?
>
> -mike
>
>
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/u2jata%24t38%241%40ciao.gmane.io.
> Briefly, I have a case where glob("*.ext") returns more files than I
> expect.
>
> To give an example, in a directory of your choice create two files named
> "test.any" and "zest.anyother". The important detail is that the second
> filename's extension be prefixed by the first filename's extension.
>
> Then launch Vim in that directory and run the command
> :echo glob("*.any")
> Both files are returned, not just "test.any".
>
> I see this on Windows running vim 9.0.1240 with normal features built
> with Visual C. On the other hand, Vim on my linux box returns only
> "test.any", as I would expect, so I don't think this a feature. :)
I've since rebuilt Vim to include patches up to 1494 and still see the
same results on my Windows 10 system. I thought that patches 1400 and
1458 might help but they did not.
>
> Any comments?
>
> -mike
>
>
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/u2jata%24t38%241%40ciao.gmane.io.
Re: surprising glob() result on Windows
On 04/29/2023 9:26 AM, Bram Moolenaar wrote:
>
>> Briefly, I have a case where glob("*.ext") returns more files than I
>> expect.
>>
>> To give an example, in a directory of your choice create two files named
>> "test.any" and "zest.anyother". The important detail is that the second
>> filename's extension be prefixed by the first filename's extension.
>>
>> Then launch Vim in that directory and run the command
>> :echo glob("*.any")
>> Both files are returned, not just "test.any".
>>
>> I see this on Windows running vim 9.0.1240 with normal features built
>> with Visual C. On the other hand, Vim on my linux box returns only
>> "test.any", as I would expect, so I don't think this a feature. :)
>>
>> Any comments?
>
> What file system is being used?
Windows 10 with NTFS.
Some older filesystems use a trick to
> make long file names possible. The file then appears twice in the
> directory, once with the short name and once with the long name. Vim
> may find a match with the short name, includes it in the list of
> matches and then expands it to the long name.
> See https://en.wikipedia.org/wiki/Long_filename
>
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/u2j8je%2419c%241%40ciao.gmane.io.
>
>> Briefly, I have a case where glob("*.ext") returns more files than I
>> expect.
>>
>> To give an example, in a directory of your choice create two files named
>> "test.any" and "zest.anyother". The important detail is that the second
>> filename's extension be prefixed by the first filename's extension.
>>
>> Then launch Vim in that directory and run the command
>> :echo glob("*.any")
>> Both files are returned, not just "test.any".
>>
>> I see this on Windows running vim 9.0.1240 with normal features built
>> with Visual C. On the other hand, Vim on my linux box returns only
>> "test.any", as I would expect, so I don't think this a feature. :)
>>
>> Any comments?
>
> What file system is being used?
Windows 10 with NTFS.
Some older filesystems use a trick to
> make long file names possible. The file then appears twice in the
> directory, once with the short name and once with the long name. Vim
> may find a match with the short name, includes it in the list of
> matches and then expands it to the long name.
> See https://en.wikipedia.org/wiki/Long_filename
>
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/u2j8je%2419c%241%40ciao.gmane.io.
Re: surprising glob() result on Windows
> Briefly, I have a case where glob("*.ext") returns more files than I
> expect.
>
> To give an example, in a directory of your choice create two files named
> "test.any" and "zest.anyother". The important detail is that the second
> filename's extension be prefixed by the first filename's extension.
>
> Then launch Vim in that directory and run the command
> :echo glob("*.any")
> Both files are returned, not just "test.any".
>
> I see this on Windows running vim 9.0.1240 with normal features built
> with Visual C. On the other hand, Vim on my linux box returns only
> "test.any", as I would expect, so I don't think this a feature. :)
>
> Any comments?
What file system is being used? Some older filesystems use a trick to
make long file names possible. The file then appears twice in the
directory, once with the short name and once with the long name. Vim
may find a match with the short name, includes it in the list of
matches and then expands it to the long name.
See https://en.wikipedia.org/wiki/Long_filename
--
ARTHUR: Now stand aside worthy adversary.
BLACK KNIGHT: (Glancing at his shoulder) 'Tis but a scratch.
ARTHUR: A scratch? Your arm's off.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// \\\
\\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/20230429132628.E64621C09E0%40moolenaar.net.
> expect.
>
> To give an example, in a directory of your choice create two files named
> "test.any" and "zest.anyother". The important detail is that the second
> filename's extension be prefixed by the first filename's extension.
>
> Then launch Vim in that directory and run the command
> :echo glob("*.any")
> Both files are returned, not just "test.any".
>
> I see this on Windows running vim 9.0.1240 with normal features built
> with Visual C. On the other hand, Vim on my linux box returns only
> "test.any", as I would expect, so I don't think this a feature. :)
>
> Any comments?
What file system is being used? Some older filesystems use a trick to
make long file names possible. The file then appears twice in the
directory, once with the short name and once with the long name. Vim
may find a match with the short name, includes it in the list of
matches and then expands it to the long name.
See https://en.wikipedia.org/wiki/Long_filename
--
ARTHUR: Now stand aside worthy adversary.
BLACK KNIGHT: (Glancing at his shoulder) 'Tis but a scratch.
ARTHUR: A scratch? Your arm's off.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// \\\
\\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/20230429132628.E64621C09E0%40moolenaar.net.
Friday, April 28, 2023
surprising glob() result on Windows
Briefly, I have a case where glob("*.ext") returns more files than I
expect.
To give an example, in a directory of your choice create two files named
"test.any" and "zest.anyother". The important detail is that the second
filename's extension be prefixed by the first filename's extension.
Then launch Vim in that directory and run the command
:echo glob("*.any")
Both files are returned, not just "test.any".
I see this on Windows running vim 9.0.1240 with normal features built
with Visual C. On the other hand, Vim on my linux box returns only
"test.any", as I would expect, so I don't think this a feature. :)
Any comments?
-mike
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/u2hs3o%24p9r%241%40ciao.gmane.io.
expect.
To give an example, in a directory of your choice create two files named
"test.any" and "zest.anyother". The important detail is that the second
filename's extension be prefixed by the first filename's extension.
Then launch Vim in that directory and run the command
:echo glob("*.any")
Both files are returned, not just "test.any".
I see this on Windows running vim 9.0.1240 with normal features built
with Visual C. On the other hand, Vim on my linux box returns only
"test.any", as I would expect, so I don't think this a feature. :)
Any comments?
-mike
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/u2hs3o%24p9r%241%40ciao.gmane.io.
Monday, April 24, 2023
Re: Search multiple windows
On 2023-04-24 12:38, Ben Mehmet wrote:
> My question, however, is is there a way/plugin/mapping that I
> could enable to have vim highlight and move to next occurrence
> of my search pattern in all the rest of windows highlighted
I usually do this semi-manually with something like
:windo /pattern
to jump to the next match in each window or
:windo g/pattern/#
to list all the matching lines in all of the windows
Because 'hls' is a global option, if you have it enabled, it should
highlight things in the rest of the windows too, not just the current
one.
-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 on the web visit https://groups.google.com/d/msgid/vim_use/ZEbgWqkfrz2hjjJw%40thechases.com.
> My question, however, is is there a way/plugin/mapping that I
> could enable to have vim highlight and move to next occurrence
> of my search pattern in all the rest of windows highlighted
I usually do this semi-manually with something like
:windo /pattern
to jump to the next match in each window or
:windo g/pattern/#
to list all the matching lines in all of the windows
Because 'hls' is a global option, if you have it enabled, it should
highlight things in the rest of the windows too, not just the current
one.
-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 on the web visit https://groups.google.com/d/msgid/vim_use/ZEbgWqkfrz2hjjJw%40thechases.com.
Re: Search multiple windows
https://www.vim.org/scripts/script.php?script_id=5875
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/90e3a8ea-5da6-4e06-9df5-afdd128b441cn%40googlegroups.com.
was just announced (the update, anyway). Not sure if it auto advances to the next tab though.
On Monday, April 24, 2023 at 3:38:10 PM UTC-4 Ben Mehmet wrote:
Hi All,I have this searching within multiple windows open.Basically, lets say I have a VIM session with 2 or more windows open and I end searching for some text in one of the windows. Search will end up taking me the next occurrence of the search pattern and if I have highlighting set it will also highlight it for me. This by itself is very helpful and nice.My question, however, is is there a way/plugin/mapping that I could enable to have vim highlight and move to next occurrence of my search pattern in all the rest of windows highlighted as well.Thanks for any help with this question.-Ben
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/90e3a8ea-5da6-4e06-9df5-afdd128b441cn%40googlegroups.com.
Search multiple windows
Hi All,
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/71ef7db6-4a36-405d-bacf-1aa66ba75492n%40googlegroups.com.
I have this searching within multiple windows open.
Basically, lets say I have a VIM session with 2 or more windows open and I end searching for some text in one of the windows. Search will end up taking me the next occurrence of the search pattern and if I have highlighting set it will also highlight it for me. This by itself is very helpful and nice.
My question, however, is is there a way/plugin/mapping that I could enable to have vim highlight and move to next occurrence of my search pattern in all the rest of windows highlighted as well.
Thanks for any help with this question.
-Ben
-- --
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 on the web visit https://groups.google.com/d/msgid/vim_use/71ef7db6-4a36-405d-bacf-1aa66ba75492n%40googlegroups.com.
Re: What are some alternatives of vim-surround
I have gathered a bunch of native alternatives to some of Surround's features in this gist: https://gist.github.com/romainl/ca742f241457b8609836202fe05ee5c0 for the fun of it.
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/d906ce32-608d-4f17-8961-15ee4005474cn%40googlegroups.com.
On Wednesday, April 19, 2023 at 3:29:08 PM UTC+2 Christian Brabandt wrote:
On Mi, 19 Apr 2023, Tim Chase wrote:
> Strange in its inconsistency, that one would remember that part of
> the source-text was from a register while the other doesn't.
>
> Is there documentation on why this difference? I poked around at
>
> :help "-
> :help i_CTRL-R (and following on its variants)
> :help .
> :help simple-change
>
> but didn't see anything noting this small-delete peculiarity.
Well, it was a small annoyance of me in particular :)
https://github.com/vim/vim/pull/7527
You are right, it's not documented. Do you have an idea on how to
improve the documentation?
Best,
Christian
--
Die Jugend ist etwas Wundervolles. Es ist eine wahre Schande, daß man
sie an Kinder vergeudet.
-- George Bernard Shaw
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/d906ce32-608d-4f17-8961-15ee4005474cn%40googlegroups.com.
Re: What to use for....
On 2023-04-24 12:07, 'Sebastian G??decke' via vim_use wrote:
> Actually it's 1779 counts long and for this, i don't see the missing
> "=".Ā
> So how could i improve vim to "show" me that in my config-file is
> something missing.
I've done one-off things like
:match Error /^[^=]\=$/
which will highlight any lines that don't have an "=" in them.
You might wire that up with a file-type detection to do that more
automatically.
If there are lines that can validly lack an "=", then you'd have
to add some context to identify lines that should have "=" but
don't.
-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 on the web visit https://groups.google.com/d/msgid/vim_use/ZEZt77JNiPJfzLX7%40thechases.com.
> Actually it's 1779 counts long and for this, i don't see the missing
> "=".Ā
> So how could i improve vim to "show" me that in my config-file is
> something missing.
I've done one-off things like
:match Error /^[^=]\=$/
which will highlight any lines that don't have an "=" in them.
You might wire that up with a file-type detection to do that more
automatically.
If there are lines that can validly lack an "=", then you'd have
to add some context to identify lines that should have "=" but
don't.
-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 on the web visit https://groups.google.com/d/msgid/vim_use/ZEZt77JNiPJfzLX7%40thechases.com.
Re: What to use for....
On Mo, 24 Apr 2023, 'Sebastian Gödecke' via vim_use wrote:
> Hi there,
> i'm running into issue if i don't get solution for getting older....
> I'm working with config files for an application that is using DN's
> In this config-file the ldap-dn has to be written in one (long) line.
> Actually it's 1779 counts long and for this, i don't see the missing "=".
> So how could i improve vim to "show" me that in my config-file is something
> missing.
> Could this be done with a template, syntax-checking or what else?
> Any hints for this would be great :D
Not sure I understand the problem. I think using numbered lines with
wrapping (possibly with breakindent/showbreak setting enabled) enabled
should allow you to show everything. So something like this:
:set wrap number breakindent showbreak=>>
For very long lines, smoothscroll feature could also be helpful (:set
smoothscroll) and then scroll using Ctrl-E/CTRL-Y
Best,
Christian
--
Humor ist nicht erlernbar. Neben Geist und Witz setzt er vor allem ein
großes Maß an Herzensgüte voraus, an Geduld, Nachsicht und
Menschenliebe.
-- Curt Goetz
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/ZEZmDb9YGtrtmFIQ%40256bit.org.
> Hi there,
> i'm running into issue if i don't get solution for getting older....
> I'm working with config files for an application that is using DN's
> In this config-file the ldap-dn has to be written in one (long) line.
> Actually it's 1779 counts long and for this, i don't see the missing "=".
> So how could i improve vim to "show" me that in my config-file is something
> missing.
> Could this be done with a template, syntax-checking or what else?
> Any hints for this would be great :D
Not sure I understand the problem. I think using numbered lines with
wrapping (possibly with breakindent/showbreak setting enabled) enabled
should allow you to show everything. So something like this:
:set wrap number breakindent showbreak=>>
For very long lines, smoothscroll feature could also be helpful (:set
smoothscroll) and then scroll using Ctrl-E/CTRL-Y
Best,
Christian
--
Humor ist nicht erlernbar. Neben Geist und Witz setzt er vor allem ein
großes Maß an Herzensgüte voraus, an Geduld, Nachsicht und
Menschenliebe.
-- Curt Goetz
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/ZEZmDb9YGtrtmFIQ%40256bit.org.
Re: What to use for....
'Sebastian Gödecke' via vim_use (12023-04-24):
> i'm running into issue if i don't get solution for getting older....
> I'm working with config files for an application that is using DN's
> In this config-file the ldap-dn has to be written in one (long) line.
> Actually it's 1779 counts long and for this, i don't see the missing "=".
> So how could i improve vim to "show" me that in my config-file is something
> missing.
> Could this be done with a template, syntax-checking or what else?
Write your config file how you want to write it, split the lines to make
them readable. And then use a pre-processor, possibly along with a
makefile, to turn it to the syntax you need.
Regards,
--
Nicolas George
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/ZEZaNgyR%2BpGIml3t%40phare.normalesup.org.
> i'm running into issue if i don't get solution for getting older....
> I'm working with config files for an application that is using DN's
> In this config-file the ldap-dn has to be written in one (long) line.
> Actually it's 1779 counts long and for this, i don't see the missing "=".
> So how could i improve vim to "show" me that in my config-file is something
> missing.
> Could this be done with a template, syntax-checking or what else?
Write your config file how you want to write it, split the lines to make
them readable. And then use a pre-processor, possibly along with a
makefile, to turn it to the syntax you need.
Regards,
--
Nicolas George
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/ZEZaNgyR%2BpGIml3t%40phare.normalesup.org.
Re: What to use for....
On Mon, Apr 24, 2023 at 12:07 PM 'Sebastian Gödecke' via vim_use
<vim_use@googlegroups.com> wrote:
>
> Hi there,
> i'm running into issue if i don't get solution for getting older....
> I'm working with config files for an application that is using DN's
> In this config-file the ldap-dn has to be written in one (long) line. Actually it's 1779 counts long and for this, i don't see the missing "=".
> So how could i improve vim to "show" me that in my config-file is something missing.
> Could this be done with a template, syntax-checking or what else?
> Any hints for this would be great :D
> Regards Sebastian
By setting 'wrap' on, you will see as much of the current line as fits
in the current window ("window" in the Vim sense, there may be one or
more windows in a single Vim). Then you can scroll the text (by means
of the down-arrow key or, in Normal mode, by Ctrl-E) to display any
part of the current file line that overflow the current line. To get
at the next equal sign (if any), but only on the current line
(including any part of it overflowing the screen), use
f=
("forward to =", see ":help f"); or to go to the end of the line,
scrolling if necessary, use the <End> key or, in Normal mode, the $
key.
Best regards,
Tony.
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/CAJkCKXu_1S_DcBHmaATnyxBXtmXkeMHEOFCA3Q2f6CEUssDh_g%40mail.gmail.com.
<vim_use@googlegroups.com> wrote:
>
> Hi there,
> i'm running into issue if i don't get solution for getting older....
> I'm working with config files for an application that is using DN's
> In this config-file the ldap-dn has to be written in one (long) line. Actually it's 1779 counts long and for this, i don't see the missing "=".
> So how could i improve vim to "show" me that in my config-file is something missing.
> Could this be done with a template, syntax-checking or what else?
> Any hints for this would be great :D
> Regards Sebastian
By setting 'wrap' on, you will see as much of the current line as fits
in the current window ("window" in the Vim sense, there may be one or
more windows in a single Vim). Then you can scroll the text (by means
of the down-arrow key or, in Normal mode, by Ctrl-E) to display any
part of the current file line that overflow the current line. To get
at the next equal sign (if any), but only on the current line
(including any part of it overflowing the screen), use
f=
("forward to =", see ":help f"); or to go to the end of the line,
scrolling if necessary, use the <End> key or, in Normal mode, the $
key.
Best regards,
Tony.
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/CAJkCKXu_1S_DcBHmaATnyxBXtmXkeMHEOFCA3Q2f6CEUssDh_g%40mail.gmail.com.
What to use for....
Hi there,
i'm running into issue if i don't get solution for getting older....
I'm working with config files for an application that is using DN's
In this config-file the ldap-dn has to be written in one (long) line. Actually it's 1779 counts long and for this, i don't see the missing "=".
So how could i improve vim to "show" me that in my config-file is something missing.
Could this be done with a template, syntax-checking or what else?
Any hints for this would be great :D
Regards Sebastian
Mit freundlichen Grüßen
Sebastian Gödecke
Sebastian Gödecke
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/CAJRNCba5OjLHSAkHvEGkbqFk_osdSVYj%2BOqV8uyQY7tpV2xo%3Dw%40mail.gmail.com.
Saturday, April 22, 2023
Re: Unexpected cterm-colors in Windows
On Fri, 21 Apr 2023 23:54:44 -0700 (PDT)
Romain Lafourcade <romainlafourcade@gmail.com> wrote:
> > Another thing: what does NR-16 and NR-8 mean? I can't find these terms
> > on the internet. Every hit I get is in the context of Vim.
>
> They are explained a few lines below the block you cited.
>
> Vim is not very good at detecting terminal features in general and it is
> pretty bad with colors so you should probably notch down your expectations
> regarding syntax highlighting.
>
> Basically, if you stop at that table you would _think_ that 1 and DarkBlue
> should be interchangeable when &t_Co == 16, while they are very different
> when testing it in your terminal emulator.
> There is a very short explanation a few paragraphs below the table:
>
> > Note that for 16 color ansi style terminals (including xterms), the
> > numbers in the NR-8 column is used. Here '*' means 'add 8' so that
> > Blue is 12, DarkGray is 8 etc.
>
> That explanation is frustrating, though, because most terminal emulators in
> use nowadays fall into that broad "color ansi style terminals (including
> xterms)" category... which is still treated ("brushed off", even) as a
> special case.
> This makes the table and most of the text below it unnecessarily confusing.
Thanks for the explanation. It's clear to me now, or close enough.
For completion's sake: I dug into this issue because I saw cterm-colors
were different in my Windows terminals (both xterm-like Windows Terminal
_and_ old Conhost terminal) than in Ubuntu suckless/Gnome terminals
(both xterm-like). I guess Vim doesn't consider Windows terminals as
xterm-like.
I recently switched from using 256-colors to 16-colors on my Ubuntu
machine (because Vim colors would then correspond to the terminal
emulator colors: I'll need to change only terminal emulator colors).
When I pulled my config changes to my Windows computer, the colors were
different.
--
Enan
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/20230422222712.00003d41%40gmail.com.
Romain Lafourcade <romainlafourcade@gmail.com> wrote:
> > Another thing: what does NR-16 and NR-8 mean? I can't find these terms
> > on the internet. Every hit I get is in the context of Vim.
>
> They are explained a few lines below the block you cited.
>
> Vim is not very good at detecting terminal features in general and it is
> pretty bad with colors so you should probably notch down your expectations
> regarding syntax highlighting.
>
> Basically, if you stop at that table you would _think_ that 1 and DarkBlue
> should be interchangeable when &t_Co == 16, while they are very different
> when testing it in your terminal emulator.
> There is a very short explanation a few paragraphs below the table:
>
> > Note that for 16 color ansi style terminals (including xterms), the
> > numbers in the NR-8 column is used. Here '*' means 'add 8' so that
> > Blue is 12, DarkGray is 8 etc.
>
> That explanation is frustrating, though, because most terminal emulators in
> use nowadays fall into that broad "color ansi style terminals (including
> xterms)" category... which is still treated ("brushed off", even) as a
> special case.
> This makes the table and most of the text below it unnecessarily confusing.
Thanks for the explanation. It's clear to me now, or close enough.
For completion's sake: I dug into this issue because I saw cterm-colors
were different in my Windows terminals (both xterm-like Windows Terminal
_and_ old Conhost terminal) than in Ubuntu suckless/Gnome terminals
(both xterm-like). I guess Vim doesn't consider Windows terminals as
xterm-like.
I recently switched from using 256-colors to 16-colors on my Ubuntu
machine (because Vim colors would then correspond to the terminal
emulator colors: I'll need to change only terminal emulator colors).
When I pulled my config changes to my Windows computer, the colors were
different.
--
Enan
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/20230422222712.00003d41%40gmail.com.
Friday, April 21, 2023
Re: Unexpected cterm-colors
> Another thing: what does NR-16 and NR-8 mean? I can't find these terms
> on the internet. Every hit I get is in the context of Vim.They are explained a few lines below the block you cited.
Vim is not very good at detecting terminal features in general and it is pretty bad with colors so you should probably notch down your expectations regarding syntax highlighting.
Basically, if you stop at that table you would _think_ that 1 and DarkBlue should be interchangeable when &t_Co == 16, while they are very different when testing it in your terminal emulator.
There is a very short explanation a few paragraphs below the table:
> Note that for 16 color ansi style terminals (including xterms), the
> numbers in the NR-8 column is used. Here '*' means 'add 8' so that
> Blue is 12, DarkGray is 8 etc.
> numbers in the NR-8 column is used. Here '*' means 'add 8' so that
> Blue is 12, DarkGray is 8 etc.
That explanation is frustrating, though, because most terminal emulators in use nowadays fall into that broad "color ansi style terminals (including xterms)" category… which is still treated ("brushed off", even) as a special case.
This makes the table and most of the text below it unnecessarily confusing.
IMO, that specific part of the documentation should document the behavior experienced by most users rather than the antiquated heuristics that are used under the hood.
On Saturday, April 22, 2023 at 7:37:47 AM UTC+2 Enan Ajmain wrote:
On Fri, 21 Apr 2023 13:25:42 +0200
Christian Brabandt <cbl...@256bit.org> wrote:
> On Fr, 21 Apr 2023, Enan Ajmain wrote:
> > [...]
> > The color codes for NR-16 don't make sense to me. Take Yellow, for example.
> > Why is it numbered 14? 16-bit terminals use 11 for bright yellow [1]. Why is
> > it different inside Vim?
>
> It's not like Vim chose a different color, it's more like this documents
> "standard" behaviour back in the time.
>
> I believe this is just documenting the CGA standard. You can find it
> e.g. here: https://en.wikipedia.org/wiki/Color_Graphics_Adapter and
> check the Full CGA 16-color palette chart.
Thanks for the info. I haven't understood why CGA 16-color palette is
different than terminal 16-color palette, but I will try and find out.
Another thing: what does NR-16 and NR-8 mean? I can't find these terms
on the internet. Every hit I get is in the context of Vim.
P.S. In the thread-top email, I mistakenly wrote "16-bit terminals"
instead of "16-color terminals." I hope that didn't cause confusion.
--
Enan
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/74085fdf-143a-4065-8c1f-ceff8cc86765n%40googlegroups.com.
Re: Unexpected cterm-colors
On Fri, 21 Apr 2023 13:25:42 +0200
Christian Brabandt <cblists@256bit.org> wrote:
> On Fr, 21 Apr 2023, Enan Ajmain wrote:
> > [...]
> > The color codes for NR-16 don't make sense to me. Take Yellow, for example.
> > Why is it numbered 14? 16-bit terminals use 11 for bright yellow [1]. Why is
> > it different inside Vim?
>
> It's not like Vim chose a different color, it's more like this documents
> "standard" behaviour back in the time.
>
> I believe this is just documenting the CGA standard. You can find it
> e.g. here: https://en.wikipedia.org/wiki/Color_Graphics_Adapter and
> check the Full CGA 16-color palette chart.
Thanks for the info. I haven't understood why CGA 16-color palette is
different than terminal 16-color palette, but I will try and find out.
Another thing: what does NR-16 and NR-8 mean? I can't find these terms
on the internet. Every hit I get is in the context of Vim.
P.S. In the thread-top email, I mistakenly wrote "16-bit terminals"
instead of "16-color terminals." I hope that didn't cause confusion.
--
Enan
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/20230422113730.00002d6e%40gmail.com.
Christian Brabandt <cblists@256bit.org> wrote:
> On Fr, 21 Apr 2023, Enan Ajmain wrote:
> > [...]
> > The color codes for NR-16 don't make sense to me. Take Yellow, for example.
> > Why is it numbered 14? 16-bit terminals use 11 for bright yellow [1]. Why is
> > it different inside Vim?
>
> It's not like Vim chose a different color, it's more like this documents
> "standard" behaviour back in the time.
>
> I believe this is just documenting the CGA standard. You can find it
> e.g. here: https://en.wikipedia.org/wiki/Color_Graphics_Adapter and
> check the Full CGA 16-color palette chart.
Thanks for the info. I haven't understood why CGA 16-color palette is
different than terminal 16-color palette, but I will try and find out.
Another thing: what does NR-16 and NR-8 mean? I can't find these terms
on the internet. Every hit I get is in the context of Vim.
P.S. In the thread-top email, I mistakenly wrote "16-bit terminals"
instead of "16-color terminals." I hope that didn't cause confusion.
--
Enan
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/20230422113730.00002d6e%40gmail.com.
Re: Unexpected cterm-colors
On Fr, 21 Apr 2023, Enan Ajmain wrote:
> I know colorschemes have been a source of issue for ignorant vimmers
> for a long time. This is not an attempt to restart old conversation. I
> am looking for pointers where to research this question.
>
> From ':h cterm-colors':
>
> NR-16 NR-8 COLOR NAME
> 0 0 Black
> 1 4 DarkBlue
> 2 2 DarkGreen
> 3 6 DarkCyan
> 4 1 DarkRed
> 5 5 DarkMagenta
> 6 3 Brown, DarkYellow
> 7 7 LightGray, LightGrey, Gray, Grey
> 8 0* DarkGray, DarkGrey
> 9 4* Blue, LightBlue
> 10 2* Green, LightGreen
> 11 6* Cyan, LightCyan
> 12 1* Red, LightRed
> 13 5* Magenta, LightMagenta
> 14 3* Yellow, LightYellow
> 15 7* White
>
> The color codes for NR-16 don't make sense to me. Take Yellow, for example.
> Why is it numbered 14? 16-bit terminals use 11 for bright yellow [1]. Why is
> it different inside Vim?
It's not like Vim chose a different color, it's more like this documents
"standard" behaviour back in the time.
I believe this is just documenting the CGA standard. You can find it
e.g. here: https://en.wikipedia.org/wiki/Color_Graphics_Adapter and
check the Full CGA 16-color palette chart.
Best,
Christian
--
Die Zahl derer, die durch zu viele Informationen nicht mehr informiert
sind, wächst.
-- Rudolf Augstein
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/ZEJytsJ8KkIaRXiH%40256bit.org.
> I know colorschemes have been a source of issue for ignorant vimmers
> for a long time. This is not an attempt to restart old conversation. I
> am looking for pointers where to research this question.
>
> From ':h cterm-colors':
>
> NR-16 NR-8 COLOR NAME
> 0 0 Black
> 1 4 DarkBlue
> 2 2 DarkGreen
> 3 6 DarkCyan
> 4 1 DarkRed
> 5 5 DarkMagenta
> 6 3 Brown, DarkYellow
> 7 7 LightGray, LightGrey, Gray, Grey
> 8 0* DarkGray, DarkGrey
> 9 4* Blue, LightBlue
> 10 2* Green, LightGreen
> 11 6* Cyan, LightCyan
> 12 1* Red, LightRed
> 13 5* Magenta, LightMagenta
> 14 3* Yellow, LightYellow
> 15 7* White
>
> The color codes for NR-16 don't make sense to me. Take Yellow, for example.
> Why is it numbered 14? 16-bit terminals use 11 for bright yellow [1]. Why is
> it different inside Vim?
It's not like Vim chose a different color, it's more like this documents
"standard" behaviour back in the time.
I believe this is just documenting the CGA standard. You can find it
e.g. here: https://en.wikipedia.org/wiki/Color_Graphics_Adapter and
check the Full CGA 16-color palette chart.
Best,
Christian
--
Die Zahl derer, die durch zu viele Informationen nicht mehr informiert
sind, wächst.
-- Rudolf Augstein
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/ZEJytsJ8KkIaRXiH%40256bit.org.
Unexpected cterm-colors
I know colorschemes have been a source of issue for ignorant vimmers
for a long time. This is not an attempt to restart old conversation. I
am looking for pointers where to research this question.
From ':h cterm-colors':
NR-16 NR-8 COLOR NAME
0 0 Black
1 4 DarkBlue
2 2 DarkGreen
3 6 DarkCyan
4 1 DarkRed
5 5 DarkMagenta
6 3 Brown, DarkYellow
7 7 LightGray, LightGrey, Gray, Grey
8 0* DarkGray, DarkGrey
9 4* Blue, LightBlue
10 2* Green, LightGreen
11 6* Cyan, LightCyan
12 1* Red, LightRed
13 5* Magenta, LightMagenta
14 3* Yellow, LightYellow
15 7* White
The color codes for NR-16 don't make sense to me. Take Yellow, for example.
Why is it numbered 14? 16-bit terminals use 11 for bright yellow [1]. Why is
it different inside Vim?
For extra info: I used guicolors before. That's why I hadn't noticed this.
[1]: https://jeffkreeftmeijer.com/vim-16-color/
--
Enan
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/20230421165606.00002f18%40gmail.com.
for a long time. This is not an attempt to restart old conversation. I
am looking for pointers where to research this question.
From ':h cterm-colors':
NR-16 NR-8 COLOR NAME
0 0 Black
1 4 DarkBlue
2 2 DarkGreen
3 6 DarkCyan
4 1 DarkRed
5 5 DarkMagenta
6 3 Brown, DarkYellow
7 7 LightGray, LightGrey, Gray, Grey
8 0* DarkGray, DarkGrey
9 4* Blue, LightBlue
10 2* Green, LightGreen
11 6* Cyan, LightCyan
12 1* Red, LightRed
13 5* Magenta, LightMagenta
14 3* Yellow, LightYellow
15 7* White
The color codes for NR-16 don't make sense to me. Take Yellow, for example.
Why is it numbered 14? 16-bit terminals use 11 for bright yellow [1]. Why is
it different inside Vim?
For extra info: I used guicolors before. That's why I hadn't noticed this.
[1]: https://jeffkreeftmeijer.com/vim-16-color/
--
Enan
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/20230421165606.00002f18%40gmail.com.
Wednesday, April 19, 2023
Re: What are some alternatives of vim-surround
On Mi, 19 Apr 2023, Tim Chase wrote:
> Strange in its inconsistency, that one would remember that part of
> the source-text was from a register while the other doesn't.
>
> Is there documentation on why this difference? I poked around at
>
> :help "-
> :help i_CTRL-R (and following on its variants)
> :help .
> :help simple-change
>
> but didn't see anything noting this small-delete peculiarity.
Well, it was a small annoyance of me in particular :)
https://github.com/vim/vim/pull/7527
You are right, it's not documented. Do you have an idea on how to
improve the documentation?
Best,
Christian
--
Die Jugend ist etwas Wundervolles. Es ist eine wahre Schande, daß man
sie an Kinder vergeudet.
-- George Bernard Shaw
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/ZD/snMMEdzwBqOSt%40256bit.org.
> Strange in its inconsistency, that one would remember that part of
> the source-text was from a register while the other doesn't.
>
> Is there documentation on why this difference? I poked around at
>
> :help "-
> :help i_CTRL-R (and following on its variants)
> :help .
> :help simple-change
>
> but didn't see anything noting this small-delete peculiarity.
Well, it was a small annoyance of me in particular :)
https://github.com/vim/vim/pull/7527
You are right, it's not documented. Do you have an idea on how to
improve the documentation?
Best,
Christian
--
Die Jugend ist etwas Wundervolles. Es ist eine wahre Schande, daß man
sie an Kinder vergeudet.
-- George Bernard Shaw
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/ZD/snMMEdzwBqOSt%40256bit.org.
Re: What are some alternatives of vim-surround
On 2023-04-19 14:35, Christian Brabandt wrote:
> On Di, 18 Apr 2023, Tim Chase wrote:
> > c<motion/object>'<c-r>"'<esc>
[snip]
> > It's not repeatable with "." (well, it is, but it repeats the
> > original replacement, not with the second text).
>
> If you use the small delete register, it is dot-repeatable.
Strange in its inconsistency, that one would remember that part of
the source-text was from a register while the other doesn't.
Is there documentation on why this difference? I poked around at
:help "-
:help i_CTRL-R (and following on its variants)
:help .
:help simple-change
but didn't see anything noting this small-delete peculiarity.
-tkc
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/ZD/oevBqZG5r9pEO%40thechases.com.
> On Di, 18 Apr 2023, Tim Chase wrote:
> > c<motion/object>'<c-r>"'<esc>
[snip]
> > It's not repeatable with "." (well, it is, but it repeats the
> > original replacement, not with the second text).
>
> If you use the small delete register, it is dot-repeatable.
Strange in its inconsistency, that one would remember that part of
the source-text was from a register while the other doesn't.
Is there documentation on why this difference? I poked around at
:help "-
:help i_CTRL-R (and following on its variants)
:help .
:help simple-change
but didn't see anything noting this small-delete peculiarity.
-tkc
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/ZD/oevBqZG5r9pEO%40thechases.com.
Re: What are some alternatives of vim-surround
On Di, 18 Apr 2023, Tim Chase wrote:
> On 2023-04-18 07:29, 'Devin Weaver' via vim_use wrote:
> > leads me to wonder what are the "vim --clean" ways to perform the
> > same actions that vim-surround offers.
>
> vim-surround offers a number of features, some easier to replicate,
> others more challenging.
>
> I commonly use
>
> c<motion/object>'<c-r>"'<esc>
>
> to wrap <motion/object> in quotes, using control+r followed by
> double-quote to enter the text of the most recent deletion/yank.
> It's not repeatable with "." (well, it is, but it repeats the
> original replacement, not with the second text).
If you use the small delete register, it is dot-repeatable. So for e.g.
quoting a single word, cw'<c-r>-' works quite well, which for me is the
main surround use case.
Best,
Christian
--
Konsequent ist nur der, der sich selber mit den Umständen wandelt.
-- Winston Spencer Churchill
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/ZD/gDZYsx8GyPBDt%40256bit.org.
> On 2023-04-18 07:29, 'Devin Weaver' via vim_use wrote:
> > leads me to wonder what are the "vim --clean" ways to perform the
> > same actions that vim-surround offers.
>
> vim-surround offers a number of features, some easier to replicate,
> others more challenging.
>
> I commonly use
>
> c<motion/object>'<c-r>"'<esc>
>
> to wrap <motion/object> in quotes, using control+r followed by
> double-quote to enter the text of the most recent deletion/yank.
> It's not repeatable with "." (well, it is, but it repeats the
> original replacement, not with the second text).
If you use the small delete register, it is dot-repeatable. So for e.g.
quoting a single word, cw'<c-r>-' works quite well, which for me is the
main surround use case.
Best,
Christian
--
Konsequent ist nur der, der sich selber mit den Umständen wandelt.
-- Winston Spencer Churchill
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/ZD/gDZYsx8GyPBDt%40256bit.org.
Tuesday, April 18, 2023
Re: What are some alternatives of vim-surround
On 2023-04-18 07:29, 'Devin Weaver' via vim_use wrote:
> leads me to wonder what are the "vim --clean" ways to perform the
> same actions that vim-surround offers.
vim-surround offers a number of features, some easier to replicate,
others more challenging.
I commonly use
c<motion/object>'<c-r>"'<esc>
to wrap <motion/object> in quotes, using control+r followed by
double-quote to enter the text of the most recent deletion/yank.
It's not repeatable with "." (well, it is, but it repeats the
original replacement, not with the second text). However you can
record a macro if you need to redo that. I can do the same sort
of thing if I'm using tags, things like
caw<a href="#target"><c-r>"</a><esc>
to wrap the current link in an HTML <a> element.
For large numbers of changes, I tend to switch to using :g or :s
commands
:g/pattern/-pu='<p>'|+pu='</p>'
:%s@pattern@<a href="#target">&</a>@g
rather than trying to do one and then "."-repeat subsequent ones.
-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 on the web visit https://groups.google.com/d/msgid/vim_use/ZD6264ioV0s2XZFJ%40thechases.com.
> leads me to wonder what are the "vim --clean" ways to perform the
> same actions that vim-surround offers.
vim-surround offers a number of features, some easier to replicate,
others more challenging.
I commonly use
c<motion/object>'<c-r>"'<esc>
to wrap <motion/object> in quotes, using control+r followed by
double-quote to enter the text of the most recent deletion/yank.
It's not repeatable with "." (well, it is, but it repeats the
original replacement, not with the second text). However you can
record a macro if you need to redo that. I can do the same sort
of thing if I'm using tags, things like
caw<a href="#target"><c-r>"</a><esc>
to wrap the current link in an HTML <a> element.
For large numbers of changes, I tend to switch to using :g or :s
commands
:g/pattern/-pu='<p>'|+pu='</p>'
:%s@pattern@<a href="#target">&</a>@g
rather than trying to do one and then "."-repeat subsequent ones.
-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 on the web visit https://groups.google.com/d/msgid/vim_use/ZD6264ioV0s2XZFJ%40thechases.com.
What are some alternatives of vim-surround
I use vim-surround so much that it has become an essential part of my Vim experience. I will continue to use it with gusto. But it does garner a question and that the facilities it provides are rather common in editing source code in general which leads me to wonder what are the "vim --clean" ways to perform the same actions that vim-surround offers.
Say I run Vim on a device where getting a git clone of the plugin difficult. Maybe it only has access to its own config and doesn't have a user accessible file system or something. What kinds of vanilla commands could be done to simulate what vim-surround does?
And if there isn't a clean alternative shouldn't the facilities vim-surround offeres be built into the base executable to begin with? I find it hard to believe we never needed to surround text in Vim prior to Tpope's amazing plugin. There has to have been more basic ways to accomplish such.
CONFIDENTIALITY NOTICE: The information contained in this message may be privileged and/or confidential. It is the property of CrowdStrike. If you are not the intended recipient, or responsible for delivering this message to the intended recipient, any review, forwarding, dissemination, distribution or copying of this communication or any attachment(s) is strictly prohibited. If you have received this message in error, please notify the sender immediately, and delete it and all attachments from your computer and network.--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/c0b94c55-1020-40bc-a37e-d7da67833c2fn%40googlegroups.com.
Monday, April 17, 2023
Re: Unable to log in to vim.org
On Mo, 17 Apr 2023, cjsmall wrote:
> I have just found out that vim.org is not accessible. Firefox reports: "We can't connect to the server at vim.org. Did you mean to go to www.vim.org?"
>
> Indeed, www.vim.org does allow access to the main site. When I attempt to ping vim.org:
>
> # ping vim.org
> ping: vim.org: Name or service not known
>
> Pinging www.vim.org attempts to work, but it never completes. Maybe you have ping blocked to avoid other networking problems.
>
> In any event, it looks like vim.org is not properly forwarding to www.vim.org and not properly DNS registered..
This has been discussed several times. TLDR: always use www.vim.org
But this is a different issue than the one reported before, which was an
issue with the database connection at the vim.org server side.
> [Note: I tried sending this message as a reply from my news reader and it disappeared - likely because I had the moderator address as vim@vim.org. This post was made on Google Groups, so
> apologies if the duplicate ever shows up.]
I did not see any message in the moderation queue. Usually posting via a
NNTP News Reader does not work.
Best,
Chris
--
Man kann sich das menschliche Geschlecht als einen Polypen denken, so
kommt man schon auf mein System von Seelenwanderung.
-- Georg Christoph Lichtenberg
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/ZD3IqpFjhz8YX/45%40256bit.org.
> I have just found out that vim.org is not accessible. Firefox reports: "We can't connect to the server at vim.org. Did you mean to go to www.vim.org?"
>
> Indeed, www.vim.org does allow access to the main site. When I attempt to ping vim.org:
>
> # ping vim.org
> ping: vim.org: Name or service not known
>
> Pinging www.vim.org attempts to work, but it never completes. Maybe you have ping blocked to avoid other networking problems.
>
> In any event, it looks like vim.org is not properly forwarding to www.vim.org and not properly DNS registered..
This has been discussed several times. TLDR: always use www.vim.org
But this is a different issue than the one reported before, which was an
issue with the database connection at the vim.org server side.
> [Note: I tried sending this message as a reply from my news reader and it disappeared - likely because I had the moderator address as vim@vim.org. This post was made on Google Groups, so
> apologies if the duplicate ever shows up.]
I did not see any message in the moderation queue. Usually posting via a
NNTP News Reader does not work.
Best,
Chris
--
Man kann sich das menschliche Geschlecht als einen Polypen denken, so
kommt man schon auf mein System von Seelenwanderung.
-- Georg Christoph Lichtenberg
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/ZD3IqpFjhz8YX/45%40256bit.org.
Re: Unable to log in to vim.org
I have just found out that vim.org is not accessible. Firefox reports: "We can't connect to the server at vim.org. Did you mean to go to www.vim.org?"
Indeed, www.vim.org does allow access to the main site. When I attempt to ping vim.org:
# ping vim.org
ping: vim.org: Name or service not known
ping: vim.org: Name or service not known
Pinging www.vim.org attempts to work, but it never completes. Maybe you have ping blocked to avoid other networking problems.
In any event, it looks like vim.org is not properly forwarding to www.vim.org and not properly DNS registered..
Regards,
--
Jeffery Small
[Note: I tried sending this message as a reply from my news reader and it disappeared - likely because I had the moderator address as vim@vim.org. This post was made on Google Groups, so apologies if the duplicate ever shows up.]
On Monday, April 17, 2023 at 7:54:02 AM UTC-7 Bram Moolenaar wrote:
Christian wrote:
> On Mo, 17 Apr 2023, 'Sebastian G=C3=B6decke' via vim_use wrote:
> > Hm, now it's complete offline?
>
> It seems to work now again. I can login and do not see issues with the
> database anymore.
For me it looks like it's fully working again. I don't have information
about what was wrong. I hope it won't happen again.
--
Men may not be seen publicly in any kind of strapless gown.
[real standing law in Florida, United States of America]
/// Bram Moolenaar -- Br...@Moolenaar.net -- http://www.Moolenaar.net \\\
/// \\\
\\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/03769068-1870-456f-8b13-6a41766af160n%40googlegroups.com.
Re: You Need VIM
On Mon, Apr 17, 2023 at 04:08:20AM -0700, rwmit...@gmail.com wrote:
> No, no it isn't. Vim is the way. All else is peril.
>
> On Sunday, April 16, 2023 at 11:40:33 PM UTC-4 Enan Ajmain wrote:
>
> > On Sun, 16 Apr 2023 09:04:25 -0400
> > Steve Litt <sl...@troubleshooters.com> wrote:
> > > meine said on Sun, 16 Apr 2023 09:57:20 +0200
> > >
> > > >Something to enjoy on a Sunday morning...
> > > >
> > > >https://youtu.be/9n1dtmzqnCU
> > >
> > > That's pretty bizarre :-)
> > >
> > > When the guy says you don't need anything but Vim, it makes me ask a
> > > question. I use VSCode to author HTML because VSCode has great
> > > zen-coding and coaches you on tags and legal CSS identifiers and
> > > values. The time I looked at a zen-coding addon for Vim, it was a
> > > total mess. What HTML aware zen-coding addons are all of you using
> > > these days?
> >
> > Damn! you're committing _hard_. You do realize the video is a parody,
> > right?
Glad to see the show here :-) TNX!
//meine
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/ZD2kYphblBlWAcTj%40trackstand.
> No, no it isn't. Vim is the way. All else is peril.
>
> On Sunday, April 16, 2023 at 11:40:33 PM UTC-4 Enan Ajmain wrote:
>
> > On Sun, 16 Apr 2023 09:04:25 -0400
> > Steve Litt <sl...@troubleshooters.com> wrote:
> > > meine said on Sun, 16 Apr 2023 09:57:20 +0200
> > >
> > > >Something to enjoy on a Sunday morning...
> > > >
> > > >https://youtu.be/9n1dtmzqnCU
> > >
> > > That's pretty bizarre :-)
> > >
> > > When the guy says you don't need anything but Vim, it makes me ask a
> > > question. I use VSCode to author HTML because VSCode has great
> > > zen-coding and coaches you on tags and legal CSS identifiers and
> > > values. The time I looked at a zen-coding addon for Vim, it was a
> > > total mess. What HTML aware zen-coding addons are all of you using
> > > these days?
> >
> > Damn! you're committing _hard_. You do realize the video is a parody,
> > right?
Glad to see the show here :-) TNX!
//meine
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/ZD2kYphblBlWAcTj%40trackstand.
Re: Unable to log in to vim.org
Christian wrote:
> On Mo, 17 Apr 2023, 'Sebastian G=C3=B6decke' via vim_use wrote:
> > Hm, now it's complete offline?
>
> It seems to work now again. I can login and do not see issues with the
> database anymore.
For me it looks like it's fully working again. I don't have information
about what was wrong. I hope it won't happen again.
--
Men may not be seen publicly in any kind of strapless gown.
[real standing law in Florida, United States of America]
/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// \\\
\\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/20230417145356.0D0A31C0423%40moolenaar.net.
> On Mo, 17 Apr 2023, 'Sebastian G=C3=B6decke' via vim_use wrote:
> > Hm, now it's complete offline?
>
> It seems to work now again. I can login and do not see issues with the
> database anymore.
For me it looks like it's fully working again. I don't have information
about what was wrong. I hope it won't happen again.
--
Men may not be seen publicly in any kind of strapless gown.
[real standing law in Florida, United States of America]
/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// \\\
\\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/20230417145356.0D0A31C0423%40moolenaar.net.
Re: You Need VIM
No, no it isn't. Vim is the way. All else is peril.
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/2c3f8feb-8094-452e-b0c3-63c45e38691fn%40googlegroups.com.
On Sunday, April 16, 2023 at 11:40:33 PM UTC-4 Enan Ajmain wrote:
On Sun, 16 Apr 2023 09:04:25 -0400
Steve Litt <sl...@troubleshooters.com> wrote:
> meine said on Sun, 16 Apr 2023 09:57:20 +0200
>
> >Something to enjoy on a Sunday morning...
> >
> >https://youtu.be/9n1dtmzqnCU
>
> That's pretty bizarre :-)
>
> When the guy says you don't need anything but Vim, it makes me ask a
> question. I use VSCode to author HTML because VSCode has great
> zen-coding and coaches you on tags and legal CSS identifiers and
> values. The time I looked at a zen-coding addon for Vim, it was a
> total mess. What HTML aware zen-coding addons are all of you using
> these days?
Damn! you're committing _hard_. You do realize the video is a parody,
right?
--
Enan
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/2c3f8feb-8094-452e-b0c3-63c45e38691fn%40googlegroups.com.
Re: Unable to log in to vim.org
On Mo, 17 Apr 2023, 'Sebastian Gödecke' via vim_use wrote:
> Hm, now it's complete offline?
It seems to work now again. I can login and do not see issues with the
database anymore.
Best,
Christian
--
Bei der Schürze liegt die Würze in der Kürze.
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/ZD0oLFokqAub6de0%40256bit.org.
> Hm, now it's complete offline?
It seems to work now again. I can login and do not see issues with the
database anymore.
Best,
Christian
--
Bei der Schürze liegt die Würze in der Kürze.
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/ZD0oLFokqAub6de0%40256bit.org.
Re: Unable to log in to vim.org
Hm, now it's complete offline?
Regards S
Am Sa., 15. Apr. 2023 um 22:44 Uhr schrieb Brett Stahlman <brettstahlman@gmail.com>:
On Saturday, April 15, 2023 at 4:33:41 PM UTC-4 Bram Moolenaar wrote:--
> When I attempt to log in to vim.org to upload a script release, either the
> login page hangs, or I get a "query failed IX3" error. Does anyone know
> whether the site is down? I think I have the correct username and password
> but can't tell for sure.
If you go to the home page you should see a warning for "Database
Problems". The website depends on a database, which currently isn't
working. Usually this kind of problem goes away after a short while.
I'll add a remark that this also affects login.Thanks!Brett S.
--
ARTHUR: No, hang on! Just answer the five questions ...
GALAHAD: Three questions ...
ARTHUR: Three questions ... And we shall watch ... and pray.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- Br...@Moolenaar.net -- http://www.Moolenaar.net \\\
/// \\\
\\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/1a02dd6e-73cd-4b43-aade-d4b9a623b01fn%40googlegroups.com.
Mit freundlichen Grüßen
Sebastian Gödecke
-- Sebastian Gödecke
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/CAJRNCbYkdxnsbZwpUR5hW6TazrLt3NWVD%2BGnWu3eD-tyB0kCig%40mail.gmail.com.
Sunday, April 16, 2023
Re: You Need VIM
On Sun, 16 Apr 2023 09:04:25 -0400
Steve Litt <slitt@troubleshooters.com> wrote:
> meine said on Sun, 16 Apr 2023 09:57:20 +0200
>
> >Something to enjoy on a Sunday morning...
> >
> >https://youtu.be/9n1dtmzqnCU
>
> That's pretty bizarre :-)
>
> When the guy says you don't need anything but Vim, it makes me ask a
> question. I use VSCode to author HTML because VSCode has great
> zen-coding and coaches you on tags and legal CSS identifiers and
> values. The time I looked at a zen-coding addon for Vim, it was a
> total mess. What HTML aware zen-coding addons are all of you using
> these days?
Damn! you're committing _hard_. You do realize the video is a parody,
right?
--
Enan
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/20230417094019.7a6940d5%40cirdan.
Steve Litt <slitt@troubleshooters.com> wrote:
> meine said on Sun, 16 Apr 2023 09:57:20 +0200
>
> >Something to enjoy on a Sunday morning...
> >
> >https://youtu.be/9n1dtmzqnCU
>
> That's pretty bizarre :-)
>
> When the guy says you don't need anything but Vim, it makes me ask a
> question. I use VSCode to author HTML because VSCode has great
> zen-coding and coaches you on tags and legal CSS identifiers and
> values. The time I looked at a zen-coding addon for Vim, it was a
> total mess. What HTML aware zen-coding addons are all of you using
> these days?
Damn! you're committing _hard_. You do realize the video is a parody,
right?
--
Enan
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/20230417094019.7a6940d5%40cirdan.
Re: You Need VIM
Benjamin Atkin said on Sun, 16 Apr 2023 14:05:38 -0700
>> coaches you on tags and legal CSS identifiers
>
>i. e. autocomplete
>
>sometimes useful, but annoying.
When writing HTML, with its begin and end tags, ids, classes, and
values, zencoding/autocomplete saves keystrokes and trips to the
Internet to look up seldom used entities. I find it an absolute
necessity for HTML.
Sure, I write C and Python in Vim, but HTML, no, I need
zencoding/autocoding.
SteveT
Steve Litt
Autumn 2022 featured book: Thriving in Tough Times
http://www.troubleshooters.com/bookstore/thrive.htm
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/20230416184322.02e158c9%40mydesk.domain.cxm.
>> coaches you on tags and legal CSS identifiers
>
>i. e. autocomplete
>
>sometimes useful, but annoying.
When writing HTML, with its begin and end tags, ids, classes, and
values, zencoding/autocomplete saves keystrokes and trips to the
Internet to look up seldom used entities. I find it an absolute
necessity for HTML.
Sure, I write C and Python in Vim, but HTML, no, I need
zencoding/autocoding.
SteveT
Steve Litt
Autumn 2022 featured book: Thriving in Tough Times
http://www.troubleshooters.com/bookstore/thrive.htm
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/20230416184322.02e158c9%40mydesk.domain.cxm.
Re: You Need VIM
> coaches you on tags and legal CSS identifiers
i. e. autocomplete
sometimes useful, but annoying. that's why there are so many different types of it. I like ido-mode in emacs which stays out of the way, fitting into the area on the bottom of the screen. Looks like there is something like this for neovim: https://github.com/ido-nvim/ido.nvim
El dom, 16 abr 2023 a la(s) 06:04, Steve Litt (slitt@troubleshooters.com) escribió:
meine said on Sun, 16 Apr 2023 09:57:20 +0200
>Something to enjoy on a Sunday morning...
>
>https://youtu.be/9n1dtmzqnCU
That's pretty bizarre :-)
When the guy says you don't need anything but Vim, it makes me ask a
question. I use VSCode to author HTML because VSCode has great
zen-coding and coaches you on tags and legal CSS identifiers and
values. The time I looked at a zen-coding addon for Vim, it was a total
mess. What HTML aware zen-coding addons are all of you using these days?
SteveT
Steve Litt
Autumn 2022 featured book: Thriving in Tough Times
http://www.troubleshooters.com/bookstore/thrive.htm
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/20230416090425.3b8f7826%40mydesk.domain.cxm.
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/CAKBexDVgzFbAE4_17waQ%3DeQW%3D%2B58QqVJjantRA6eMGLa3Xxd5g%40mail.gmail.com.
Re: You Need VIM
On April 16, 2023 12:57:20 AM PDT, meine <trialero@gmx.com> wrote:
>Something to enjoy on a Sunday morning...
>
>https://youtu.be/9n1dtmzqnCU
>
A little too close to home haha, which is why I am sure he uses vim plugins everywhere at least. I've seen some of his GNU gag videos and they are out of touch by comparison.
Still worth watching his other stuff though, its funny.
>KR,
>
>//meine
>
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/EBCDA56C-57F3-4280-B424-3941779F4434%40trevdev.ca.
>Something to enjoy on a Sunday morning...
>
>https://youtu.be/9n1dtmzqnCU
>
A little too close to home haha, which is why I am sure he uses vim plugins everywhere at least. I've seen some of his GNU gag videos and they are out of touch by comparison.
Still worth watching his other stuff though, its funny.
>KR,
>
>//meine
>
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/EBCDA56C-57F3-4280-B424-3941779F4434%40trevdev.ca.
Re: You Need VIM
> When the guy says you don't need anything but Vim, it makes me ask a
> question. I use VSCode to author HTML because VSCode has great
> zen-coding and coaches you on tags and legal CSS identifiers and
> values. The time I looked at a zen-coding addon for Vim, it was a total
> mess. What HTML aware zen-coding addons are all of you using these days?
There seem to be several plugins for zen-coding, and I encountered a
site that mentioned it is called 'Emmet' now/also.
Mayby this link helps:
https://vimawesome.com/plugin/emmet-vim
vimawesome.com is a good site and catalog for plugins, but since github
was marketed extensively there is some diversion and dispersion of
sites providing a clear catalog of working plugins...
KR,
//meine
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/ZDwmx-0uN_ZT3BZc%40trackstand.
> question. I use VSCode to author HTML because VSCode has great
> zen-coding and coaches you on tags and legal CSS identifiers and
> values. The time I looked at a zen-coding addon for Vim, it was a total
> mess. What HTML aware zen-coding addons are all of you using these days?
There seem to be several plugins for zen-coding, and I encountered a
site that mentioned it is called 'Emmet' now/also.
Mayby this link helps:
https://vimawesome.com/plugin/emmet-vim
vimawesome.com is a good site and catalog for plugins, but since github
was marketed extensively there is some diversion and dispersion of
sites providing a clear catalog of working plugins...
KR,
//meine
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/ZDwmx-0uN_ZT3BZc%40trackstand.
Re: You Need VIM
meine said on Sun, 16 Apr 2023 09:57:20 +0200
>Something to enjoy on a Sunday morning...
>
>https://youtu.be/9n1dtmzqnCU
That's pretty bizarre :-)
When the guy says you don't need anything but Vim, it makes me ask a
question. I use VSCode to author HTML because VSCode has great
zen-coding and coaches you on tags and legal CSS identifiers and
values. The time I looked at a zen-coding addon for Vim, it was a total
mess. What HTML aware zen-coding addons are all of you using these days?
SteveT
Steve Litt
Autumn 2022 featured book: Thriving in Tough Times
http://www.troubleshooters.com/bookstore/thrive.htm
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/20230416090425.3b8f7826%40mydesk.domain.cxm.
>Something to enjoy on a Sunday morning...
>
>https://youtu.be/9n1dtmzqnCU
That's pretty bizarre :-)
When the guy says you don't need anything but Vim, it makes me ask a
question. I use VSCode to author HTML because VSCode has great
zen-coding and coaches you on tags and legal CSS identifiers and
values. The time I looked at a zen-coding addon for Vim, it was a total
mess. What HTML aware zen-coding addons are all of you using these days?
SteveT
Steve Litt
Autumn 2022 featured book: Thriving in Tough Times
http://www.troubleshooters.com/bookstore/thrive.htm
--
--
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 on the web visit https://groups.google.com/d/msgid/vim_use/20230416090425.3b8f7826%40mydesk.domain.cxm.
Subscribe to:
Posts (Atom)