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

Allow disabling the use of patched fonts #5

Closed
petrhosek opened this issue Apr 25, 2017 · 2 comments · Fixed by #11
Closed

Allow disabling the use of patched fonts #5

petrhosek opened this issue Apr 25, 2017 · 2 comments · Fixed by #11

Comments

@petrhosek
Copy link

It'd be useful to make the use of patched fonts optional (same as in lightline).

@arcticicestudio
Copy link
Contributor

arcticicestudio commented Jul 9, 2017

Sorry for my late reply, I've been busy with my job.
I'll check if it is possible to implement theme settings to add a option to disable the symbols from the status bar.


Related to #7

arcticicestudio added a commit that referenced this issue Oct 3, 2017
This commit implements a configuration to allow users to disable status
content that needs a patched font setup.

The config can be enabled by setting the global variable
"@nord_tmux_no_patched_font" to "1".

GH-5
arcticicestudio added a commit that referenced this issue Oct 3, 2017
…s-content-no-patched-font

Configuration to disable patched font usage in status content
@arcticicestudio
Copy link
Contributor

@petrhosek Sorry for the delay again. I've implemented a configuration to disable the usage of patched fonts for the status content in #11.

lucasfcosta pushed a commit to lucasfcosta/nord-tmux that referenced this issue Jan 26, 2019
This commit implements a configuration to allow users to disable status
content that needs a patched font setup.

The config can be enabled by setting the global variable
"@nord_tmux_no_patched_font" to "1".

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

Successfully merging a pull request may close this issue.

3 participants