Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Invisible characters is an all-or-nothing option now. Before 4.0 I had my editor configured to show only tabs, since I use them for indentation and in contrast to that, spaces for alignment. In effect this also gave me indentation guides for free.
The situation now is pretty distracting, especially with all the dots where a space character is. With "remove trailing whitespace" and the automatic line-ending conversion in place, I personally don't see much benefit in displaying spaces, line-breaks and the EOF at all: We know where they are, when we know where the tabs are!
I am using a plugin for the D programming language which recently started to add tabs for alignment. So I really need to see what's going on and correct my code before committing it.
Was more a test - the new option was all - nothing - selection :) - personally I thought that show in selection, but all was a good tradeoff between all worlds.
Glad to hear that. I hoped you just removed that 'feature' because you saw no use case for it and wanted to stream line the UI. By the way... maybe some of the 107 syntax highlighter options are too much and could be refactored. Some of them also seem to have become defunct(?) over the course of development. Yet I cannot find the "invisible character color" there. :)
Anyway I think the team did a good job so far with that IDE. It has reached a point where I use it every day and don't miss anything from older projects like Eclipse.
I think all syntax colors are functional atm - I've just reworked the whole color system :)
- and still doing so :( ... will take some time.
I've merged ours with the vs.net therefore it's the superset of the vs.net and the monodevelop colors.
The inivisible character color got removed because the invisible characters use the color from the span - invisible characters in a string use different colors than in a comment for example. I'm open for suggestions about that.
In fact eclipse is newer - the IDE was first created in 2000 as windows project :). (But didn't get a 40 million funding for v1 :( )
No, I have no suggestions. I just wanted to dim the color some more while I was at it, because my TFT has a high gamma and the dash is so big. Is it the human aversion against change or was » a better symbol?
I'm surprised the IDE is 13 years old. Well then... it still feels modern! What fascinates me about Eclipse is the extensibility of course and the synergy with Java. The IDE helps with Java's verbosity, by giving you shortcuts and Java helps the IDE by being a simple, easy to analyze language. MonoDevelop's AddIn manager is quite nice at the moment as well. I don't know how it would work with dependencies, but it currently has everything in one place and categorized with only few buttons. I like that.
The line draws faster than the glyph and is a bit better when the tab size changes.
I think our IDE is as extensible as Eclipse ... but doesn't get that much 3rd party support :( ... the .NET world is really locked in VS.NET ... unfortunately.
That java is easier to analyze is true - we try it with c# as well :) - just turn on source code analysis in the options and you'll see it.