[mosh-devel] --predict=always

[Keith Winstein]

Hello Eric,

By popular request, I added a --predict=experimental option to the mosh in 
Git. (https://github.com/keithw/mosh)

It shows some interesting behavior but it does give faster feedback than 
waiting to see if each epoch is an echoing one.

Best regards,
Keith

On Sun, 10 Jun 2012, Hari Balakrishnan wrote:

> Eric,
>
> I'm not entirely sure it's a good idea to make it super-aggressive. So you might want to try it first yourself.
>
> For example, you don't want to echo a password ever.  Or if you're running an application where "n" means "next message", for example.  There are several such cases where being super-aggressive would do the wrong thing.
>
> Hari
>
> On Jun 10, 2012, at 6:52 AM, Eric Frey wrote:
>
>> Yes, it would be useful, and shouldn’t require more than a few lines of code change.  I’ll try to add it.
>>
>> What’s the process used to become a committer?
>>
>> Eric
>>
>> From: Hari Balakrishnan [mailto:hari at csail.mit.edu]
>> Sent: Saturday, June 09, 2012 4:48 PM
>> To: Eric Frey
>> Cc: <mosh-devel at mit.edu>
>> Subject: Re: [mosh-devel] --predict=always
>>
>> This is the intended conservative behavior... The prediction works in epochs and echoes speculatively after verifying that it's predicting correctly for the first few chars in each epoch.
>>
>> I can see an 'aggressive' option being potentially useful for you, in principle.
>>
>> Hari
>>
>> Sent from my phone, sorry for any typos.
>>
>> On Jun 9, 2012, at 4:29 PM, "Eric Frey" <ric at jhfrey.com> wrote:
>>
>> I'm trying to use mosh in a Linux development environment over a satellite link.  Ping times are typically >700 ms, so mosh is conceptually very useful.  I'm a programmer, and would be happy to contribute to the project.
>>
>> After what are probably the typical "getting up" problems, I've got it working from my desktop (Fedora 16 running in a VMware virtual machine on Windows) to a variety of servers running Centos (fairly old distro).  It appears to work as advertised, except that I've been unable to get --predict=always to work.  The first characters of a new line don't display until they have been echoed back, but then things work as expected.
>>
>> Before I go hunting around in the code, I thought I'd check if this was a known issue (I didn't see it listed as one).  If it's not a known issue, I'll open an new issue on it.
>>
>> Thanks,
>>
>> Eric Frey
>>
>> NVIDIA
>>
>> _______________________________________________
>> mosh-devel mailing list
>> mosh-devel at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/mosh-devel
>
>