wmjordan / codist Goto Github PK

It would be nice if it was possible to toggle the Bar's visibility with a modifier key (similar to how it is done with Tooltips). So that the bar will only be shown if there is a selection AND modifier key (say Ctrl) was pressed.

What I find is that the Smart Bar often gets in the way when doing mouse manipulations with the text.

Also, that would probably "solve" the crashes I reported and all related possible future crashes, since it would no longer be displayed automatically on selection but instead also require a key toggle.

The line top margin and bottom margin setting will be reset after loading predefined themes.

The default text color in Super Quick Info is black.
It is hard to read when using the Dark theme in VS.
It is preferable if the text color is theme-awared.

We are using Codist with Visual Studio 15.8.0 and VS Live Share v0.3.535.25078.
Codist works fine in Visual Studio of the computer "Sharing" the solution, but any participants who joins the "Sharing Session" and is running Codist on their computer does not get any of the syntax highlighting, quick info, smart bar, or any other features of Codist. The Codist extension is enabled and configured correctly because it works fine for stand alone solutions (without VS Live Share).

I don't know if this is an issue with VS Live Share, or if there is some kind of change in Codist which will make it work?
Any insight or help is very much appreciated.

I really like how the Super Quick Info tooltip displays what assembly a particular member or type comes from.

That gave me an idea that may be you can add a new kind of syntax highlighting style that would apply to either all user code identifiers (types and members) and/or all non-user code identifiers. I am not sure yet what the best way to approach this will be in terms of the actual style possibilities, however, for a start, if you could just expose those 2 categories for syntax highlighting that would be great!

And one more smallish suggestion: it would be nice if you could add another category for #region and #end region directives (for the whole line). Right now I am using separate extension to highlight those.

PS Love your latest edition that lets you preview styles directly in the list! Very handy!

Sometimes during editing the document, the syntax parse results could generate incomplete class declarations, which were consequently marked on the scrollbar margin.
Afterwards, those markers were remained there and no eliminated when we fixed the editing source code.

After upgrading VS to 15.8, the Click and Go and other Quick Info overrides no longer worked for the Quick Info has changed its underlying controls.

Perhaps you can find a way to display useful statistics in the NavBar (either directly on the headers/titles, or in the tooltips, or some other way):

• number of lines that make up a member (if more than 1)
• number and kinds of members in a type / region
• number of types in a namespace

Somewhere else it might be useful too to include:

• number of lines with code (in a file / type)
• number of empty/blank lines (in a file / type)
• number of comment / xml-doc-comment lines (in a file / type)

This is a low priority thing - just something to maybe integrate eventually in a useful way into the extension.

Hello,
I have finally managed to compile the extension from the source code today to the latest provided version.
The improvements are much appreciated!

While using the latest version, I have noticed that inherited documentation doesn't work.

My apologies if I'm doing something wrong.

Thank you for the excellent extension! Great new features lately!

I think another very useful feature would be a simple dockable window that shows the outline of the currently opened .cs file: classes/structs/enums/delegates, regions, methods/properties, etc. You can grow this feature over time, adding support for sorting, reordering, etc.

Perhaps you can start with just a read-only mode, click-navigation, and automatic sync with the active document. Also, it would be great if you can emphasize speed, because while there are other extensions with this feature, they are all very slow, so not practical to use. So, if you can implement this feature, at least on the basic level that is also fast, it would be awesome!

PS: Love your modular approach where you can toggle each individual feature!

The Selection info feature was disabled in the C# Interactive window due to the snapshot mismatch.
Anyone knows how to fix this?

The workaround at this moment is typing something in the document to refresh the syntax highlight.

Hello, I absolutely love your extension and I use it for the enhanced tooltips (Super Quick Info), but after installing it, I have realized that the Supercharger "magic comments" aren't working anymore and those are extremely important for me as well.

The only way to make Supercharger's magic comments work again is to completely disable the Codist extension, disabling its features on the General page doesn't have any effect.

The Codist comments formatting doesn't work either when Supercharger is enabled (even if magic comments are disabled), so using the Codist comment formatting as a replacement isn't an option.

I'll have to prioritize Supercharger because losing all the functionality that depends on it (all its other components/features) is much worse than not having enhanced QuickInfo tooltips. Hope this can be solved, thank you!

Supercharger links:
http://supercharger.tools/#sectionMagicComments
https://marketplace.visualstudio.com/items?itemName=MichaelKissBG8.Supercharger

