BG> There is one more thing I'd really like to see added to Msged,
BG> and that's the ability to perform an external operation without
BG> having to manually enter the command in a Msged prompt window
BG> (OLX uses token keywords for this).

RS> What the fuck do you want to use externals for anyway ?
RS> You should be using another multitasker window for that stuff.

BG> I already do, but I choose to run Msged in a FS session, and
BG> there are times when it would be much easier to hit just one
BG> key instead of 3 or 4, plus a couple of mouse strokes.

In that case the answer is a decent OS level task switcher which
uses the keyboard. There are some around for OS2 , including one
which implements the Desqview task switch style.

BG> It doesn't hurt to have the choice,

The problem with the traditional external stuff in the app itself
is that it inevitably incurs the time to actually do it. Medieval
and dinosaury.

BG> and in the DOS version, it would be a real advantage IMO.

I still cant see that either. Its only useful if you arent
running any multitasker at all, just a single tasking system.
There must be damned few people doing that today, even if
they are using the DOS version. A few dorks on XTs at most.

BG> For example, if I want to run LIST or something like
BG> that, I currently have to do either of the following
BG> (this is in edit mode, but although the read mode keystrokes
BG> are slightly different, the principle is the same)...

RS> You should just have List already open in another multitasker window,
RS> and have some decent window switch mech in the multitasker itself,
RS> like the Desqview Alt-n approach, even with something like OS2.

BG> Alt-Esc toggles between sessions under OS/2, or Ctl-Esc brings
BG> up the window list,

No news to me Bill.

BG> and I do already have Qedit/2 and List/2 running so it's no big deal here,

So no need for a better external capability.

BG> but I still maintain that it wouldn't be a useless addition at all.

Well, it really comes down to how many people are reading their
mail on a single tasker. IMO there arent enough to worry about
too much, and they should be taken out the back and shot anyway.

BG> 1.  Press Alt-1, then enter the command name in the prompt
BG> window. When the external command or program has exited, I
BG> then have to press  to clear the "DOS command
info" window.

BG> 2.  Press Alt-O, which shells to a system prompt,
BG> run the command, then type EXIT to return to Msged.

RS> And there is none of that farting around with another
RS> multitasker window, just use the same ALT-n approach
RS> go get back to the OLR window when you want to.

BG> Jeeze Rod, after nearly 3 years with OS/2, at least give
BG> me a bit of credit for knowing how to use it productively!

No thanks, you are faking away your medieval way of using it, if you
really did use it properly, you wouldnt want the enhanced external stuff.

BG> I know all that, and I agree that it's a far better method
BG> over all, but that still doesn't mean that my suggestion is
BG> useless, especially for the DOS version.  Some people still
BG> single-task under DOS, believe it or not. |-)

Not basically, and if they are that brain dead, thats their problem.

RS> With the n permanently assigned by your auto desktop restart
RS> or even more radical not turning the machine off ever.

BG> No point leaving it on all night here,

Fraid so, much better machine reliability, no farting around starting up
the apps again when you turn it on, even if that stuff is autostarted.

BG> but it runs non-stop between 0600 and 2300 or so daily, and all
BG> smaller utes and apps are already loaded and running during that period.

They all should be, even stuff used only once a week,
machine never turned off. Only way to go for quick
task switches. Anything else is medieval dinosaur stuff.

RS> Anything else is dinosaur technology.

BG> Not all of it.

Fraid so.

BG> I'll even concede that some people don't need a MTer at all,
BG> and straight DOS is quite sufficient for their purposes.

I dont believe it, thats crap basically. Yes, some people are
using such pathetically inadequate hardware that they dont
have much choice, but they should get something better. Single
tasking is medieval dinosaur stuff. Long past its use by date.

BG> Not me though, but I'm still not arrogant enough to suggest
BG> that everybody should use their machines the way I prefer to,

Pathetic Bill, try harder boy |-)

BG> right or wrong (and who's to say what that is
BG> anyway, as circumstances and needs differ?).

Thats crap basically. You could say the same thing about
pencil and paper when writing a novel. Only someone who
is brain dead would claim 'circumstances and needs differ',
its just plain fucked. It really is as simple as that.

BG> function 5  {at}SHELL list.exe
BG> function 6  {at}SHELL q.exe

BG> ...and so on (get my drift?).

RS> Well, its clearly better than what you have now, but you
RS> still have the farting around as the OS does that work,
RS> loading that task and closing it again. Dinosaur stuff.

BG> Only as a useful adjunct though, not as a replacement.

I dont believe its a useful adjunct either,
only useful for dorks who are single tasking.

BG> I've tried doing this with macros, but as both the DOSCMD
BG> and DOS keywords require user input, it can't be done.

RS> Urgh. Thats always been another area where DV pisses on
RS> OS2 too, you can much more easily overlay key definitions
RS> on a particular tasks window than you can with OS2.

BG> You misunderstand.

Nope.

BG> These are internal Msged macro commands, nothing

(Continued to next message)

--- PQWK202