[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [gftp] Help. 2.0.17 won't save edited file on remote

To: gftp-users@seul.org
Subject: Re: [gftp] Help. 2.0.17 won't save edited file on remote
From: Brian Masney <masneyb@gftp.org>
Date: Tue, 17 Aug 2004 16:41:15 -0400
Delivered-to: archiver@seul.org
Delivered-to: gftp-users-outgoing@seul.org
Delivered-to: gftp-users@seul.org
Delivery-date: Tue, 17 Aug 2004 16:41:28 -0400
In-reply-to: <200408171339.37888.acanton@adams-blake.net>
References: <200408171339.37888.acanton@adams-blake.net>
Reply-to: gftp-users@seul.org
Sender: owner-gftp-users@seul.org
User-agent: Mutt/1.5.5.1+cvs20040105i

On Tue, Aug 17, 2004 at 01:39:37PM -0700, Adams-Blake Co. wrote:
> Slack 9.1
> gftp 2.0.17
> 
> I compiled 2.0.17 from source. Works fine except that when I right-click EDIT 
> on a remote file, the editor (nedit) pops up with the file but any changes 
> are not transfered back to the host. They are saved in /tmp with a mungled 
> name. With the past version I would get a dialogue box that would pop up 
> asking if I want to save (i.e. upload) the file. I get nothing now. Any 
> ideas? Should I go back to 2.0.16?

This is fixed in CVS. I have a tarball of my CVS code at
http://www.gftp.org/gftp-test.tar.bz2.

Brian

Follow-Ups:
- Re: [gftp] Help. 2.0.17 won't save edited file on remote
  - From: "Adams-Blake Co." <acanton@adams-blake.net>

References:
- [gftp] Help. 2.0.17 won't save edited file on remote
  - From: "Adams-Blake Co." <acanton@adams-blake.net>

Prev by Author: Re: [gftp] gftp + ssh + rtf + FreeBSD
Next by Author: Re: [gftp] gftp + ssh + rtf + FreeBSD
Previous by thread: [gftp] Help. 2.0.17 won't save edited file on remote
Next by thread: Re: [gftp] Help. 2.0.17 won't save edited file on remote
Index(es):
- Author
- Thread