Author Topic: Git blame editor window should be RO  (Read 177 times)

jporkkahtc

  • Senior Community Member
  • Posts: 2615
  • Hero Points: 210
  • Text
Git blame editor window should be RO
« on: September 26, 2022, 07:16:09 pm »
Since the title bar still shows the original filename, it would be best for this buffer to be RO to avoid accidentally editing and losing changes.

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2798
  • Hero Points: 146
Re: Git blame editor window should be RO
« Reply #1 on: September 26, 2022, 07:29:07 pm »
I don't see how it can get out of svc_get_annotated_buffer without turning it read only, unless it fails to get the file.

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2798
  • Hero Points: 146
Re: Git blame editor window should be RO
« Reply #2 on: September 27, 2022, 12:41:42 pm »
Can you send us your user.cfg.xml?

jporkkahtc

  • Senior Community Member
  • Posts: 2615
  • Hero Points: 210
  • Text
Re: Git blame editor window should be RO
« Reply #3 on: September 27, 2022, 10:21:30 pm »
Well, I cannot repro that problem now.

However, I found something else :-)

#1: Do Git-blame, then Ctrl-Z (undo).
The buffer is now empty

#2: Do Git-blame, then Save
It complains the file is RO and prompts with "do you wish to: ..."
Of course, the file doesn't really exist.
When you select "Make file writable", then hit OK:
---------------------------
SlickEdit Pro
---------------------------
Unable to update read only attribute for: Untitled 2022-09-27 1517
---------------------------
OK   
---------------------------