Currently it is possible to override the default Quick Info, is it possible to override the completion tooltip?

It would be nice if the parenthesis in the (type)variable cast operator would be colored differently (i.e. blue by default) if the type inside the parenthesis is written as a language keyword (all lower case, i.e. bool) as opposed to being written-out fully as type (i.e. Boolean). Right now, in all cases the latter formatting is assumed.

So, is it possible to have this:

turned into this (ignore the bold style of the parenthesis):

I have noticed that whenever I am using Alt+[Letter] keyboard shortcuts in VS (Alt+D to duplicate line, or Alt+F, Alt+M to filter Intellisense completion list) NavBar gets focus and editor loses focus, causing unintended navigation. Using Codist 4.1.0.2718.

Drag and drop/Rearrange items in Navi Bar:

• Within the same type
• To another code file within the partial type
• To another type within the same code file
• Copy/Delete/Duplicate the member
• Reformat the member

It would be nice to add the following improvements to Syntax Highlighting:

1. Control Flow Keyword option should include if, else if, else, switch, case, for, yield, break, foreach, try, catch, finally. So these get appropriate formatting as well.

2. Add "Local Variable" category for identifiers declared within method bodies, i.e. locals, so these can be colored/formatted differently and thus distinguished from say method parameters, or local fields.

Thank you.

When we click into methods, long property declarations, types, etc. the range of them could be drawn on the scrollbar margin.

From K. L. Carter Sr.:

Would be nice if there was a turn off checkbox for just syntax highlighting just like the box to turn off the whole Codist.

A new configuration section to customize markers displayed on the scrollbar margin.

Super Quick Info is well executed and extremely useful, thank you for such a great tool.

Sometimes information in the Quick Info tooltip can be overwhelming with a lot of rows displaying different kinds of information, so it would be great to have an option that allows separating sections using lines or dotted lines (and maybe even section names, similarly to the group box control).

I think it would make the Super Quick Info tooltip more aesthetically pleasing and would help the user to visually separate different sections of it.

Thank you!

The markers were not updated until the document were reopened.

Can someone tell me how to apply VS themes onto the Context Menus?

Super Quick info already does an excellent job as it is, but I fell like the XML Doc description can be further improved by adding a couple more features to it.

Considering the following code: https://www.servicehusky.com/textbin/WTXjcib1
Results in the following Super Quick Info tooltip: https://imgur.com/bwPgMDu

As you can see, the remarks aren't displayed in the tooltip. however, the exceptions are being displayed, but not their documentation.

So I think having these additions to the Super Quick Info would increase its usefulness.

Thank you!

Enum Value and Const now has same style, maybe should has different style?

It would be nice if Compiler/Analyzer errors/warnings/suggestions would be somehow separated from the rest of the text (such as member description), for example by having an appropriate icon (cross, exclamation, tip) to the left of the message as I suggest on the screenshot:

VS will appear as if it is running into an infinite deadlock, consuming a lot of CPU resources, sometimes when adjusting settings in the syntax highlight style options pages, since Codist version 3.8.

Thank you for the update and the theme related improvements, however there are still some lingering issues.

1. the code tag still doesn't highlight code and it is creating new line feeds before and after it (maybe the line feeds are intended, I'm not sure); it's not a big problem really, but the way it acts is unintuitive;
2. the remarks tag content is still not being displayed;

3. the conflict with Supercharger's magic comments still exists and I doubt Supercharger will do anything about it given the fact that they aren't responding back, so at least for me personally I can't use this version and I'll have to roll back to the one you've provided to me a few days ago;

Using VS 2017 15.8.1 and Codist 3.05.0.1702:

