You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This has been implemented with $ansi global variable. It will work in almost all cases. But there are still a few edge cases that will need address in the future, and also it doesn't effect BBCode yet b/c that lib still needs to be fully integrated with ANSI::Code.
It has been pointed out to me that it would probably be better if a global wasn't set by default. For that to work there are two options.
Either $ansi = nil would have to be equivalent to $ansi = true and only setting it specifically to false would deactivate it. That'll work but it is a bit odd to have nil === true.
Or we need to use a $noansi (or $no_ansi) global instead.
Both cases may cause backward compatibility issues --the later more so than the former. So does the benefit out way the downside of change?
Activity
trans commentedon May 7, 2011
Should this effect all codes including moving the cursor, or just effect colorization codes?
trans commentedon Nov 10, 2011
This has been implemented with
$ansiglobal variable. It will work in almost all cases. But there are still a few edge cases that will need address in the future, and also it doesn't effect BBCode yet b/c that lib still needs to be fully integrated with ANSI::Code.trans commentedon Jan 6, 2015
It has been pointed out to me that it would probably be better if a global wasn't set by default. For that to work there are two options.
$ansi = nilwould have to be equivalent to$ansi = trueand only setting it specifically tofalsewould deactivate it. That'll work but it is a bit odd to havenil === true.$noansi(or$no_ansi) global instead.Both cases may cause backward compatibility issues --the later more so than the former. So does the benefit out way the downside of change?