I'm often work with FTP and remote files with KWrite from kde 3.5.

With your new "Functionality" when i change some file on ftp, i should close it to affect changes and see the result (in browser, for example).

That makes work with a number of remote files just IMPOSSIBLE.

And in openSuSE there's only new kwrite with this stupid function


* Riki_tiki_tavi goes to find ways to return old kwrite from kde 3.5

Hi,

you should file a bug report. Does save not work?

However, i'll forward this to the mailing list.

-- Panke

No! The save function is working, but very complicated.

In 3.5 version the process was simple: i make changes, press Ctrl + S and the new version of the file is being uploaded to FTP server automatically.

Now, in 4-th version when i make some changes, press Ctrl + S, and then i should close editor window, and press "Yes" on file upload dialog and then open it again (if i wish to continue editing).

So imagine, when you write (or debug) some script on a remote server and make changes every 2-3 minutes, how many times you should close/open it, and how many time it will take?


I suppose there should be an option to disable this new "advanced save function"

Riki_tiki_tavi wrote:In 3.5 version the process was simple: i make changes, press Ctrl + S and the new version of the file is being uploaded to FTP server automatically.

Now, in 4-th version when i make some changes, press Ctrl + S, and then i should close editor window, and press "Yes" on file upload dialog and then open it again (if i wish to continue editing).

I've just tried with KWrite4 trunk and it works exactly as you described for KDE3: saving back to the ftp happens automatically for me, and there is no need to close the kwrite instance.

Edit:

How are you opening your ftp file in kwrite? I remember in KDE3 that opening it in some way - maybe right-click in a file manager and "open with kwrite" - would give the "incorrect" saving procedure like you described, but dragging the ftp file from the file manager onto a blank kwrite window would work correctly.

GeneralZod wrote:How are you opening your ftp file in kwrite? I remember in KDE3 that opening it in some way - maybe right-click in a file manager and "open with kwrite" - would give the "incorrect" saving procedure like you described, but dragging the ftp file from the file manager onto a blank kwrite window would work correctly.

I open them with dolphin. Dragging works fine, thanks for advice.

Looks like it's a dolphin *feature*

Oh i'm so sorry, my lovely kwrite
Thanks for help

Edit:

Btw, Konqueror still works normally with ftp. I've hated Dolphin from a first sight

Riki_tiki_tavi wrote:I open them with dolphin. Dragging works fine, thanks for advice.

Looks like it's a dolphin *feature*

No, it's definitely not a "feature", and certainly not one that Dolphin has deliberately introduced (as I mentioned, I had the same thing with KDE3 + Konqueror). If I were to guess, I'd say that whatever subsystem is responsible for launching apps with a URL is not aware that kwrite can handle ftp:// urls, and so is downloading the file to a temporary location where kwrite can edit it locally and then re-uploading when it detects that kwrite has terminated. i.e. - it's a bug, IMO.

I edit remote files on KDE 4 a lot, using Kate and accessing the files over ssh (not through the command line, I added a network folder in Dolphin and chose ssh as the protocol). My experience matches what you describe yours was in KDE 3. It is nearly impossible to notice that I'm editing a remote file and behaves almost exactly like if I were editing a local one. I've never tried a remote FTP folder, so I don't know if it works for me or not. You might try accessing the files through ssh if you can and see if you have the same experience.