Closed lucascosti closed 10 months ago
This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. If you have found a problem that seems similar, please open a discussion first, complete the body with all the details necessary to reproduce, and mention this issue as reference.
Code of Conduct
What happened?
Some node projects that I use recently changed their
.nvmrc
files to use the LTS codenames instead of an actual version number. e.g. previously, the contents of.nvmrc
wasv20.10.0
, whereas now it islts/iron
.At the moment, NVM resolves
lts/iron
tov20.10.0
, but the oh-my-poshnode
segment doesn't in its mismatch logic.e.g. here is my segment:
Is it possible for the segment to resolve the LTS codename in the
.Mismatch
property's logic?Thanks for the consideration!
Theme
Here is my segment's config:
What OS are you seeing the problem on?
macOS
Which shell are you using?
zsh
Log output