miawendell / puttycyg

Automatically exported from code.google.com/p/puttycyg
0 stars 2 forks source link

Status of project #68

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Is this project dead?  Are there alternatives?

Original issue reported on code.google.com by mark.fa...@gmail.com on 13 Dec 2011 at 1:59

GoogleCodeExporter commented 8 years ago
I've since switched to the solution documented by Simon Tatham (PuTTY author) 
at 
http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/cygwin-terminal-windo
w.html.  Despite being tagged as "currently rather long and involved" at one 
point, it takes less than 5 minutes to setup - especially if Cygwin is already 
installed with "make" and "gcc".

I agree with the notes on that solution, that the only thing to make this 
process better would be to have Cygwin's telnetd properly fixed so that a 
special cygtermd was not necessary.

Since doing this, I haven't looked back.  I no longer have to worry about any 
issues specific to puttycyg, or having a working puttycyg version available for 
the rare occasion that a new PuTTY version is made available.  The cygtermd 
solution will also work with any of PuTTY's daily development snapshots - 
something that would have been difficult (at least to maintain) with puttycyg.

For me, puttycyg was an excellent project - one that I've used for probably 5+ 
years, and have shared with many others on my development teams.  However, 
since the release of PuTTY 0.61 (containing the fix necessary for the cygtermd 
solution to work) and now 0.62 just on 2011-12-10, I honestly no longer see the 
need for puttycyg.

Original comment by ziese...@gmail.com on 13 Dec 2011 at 3:01

GoogleCodeExporter commented 8 years ago
It seems that there are at least three solid replacements which meet PuTTYcyg's 
original goal of a better Cygwin terminal without requiring X11:

* PuTTY 0.61 + cygtermd

* mintty

* rxvt

If you know others, feel free to list them here.

Unfortunately, I can no longer maintain PuTTYcyg and so the project is looking 
for an active maintainer (if it's useful to continue maintaining it).

Original comment by medgar123 on 17 Dec 2011 at 9:04

GoogleCodeExporter commented 8 years ago
Yeah, I started looking around and found KiTTY.  I like it but it would be even 
better if I could group sessions in a window like putty connection manager.  
I'll use that for now until/unless I find something better.

Original comment by mark.fa...@gmail.com on 17 Dec 2011 at 11:19

GoogleCodeExporter commented 8 years ago
Well, KiTTY is PuTTYcyg.  Or was: I can't tell if it has been maintained within 
KiTTY or not; you'll probably have to ask the maintainer.  It might be better 
to use KiTTY with cygtermd.

Note that mintty is also minimized version of PuTTY, but with the Cygwin 
component compiled in to the same binary so that mintty requires Cygwin to run.

Original comment by medgar123 on 18 Dec 2011 at 10:03

GoogleCodeExporter commented 8 years ago
Yep, mintty is based on PuTTY's terminal emulation and Windows UI parts, but 
leaves out the networking functionality, which is already provided by Cygwin 
packages such as openssh. Cygwin's latest setup.exe installs mintty as the 
default terminal.

Original comment by andy.koppe on 19 Dec 2011 at 5:50

GoogleCodeExporter commented 8 years ago
PuTTYCyg provides a feature that MinTTY does not, logging term output to disk, 
which I use all the time.  Very useful for capturing process output and so 
forth.

It will be a sad day when the most recently released version of PuTTYCyg 
doesn't work with a Cygwin update.

Original comment by keith1ch...@gmail.com on 11 Apr 2012 at 8:49

GoogleCodeExporter commented 8 years ago
Keith - nothing against PuTTYCyg, but please review 
http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/cygwin-terminal-windo
w.html for use with PuTTY directly.  Under PuTTY, under Session/Logging, enable 
"Session logging".  I just tested this, and it works with at least the 
"Printable output" option.

Original comment by ziese...@gmail.com on 11 Apr 2012 at 9:25

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
@Keith Mintty has the --log command line option for that, and there's also the 
'script' utility for logging specific commands.

Original comment by andy.koppe on 11 Apr 2012 at 11:37