Comments for Brett's Blog http://brett.batie.com Thoughts of a Software Developer. Fri, 04 Jul 2008 17:13:08 +0000 http://wordpress.org/?v=2.3.1 Comment on Count number of lines in a file using DOS by iNFiNiTyLoOp http://brett.batie.com/dosshell/count-number-of-lines-in-a-file-using-dos/#comment-129 iNFiNiTyLoOp Mon, 16 Jun 2008 06:45:36 +0000 http://brett.batie.com/dosshell/count-number-of-lines-in-a-file-using-dos/#comment-129 find /c/v "" afile.txt Is the way I figured out how to do it. find /c/v “” afile.txt
Is the way I figured out how to do it.

]]> Comment on Count number of lines in a file using DOS by Brett http://brett.batie.com/dosshell/count-number-of-lines-in-a-file-using-dos/#comment-124 Brett Wed, 04 Jun 2008 21:17:02 +0000 http://brett.batie.com/dosshell/count-number-of-lines-in-a-file-using-dos/#comment-124 I think the below searches might help you if I understand the problem correctly. The below line will find "pattern" anywhere in a line. findstr /R ".*pattern.*" afile.txt The below line will find "pattern" after 140 characters. findstr /r "^(.*){140}pattern.*$" afile.txt I think the below searches might help you if I understand the problem correctly.

The below line will find “pattern” anywhere in a line.
findstr /R “.*pattern.*” afile.txt

The below line will find “pattern” after 140 characters.
findstr /r “^(.*){140}pattern.*$” afile.txt

]]> Comment on Count number of lines in a file using DOS by Ken Happich http://brett.batie.com/dosshell/count-number-of-lines-in-a-file-using-dos/#comment-123 Ken Happich Wed, 04 Jun 2008 07:36:42 +0000 http://brett.batie.com/dosshell/count-number-of-lines-in-a-file-using-dos/#comment-123 I find this to be a very interesting use of findstr and like your website. I recently ran into an issue/limitation with findstr that I did not know existed. I was trying to find a pattern at a particular column location in the file and it might have been at column position aprox 140. I used the following command findstr ^...........................................................pattern *.txt>testOutput.txt In my case there were serveral more periods (single charter wildcard) and I got the error message search string too long. Is there anyway with findstr to find a pattern at a unique location in a very long line when the pattern is closer to the end of the line? I find this to be a very interesting use of findstr and like your website. I recently ran into an issue/limitation with findstr that I did not know existed.

I was trying to find a pattern at a particular column location in the file and it might have been at column position aprox 140. I used the following command

findstr ^…………………………………………………..pattern *.txt>testOutput.txt

In my case there were serveral more periods (single charter wildcard) and I got the error message search string too long.

Is there anyway with findstr to find a pattern at a unique location in a very long line when the pattern is closer to the end of the line?

]]> Comment on touch with DOS commands by masc http://brett.batie.com/dosshell/touch-with-dos-commands/#comment-65 masc Sun, 17 Feb 2008 23:24:48 +0000 http://brett.batie.com/dosshell/touch-with-dos-commands/#comment-65 @copy %1 + nul %1 /by also works, provided copy is new enough to test that it shouldn't overwrite the original file @copy %1 + nul %1 /by

also works, provided copy is new enough to test that it shouldn’t overwrite the original file

]]> Comment on touch with DOS commands by masc http://brett.batie.com/dosshell/touch-with-dos-commands/#comment-64 masc Sun, 17 Feb 2008 22:24:40 +0000 http://brett.batie.com/dosshell/touch-with-dos-commands/#comment-64 @copy nul: /b +%1 tmp.$$$ @move tmp.$$$ %1 =touch.bat doesn't change anything in file.org, only time and date @copy nul: /b +%1 tmp.$$$
@move tmp.$$$ %1

=touch.bat
doesn’t change anything in file.org, only time and date

]]> Comment on touch with DOS commands by Brett http://brett.batie.com/dosshell/touch-with-dos-commands/#comment-57 Brett Tue, 12 Feb 2008 23:02:12 +0000 http://brett.batie.com/dosshell/touch-with-dos-commands/#comment-57 You are right! I have only used that command to quickly create an empty file. I have never used it for updating the modification time of an existing file. I do not know of a way to modify the date modified of a file in dos without using a third party program. Although, if you want the date modified to be updated to the current time you could use one of the follow commands: 1. This copies the file to a temp File and then copies the temp File back over the original. Then deletes the temp File. type file.txt > tmpFile.txt | type tmpFile.txt > file.txt | del tmpFile.txt 2. Type: edit file.txt, then hit: alt, f, s, alt, f, x I really think both solutions are hacks at best. I also wonder what would happen to unicode files or files that have unix style line endings. You are right! I have only used that command to quickly create an empty file. I have never used it for updating the modification time of an existing file.

I do not know of a way to modify the date modified of a file in dos without using a third party program. Although, if you want the date modified to be updated to the current time you could use one of the follow commands:

1. This copies the file to a temp File and then copies the temp File back over the original. Then deletes the temp File.
type file.txt > tmpFile.txt | type tmpFile.txt > file.txt | del tmpFile.txt

2. Type: edit file.txt, then hit: alt, f, s, alt, f, x

I really think both solutions are hacks at best. I also wonder what would happen to unicode files or files that have unix style line endings.

]]> Comment on touch with DOS commands by errr http://brett.batie.com/dosshell/touch-with-dos-commands/#comment-56 errr Tue, 12 Feb 2008 20:46:28 +0000 http://brett.batie.com/dosshell/touch-with-dos-commands/#comment-56 That seems to clear(!!) the file, rather than touching it That seems to clear(!!) the file, rather than touching it

]]>