On 2023-04-30 20:58, Enan Ajmain wrote:
> 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.
On my Windows 10 Pro system, my boot partition "C:" had SFNs and LFNs,
but the new partitions I created on the same physical drive had LFNs
only. I don't know if it would have been the same on Windows 10 Home, or
on Windows 11 Home and Pro. In any case, SFNs seem to be enabled on the
partition where the OP is running.
<https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/fsutil-8dot3name>
explains how to enable or disable SFNs on a partition. There are
warnings about not disabling SFNs on a partition that already has them.
Stan Brown
Tehachapi, CA, USA
https://BrownMath.com
--
--
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/1d8a1a81-556b-af5e-09a2-4d3c95eb17d3%40fastmail.fm.
No comments:
Post a Comment