[Salacity]

Has been fixed, the solution is at the end of the OP, or refer to Sir-TeaBags post Thank you, Sir-TeaBag for helping me fix this

So, i'm trying to decipher the meaning of certain typedef definitions inside of header files and to do this I decided to use the FIND command to trace their meanings, but since it only looks in one directory at a time, I have to re-write the command in order for it to look inside of other directories. I wrote a bash script to automate this, but i keep getting a weird error i cant fix. Basically, the pipe symbols ( >> ) turn into (1>) so:

find \i "moneyTree" C:\Users\John\Desktop\MyHouse >> myWallet.txt

Turns into:

find \i "moneyTree" C:\Users\John\Desktop\MyHouse 1> myWallet.txt

After trying a few things and looking in google, I decided to make a thread hopefully I can get some help here:

=-=-=-=      START - CODE     -=-=-=-=-=-=-

SET KEYWORD=PASCAL
SET SEARCH_PATH=C:\MingGW\Include\*
SET ALT_SEARCH_PATH=C:\MingGW\Include\
SET OUTPUT_FILE=C:\users\john\desktop\output.txt

FIND \I "%KEYWORD%" %SEARCH_PATH% >>  %OUTPUT_FILE%

PAUSE

=-=-=-=      END - CODE     -=-=-=-=-=-=-

🎉


-=-=-=-=-  FIX -=-=-=-=-=-=-=-=-
For some reason, I have to add carets before each "greater than" symbol. So the correct code would be:

find \i "moneyTree" C:\Users\John\Desktop\MyHouse ^>^> myWallet.txt

[Sir-Teabag]

Using >> shouldn't turn in to a 1 since i use that all the time...

Did you try adding carets?
Tell me if this works for you

Code

FIND \I "%KEYWORD%" %SEARCH_PATH% ^>^> %OUTPUT_FILE%

[Salacity]

Using >> shouldn't turn in to a 1 since i use that all the time...

Did you try adding carets?
Tell me if this works for you

Code

FIND \I "%KEYWORD%" %SEARCH_PATH% ^>^> %OUTPUT_FILE%

Thank you so much!! That was it

[Sir-Teabag]

Thank you so much!! That was it

Awesome! Glad I could help ✌ 🎉