[Github-comments] [geany/geany] An insufficient behavior when an open file was updated outside Geany (#1885)

dyura notifications at xxxxx
Wed Oct 31 14:53:42 UTC 2018


oh, now I see where is the confusion. It is weird, but from the beginning
we were talking about different things. You assumed that after timestamp
change we were getting a nice info bar, and still we could be working with
the content. It would be great! Then it would be really insane even to
think about "save as" button or Ignore instead of Cancel.
However,  I was talking about locked content and confusing Cancel button.
So, most probably it  is a bug.
Just one more fact.  When the bar is on and the content is locked, I still
can use Save As from the file menu. Then obviously the bar stays the same.
But, the buffer becomes "dirty" and the content becomes editable.

On Wed, Oct 31, 2018, 10:33 Matthew Brush <notifications at github.com wrote:

> Hmmm, the cursor still works, but text entry doesn't. Not sure why.
>
> The document is locked/read-only when the infobar is shown. IIRC this was
> discussed quite a bit back when those infobar changes were being developed.
>
>> You are receiving this because you modified the open/close state.
> Reply to this email directly, view it on GitHub
> <https://github.com/geany/geany/issues/1885#issuecomment-434710199>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/Al5v5GxiFkUKbMr2pcC76cGcl2tclR4mks5uqbTRgaJpZM4UsYx0>
> .
>


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1885#issuecomment-434717429
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20181031/91dddb3a/attachment.html>


More information about the Github-comments mailing list