How to? SOLVED: UnicodeOutput & UTF8Output settings not being respected in INI? [ANSWER: they must be in the 4NT section of the INI file!]

[Claire_CJS]

They are right there in my INI file, yet..... Setting them to the same values at the command line changes the behavior

have i bugged out the INI processor somehow?

Still trying to figure out how setting option to the same as my INI could change behavior....

I can always run this in my environm.btm {my personal tcstart.bat equivalent} but i'd rather address the root cause. Just want my pipes to work without having to ":u8" them allllll the timiiime

 

[Charles Dye]

I don't fully understand what you are doing, but you can check the current settings with commands like:

option unicodeoutput
option utf8output

Dunno why they would not be read from the .INI file, unless they were in the wrong section; they should be under TCC. Or unless TCC is not using the .INI file you think it is; check the %_ININAME variable.

What is GR? A batch file? Be aware that piping can open a new shell. You might try with |! just to see if there's a difference.

 

[Claire_CJS]

I don't fully understand what you are doing, but you can check the current settings with commands like:

option unicodeoutput
option utf8output

Dunno why they would not be read from the .INI file, unless they were in the wrong section; they should be under TCC. Or unless TCC is not using the .INI file you think it is; check the %_ININAME variable.

They have to be in sections? Oof. I've been freely moving things around all my life. This explains a lot.

I don't even have a TCC section. I have a [4NT] section. This may be an INI file passed down through the ages. Should I change the 4NT to TCC?

What is GR? A batch file? Be aware that piping can open a new shell. You might try with |! just to see if there's a difference.

Yea, i grep a lot, grep is an alias for grep -i --text --color=always -d skip ... and i have GREP_COLOR variables set ... use this everywhere, but have to run through strip-ansi to get the color out sometimes to use the results elsewhere.

Piping stuff like that is how I got here. This is all about piping :) But yea, i didn't know that about piping for a couple decades. My tcstart detects if it's transient or not to decide whether to run my environment.btm very heavy startup script. Have done a lot of timing and optimization on that to trim 10ths of seconds off of it, but the best speedup was not running it at all if it's transient shell.

Anyway —
I ran a grep "" <con: [in between quotes is the alien emoji, which won't display here i don't think] to force an emoji into my process list.

Then i did a tasklist /l | grep grep to spit out all the greps in my process list and see if the emoji would display correctly through both kids of pipes: | and |:u8

I tried both pipes with all 4 Yes/No combinations of Set[Unicode|UTF8\Output=[Yes|No] to find out which combinaton(s) made it work with not just |:u8, but with | .

Only 1 of the 4 combinations worked for that, and it was Unicode=no, UTF=yes

 

[Charles Dye]

I don't even have a TCC section. I have a [4NT] section. This may be an INI file passed down through the ages. Should I change the 4NT to TCC?

No no no — my mistake. 4NT is correct.

 

[Claire_CJS]

No no no — my mistake. 4NT is correct.

Phew! I'd rather only be doing 1 wrong thing than 2. :)

So that was probably the problem, then. That I had it in the wrong section of the ini. Thanks! Issue closed :)