[Extremely short] No multishell & TLCO -- Kills multishell, runs normal shell as the top-level coroutine.

term.redirect(term.native())

if window or multishell then
  sleep(0)
  --tlco
  local a = _G.printError
  function _G.printError()--when the bios goes to print the error, we run our code
	_G.printError=a
	--no multishell
	term.redirect(term.native())
	multishell=nil
	--no window
	term.setTextColor(colors.yellow)term.setBackgroundColor(colors.black)
	term.clear()term.setCursorPos(1,1)
	write"Multishelless Top-level "
	os.run({},"rom/programs/shell")
  end
  os.queueEvent"terminate"--cause the shell to terminaye
else
  shell.run"newStartup"
end

term.redirect(term.native())
multishell = nil--optional, probably not necessary if you never return to the shell, but you have problems include this.

Geforce Fan, on 21 February 2015 - 05:26 AM said:

You shouldn't add this to bedrock. term.redirect(term.native()) disables the window api, meaning they couldn't fg or bg it–if they tried to click on a different tab, the next time it drew to the screen, it would just draw over what they're on on the other tab.
In other words, it breaks multishell's ability to prevent apps from writing to the screen while not focused. OneOS,on the other hand, should not be ran in multishell–it's an OS for pete's sake.
I'm going to try OneOS without the window api
Wow… OneOS runs EXTREMELY smooth without the window API. I'm really blown away, I remember your OS as laggy and slow, and with 2 lines of code it's suddenly zipping around like insertanalagyhere!

oeed, on 21 February 2015 - 06:54 AM said:

Geforce Fan, on 21 February 2015 - 05:26 AM said:

You shouldn't add this to bedrock. term.redirect(term.native()) disables the window api, meaning they couldn't fg or bg it–if they tried to click on a different tab, the next time it drew to the screen, it would just draw over what they're on on the other tab.
In other words, it breaks multishell's ability to prevent apps from writing to the screen while not focused. OneOS,on the other hand, should not be ran in multishell–it's an OS for pete's sake.
I'm going to try OneOS without the window api
Wow… OneOS runs EXTREMELY smooth without the window API. I'm really blown away, I remember your OS as laggy and slow, and with 2 lines of code it's suddenly zipping around like insertanalagyhere!

Hmmmm, yeah I didn't think about that actually… I wonder if there's a way to detect if it's within multishell or not.

oeed, on 21 February 2015 - 06:54 AM said:

Hmmmm, yeah I didn't think about that actually… I wonder if there's a way to detect if it's within multishell or not.

Geforce Fan, on 21 February 2015 - 07:05 AM said:

multishell.setFocus, then if multishell.getFocus() is 2, they're running at least 2 tabs, meaning they're running it within a multishell tab.
edit: or just multishell.getCount(). :\

if not multishell then
  print( "Hey, guess what? I'm not running in multishell!" )
end

MKlegoman357, on 21 February 2015 - 12:21 PM said:

oeed, on 21 February 2015 - 06:54 AM said:

Hmmmm, yeah I didn't think about that actually… I wonder if there's a way to detect if it's within multishell or not.

Geforce Fan, on 21 February 2015 - 07:05 AM said:

multishell.setFocus, then if multishell.getFocus() is 2, they're running at least 2 tabs, meaning they're running it within a multishell tab.
edit: or just multishell.getCount(). :\

if not multishell then
  print( "Hey, guess what? I'm not running in multishell!" )
end

Geforce Fan, on 21 February 2015 - 07:04 PM said:

Or, you could just check if it's an advanced terminal.
This will say it's in multishell regardless of weather you have tabs open or not.
I don't think you understand what we're trying to do. We're checking if they're running in a tab or not.

MKlegoman357, on 21 February 2015 - 07:18 PM said:

Geforce Fan, on 21 February 2015 - 07:04 PM said:

Or, you could just check if it's an advanced terminal.
This will say it's in multishell regardless of weather you have tabs open or not.
I don't think you understand what we're trying to do. We're checking if they're running in a tab or not.

Regardless of the number of tabs running, if a program is running in multishell it is running in a multishell tab - inside a window object, so whenever there are more tabs opened multishell could just resize the current program's window. So checking if it's running in multishell should be enough.

MKlegoman357, on 21 February 2015 - 07:18 PM said:

EDIT: oh, and a good OS IMO should be running TLCO anyways, not as a shell program.

MKlegoman357, on 22 February 2015 - 08:10 AM said:

And what if I have multishell running in multishell? It's not gonna work then. I think Bomb Bloke made a good point about the whole window and multishell things - leave it to the user. If he/she wants it they can do it themselves. Well, I don't really remember how any of the CC update broke a TLCO. And no, it's not about performance. But running an 'OS' as a program of another OS (CraftOS) just looks like running Linux on a Windows machine in a VM. Remember that by running the 'OS' that way you can also catch any errors that may happen in rednet or shell/multishell, which a good 'OS' should be catching and dealing with. You wouldn't be able to do that without TLCO.

Geforce Fan, on 22 February 2015 - 11:47 PM said:

-snip-
CC updates have broken Nevercast's TLCO, AND ElvishJerrico's.
-snip-

os.queueEvent('modem_message')

os.queueEvent('modem_message',0)