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

Arbitrary-length arrows #346

Closed
be5invis opened this issue Jan 16, 2017 · 8 comments
Closed

Arbitrary-length arrows #346

be5invis opened this issue Jan 16, 2017 · 8 comments
Milestone

Comments

@be5invis
Copy link

To support LONG arrows like <----------------------- and ---------------------->
The current Iosevka implementation is:

Leftward : A chaining substitution like sub hyphen.cont hyphen' by hyphen.cont
Rightward : A Reverse Chained Single Substitution table like reversesub hyphen' hyphen.cont by hyphen.cont. See here.

NOTE: FontForge cannot export Reverse Subs.

@tonsky
Copy link
Owner

tonsky commented Jan 17, 2017

it’s actually not a bad idea

@wopian
Copy link
Contributor

wopian commented Jan 17, 2017

This is it in action for reference (Coq language variant in Iosevka):

And currently in FiraCode (ofc a few of the top 2 rows isn't possible until there's language flavoured variants)

@tonsky
Copy link
Owner

tonsky commented May 11, 2020

@wopian what font is that on the screenshot?

tonsky added a commit that referenced this issue May 11, 2020
@alexeyten
Copy link

Iosevka, I guess
https://typeof.net/Iosevka/

@wopian
Copy link
Contributor

wopian commented May 11, 2020

@wopian what font is that on the screenshot?

Sorry, don't know why I didn't specify the font originally. It's Losevka's Iosevka's ligatures: https://github.com/be5invis/Iosevka/blob/master/README.md#ligations

@tonsky
Copy link
Owner

tonsky commented May 11, 2020

Thanks! I checked it but missed the point that not all arrows are enabled by default. Also double arrows looked differently in 2017.

BTW it’s iosevka, not Losevka (although I was wondering the same question every time I saw the name. I went and checked to be sure just now. The importance of using the proper font :)

@wopian
Copy link
Contributor

wopian commented May 11, 2020

BTW it’s iosevka, not Losevka (although I was wondering the same question every time I saw the name. I went and checked to be sure just now. The importance of using the proper font :)

The downside of most repositories being all-lowercase and I being identical to l 😞

@tonsky
Copy link
Owner

tonsky commented May 18, 2020

Done in v4

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