When I navigate to source for System.IO.FileInfo (click Yes in VS to confirm decompiling sources), and then from the opened decompiled FileInfo document I then navigate to source of System.IO.FileSystemEntry I get a crash: NullReferenceException in Codist.dll:

 at Codist.CodeAnalysisHelper.GetDocument(Workspace workspace, SnapshotSpan span) in E:\Codes\Open Source Projects\Codist\Codist\Helpers\CodeAnalysisHelper.cs:line 26
 at Codist.SmartBars.CSharpSmartBar.UpdateSemanticModel() in E:\Codes\Open Source Projects\Codist\Codist\SmartBars\CSharpSmartBar.cs:line 0
 at Codist.SmartBars.CSharpSmartBar.AddCommands() in E:\Codes\Open Source Projects\Codist\Codist\SmartBars\CSharpSmartBar.cs:line 34
 at Codist.SmartBars.SmartBar.CreateToolBar(Object dummy) in E:\Codes\Open Source Projects\Codist\Codist\SmartBars\SmartBar.cs:line 159
 at Codist.SmartBars.SmartBar.<CreateToolBar>b__26_0() in E:\Codes\Open Source Projects\Codist\Codist\SmartBars\SmartBar.cs:line 145
 at System.Windows.Threading.DispatcherOperation.InvokeDelegateCore()
 at System.Windows.Threading.DispatcherOperation.InvokeImpl()
--- End of stack trace from previous location where exception was thrown ---
 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
 at System.Windows.Threading.DispatcherOperation.Wait(TimeSpan timeout)
 at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherOperation operation, CancellationToken cancellationToken, TimeSpan timeout)
 at System.Windows.Threading.Dispatcher.Invoke(Action callback, DispatcherPriority priority, CancellationToken cancellationToken, TimeSpan timeout)
 at System.Windows.Threading.Dispatcher.Invoke(Action callback)
 at Codist.SmartBars.SmartBar.CreateToolBar(Object dummy) in E:\Codes\Open Source Projects\Codist\Codist\SmartBars\SmartBar.cs:line 145
 at System.Threading.TimerQueueTimer.CallCallbackInContext(Object state)
 at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
 at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
 at System.Threading.TimerQueueTimer.CallCallback()
 at System.Threading.TimerQueueTimer.Fire()
 at System.Threading.TimerQueue.FireNextTimers()
 at System.Threading.TimerQueue.AppDomainTimerCallback()

Multiline attribute notations are not completely highlighted.
Only the first line is highlighted.
For instance, in the following code, SystemDataAccess = SystemDataAccessKind.None, and DataAccess = DataAccessKind.None)] would not have the Attribute Notation style.

[SqlFunction (IsDeterministic = true,
	SystemDataAccess = SystemDataAccessKind.None,
	DataAccess = DataAccessKind.None)]
[return: SqlFacet (MaxSize = __MaxSize)]
public static SqlString Base64Encode (
	[SqlFacet (MaxSize = __MaxSize)] SqlString text
	) {
	if (text.IsNull) {
		return text;
	}
	return new SqlString (Convert.ToBase64String (System.Text.Encoding.UTF8.GetBytes (text.Value)));
}

Since I just recently started using Codist, and especially the Super Quick Info, I discover a lot of its beauties, but also a couple discrepancies from a visual perspective.

I make heavy use of XML documentation and its tags, and one of those tags is the c tag which is used to put emphasis on certain parts of the documentation comment, the problem is that text in the code tag is being displayed as bold white text over a nearly white background which makes it very hard to read. Ideally, an option to allow the user how certain elements are displayed would be great (i.e. choosing font, font size, foreground/background color), but if not, at least something that's readable. Also notice that only the c tag is being rendered, while the code tag is ignored, and they should give the same result (the only difference being that one is for in-line and the other for multi-line).

My second remark would be in regard to enumerators, which I also use a lot. I very much appreciate the fact that Super Quick Info can display an enum's decimal, hexadecimal and binary values, the only visual issue with it is that the text boxes are not in line with the Visual Studio theme, making them stand out more than I'd like for my eyes:

The high contrast between the overall dark theme and extremely luminous elements like the way the code tag is displayed or the text boxes for the enum values are a discomfort for the eye, and I'm sure the same would apply to people using light themes.

If this can already be adjusted and I don't know how yet, my apologies.
These are my enabled modules in Codist:

Thanks again for this wonderful free product!

Other references:
https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/xmldoc/code-inline
https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/xmldoc/code

Perhaps you could further extend the Super Quick Info with information on whether the API is available in a particular framework (i.e. something like: ".Net Framework 4.5+, .Net Core 2.0+, ...").

The only feasible way to implement this that I see would probably to use ApisOf.Net website. Of course there will be some latency (not sure if it is even possible to update VS tooltip once it has been displayed), but at least it would be a much more convenient way to find out about framework differences than by going to the browser and manually looking for it.

Of course on top of that you can include additional info from the website, like popularity.

