Start the putty from the fluent terminal, and after closing the fluent terminal, the putty is automatically quit.

[yar999]

Start the putty from the fluent terminal, and after closing the fluent terminal, the putty is automatically quit.

[felixse]

You can disable ConPty for your profile to circumvent this

[yar999]

I tried to disable the ConPty option, but the result is the same, when I exit Fluent Terminal, the program started from Fulent Terminal also exits automatically!

[robinmaisch]

This might be a more general problem: for me, this seems to apply to just about any application. While in stand-alone CMD, the child processes live on after the console is terminated, with Fluent Terminal they are killed together with the tab that started it, regardless of which shell was used, too. It would be very helpful if that could be fixed. Great job otherwise, I like the Fluent Terminal very much!

[hanskokx]

This isn't so much of an issue with FT, but with how windows handles processes spawned from UWP applications. Without digging into the code, it's possible that putty could be spawned from the tray process, but that would very likely introduce memory leaks, security issues, and generally be undesirable. I think you are better off launching putty via a different mechanism, or leaving the shell open.

If you use powershell and launched putty from there, you could maybe use Start-Job to launch the task - https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/start-job?view=powershell-7.1

• but you would, I think, still need to keep the shell open. (I'm more familiar with Linux background tasks than windows, where this sort of thing is much more common.) If you did that, you'd still have access to your shell. Maybe that's good enough for you? 🤷🏼‍♂️

Alternatively, you could simply use ssh instead of putty (unless you are using putty's more advanced features, like connecting to a serial connection or something, in which case there are other tools to handle that.)

I've found that, in general, putty can fairly easily be replaced entirely by a solid .ssh_config file and learning a few common commands... But that may not be for everyone.

Maybe you'd like to elaborate on the issue further, or perhaps I've answered your question sufficiently?