r-hoogenboom
r-hoogenboom
Something like: gl submodule init [ []] (clone or start a submodule) gl submodule switch gl submodule list (list all submodules in repo with their tag/branch/hash) gl submodule merge/fuse (do...
gl submodule rm might lead someone to believe that the whole tree will be deleted, while you probably mean to just 'unlink' it as a submodule. Maybe gl submodule uninit...
My changes are all about _shrinking_ sections, not growing. Do you mean that I don't need to call rewriteSections after shrinking? What else should I call to 'propagate' the shrinking...
HMM, I expected that exactly this was the responsibility of rewriteSections. If it can deal with grown sections, why wouldn't it be able to deal with shrunk sections. Note sections...
Yes, it seems the issue #453 is the same root cause: only the .dynamic is changed to remove the reference to the string, but it still leaves the orphaned string...
I think this depends on which 'base' font is chosen. I have also noticed that the 'sextants' don't align nicely with the "missing" sextants 'SPACE'/'NO BREAK SPACE', 'LEFT HALF BLOCK',...
I see the word TEST for the U+1FB1E, but it's not very useful to have increased the height of that same glyph. Better have changed one of the 'full-height' sectants,...
Oh, I see that U+1FB1F is enlarged, not U+1FB1E... Changed the html file accordingly and it seems to have fixed the problem. Try it yourself [legacycomputing2.txt](https://github.com/dokutan/legacy_computing-font/files/8853138/legacycomputing2.txt) !
The narrowing of U+1FB21 seems to worsen the situation. The glyph is much narrower than, for instance, U+2583 from liberation mono.
The alignment is better but still not perfect and it depends on which font it is 'paired' with. The only way I get good co-rendering of the block elements and...