I was navigating to a member (Ctrl+Click), when VS crashed. Upon, investigation, I discovered this stack trace:

  mscorlib.dll!System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task task)	Unknown
  mscorlib.dll!System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task)	Unknown
  WindowsBase.dll!System.Windows.Threading.DispatcherOperation.Wait(System.TimeSpan timeout)	Unknown
  WindowsBase.dll!System.Windows.Threading.Dispatcher.InvokeImpl(System.Windows.Threading.DispatcherOperation operation, System.Threading.CancellationToken cancellationToken, System.TimeSpan timeout)	Unknown
  WindowsBase.dll!System.Windows.Threading.Dispatcher.Invoke(System.Action callback, System.Windows.Threading.DispatcherPriority priority, System.Threading.CancellationToken cancellationToken, System.TimeSpan timeout)	Unknown
  WindowsBase.dll!System.Windows.Threading.Dispatcher.Invoke(System.Action callback)	Unknown
  ==>  Codist.dll!Codist.SmartBars.SmartBar.CreateToolBar(object dummy)	Unknown
  mscorlib.dll!System.Threading.TimerQueueTimer.CallCallbackInContext(object state)	Unknown
  mscorlib.dll!System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state, bool preserveSyncCtx)	Unknown
  mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state, bool preserveSyncCtx)	Unknown
  mscorlib.dll!System.Threading.TimerQueueTimer.CallCallback()	Unknown
  mscorlib.dll!System.Threading.TimerQueueTimer.Fire()	Unknown
  mscorlib.dll!System.Threading.TimerQueue.FireNextTimers()	Unknown
  mscorlib.dll!System.Threading.TimerQueue.AppDomainTimerCallback()	Unknown

When I disabled the new floating Code Bar feature, it no longer crashed.

In a long document, typing #if would exclude the rest part of the code. It may lead to an exception on Snapshots.
Here's the stack trace:

