Harald Ums

out-file a.txt
still results in ...

BTW it is not a format-table problem
ls C:\WINDOWS\system32\drivers\etc | select LastWriteTime,FullName | grep
ices

shows the same stupid behaviour

"ebgreen" <ebgreen@discussions.microsoft.com> wrote in message
news:BD7C8430-FFE3-44E0-893E-49AEB039420C@microsoft.com...
>I believe this will address the problem when sending to a file:
>
> ls C:\WINDOWS\system32\drivers\etc | ft LastWriteTime,FullName | Out-File
> a.txt
>
> If you want to pipe it to some other command, then leave the ft pipe out
> altogether. If you want the results fomatted then make the ft the last
> pipe
> in the pipe line.
>
> "Harald Ums" wrote:
>
>> I am doing:
>> PS C:\> ls C:\WINDOWS\system32\drivers\etc | ft LastWriteTime,FullName
>>
>> LastWriteTime FullName
>> ------------- --------
>> 23.08.2001 14:00:00
>> C:\WINDOWS\system32\drivers\etc\hosts
>> 23.08.2001 14:00:00
>> C:\WINDOWS\system32\drivers\etc\lmho...
>> 23.08.2001 14:00:00
>> C:\WINDOWS\system32\drivers\etc\netw...
>> 23.08.2001 14:00:00
>> C:\WINDOWS\system32\drivers\etc\prot...
>> 23.08.2001 14:00:00
>> C:\WINDOWS\system32\drivers\etc\serv...
>>
>> I would strongly prefer a wordwrap here instead of limiting the output to
>> .
>> But the whole thing is really bad, when redirecting the whole thing to a
>> file like:
>> PS C:\> ls C:\WINDOWS\system32\drivers\etc | ft LastWriteTime,FullName
>> >a.txt
>>
>> Still powershell seems to use the column width of my cmd window.
>> The whole thing gets even more ridiculous when piping the whole thing
>> into a
>> non powershell command:
>> ls C:\WINDOWS\system32\drivers\etc | ft LastWriteTime,FullName | grep
>> ices
>> finds the line when run in a 120 column window there is a match, but no
>> match when run in a 80 column window.
>>
>>
>>
>>
>>