Subj : Re: dosemu
To   : tenser
From : Al
Date : Tue Feb 04 2020 16:14:24

 Al> I have eliminated all the chatter when running doors with
 Al> dosemu by ending the dosemu execution line with 2>&1>/dev/null
 Al> but I still see..
 
 te> Just a drive-by comment, but that redirection probably isn't
 te> quite what you want.

Thanks for reading and replying to my post. Your probably right. I just
recently got a couple doors setup and they seem to work just as I need
them to but I see the contents of the .bat file when I run those doors
before the door runs, so I was trying to stop that. I have been googling
trying to find a way to stop it.

 te> In particular, when using Bourne-like shells (ksh, bash, dash, zsh,
 te> etc), order of redirection matters.  Redirections are evaluated
 te> left-to-right, so `2>&1>/dev/null` with redirect file descriptor
 te> number 2 (conventionally, "standard error") to whatever file
 te> descriptor 1 (also by convention "standard output") refers to
 te> _at the time of redirection_, and _then_ redirect file descriptor
 te> 1 to /dev/null.  Notably after both redirections are processed,
 te> file descriptor 2 will still point to whatever 1 referred to
 te> before 1 was redirected to /dev/null.

OK, I read that a couple times and will try to get that in my head.. :)

 te> In other words, this doesn't redirect both stderr and stdout to
 te> /dev/null.  To do that, you want to do: `>/dev/null2>&1`.

I'm still not certain what I should do to eliminate the .bat file
displaying it's contents before the door runs, is 1>&2>/dev/null what I
want?

Thanks for your comments.. :)

 Ttyl :-),
         Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
 * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

.