Jan Klass

Results 17 comments of Jan Klass

I tested with VS2013 and am able to confirm that indeed the settings are not restored when closing a file, that on opening set a indendation setting (language Tabs settings).

I see `--prefix` already does semantic interpretation or expects semantic versioning. ``` -p, --prefix Prefix used in front of the semantic version [default: v] ```

The advantage of --max-x is that it’s relative. Specifying the git baseline requires logic integrating with git and ci at least.

What is a “milestone” or “milestone release” in your case? And how, if at all, does it relate to semantic versioning with major.minor.patch version numbering?

That makes sense, to exclude pre-releases when counting tags/releases for changelog generating. It’s the two sides of a minor release; pre-release before, and patch release after. So, with both cases...

What’s the status and plan on this? Looks like the changes currently only change the tests, but not the actual functionality/output?

I see. PR https://github.com/xunit/assert.xunit/pull/50

I tested in the text/code editor. ![screenshot of VS with font setting set to Caskaydia Code and VS using fallback font](https://github.com/ryanoasis/nerd-fonts/assets/8045680/ae1a98d8-2a48-442f-814b-0ebd7553e442) As you can see in the settings dialog the...

Cascadia Code works fine. screenshot… ![screenshot of VS with Cascadia Code font selected working fine](https://github.com/ryanoasis/nerd-fonts/assets/8045680/2e27b7b9-9b09-48f2-9bd7-5e6beed33f43)

Thank you for the extensive analysis @Finii I installed v3.0.2 and set the font to CaskadiaCove NFM, and VS still falls back to the default font. > The issue with...