Both my and KingofGamesYami's code will repeat forever, that is what the
while true do
...
end
is for, it loops for as long as true is true
We also both used
os.pullEvent("redstone")
which is a little more advanced than just a sleep loop, basically it "sleeps" the turtle until the redstone inputs change, then it checks whether the redstone inputs are the ones we care about, then either does something about it, or sleeps again. Just trust me when I say this is better for lag than sleep(2).
--#i=1 --uncomment for your debug output
while true do --#loop forever
os.pullEvent("redstone") --#waits for the redstone to change
if rs.getInput("left") and rs.getInput("right") then --#if both inputs are high
rs.setOutput("back",true) --#output high at the back
else --#otherwise
rs.setOutput("back",false) --#output low
end
--#print(i)
--#i=i+1
end
You can uncomment the debug lines, but remember it will only actually loop through this if the redstone signals change, so maybe use a lever or a button to test it (you will get 2 loops per on-off as the event triggers on high and on low)
As for getting it into your turtle via pastebin - copy the code onto it and make a paste, you will get a heinous code looking something like "QJju77jw" - copy that
Open up your turtle and type "pastebin get <heinous code> startup" - this will copy it into the startup program which will mean the programs will run automatically if the computers restart (chunks become unloaded, server resets/crashes etc)
If you are playing single player or are a server admin it's a bit easier, go into <your Minecraft folder>\saves\<whichever save this is stored in>\computer\<computer id>\ and then save it there. Again I would recommend saving it as startup (no extension)
Also, fair enough with the explosions, normally I would suggest a Project Red AND gate or similar, but turtles are explosion proof so it does create extra robustness
