filePro in a Mac Pro

[Brian K. White]

On 7/28/2016 11:11 AM, Walter Vaughan via Filepro-list wrote:
> A single user native UX application - probably not
> A single user terminal application - nothing from an engineering standpoint preventing, just no market (per KB's post)
> A single/multi user cloud based solution -
> 	Install putty for mac
> 		- http://techgeek.tech/use-putty-for-mac-os-x/
> 	Purchase a virtual host for about $10 month
> 		- https://www.digitalocean.com/pricing/
> 	Purchase a new license or transfer and install filePro on new virtual host running either Linux or FreeBSD (which feels more like operating with Mac Terminal applications).
> 		- http://www.fptech.com/fptech/fp_prices.php
>
> So yes you can have an icon on your Mac Pro Desktop and run filePro like a boss.


I have made a customized iTerm2 similar to the way I customized putty 
(minus the scoansi emulation and facetwin color pallette)

It's a native app you can just install, no building, no macports or 
brew, no X11.

Most of my changes actually got incorporated back in to the upstream 
iTerm2, but I didn't even try to offer the run-program-escape sequence, 
since it's obviously a security hole.
https://github.com/gnachman/iTerm2/pulls?q=is%3Apr+is%3Aclosed+author%3Aaljex

Here is the Aljex iTerm2
https://github.com/aljex/iTerm2/releases

And a video showing how to install and set up a saved ssh session
https://www.youtube.com/watch?v=M6LMyh9kY6s

And here is the upstream generic iTerm2
https://iterm2.com/


The generic upstream iTerm2 is usable with filepro since the character 
encoding fix got incorporated. The rest is just nice but not necessary.
You just need to do a few things manually like select cp437 or latin1 
character encoding to match whatever expectations you have in your 
fp/termcap.

For keepalives, although upstream accepted most of my anti-idle fix, 
there is a difference of opinion on one detail and they still do one 
thing slightly wrong by choice. They only look at the keyboard instead 
of anything that passes over the tty. My version looks at the tty. But 
that doesn't matter in most cases, because if you are using ssh to 
connect, then there is a better keepalive mechanism in openssh itself, 
instead of injecting null bytes into the tty session, and just hoping 
most software ignores them. (not all software does)
So, whichever version of iTerm2, do *this* for keepalive:

https://patrickmn.com/aside/how-to-keep-alive-ssh-sessions/

https://forum.ivorde.com/how-to-prevent-linux-ssh-client-from-disconnecting-using-serveraliveinterval-t19451.html

-- 
bkw