Oh, I see the issue - when you give ssh a command to run that isn't your
shell then environment vars aren't passed through. I don't want to make it
difficult to be more flexible in the future, so I'll add a new command for
this. I could imagine one day supporting different settings for character
encoding, color, and terminfo per pty, and doing that in command line
arguments makes it impossible. (For the first iteration I think it's fine to
have a global setting).
On Mon, Dec 6, 2010 at 3:44 PM, Nicholas Marriott <
nicholas.marri...@gmail.com> wrote:
> On Mon, Dec 06, 2010 at 03:36:56PM -0800, George Nachman wrote:
> > > - There needs to be a mechanism to specify the client "identify"
> > > information, particularly the terminfo description tmux should use
> but
> > > also the terminal flags (if is UTF-8, 256 colours, 88
> > > colours). Easiest probably to have that as an argument to -C.
> > >
> > > Why not use -2, -8, -u?
> >
> > Yep they are fine for flags, what about terminfo description? Passed
> as
> > -C or in the protocol?
> >
> > Any reason not to use the value of $TERM for this?
>
> Sure, that'll be fine (easier in fact), if you want to set it you'll
> just need to put it in the environment with ssh.
>
------------------------------------------------------------------------------
What happens now with your Lotus Notes apps - do you make another costly
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
_______________________________________________
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users
