anyone got any resolution for this issue?
is conqterm a dead project ?
there seems to be no bug fix since 2 years ago...
it's just unfortunate since this is one of the greatest extensions that far
expand vim's magic...
On Wed, Mar 6, 2013 at 2:16 PM, ping wrote:
> On 12/20/2012 12:15 PM, ping w
On 12/20/2012 12:15 PM, ping wrote:
On 12/20/2012 12:11 PM, ping wrote:
On 12/20/2012 12:08 PM, ping wrote:
hi nico and other vim conquetermers:
>
> I found this a (relatively) "big" issue:
> say if you have your capture of output from a command you issued to
your remote machine from withi
hi nico and other vim conquetermers:
I found this a (relatively) "big" issue:
say if you have your capture of output from a command you issued to your
remote machine from within conqterm,
the big advantage of using conqueterm is the ability to leverage the
existing vim search knowledge you acqu
On 12/20/2012 12:11 PM, ping wrote:
On 12/20/2012 12:08 PM, ping wrote:
hi nico and other vim conquetermers:
>
> I found this a (relatively) "big" issue:
> say if you have your capture of output from a command you issued to
your remote machine from within conqterm,
> the big advantage of us
On 12/20/2012 12:08 PM, ping wrote:
hi nico and other vim conquetermers:
>
> I found this a (relatively) "big" issue:
> say if you have your capture of output from a command you issued to
your remote machine from within conqterm,
> the big advantage of using conqueterm is the ability to lever
