oh, now I see where is the confusion. It is weird, but from the beginning<br>
we were talking about different things. You assumed that after timestamp<br>
change we were getting a nice info bar, and still we could be working with<br>
the content. It would be great! Then it would be really insane even to<br>
think about "save as" button or Ignore instead of Cancel.<br>
However,  I was talking about locked content and confusing Cancel button.<br>
So, most probably it  is a bug.<br>
Just one more fact.  When the bar is on and the content is locked, I still<br>
can use Save As from the file menu. Then obviously the bar stays the same.<br>
But, the buffer becomes "dirty" and the content becomes editable.<br>
<br>
On Wed, Oct 31, 2018, 10:33 Matthew Brush <notifications@github.com wrote:<br>
<br>
> Hmmm, the cursor still works, but text entry doesn't. Not sure why.<br>
><br>
> The document is locked/read-only when the infobar is shown. IIRC this was<br>
> discussed quite a bit back when those infobar changes were being developed.<br>
><br>
> —<br>
> You are receiving this because you modified the open/close state.<br>
> Reply to this email directly, view it on GitHub<br>
> <https://github.com/geany/geany/issues/1885#issuecomment-434710199>, or mute<br>
> the thread<br>
> <https://github.com/notifications/unsubscribe-auth/Al5v5GxiFkUKbMr2pcC76cGcl2tclR4mks5uqbTRgaJpZM4UsYx0><br>
> .<br>
><br>


<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/1885#issuecomment-434717429">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ50WsblNJa0fzprVQA0J5RD9nf1dks5uqbl2gaJpZM4UsYx0">mute the thread</a>.<img src="https://github.com/notifications/beacon/ABDrJzAzEZXTWYe75OXMLjXuGHBR0B35ks5uqbl2gaJpZM4UsYx0.gif" height="1" width="1" alt="" /></p>
<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://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/geany/geany"}},"updates":{"snippets":[{"icon":"PERSON","message":"@dyura in #1885: oh, now I see where is the confusion. It is weird, but from the beginning\nwe were talking about different things. You assumed that after timestamp\nchange we were getting a nice info bar, and still we could be working with\nthe content. It would be great! Then it would be really insane even to\nthink about \"save as\" button or Ignore instead of Cancel.\nHowever,  I was talking about locked content and confusing Cancel button.\nSo, most probably it  is a bug.\nJust one more fact.  When the bar is on and the content is locked, I still\ncan use Save As from the file menu. Then obviously the bar stays the same.\nBut, the buffer becomes \"dirty\" and the content becomes editable.\n\nOn Wed, Oct 31, 2018, 10:33 Matthew Brush \u003cnotifications@github.com wrote:\n\n\u003e Hmmm, the cursor still works, but text entry doesn't. Not sure why.\n\u003e\n\u003e The document is locked/read-only when the infobar is shown. IIRC this was\n\u003e discussed quite a bit back when those infobar changes were being developed.\n\u003e\n\u003e —\n\u003e You are receiving this because you modified the open/close state.\n\u003e Reply to this email directly, view it on GitHub\n\u003e \u003chttps://github.com/geany/geany/issues/1885#issuecomment-434710199\u003e, or mute\n\u003e the thread\n\u003e \u003chttps://github.com/notifications/unsubscribe-auth/Al5v5GxiFkUKbMr2pcC76cGcl2tclR4mks5uqbTRgaJpZM4UsYx0\u003e\n\u003e .\n\u003e\n"}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/1885#issuecomment-434717429"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/geany/geany/issues/1885#issuecomment-434717429",
"url": "https://github.com/geany/geany/issues/1885#issuecomment-434717429",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
},
{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"hideOriginalBody": "false",
"originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB",
"title": "Re: [geany/geany] An insufficient behavior when an open file was updated outside Geany (#1885)",
"sections": [
{
"text": "",
"activityTitle": "**dyura**",
"activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png",
"activitySubtitle": "@dyura",
"facts": [

]
}
],
"potentialAction": [
{
"name": "Add a comment",
"@type": "ActionCard",
"inputs": [
{
"isMultiLine": true,
"@type": "TextInput",
"id": "IssueComment",
"isRequired": false
}
],
"actions": [
{
"name": "Comment",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueComment\",\n\"repositoryFullName\": \"geany/geany\",\n\"issueId\": 1885,\n\"IssueComment\": \"{{IssueComment.value}}\"\n}"
}
]
},
{
"name": "Close issue",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueClose\",\n\"repositoryFullName\": \"geany/geany\",\n\"issueId\": 1885\n}"
},
{
"targets": [
{
"os": "default",
"uri": "https://github.com/geany/geany/issues/1885#issuecomment-434717429"
}
],
"@type": "OpenUri",
"name": "View on GitHub"
},
{
"name": "Unsubscribe",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"MuteNotification\",\n\"threadId\": 347180148\n}"
}
],
"themeColor": "26292E"
}
]</script>