Home
| Search
| C & C++
| D
| DMDScript
| News Groups
| index
| prev
| next
|
Archives
D Programming
DD.gnu digitalmars.D digitalmars.D.bugs digitalmars.D.dtl digitalmars.D.dwt digitalmars.D.announce digitalmars.D.learn digitalmars.D.debugger C/C++ Programming
c++c++.announce c++.atl c++.beta c++.chat c++.command-line c++.dos c++.dos.16-bits c++.dos.32-bits c++.idde c++.mfc c++.rtl c++.stl c++.stl.hp c++.stl.port c++.stl.sgi c++.stlsoft c++.windows c++.windows.16-bits c++.windows.32-bits c++.wxwindows digitalmars.empire digitalmars.DMDScript |
c++ - Scrolling up and down in MSDOS command window
Does anyone know how to scroll up and down in a MSDOS command prompt window? If I print a list or my program has a lot of bugs in it and runs through the whole screen, what can I do to see the all the errors that are not in the immediate window? Jan 30 2003
Which operating system are you using?
In Windows XP I have a command prompt configured with.
Options:
Cursor Size: Small
Display Options: Window
Command History
Buffer Size 999
Number of Buffers 4
Font:
Size: 8 x 12
Layout:
Screen Buffer Size:
Width: 80
Height: 1024 (you can scroll SEVERAL pages back with this.
Window Size:
Width: 80
Height: 48
HTH
Jan
Antwan Williams wrote:
Jan 30 2003
I have Windows 98. "Jan Knepper" <jan smartsoft.us> wrote in message news:3E39A5F8.7F195530 smartsoft.us... Jan 30 2003
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
If you are using MS-DOS (and Windows Console and Unix),
the easiest way of redirecting your all printf and fprintf is to
add this in the beginning of your program:
freopen("wherestdoutgoes.txt", stdout);freopen("wherestderrgoes.txt", =
stderr);
This way, you can keep a record of all the text generated by your =
program
using printf(...) and fprintf(stderr, ...) including system errors.
You may chose to only redirect stderr only since stdout is for
normal screen output.
"Antwan Williams" <antwan799 attbi.com> wrote in message =
news:b1c24i$19g1$1 digitaldaemon.com...
Jan 30 2003
I can simply redirect output to file and then view this file wherever you want: Far, Notepad, etc. To redirect file add "> filename" (without quotes) at the end of command line, e.g..: sc test.cpp > err.log The same can be done for your own program: test.exe > exe.log Nic Tiger. "Antwan Williams" <antwan799 attbi.com> сообщил/сообщила в новостях следующее: news:b1c24i$19g1$1 digitaldaemon.com...Does anyone know how to scroll up and down in a MSDOS command prompt Jan 30 2003
Yes, but not for stderr "Nic Tiger" <nictiger progtech.ru> wrote in message news:b1cung$2jlu$1 digitaldaemon.com...I can simply redirect output to file and then view this file wherever you want: Far, Notepad, etc. To redirect file add "> filename" (without quotes) at the end of command line, e.g..: sc test.cpp > err.log The same can be done for your own program: test.exe > exe.log Nic Tiger. "Antwan Williams" <antwan799 attbi.com> сообщил/сообщила в новостях следующее: news:b1c24i$19g1$1 digitaldaemon.com...Does anyone know how to scroll up and down in a MSDOS command prompt Feb 03 2003
Under Linux, you can do:
make 2> err.log
for redirecting stderr to a file. ('1' for stdout). Too bad this does not
work in dos.
- Rajiv Bhagwat
"KarL" <someone somewhere.org> wrote in message
news:b1nl8t$sre$1 digitaldaemon.com...
Feb 03 2003
Rajiv Bhagwat wrote: Feb 04 2003
Sigh..... The title says MS-DOS, please.... I know you are trying to be helpful. "Rajiv Bhagwat" <dataflow vsnl.com> wrote in message news:b1nr7c$vub$1 digitaldaemon.com... Feb 05 2003
In article <b1nl8t$sre$1 digitaldaemon.com>, KarL (someone somewhere.org) says...Yes, but not for stderr Feb 05 2003
"Larry Brasfield" <larry_brasfield snotmail.com>:If you are using command.com, then there is no hope of doing anything sensible with it. Feb 05 2003
Gisle Vanem schrieb...Doesn't all DOS power-users use 4DOS? Is so it's easy: "command >&> file". Feb 06 2003
In article <b1st1h$147o$1 digitaldaemon.com>, Gisle Vanem (gisle war.hell.no) says..."Larry Brasfield" <larry_brasfield snotmail.com>:If you are using command.com, then there is no hope of doing anything sensible with it. Feb 06 2003
|