Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Direct display of symbols #197

Closed
Alexander-N opened this issue Jan 31, 2021 · 2 comments
Closed

Direct display of symbols #197

Alexander-N opened this issue Jan 31, 2021 · 2 comments
Labels
discussion Discussion

Comments

@Alexander-N
Copy link

Alexander-N commented Jan 31, 2021

Thank you for this great extension, for me it really makes a huge difference when working with TLA+!

One advantage compared to the TLA Toolbox is that it's possible to configure VSCode so that the mathematical symbols are directly displayed, which I find much easier to read. There is vsc-conceal which can be used with the settings from this PR. Since I found the unicode characters a bit small I use it together with FiraCode which gives results like this:

before
image

after
image

I was wondering what others think of this, maybe there are more/better ways to get similar results? Is this worth documenting in the wiki? The settings I used are in this gist.

@alygin
Copy link
Contributor

alygin commented Jan 31, 2021

@Alexander-N, thanks for bringing up an interesting subject.

VSC-Conceal looks cool and it really works best in conjunction with Fira Code. I agree that it's worth mentioning in the wiki, I'll get back to it soon.

I myself prefer narrow fonts and use Pragmata Pro with ligatures that cover many substitutions mentioned in your vsc-conceal config. Unfortunately, not all unicode symbols that represent math operators are displayed as good as in Fira Code, so I switched them off. Actually, I only left few vsc-conceal substitutions for TLA+, but they work fine for me.

@alygin alygin added the discussion Discussion label Jan 31, 2021
@Alexander-N
Copy link
Author

The goal of my settings was to use substitutions to unicode only for the cases which are not covered by FiraCode.

So for example in the linked PR there was

{
  "ugly": "#|/=",
  "pretty": ""
}

which I changed so that it matches the ligature for "not equal" by FiraCode:

{
  "ugly": "#|/=",
  "pretty": "!="
}

@alygin alygin closed this as completed Feb 2, 2021
@tlaplus tlaplus locked and limited conversation to collaborators Feb 2, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
discussion Discussion
Development

No branches or pull requests

2 participants