<p>I found more about this. The temporary file written with the methods 'use_atomic_file_saving' and 'use_gio_unsafe_file_saving' is named like this : <code>/tmp/archivemount_.goutputstream-0HQLEZ_EWe3lj</code>  and it stops there.</p>
<p>When I do a move on the command line <code>mv /tmp/archivemount_.goutputstream-0HQLEZ_EWe3lj /mnt/existingfile.txt</code> it is renamed to something like <code>/tmp/archivemount_existingfile.txt_L801KG</code> and the changed content is accessible from the mountpoint.</p>
<p>When it is written with the method programmed in geany itself, it is immediataly named like this: <code>/tmp/archivemount_existingfile.txt_SFb30S</code> and the changed content is immediately accessible from the mountpoint, without needing my intervention to move explicitely</p>
<p>Of course the <code>/tmp/archivemount_.goutputstream-...</code> gives me no indication of what name it should be, if there are many of these files, and the command-line move procedure is therefor not practical.</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/issues/1774#issuecomment-366543980">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ-UGGa-PKeJMlqtEc0mJPvyrf-mPks5tWIS-gaJpZM4SJpbt">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJz267eh64PDJT_wrkWew7dpwTT1qks5tWIS-gaJpZM4SJpbt.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/issues/1774#issuecomment-366543980"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue 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":"@db-inf in #1774: I found more about this. The temporary file written with the methods 'use_atomic_file_saving' and 'use_gio_unsafe_file_saving' is named like this : `/tmp/archivemount_.goutputstream-0HQLEZ_EWe3lj`  and it stops there.\r\n\r\nWhen I do a move on the command line `mv /tmp/archivemount_.goutputstream-0HQLEZ_EWe3lj /mnt/existingfile.txt` it is renamed to something like `/tmp/archivemount_existingfile.txt_L801KG` and the changed content is accessible from the mountpoint.\r\n\r\nWhen it is written with the method programmed in geany itself, it is immediataly named like this: `/tmp/archivemount_existingfile.txt_SFb30S` and the changed content is immediately accessible from the mountpoint, without needing my intervention to move explicitely\r\n\r\nOf course the `/tmp/archivemount_.goutputstream-...` gives me no indication of what name it should be, if there are many of these files, and the command-line move procedure is therefor not practical."}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/1774#issuecomment-366543980"}}}</script>