Hi Johnson, I agree that there are problems with help
screens which are more than 1 page long. However, I do
not suggest to call MORE or other tools. The better
solution is to keep the help screen limited to 1 page
and do something like
program /? > program.txt
edit program.txt
to create a more verbose help text for users who want
to know more... Or, alternatively, call something like
if (isatty(1)) { printf("-- more --"); r.h.ah = 7; intdos(&r, &r);
printf("\n"); }
after every 20something lines of help screen.
Adding a blatant ad...: I am looking for somebody who
could write some documentation / examples for ADD and
EECHO2 (replaces sysdelay + syseecho) which can be found
at http://www.coli.uni-sb.de/~eric/command-line-add-subtract.zip and
http://www.coli.uni-sb.de/~eric/stuff/soft/specials/syseecho-sysdelay.zip
... so if you do not feel like programming but have some time for DOS
gadgets, then YOU could help. Thanks :-).
ADD can add and subtract signed 16 bit values and returns the low byte
in the errorlevel (cool with FreeCOM), and EECHO2 contains EECHO (also
present in FreeDOS kernel), clearscreen and delay (if scroll lock is
on, it will instead wait for a key, and if scroll lock is kept pressed,
the delay will be bypassed). Both eecho2 and add are < 512 bytes each =8-).
Bernd already played with ADD a bit, maybe he has some nice examples.
Eric
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
