Yeah, I figured it needs properties in order to execute the sorting over, but it still has to be done w/ OrderBy(GroupingDescription).ThenBy(SortDescription)?
I'm using Antlr 4 with c# target.
Here is a subset of my grammar:
/*
* Parser Rules
*/
text : term+ EOF;
term : a1 a2 a3;
a1: ....
...
...
I want to accept valid data blocks as (term)s, when error exists I want to search for the next valid term and print out the whole text which caused the ...
> It's expected that the implementer is already an expert in ANTLR 4's implementation of the Adaptive LL(*) parsing algorithm (we're talking researcher-level understanding).
I tried this solution but it didn't seem to work for me
Here's an excerpt from my grammer:
module
: BEGIN MODULE IDENT STRING module_element* END MODULE
;
module_element
: element_1 | element_2 | element_3 | ...
;
There is a bigger tree below each element. Now when a Recognit...
I've deleted some branches from my GH account. I still see them in VS even after I've done fetch. Is there a way to make sure what I have in GH is reflected in VS. Have it delete anything that is comitted and syncd?
> Well.... I was considering the scenario where the `FinalReleaseComObject` returns a nonzero result... That is IMO, a fatal error because its basically saying we can't release it and probably should not be at this moment. So an Error level seems more apropos there.
That said, we ought to *trace* the non-final calls to `ReleaseComObject`. That would greatly aid us in tracking whether non-final calls allow us to gently put down the referenced COM object in appropriate order. We shouldn't be rely
If a branch previously existed in both the remote and local but was deleted from remote is there a way to have that reflected? Currently I'm just doing manual deletion and re-checking my GH repo for those branches that were merged and subsequently deleted.
@Duga I'm hoping this doesn't bite me too bad. I think it's tough enough to require me to learn new things while not too hard that I'm incapable of completing it.
Hi folks! I've maybe discovered my future contribution to rubberduct :-) I don't know C# (for now, planning to learn a bit), BUT I do speak language that's not there yet. :)
What do you think. I can help with Czech translation.
I think, since we ought to release as many of our COM objects as feasible, I will move the release code back into the COM wrapper and remove the new interface before adding the logging. Any objections, @Mat'sMug @this?
If you do try that, at least make sure you trace the count. I doubt we did that before, and I think we do need that information to tell us if we are releasing properly
yes, with the info we now know, it would help to trace them all and see what happens. I don't think we used that information previously and just assumed it didn't work.
@SonGokussj4 that was the old way - @Vogel612 wrote this tool before they came up with a better resx editor --- I think you want this: marketplace.visualstudio.com/…
@Vogel612 Oh. Good. :) Well, I don't expect I would translate it within a week or two :-D Just in my free time. So I'll let you all know when I have a big chunk and you can implement it or tell me what else should I download and try to translate :-)
Tip: when you have a whole file done, git commit -m "added cs translations" - and then git push origin and then a bus can run your laptop over and you'll still be able to recover your work from anywhere =)
(assuming you weren't too near the bus/laptop interaction)
@ thanks for tips. I know git even with commits, pushing to origin or my GitHub repo or GitLab, even deleting some big files from history and customizing my log view. I don't say I know whole lot of git but I know the basics.
> ``` 2017-12-19 10:00:55.2626;FATAL-2.1.1.2532;Rubberduck.Common.LogLevelHelper; Rubberduck version 2.1.1.2532 loading: Operating System: Microsoft Windows NT 6.1.7601 Service Pack 1 x64 Host Product: Microsoft Office 2013 x86 Host Version: 15.0.4911.1000 Host Executable: EXCEL.EXE; 2017-12-19 10:09:56.4411;TRACE-2.1.1.2532;Rubberduck.UI.SourceControl.SourceControlViewViewModel;Cloning repo; 2017-12-19 10:09:56.4461;TRACE-2.1.1.2532;Rubberduck.UI.SourceControl.SourceControlViewVi
actually there are two options, which one do you prefer:
we change the installer .iss to copy the file at the package downloaded by NuGet (in which case, if in the future Nuget downloads a new one, the .iss won't compile saying it didn't find it and we can guess what was going on
or, we just manually copy the files to the \libs folder
I'm going to be a bit of for the next week, tomorrow my mother is visiting for Christmas and she'll meet my girlfriend's family and they'll need translators for this because they're natives to different languages... :D
Mug. I'm looking to address your comment on PR3622. Would the following be along the lines of what you had in mind?
var inspectionSettings = new CodeInspectionSettings
{
CodeInspections = new HashSet<CodeInspectionSetting>(new[]
{
new CodeInspectionSetting("DoNotShowInspection", "Do not show me", CodeInspectionType.LanguageOpportunities, CodeInspectionSeverity.DoNotShow, CodeInspectionSeverity.DoNotShow),
new CodeInspectionSetting("HintInspection", "I'm a hint", CodeInspectionType.LanguageOpportunities, CodeInspectionSeverity.Hint, CodeInspectionSeverity.Hint),
new CodeInspectionSetting("SuggestionInspection", "I'm a suggestion", CodeInspectionType.MaintainabilityAndReadab…
How would I go about making the grid filterable? There's space after Inspection Severities to add an InputBox that could be used to filter on the Description. I'm not sure how that would attach to the InspectionSettings property though.
I'm using Antlr 4 with c# target.
Here is a subset of my grammar:
/*
* Parser Rules
*/
text : term+ EOF;
term : a1 a2 a3;
a1: ....
...
...
I want to accept valid data blocks as (term)s, when error exists I want to search for the next valid term and print out the whole text which caused the ...
I tried this solution but it didn't seem to work for me
Here's an excerpt from my grammer:
module
: BEGIN MODULE IDENT STRING module_element* END MODULE
;
module_element
: element_1 | element_2 | element_3 | ...
;
There is a bigger tree below each element. Now when a Recognit...
VBA Rubberducking
VBA Rubberducking