Bug 333214 - kate sets executable bit upon save for php, javascript and html files mounted over sshfs
Summary: kate sets executable bit upon save for php, javascript and html files mounted...
Status: RESOLVED DUPLICATE of bug 333577
Alias: None
Product: kate
Classification: Applications
Component: part (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-08 21:50 UTC by aleha
Modified: 2014-10-29 19:46 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description aleha 2014-04-08 21:50:22 UTC 
Kate and also Kdevelop set the execute bit for php and html files upon save, on an sshfs mounted directory.
This behavior occurs only when saving a file and not when creating one, although if you create a file, make some more changes and then save it later, then it still sets it as executable.
This didn't happen with okteta.

Reproducible: Always

Steps to Reproduce:
1. Mount a dir over sshfs with default opts
2. Open an existing php or html file
3. Make some changes and save it
Comment 1 Sven Brauch 2014-04-08 21:53:54 UTC 
I can reproduce this bug as described.
Comment 2 Dominik Haumann 2014-04-29 11:26:54 UTC 
@David: I have not debugged this, but Kate uses KSaveFile while Okteta does not. Might this be an issue in KSaveFile?
Comment 3 Boris Egorov 2014-10-24 16:46:26 UTC 
(In reply to Dominik Haumann from comment #2)
> @David: I have not debugged this, but Kate uses KSaveFile while Okteta does
> not. Might this be an issue in KSaveFile?

It is KSaveFile, I've debugged it today. Permissions changes after KSaveFile::finalize().

Duplicate of https://bugs.kde.org/show_bug.cgi?id=333577
Comment 4 Dominik Haumann 2014-10-29 19:46:27 UTC 
Thanks for this info, then let's mark it as such. Well, this issue should then be fixed in KSaveFile and QSaveFile in Qt5 respectively...

*** This bug has been marked as a duplicate of bug 333577 ***