On 31 August 2011 07:44, Charles Campbell wrote:
> Charles Campbell wrote:
>>
>> Benjamin R. Haskell wrote:
>>>
>>> On Wed, 31 Aug 2011, Benjamin R. Haskell wrote:
>>>
On Tue, 30 Aug 2011, Guy Halford-Thompson wrote:
> Is this something that is likely to get fixed?
Seems ve
Charles Campbell wrote:
Benjamin R. Haskell wrote:
On Wed, 31 Aug 2011, Benjamin R. Haskell wrote:
On Tue, 30 Aug 2011, Guy Halford-Thompson wrote:
Is this something that is likely to get fixed?
Seems very likely to me. And probably soon, based on his usual
turnaround time.
As far as I
Benjamin R. Haskell wrote:
On Wed, 31 Aug 2011, Benjamin R. Haskell wrote:
On Tue, 30 Aug 2011, Guy Halford-Thompson wrote:
Is this something that is likely to get fixed?
Seems very likely to me. And probably soon, based on his usual
turnaround time.
As far as I can tell, the source of
On Wed, 31 Aug 2011, Lech Lorens wrote:
On 31 August 2011 05:46, Guy Halford-Thompson wrote:
Unfortunately I can't change the sshd_config, going to have to work
around it for the moment.
With regard to your problem, you can probably work it around by
specifying in your ~/.ssh/config that the
On Wed, 31 Aug 2011, Benjamin R. Haskell wrote:
On Tue, 30 Aug 2011, Guy Halford-Thompson wrote:
Is this something that is likely to get fixed?
Seems very likely to me. And probably soon, based on his usual
turnaround time.
As far as I can tell, the source of the issue is that
autoload/
On Tue, 30 Aug 2011, Guy Halford-Thompson wrote:
Ah, sorry I wasn't too clear in my first post, thanks for clarifying.
No problem.
My turn to clarify, it seems:
Unfortunately I can't change the sshd_config, going to have to work
around it for the moment.
I wouldn't expect you to. That s
On 31 August 2011 05:46, Guy Halford-Thompson wrote:
> Ah, sorry I wasn't too clear in my first post, thanks for clarifying.
>
> Unfortunately I can't change the sshd_config, going to have to work
> around it for the moment.
>
> Is this something that is likely to get fixed?
Please, quote only th
Ah, sorry I wasn't too clear in my first post, thanks for clarifying.
Unfortunately I can't change the sshd_config, going to have to work
around it for the moment.
Is this something that is likely to get fixed?
Ty
On 30 August 2011 08:33, Benjamin R. Haskell wrote:
> On Tue, 30 Aug 2011, Charl
On Tue, 30 Aug 2011, Charles Campbell wrote:
guyht wrote:
I am experiencing a bug where Explorer does not honour a port number
when editing files over SCP.
To reproduce
Open a directory over scp (gvim scp://user@domain:1234//home/user/)
Files and directories listed as expected...
Open a fi
guyht wrote:
I am experiencing a bug where Explorer does not honour a port number
when editing files over SCP.
To reproduce
Open a directory over scp (gvim scp://user@domain:1234//home/user/)
Files and directories listed as expected...
Open a file
vim ignores the port number and attempts to
I am experiencing a bug where Explorer does not honour a port number
when editing files over SCP.
To reproduce
Open a directory over scp (gvim scp://user@domain:1234//home/user/)
Files and directories listed as expected...
Open a file
vim ignores the port number and attempts to edit the file a
11 matches
Mail list logo
