| acid_burn | Evening here. Uhhh... |
| cfedde | eval: $_ = "BAT"; $_++ for (0..9813); $_ |
| buubot | cfedde: BAT |
| cfedde | eval: $x = "BAT"; ++$x for (0..9813); $x |
| buubot | cfedde: POF |
| cfedde | eval: $x = "BAT"; ++$x for (0..9812); $x |
| buubot | cfedde: POE |
| cfedde | ack |
| acid_burn | Ackster? eval: $x = "BAT"; |
| buubot | acid_burn: BAT |
| acid_burn | Joost is awesome. |
| stuuf | GumbyBRAIN: bring me a checkbook! and a mother mole! |
| GumbyBRAIN | And when you have nothing to configure, test::harness should have gotten me to your mother. |
| rindolf | f00li5h: here? |
| dre^ | what's the proper way to get access to environment variables? using ENV I get some, but not all. e.g. if I just do 'set' on the command line, I get like 158 items, whereas 'env' only returns 21 specifically I'm going to be SIGWINCH savvy, so I need to grab $LINES when it changes I'm thinking maybe just a system("export $LINES"); at the top of the signal handler might be enough, but figured I'd ask... |
| stuuf | um.. |
| simcop2387 | thats it i'm buying Elisabeth a gross of potatoes |
| stuuf | do you actually understand how shell and environment variables work? |
| dre^ | well, you can get them and set them... I don't fully understand the difference between 'set' and 'env', so... probably no, I don't have a full understanding |
| stuuf | right, but making a new shell and exporting LINES won't do anything to *your program's* $ENV{LINES} |
| simcop2387 | eval: \%ENV; hmm buubot must filter that |
| buubot | simcop2387: {} |
| dre^ | ... right. I'm wondering if I need to be exporting it from teh program when it catches a SIGWINCH so that it shows up in %ENV |
| cfedde | eval: atan2(0, -1) |
| buubot | cfedde: 3.14159265358979 |
| stuuf | nothing will go into your %ENV unless you put it there you have to ask the terminal how big it is |
| dre^ | I thought that why $LINES and $COLUMNS were being maintained... |
| cfedde | eval: ['f', keys %ENV, 'g'] |
| buubot | cfedde: ['f','g'] |
| dre^ | those values change when I resize my terminal... through no code of my own |