Skip to content
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

=> not being converted to ligature #2

Closed
gauravkumar37 opened this issue Jan 18, 2017 · 13 comments
Closed

=> not being converted to ligature #2

gauravkumar37 opened this issue Jan 18, 2017 · 13 comments

Comments

@gauravkumar37
Copy link

>= is being converted to ligature but => is not.

@SSNikolaevich
Copy link
Owner

What meaning this sequence has? Should it be converted to some "right arrow" symbol? (For example: VHDL uses this lexeme to describe associations)

@gauravkumar37
Copy link
Author

gauravkumar37 commented Jan 21, 2017

=> is used in Scala for writing anonymous functions.

Edit: I see that the fork https://github.com/MartinPham/DejaVuSansCode has most of the ligatures added.

@SSNikolaevich
Copy link
Owner

Implemented in commits 7a43330 - 5de8aeb

@areyes-ut
Copy link

I compiled from master (using make full-ttf), but => is still not being converted in iTerm2 v3.1 beta. Other ligatures are showing just fine, such as !=.

@SSNikolaevich
Copy link
Owner

SSNikolaevich commented Jul 25, 2017

I don't have Mac so I can't reproduce this issue. Under Debian with fonts built using make full-ttf on clean working copy all ligatures displayed well. I released fonts with resent changes. Could you try it?

@SSNikolaevich SSNikolaevich reopened this Jul 25, 2017
@adityavm
Copy link

Just wanted to add that the LGC version doesn't show the => ligature, but full version does

@SSNikolaevich
Copy link
Owner

I tested LGC version in Atom and IDEA under Debian today and didn't face any problems.

@adityavm
Copy link

@SSNikolaevich I'm on a Mac

@areyes-ut
Copy link

@SSNikolaevich Sorry, I tried the tarball for 1.2.1, and it is still not showing a hashrocket ligature for me in iTerm2, v3.1 beta.

@SSNikolaevich
Copy link
Owner

Finally checked 1.2.1 LGC version on Mac OS 10.12.5, iTerm Build 3.1.beta.6. All ligatures are displayed well.

@areyes-ut
Copy link

@SSNikolaevich What shell and application (e.g. vim, emacs, whatever) are you using to check? What's your locale setup? If I just use echo in a zsh shell, it still won't work with =>. My locale variables are set to en_US.UTF-8.

@areyes-ut
Copy link

I am using OSX Yosemite, 10.10.5 .

@SSNikolaevich
Copy link
Owner

Mac OS Sierra 10.12.5
iTerm Build 3.1.beta.6
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin16)
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Apr 4 2017 18:14:54)
ru_RU.UTF-8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants