Silly batch file tricks, redirecting stdout into an evironment variable and %~dp0

re: Silly batch file tricks, redirecting stdout into an evironment variable and %~dp0

Sen2008 — Thu, 03 Dec 2009 21:27:23 GMT

Nice dialog going on here.

Someone mentioned pipes. I use biterscripting ( http://www.biterscripting.com ) for implementing pipes.

A pipe is a data connection between two commands. There can be four types of pipes. I will show an example of how I do this.

THE STRAIGHT PIPE

Output of one command goes into input of another command.

# Code

lf > $s

len $s

# End code

THE TEE (T) PIPE

Output of one command goes into input of two commands.

# Code

lf > $s

len $s

echo $s

# End code

THE WYE (Y) PIPE

Output of two commands go into input of one command.

# Code

cat x.txt > $s

cat y.txt >> $s

echo $s

# End code

THE EH (H) PPE

Output of two commands go into input of two commands.

# Code

cat x.txt > $s

cat y.txt >> $s

len $s

echo $s

# End code

These four types of pipes are also called one-to-one, one-to-many, many-to-one and many-to-many. By using variables, I can implement all four. Pretty clever. But you need a language that allows you to redirect a command's output (and errors) to a variable.

re: Silly batch file tricks, redirecting stdout into an evironment variable and %~dp0

Judago — Fri, 20 Nov 2009 07:23:56 GMT

Here's a little trick that gets the length of a variable, why oh why didn't they add a length parameter when they added substrings....

for /f %%a in ('cmd /u /c set /p "=%str:"= %"^<nul^|find /v /c ""') do echo %%a

where %str% is the variable (%str:"= % is to avoid double quote conflicts by converting "'s to spaces)

Try it without the "/c" switch to the find command ;)

re: Silly batch file tricks, redirecting stdout into an evironment variable and %~dp0

David Gray — Wed, 28 Oct 2009 22:58:22 GMT

I may be a tad old fashioned, but I still think batch files have a place. They are lean, reasonably fast, and run without a bunch of extra infrastructure that may be missing or disabled for security reasons. For instance, WSH may be disabled, and neither Perl nor PowerShell is part of a default installation of Windows.

Paraphrasing a comment that I heard, in a TechEd session long ago, about Notepad, CMD.EXE is everywhere.

Apart from the one spam message that crept into it, this blog is fabulous. I found it in the course of a Google search, pinned it into my Favorites, and have referred to it several times in the last week or so.

re: Silly batch file tricks, redirecting stdout into an evironment variable and %~dp0

Grant Peters — Wed, 07 Oct 2009 05:21:45 GMT

I'm surprised about all the hacks i saw in the comments to avoid the temp.txt file (such as using the for command). Why not just pipe directly from one into the other, i.e.

sometool.exe | set /p TOOLOUTPUT=

and thats it.

re: Silly batch file tricks, redirecting stdout into an evironment variable and %~dp0

Aloe Vera Distributor - myflp.org — Tue, 29 Sep 2009 19:10:44 GMT

Hello there.

I have something to say, about AloeVera, something about which you wrote above, about health and minerals... For a long time, I and my nice friend use the products of the flp. We every time see the good results and also we make money for our families and we are happy. My friend works with Aloe Vera in the company of forever living products has more than 5 years (My friend works ONLY in the flp company and has a wife and three children). I know aloe Vera products for weight loss for a long time, but a year ago, began working as a distributor in the Forever Living Company.

Of course, this job is some difficult, but in no other case, You can earn so much money with so much much fun and good smiling faces around..

So if you want to discuss something about which you wrote above, and about my experience with Aloe vera products for weight loss, I'll always be glad to talk.

Best regards from Washington state and have a nice day!

Andrew - Aloe Vera Distributor

re: Silly batch file tricks, redirecting stdout into an evironment variable and %~dp0

Taz — Tue, 08 Sep 2009 16:58:34 GMT

Or you could simply do:

cd /d %~dp0

And it would change both the drive and the current dir.

re: Silly batch file tricks, redirecting stdout into an evironment variable and %~dp0

Eric — Sat, 29 Aug 2009 02:51:00 GMT

Also of note: %~d0 will give the Drive Letter where the script is located.

This would be necessary in some cases; for example, if you are running the script from a different drive, you can't simply "cd %~dp0" because you have to switch drives first.

So you could do this in the batch file:

%~d0

cd %~dp0

re: Silly batch file tricks, redirecting stdout into an evironment variable and %~dp0

Maddy — Wed, 15 Apr 2009 12:14:42 GMT

Hi,

Can anyone suggest a method by which we can extract the output or the contents of an IDE to a text file.

A batch file named run.bat calls the IDE under test.

Thanks

Maddy

re: Silly batch file tricks, redirecting stdout into an evironment variable and %~dp0

ChernoJ — Fri, 13 Mar 2009 07:01:03 GMT

Date and Time: Instead of date /t and time /t, there're the built-in %date% and %time% env vars.

eg:

echo %time%

set timestamp=%date% %time%

re: Silly batch file tricks, redirecting stdout into an evironment variable and %~dp0

Timestamp — Tue, 03 Mar 2009 14:14:33 GMT

nice aswel is timestamp environment var to spool to a timestamped batch file

:: sets the timestamp arguments to the actual date & time

for /f "tokens=1,2 delims=: " %%i in ('time /t') do set hhmi=%%i%%j

for /f "tokens=2,3,4 delims=/- " %%i in ('date /t') do set yyyymmdd=%%k%%j%%i

set log_backup_changes=%yyyymmdd%-%hhmi%_backup.log

rman target / @%script_backup_changes% log=%log_backup_changes% append