Post reply

Name:
Email:
Subject:
Message icon:

Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What is the last letter in the word "SlickEdit":
How many LETTERS are in the following? "a1b2c3":
Which number is missing?  "12345689":

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: Clark
« on: February 15, 2025, 06:05:23 PM »

Hot fix added to v29.0.1 so that "git" does not get run by default. Also fixed an issue where git gets run even though auto detect has been turned off.
Posted by: jaymmartin
« on: February 15, 2025, 07:13:17 AM »

After much confusion, it seems that slickedit is messing with my ssh-agent.    I use openssh via cygwin for networking.   I also use Git which uses ssh, but only on the command line.  Well, I wanted to use slickedit to only create check in messages on git commits (instead of using vim or notepad).  I do not use slickedit Git integration and have never explicitly enabled it.   I use a file socket pointed to by a user wide SSH_AUTH_SOCK environmental variable.   After doing a (local only) "git commit" and writing a check-in message.  I saw two behaviors in my confused thrashing: either the socket file was deleted with the ssh-agent still running or a duplicate ssh-agent was created with an empty key database.  My brute force solution is to unset SSH_AUTH_SOCK in my run slickedit scripts.