adoxa/ansicon

Version 1.71

iPaat opened this issue · 5 comments

iPaat commented

Hi everyone,

I wonder if there is also a compiled version of v1.71?

At OneDrive I already have found v1.70 but if I use that version with IntellJIDEA (PhpStorm) the $ sign is missing.
V1.66 is completely not working. If I run a command in my terminal, it never will stop running. I have to close the terminal and have to open a new one.

My config says:

"C:\ansicon\x64\ansicon.exe" -p "C:\Program Files\Git\bin\sh.exe" -login -i

I'm running Windows 10 with

PhpStorm 2017.2 Build #PS-172.3317.83, built on July 18, 2017
Licensed to NAME_REMOVED
Subscription is active until April 17, 2018
JRE: 1.8.0_152-release-915-b5 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0

My .minttyrc file says:

BoldAsFont=-1
Font=Fira Code
FontHeight=12
BellFlash=yes
Term=xterm

And .bashrc says:

env=~/.ssh/agent.env

agent_load_env () { test -f "$env" && . "$env" >| /dev/null ; }

agent_start () {
    (umask 077; ssh-agent >| "$env")
    . "$env" >| /dev/null ; }

agent_load_env

# agent_run_state: 0=agent running w/ key; 1=agent w/o key; 2= agent not running
agent_run_state=$(ssh-add -l >| /dev/null 2>&1; echo $?)

if [ ! "$SSH_AUTH_SOCK" ] || [ $agent_run_state = 2 ]; then
    agent_start
    ssh-add
elif [ "$SSH_AUTH_SOCK" ] && [ $agent_run_state = 1 ]; then
    ssh-add
fi

unset env

On Windows 7 v1.66 is still running without any issues.

adoxa commented

Don't know exactly what state I've left it in, but I've pushed v1.72 and uploaded the x64 version.

If you're using mintty, you shouldn't need ANSICON at all.

iPaat commented

Thanks a lot for your efforts. I'll will test it as soon I'm at home.

If you're using mintty, you shouldn't need ANSICON at all.

Sadly some colors are present and some not. For composer I need ANSICON to show colors. For git not. Maybe I missed something in my configuration process?


Edit:
Thank you very much for your help. Version 1.72 works without any problems.

adoxa commented

Mintty is a terminal emulator, so it uses redirected output, which ANSICON will ignore. Hm, perhaps you only need the ANSICON (or ANSICON_VER) environment variable for composer to use color? ... Or explicitly add --ansi to the composer command (which is probably what the environment variable would effectively do).

Nice to know it works (so far, anyway).

iPaat commented

I've tested this again in the internal terminal of PHPStorm...

Without ANSICON:
"C:\Program Files\Git\bin\sh.exe" --login -i

no-ansicon
no-ansicon--ansi

With ANSICON:
"C:\ansicon\x64\ansicon.exe" -p "C:\Program Files\Git\bin\sh.exe" --login -i

ansicon
ansicon--ansi

If I run Mintty (C:\Program Files\Git\bin\sh.exe) directly, I don't need ANSICON at all. This is really strange in my opinion.

adoxa commented

As Richard mentioned in #106, you shouldn't need ANSICON from PHP v7.2, either; he also mentioned in #91 that it worked directly, but maybe that was due to running from cmd.

It is strange that running sh directly supports ANSI, but not when running sh --login -i (at least, I suppose that's what's you mean). If you're still going to use ANSICON, I would suggest removing -p - it's not needed when you run a program directly.