Path: utzoo!attcan!uunet!dino!ux1.cso.uiuc.edu!uwm.edu!rpi!netserv2!deven From: deven@rpi.edu (Deven T. Corzine) Newsgroups: comp.sys.amiga.tech Subject: Re: CLI I/O help needed... Message-ID: Date: 13 Apr 90 09:57:56 GMT References: <387100015@S37.Prime.COM> Organization: Rensselaer Polytechnic Institute, Troy, NY Lines: 33 In-Reply-To: GIUSTI@S37.Prime.COM's message of 11 Apr 90 12:53:00 GMT On 11 Apr 90 12:53:00 GMT, GIUSTI@S37.Prime.COM said: GIUSTI> I'm trying to write a simple program that is to be invoked at GIUSTI> the CLI level. Its purpose is to display to the CLI screen GIUSTI> formatted information about the current directory. My GIUSTI> question, what is the best "legal" way of accessing the CLI GIUSTI> window for formatted text output? I want to avoid using GIUSTI> "printf" (this is an exercise in Amigados!), and I have to be GIUSTI> able to determine current CLI screen size in order to format GIUSTI> the text properly. You might try looking at the source to LS 3.1; it was posted recently. GIUSTI> I've noticed the amigados Process structure has a pointer to a GIUSTI> Console Task. This appears to be what I am looking for, but I GIUSTI> don't know how to get at the console through this pointer. GIUSTI> How can I use the console device I/O given this pointer? The pr_ConsoleTask pointer in the Process structure is a (real) pointer to the pr_MsgPort field in the Process structure of the console handler device -- i.e. CON:... runback replaces this field with a pointer to NULL: instead to background programs more effectively, so a program openning "*" won't hold the window open. If you just want to talk to the console, you can open "*", but it's probably nicer to use Output() instead. Deven -- Deven T. Corzine Internet: deven@rpi.edu, shadow@pawl.rpi.edu Snail: 2151 12th St. Apt. 4, Troy, NY 12180 Phone: (518) 274-0327 Bitnet: deven@rpitsmts, userfxb6@rpitsmts UUCP: uunet!rpi!deven Simple things should be simple and complex things should be possible.