On 2019-07-25, Dennis Lee Bieber  wrote:

> On Thu, 25 Jul 2019 16:16:28 +0200, Axel Berger 
> declaimed the following:
>
>> Charlie Gibbs wrote:
>>
>>> It gets pretty voluminous after a while,
>>
>> My point was hat all visible lists cut off names after some number of
>> characters and in these examples all you see is completely identical for
>
> C:\VB_Shared>dir
>  Volume in drive C is OS
>  Volume Serial Number is 4ACC-3CB4
>
>  Directory of C:\VB_Shared
>
> 07/25/2019  12:03 PM              .
> 07/25/2019  12:03 PM              ..
>  
> 07/25/2019  11:58 AM                 0 This is a long file name in a junk
> file - having no content - under Windows 10. All for one, and one for All.
> Let's see ~tildes~ & # @ ! = noise. Will it ever stop.txt
>  
>               16 File(s)     44,548,564 bytes
>                3 Dir(s)  1,356,316,938,240 bytes free
>
> C:\VB_Shared>
>
>  Well... that didn't truncate, my news client wrapped the file name to
> two and half lines (note -- I had not reached the limit for Win10 file
> names but got tired of rambling).
>
>  PowerShell even formats it nicely, by not wrapping to the left margin
> -- instead indenting the wrapped text into the file name column.
>
>  Off hand, I'd say Windows will display to the physical limit of the
> file name -- and that span would be unique between entries.

Well, at least the Windows utilities you've tried so far will do so.  :-)

It reminds me of that Gary Larson cartoon of someone looking through
a book of jokes.  Everything was filed under T, since each joke's name
started with "That one about the..."

--
/~\  cgibbs@kltpzyxm.invalid (Charlie Gibbs)
\ /  I'm really at ac.dekanfrus if you read it the right way.
 X   Top-posted messages will probably be ignored.  See RFC1855.
/ \  "Alexa, define 'bugging'."

--- SoupGate-Win32 v1.05