All CLA requirements met.

Hi,

Thanks for the PR. However we usually prefer to first start a discussion about the implementation before going ahead and doing the whole thing.
Your approach seems to touch a lot of editor areas, from the editor core to the snippet controller.
Due to that I am not comfortable merging in this PR. I think the right approach would be just to make the FileEditorInput readonly from the workbench (I am not even sure if that is possible atm, I leave the exploration up to you).

@alexandrudima in case you like the editor changes feel free to review them
I am assinging this to the backlog

The code editor already has a readOnly option that works 100% correctly. See here

Simply put, the workbench must instantiate all editors and set their option to use readOnly: true to implement this, but there should be no changes inside src/vs/editor since the code editor already supports read only.

The code editor already has a readOnly option that works 100% correctly. See here

Simply put, the workbench must instantiate all editors and set their option to use readOnly: true to implement this, but there should be no changes inside src/vs/editor since the code editor already supports read only.

Dear @alexdima: Could you possibly come up with a code example, how to implement this for @holeguma or other potential contributors (or maybe implement it yourself), as this functionality has been on the wishlist for many for quite some time? ( #4873, April 2016, 55 comments ).

@henrik-jensen My feedback was specific to this PR. The code editor widget already has support to be read only, through the readOnly option. This option is used by the workbench when opening index files from the git viewlet, or when opening files provided by a readonly FS provider.