If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Command Window
Using a batch file to open a command window. BUT I cannotget the command widow to expand horizontally. How do I do this. So much stuff is generated for the .EXE I call using the command window it is very difficult to read. These are error messages the .EXE is generating. Is there a way to redirect them ? |
Ads |
#2
|
|||
|
|||
Command Window
On 6/24/2019 3:14 PM, Freepy wrote:
Using a batch file to open a command window. BUT I cannotget the command widow to expand horizontally. How do I do this. So much stuff is generated for the .EXE I call using the command window it is very difficult to read. These are error messages the .EXE is generating. Is there a way to redirect them ? Create a shortcut to the batch file. Then request the properties of the shortcut. The properties of a shortcut to a batch file are different from the properties of other shortcuts. In this case, you want Layout tab, where you can specify the width and height of the command window. For this to work, you run your batch file by selecting the shortcut and not the batch file itself. -- David E. Ross http://www.rossde.com/ Donald Trump lied his way onto the Forbes 400 richest people list. https://tinyurl.com/yx9ebrqz |
#3
|
|||
|
|||
Command Window
In message , Freepy
writes: Using a batch file to open a command window. BUT I cannotget the command widow to expand horizontally. How do I do this. Try in the command window mode con: cols=x .. (Con: is short for console!) Back in the days of real hardware, x could only take certain values (80 and 132 were usually OK, I think 40 and 20 might have worked too); these days where the command window is just GUI-generated, I think x can be anything. So much stuff is generated for the .EXE I call using the command window it is very difficult to read. These are error messages the .EXE is generating. Is there a way to redirect them ? If your executable is fred.exe, and you are calling it with something like fred [some parameters] , then try fred [parameters] log.txt ; that may or may not work. If you're actually there to see the error messages, try fred [parameters] | more , which will pause them a screenful at a time. (That's the character which in the default font in command mode will look like a vertical line with a break in it.) "More" will pause; hitting space will get another screenful, hitting enter will just get another line. -- J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf Play dirty. If a fellow contestant asks the audience if they've got any requests for what he or she should play, reply, "Yeah... Monopoly." |
#4
|
|||
|
|||
Command Window
On 6/24/2019 6:14 PM, Freepy wrote:
Using a batch file to open a command window. BUT I cannotget the command widow to expand horizontally. How do I do this. So much stuff is generated for the .EXE I call using the command window it is very difficult to read. These are error messages the .EXE is generating. Is there a way to redirect them ? Nirsoft nircmd.exe" win setsize (free utilities) -- Zaidy036 |
#5
|
|||
|
|||
Command Window
On Tue, 25 Jun 2019 00:53:01 +0100, J. P. Gilliver (John) wrote:
In message , Freepy writes: Using a batch file to open a command window. BUT I cannotget the command widow to expand horizontally. How do I do this. Try in the command window mode con: cols=x . (Con: is short for console!) Back in the days of real hardware, x could only take certain values (80 and 132 were usually OK, I think 40 and 20 might have worked too); these days where the command window is just GUI-generated, I think x can be anything. I had no idea "mode con:" was still supported in the command window, but sure enough. I tried cols=150, and it also increased the number of rows. -- Stan Brown, Oak Road Systems, Tompkins County, New York, USA http://BrownMath.com/ http://OakRoadSystems.com/ Shikata ga nai... |
#6
|
|||
|
|||
Command Window
On Mon, 24 Jun 2019 15:14:39 -0700, Freepy wrote:
These are error messages the .EXE is generating. Is there a way to redirect them ? https://stackoverflow.com/questions/...t-windows-cmd- stdout-and-stderr-to-a-single-file -- Stan Brown, Oak Road Systems, Tompkins County, New York, USA http://BrownMath.com/ http://OakRoadSystems.com/ Shikata ga nai... |
#7
|
|||
|
|||
Command Window
Stan Brown wrote:
On Mon, 24 Jun 2019 15:14:39 -0700, Freepy wrote: These are error messages the .EXE is generating. Is there a way to redirect them ? https://stackoverflow.com/questions/...t-windows-cmd- stdout-and-stderr-to-a-single-file If you need a "tee", you can get one as part of Coreutils. http://gnuwin32.sourceforge.net/packages/coreutils.htm ( http://gnuwin32.sourceforge.net/packages.html ) Then the command might be dir something 2&1 | tee dir_out.txt That puts a copy of the output into a file for you, as well as displaying it in the Command Prompt window. To make that work, you need tee.exe from Coreutils bin ZIP file libiconv2.dll from Coreutils dep ZIP file libintl3.dll from Coreutils dep ZIP file and they have to be in your path, like, dumped into the current working directory. If you use the packages as delivered, they might add an element to the path for you. Anyway, it's something to play with. If you just redirect directly, then you don't get dumpage into the Command Prompt window. dir something dir_out.txt 2&1 I typically go to the trouble of setting up "tee" when some sort of command line build is happening, and I don't want to lose any output. make world | tee X11build.txt Paul |
#8
|
|||
|
|||
Command Window
In message , Stan Brown
writes: On Tue, 25 Jun 2019 00:53:01 +0100, J. P. Gilliver (John) wrote: [] Try in the command window mode con: cols=x [] I had no idea "mode con:" was still supported in the command window, but sure enough. mode /? will bring up some nice nostalgic feelings (-: I tried cols=150, and it also increased the number of rows. Yes, me too (well, I tried 200). I was surprised. The full is MODE CON: COLS=c LINES=n -- J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf If you want to make people angry, lie to them. If you want to make them absolutely livid, then tell 'em the truth. |
#9
|
|||
|
|||
Command Window
"Freepy" wrote in message ... Using a batch file to open a command window. BUT I cannotget the command widow to expand horizontally. How do I do this. So much stuff is generated for the .EXE I call using the command window it is very difficult to read. These are error messages the .EXE is generating. Is there a way to redirect them ? If the command window stays open until you manually close it, right-click on the title bar and select Properties. You can change the window width there. Whatever you change it to will remain as the default width for any command window after that, though. Or, go the the .bat propertieslayout and check "Wrap text output on resize", if wrapping would help you out. HTH! -- SC Tom |
#10
|
|||
|
|||
Command Window
On 6/26/2019 4:45 AM, SC Tom wrote [in part]:
Or, go the the .bat propertieslayout and check "Wrap text output on resize", if wrapping would help you out. HTH! Windows 7 Layout would be in the Properties of a shortcut to the .bat file, not in the Properties of the .bat file itself. However, even with the shortcut, I do not see anything about wrapping. -- David E. Ross http://www.rossde.com/ Donald Trump lied his way onto the Forbes 400 richest people list. https://tinyurl.com/yx9ebrqz |
#11
|
|||
|
|||
Command Window
On Wed, 26 Jun 2019 07:45:37 -0400, "SC Tom" wrote:
"Freepy" wrote in message ... Using a batch file to open a command window. BUT I cannotget the command widow to expand horizontally. How do I do this. So much stuff is generated for the .EXE I call using the command window it is very difficult to read. These are error messages the .EXE is generating. Is there a way to redirect them ? If the command window stays open until you manually close it, right-click on the title bar and select Properties. You can change the window width there. Whatever you change it to will remain as the default width for any command window after that, though. There are two options in that context menu, Properties and Defaults. If you select Properties, you're only adjusting the properties of the current Command Prompt window. Other Command Prompt windows that you open later won't be affected. If you select Defaults and adjust the properties in there, the current window plus any subsequent windows will be affected. In both cases, if you already have other Command Prompt windows open, they won't be affected by any of the changes described above. These Command Prompt windows only pick up their settings during window launch. -- Char Jackson |
#12
|
|||
|
|||
Command Window
In alt.windows7.general "J. P. Gilliver (John)" wrote:
In message , Stan Brown writes: On Tue, 25 Jun 2019 00:53:01 +0100, J. P. Gilliver (John) wrote: [] Try in the command window mode con: cols=x [] I had no idea "mode con:" was still supported in the command window, but sure enough. mode /? will bring up some nice nostalgic feelings (-: Indeed. And more to the point, how else could we configure the right Code Page in a Command Prompt window!? :-) rem Code Page 28591 is the ISO-8859-1 charset: mode con: cp select=28591 |
Thread Tools | |
Display Modes | |
|
|