System.ArgumentOutOfRangeException: Argument: span
    at Microsoft.VisualStudio.Text.SnapshotSpan..ctor(ITextSnapshot snapshot, Span span)
    at Microsoft.CodeAnalysis.Editor.Implementation.Classification.SyntacticClassificationTaggerProvider.TagComputer.AddClassifiedSpansForPreviousTree[TClassificationService](IClassificationDelegationService`1 delegationService, TClassificationService classificationService, SnapshotSpan span, ITextSnapshot lastSnapshot, Document lastDocument, List`1 classifiedSpans)
    at Microsoft.CodeAnalysis.Editor.Implementation.Classification.SyntacticClassificationTaggerProvider.TagComputer.AddClassifiedSpans[TClassificationService](IClassificationDelegationService`1 delegationService, TClassificationService classificationService, SnapshotSpan span, List`1 classifiedSpans)
    at Microsoft.CodeAnalysis.Editor.Implementation.Classification.SyntacticClassificationTaggerProvider.TagComputer.GetTags[TClassificationService](NormalizedSnapshotSpanCollection spans, HostLanguageServices languageServices, IClassificationDelegationService`1 delegationService)
    at Microsoft.CodeAnalysis.Editor.Implementation.Classification.SyntacticClassificationTaggerProvider.TagComputer.GetTags(NormalizedSnapshotSpanCollection spans)
    at Microsoft.CodeAnalysis.Editor.Implementation.Classification.SyntacticClassificationTaggerProvider.Tagger.GetTags(NormalizedSnapshotSpanCollection spans)
    at Microsoft.VisualStudio.Text.Tagging.Implementation.TagAggregator`1.<GetTagsForBuffer>d__39.MoveNext()
--

I hope this is a parody extension. 😢

Using your latest beta version, I just noticed that syntax highlighting seems to be completely wrong for cases when a method returns a value tuple with non-system (primitive) types. The colors are wrong, and there seems to be no user/non-user code distinction either...

Wrong:

Correct:

After your recent improvements in brace / parenthesis colorization, I got an idea that maybe you can also add visual "guidelines" that would highlight your current scope within the code (i.e. inside the if(...){...} it would highlight / draw a guideline under / over the whole current block).

Viasfora extension has this quite nice feature. The problem though is that the 2 colors are out of sync (obviously, since the guidelines are colored by one extension, and the braces by another - yours). See the screenshot below:

Ideally the guideline should be of the same color as the brace - i.e. blue, not violet.

So maybe you could add something similar to Codist, or perhaps even improve the presentation / sty;e slightly?

Thank you.

When the mouse cursor hovers on integer values, their hex value and binary format values could be displayed on QuickInfo.

the stack:

<record>1090</record>
<time>2018/05/30 13:58:26.724</time>
<type>Error</type>
<source>Editor or Editor Extension</source>
<description>System.AggregateException: One or more errors occurred. ---&gt; System.NullReferenceException: Object reference not set to an instance of an object.&#x000D;&#x000A;   at Codist.QuickInfo.CSharpQuickInfoSourceProvider.CSharpQuickInfo.AugmentQuickInfoSession(IQuickInfoSession session, IList`1 qiContent, ITrackingSpan&amp; applicableToSpan) in E:\Codes\Open Source Projects\Codist\Codist\QuickInfo\CSharpQuickInfoSourceProvider.cs:line 181&#x000D;&#x000A;   at Microsoft.VisualStudio.Language.Intellisense.Implementation.LegacyQuickInfoSource.AugmentQuickInfoSession(IAsyncQuickInfoSession session, IList`1 content, ITrackingSpan&amp; applicableToSpan)&#x000D;&#x000A;   at Microsoft.VisualStudio.Language.Intellisense.Implementation.AsyncQuickInfoSession.&lt;TryComputeContentFromLegacySourceAsync&gt;d__45.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at Microsoft.VisualStudio.Language.Intellisense.Implementation.AsyncQuickInfoSession.&lt;ComputeSourceContentAsync&gt;d__44.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)&#x000D;&#x000A;   --- End of inner exception stack trace ---&#x000D;&#x000A;---&gt; (Inner Exception #0) System.NullReferenceException: Object reference not set to an instance of an object.&#x000D;&#x000A;   at Codist.QuickInfo.CSharpQuickInfoSourceProvider.CSharpQuickInfo.AugmentQuickInfoSession(IQuickInfoSession session, IList`1 qiContent, ITrackingSpan&amp; applicableToSpan) in E:\Codes\Open Source Projects\Codist\Codist\QuickInfo\CSharpQuickInfoSourceProvider.cs:line 181&#x000D;&#x000A;   at Microsoft.VisualStudio.Language.Intellisense.Implementation.LegacyQuickInfoSource.AugmentQuickInfoSession(IAsyncQuickInfoSession session, IList`1 content, ITrackingSpan&amp; applicableToSpan)&#x000D;&#x000A;   at Microsoft.VisualStudio.Language.Intellisense.Implementation.AsyncQuickInfoSession.&lt;TryComputeContentFromLegacySourceAsync&gt;d__45.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at Microsoft.VisualStudio.Language.Intellisense.Implementation.AsyncQuickInfoSession.&lt;ComputeSourceContentAsync&gt;d__44.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)&lt;---&#x000D;&#x000A;</description>

Great extension! Just one small issue though...

I have set attribute styles to use smaller font than the rest of the code (font = -4). It works fine for simple attributes like [DebuggerStepThrough].

However for attributes with options it does not work and looks something like this:
[MethodImpl(MethodImplOptions.AggressiveInlining), DebuggerStepThrough]
where the bolded text is rendered using normal (and not reduced font).

When VS theme was changed, the syntax highlight themes could not be fully applied. Currently we have to restart VS to make it right.

How can we get the default syntax styles for each format?

Duplication: sorry, I just see that there was another post about it.
To delete if you can

Hello,

Sorry, I am French and my English is largely perfectible.
Thanks for your extension that combines the benefits of many others and with good performances.

it's 5 minutes I tested your extension and I just realized that the dark theme is not supported in the menu of the analyzer references.

I thank you in advance for his support.
Good work :)

The search result items under the first item of the Navigation Bar ("C#//") can point to wrong positions if the document is modified.

Please help me identify in the source code the parts where you are creating the Super Quick Info syntax colorization for the <c>/<code> tags and also the place where the paragraph tag is instructed to insert a paragraph. I'd like to customize those to my preferences.

Also, as a feature request, it would be nice if there would be customization options for the way Super Quick Info displays certain tags.

Also, it would be a major readability improvement if you could make this:

look like this

Currently I am using both your extension and the EnhancedTooltips for ReSharper to get this

Feels like being doctor Frankenstein, but at least I get some of the good stuff from your extension while having the looks of EnhancedTooltips.

Thank you!

The overridden exception information could contain content in XML Doc about when the exception would be thrown.