<blockquote>
<p>I completely forgot about metadata, with this implementation all files given new names are new files, so they have new file metadata. Owner and permissions may change, but specifically the execute bit won't be carried over from the original file. So shell scripts or Python scripts or similar will no longer run until the user manually re-adds the execute.</p>
</blockquote>

<p>That was actually the difference that I was trying to realize back then.  Yeah, looks like the feature should remain. </p>

<blockquote>
<p>Sorry <a href="https://github.com/konsolebox" class="user-mention">@konsolebox</a> we probably should stick to the existing implementation.</p>
</blockquote>

<p>It's ok, this was just a side-concern and it wasn't difficult to make.  I'm actually happy with the ideas I'm hearing about this.</p>

<p>Going back to the original issues, do you still think we shouldn't abort saving changes when a rename fails?</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/geany/geany/pull/1190#issuecomment-242008806">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ9W-cchR2YFtLW1Q_674yguLNIN4ks5qjBCjgaJpZM4JrfCw">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJ26sX3wifHD4FcriajWN-0s5wqJAks5qjBCjgaJpZM4JrfCw.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/geany/geany/pull/1190#issuecomment-242008806"></link>
  <meta itemprop="name" content="View Pull Request"></meta>
</div>
<meta itemprop="description" content="View this Pull Request on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/geany/geany","title":"geany/geany","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/geany/geany"}},"updates":{"snippets":[{"icon":"PERSON","message":"@konsolebox in #1190: \u003e I completely forgot about metadata, with this implementation all files given new names are new files, so they have new file metadata. Owner and permissions may change, but specifically the execute bit won't be carried over from the original file. So shell scripts or Python scripts or similar will no longer run until the user manually re-adds the execute.\r\n\r\nThat was actually the difference that I was trying to realize back then.  Yeah, looks like the feature should remain. \r\n\r\n\u003e Sorry @konsolebox we probably should stick to the existing implementation.\r\n\r\nIt's ok, this was just a side-concern and it wasn't difficult to make.  I'm actually happy with the ideas I'm hearing about this.\r\n\r\nGoing back to the original issues, do you still think we shouldn't abort saving changes when a rename fails?"}],"action":{"name":"View Pull Request","url":"https://github.com/geany/geany/pull/1190#issuecomment-242008806"}}}</script>