| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
* Refer to new editor as "modern editor", and fix several places where
it was still called the "experimental new editor".
* Refer to old editor as "legacy editor".
* Remove link to "learn more about the New Editor", as the aka has not
been maintained and there is no useful documentation page right now.
* Change the "Open C# files in the New Editor" preference to read
"Use the legacy text editor where available (not recommended)", and
invert its effect. Move this preference to the end of its section.
In an upcoming commit, this will be the only way to enable the legacy
editor in preferences, and it will only work for file types that
explicitly maintain legacy editor support.
Users will continue to be able to use the "Open With" menu to pick the
editor they prefer at that time.
|
|
|
|
See https://github.com/dotnet/roslyn/pull/36584
|
|
|
|
|
|
|
|
|
|
|
|
https://devdiv.visualstudio.com/DevDiv/_workitems/edit/807807
The former implementation did not only respect the Indent/TabSize setting correcttly - it did overwrite configuration properties with policy style settings.
|
|
Use the new completion in the new editor and old completion in the old editor. We have to hack into Roslyn's IAsyncCompletionService to set the private field accordingly because they don't support setting it per view.
See related https://github.com/dotnet/roslyn/issues/33807
|
|
The old editor apparently still attempts to do something when WrapLines
returned true. When we introduced word wrapping in the new editor, the
property changed from a boolean to a flags enum. For compatibility we
plumbed the old WrapLines property through to the new WordWrapStyle
property. This was a bad assumption and introduced VSTS #801818.
Apparently the old editor may have at some point tried to implement word
wrapping and has been respecting the preference all along but it has
been dormant for 6 years since it was disabled in the preferences UI.
The deprecated WrapLines property will again always return false, fully
disconnecting it from the preferences UI.
https://devdiv.visualstudio.com/DevDiv/_workitems/edit/801818
|
|
https://devdiv.visualstudio.com/DevDiv/_workitems/edit/790220
|
|
When toggling the new editor on or off, if there are files open in
the workbench, offer to close them all.
Hook up the preview commands for disabling the editor, learning more
about the new editor, and reporting issues.
|
|
|
|
Obsolete old editor API
|
|
|
|
|
|
All services are now referenced from the IdeServices class
|
|
|
|
The new IdeServices class has references to the core IDE services.
Revamped the IDE initialization code. The UI loop is started earlier and
that allows starting the services asynchronously.
Code that previously was referencing static service classes or services
available in IdeApp now reference IdeServices.
|
|
Proxy the boolean WrapLines through it and deprecate that property.
|
|
preferences (#136)
* Port over some editor options
* Respect FollowCodingConventions option
* [Preferences] Remove some obsolete preferences
* [OldEditor] Remove now unneeded hack due to option propagation
|
|
This reverts commit fca46fbf97af1d49755116cae1bdd58bcdab3873.
|
|
|
|
|
|
|
|
|
|
option panel.
The options are taken by the roslyn formatting engine it's not needed
anymore on our side to check on the fly formatting options. With the
exception of the paste formatting which needs to be checked.
|
|
Mac using .NET Core Rules
https://devdiv.visualstudio.com/DevDiv/_workitems/edit/635513
VS.NET allows the code diagnostics & actions to be altered in behavior
with editconfig files. Unfortunately we've a code issue panel settings
overriding these options in a later stage where it can't be decided if
the option setting originated in .editconfig or not. And there were
plenty of code generation related settings we didn't support. So I
decided to remove the code issue panel completely and use the vs.net
panel directly.
It's using a MVVM approach therefore I ported some infrastructure from
the vs.net part of roslyn and replaced the WPF part with XWT - now
it's possible to transfer more controls over to monodevelop. Maybe
with a conversion script (translation aprroaches are done differently
- this needs to be converted to gettext calls).
The name violation rules furthermore required the implementation of
the ISymbolRenamedCodeActionOperationFactoryWorkspaceService.
.editconfig support is now working as intended and we support now all
the style & severity settings VS.NET has to offer. OptionSet
persistance will be done in a different commit.
|
|
We haven't deprecated policies yet, and code still uses it
|
|
modifying editorconfig
+ lowers the amount of objects created.
|
|
This means that the change to the default values will now
affect existing users.
|
|
https://github.com/mono/monodevelop/issues/4566
Should match the VS.NET default options.
|
|
|
|
|
|
option.
|
|
|
|
(as per VS)'
The line separator service is a roslyn feature. When EditorFeatures is
available we can directly plug it in.
|
|
with option-arrow isn't Mac-like'
It's fixed by changing the defaults.
|
|
Behavior -> Insert matching brace'
|
|
This reverts commit c53c7ebaa60e15691cbb453a9029b841b9325287.
|
|
This reverts commit 5d4710a9910833d50360e2f9df519003db109e9f.
|
|
|
|
|
|
|
|
|
|
deleting a whole line'
|
|
This option doesn't really make any sense anymore and causes unwanted
side effects. It was used for disabeling compiler errors in older
versions.
The compiler errors are now shown as message bubbles which can be
disabled separately.
This here was now used for the on the fly errors and if that's
disabled the fix system wouldn't be usable anymore.
|
