Downloads:
7,795
Downloads of v 2.1.0:
443
Last Update:
29 Jan 2020
Package Maintainer(s):
Software Author(s):
- Mozilla tonsky ryanoasis
Tags:
fira font monospaced with programming ligatures code- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Fira Code NF
This is not the latest version of Fira Code NF available.
- 1
- 2
- 3
2.1.0 | Updated: 29 Jan 2020
- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
7,795
Downloads of v 2.1.0:
443
Maintainer(s):
Software Author(s):
- Mozilla tonsky ryanoasis
Fira Code NF 2.1.0
This is not the latest version of Fira Code NF available.
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
Deployment Method: Individual Install, Upgrade, & Uninstall
To install Fira Code NF, run the following command from the command line or from PowerShell:
To upgrade Fira Code NF, run the following command from the command line or from PowerShell:
To uninstall Fira Code NF, run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download firacodenf --internalize --version=2.1.0 --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade firacodenf -y --source="'INTERNAL REPO URL'" --version="'2.1.0'" [other options]
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade firacodenf -y --source="'INTERNAL REPO URL'" --version="'2.1.0'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install firacodenf
win_chocolatey:
name: firacodenf
version: '2.1.0'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'firacodenf' do
action :install
source 'INTERNAL REPO URL'
version '2.1.0'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller firacodenf
{
Name = "firacodenf"
Version = "2.1.0"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'firacodenf':
ensure => '2.1.0',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
This package was approved by moderator Pauby on 11 Feb 2020.
Fira Code: monospaced font with programming ligatures Nerd Font
This is Fira Code with nerd fonts applied to it (https://github.com/ryanoasis/nerd-fonts)
Nerd Fonts is a project that patches developer targeted fonts with a high number of glyphs (icons). Specifically to add a high number of extra glyphs from popular 'iconic fonts' such as Font Awesome ➶, Devicons ➶, Octicons ➶, and others.
Problem
Programmers use a lot of symbols, often encoded with several characters. For the human brain, sequences like ->
or :=
are single logical tokens, even if they take two or three characters on the screen. Your eye spends a non-zero amount of energy to scan, parse and join multiple characters into a single logical one. Ideally, all programming languages should be designed with full-fledged Unicode symbols for operators, but that’s not the case yet.
Solution
Download v.2 · How to install · Troubleshooting · News and updates
Fira Code is an extension of the Fira Mono font containing a set of ligatures for common programming multi-character combinations. This is just a font rendering feature: underlying code remains ASCII-compatible. This helps to read and understand code faster. For some frequent sequences like ..
or //
, ligatures allow us to correct spacing.
Stylistic sets
See How to enable
Credits
- Author: Nikita Prokopov @nikitonsky
- Based on: Fira Mono
- Inspired by: Hasklig
$ErrorActionPreference = 'Stop'
Uninstall-ChocolateyFont "$toolsDir\otf\FiraCode-Bold.otf"
Uninstall-ChocolateyFont "$toolsDir\otf\FiraCode-Light.otf"
Uninstall-ChocolateyFont "$toolsDir\otf\FiraCode-Medium.otf"
Uninstall-ChocolateyFont "$toolsDir\otf\FiraCode-Regular.otf"
Uninstall-ChocolateyFont "$toolsDir\otf\FiraCode-Retina.otf"
md5: 196B8054BDE649FD67F85A1B730140DD | sha1: 64043894B26783CAEAB5CBA72164429E3CBEF4A4 | sha256: EB1026CF494795B3FE1378A51CD1D157FE8D7066597F4B00826F91A4524B94DD | sha512: DA5CFA63F7E0D1231075D337E1BF2AA5A445EEBBDBB29F7096BCF4359D672AAA01DEAF90F15BFE7F9464401203D37762E291C6AAC70CBA8434B2894F10EEC8EC
Copyright (c) 2014, The Fira Code Project Authors (https://github.com/tonsky/FiraCode)
This Font Software is licensed under the SIL Open Font License, Version 1.1.
This license is copied below, and is also available with a FAQ at:
http://scripts.sil.org/OFL
-----------------------------------------------------------
SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
-----------------------------------------------------------
PREAMBLE
The goals of the Open Font License (OFL) are to stimulate worldwide
development of collaborative font projects, to support the font creation
efforts of academic and linguistic communities, and to provide a free and
open framework in which fonts may be shared and improved in partnership
with others.
The OFL allows the licensed fonts to be used, studied, modified and
redistributed freely as long as they are not sold by themselves. The
fonts, including any derivative works, can be bundled, embedded,
redistributed and/or sold with any software provided that any reserved
names are not used by derivative works. The fonts and derivatives,
however, cannot be released under any other type of license. The
requirement for fonts to remain under this license does not apply
to any document created using the fonts or their derivatives.
DEFINITIONS
"Font Software" refers to the set of files released by the Copyright
Holder(s) under this license and clearly marked as such. This may
include source files, build scripts and documentation.
"Reserved Font Name" refers to any names specified as such after the
copyright statement(s).
"Original Version" refers to the collection of Font Software components as
distributed by the Copyright Holder(s).
"Modified Version" refers to any derivative made by adding to, deleting,
or substituting -- in part or in whole -- any of the components of the
Original Version, by changing formats or by porting the Font Software to a
new environment.
"Author" refers to any designer, engineer, programmer, technical
writer or other person who contributed to the Font Software.
PERMISSION & CONDITIONS
Permission is hereby granted, free of charge, to any person obtaining
a copy of the Font Software, to use, study, copy, merge, embed, modify,
redistribute, and sell modified and unmodified copies of the Font
Software, subject to the following conditions:
1) Neither the Font Software nor any of its individual components,
in Original or Modified Versions, may be sold by itself.
2) Original or Modified Versions of the Font Software may be bundled,
redistributed and/or sold with any software, provided that each copy
contains the above copyright notice and this license. These can be
included either as stand-alone text files, human-readable headers or
in the appropriate machine-readable metadata fields within text or
binary files as long as those fields can be easily viewed by the user.
3) No Modified Version of the Font Software may use the Reserved Font
Name(s) unless explicit written permission is granted by the corresponding
Copyright Holder. This restriction only applies to the primary font name as
presented to the users.
4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
Software shall not be used to promote, endorse or advertise any
Modified Version, except to acknowledge the contribution(s) of the
Copyright Holder(s) and the Author(s) or with their explicit written
permission.
5) The Font Software, modified or unmodified, in part or in whole,
must be distributed entirely under this license, and must not be
distributed under any other license. The requirement for fonts to
remain under this license does not apply to any document created
using the Font Software.
TERMINATION
This license becomes null and void if any of the above conditions are
not met.
DISCLAIMER
THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
OTHER DEALINGS IN THE FONT SOFTWARE.
============================= Fira Code NF =============================
Downloads the fira code nf otf as a .zip and installs to system fonts
courtesy of chocolatey-font-helpers.extension. Follow the step-by-step
to verify the checksums
Step 1:
Download the zip file from
https://github.com/FredHappyface/Choco.Packages/tree/master/firacodenf/package/tools.firaCodeNF.zip
Step 2:
Extract the zip file and grab/ copy the otf directory
RouteA or RouteB
RouteA to verify the individual .otf files, RouteB to verify a zip file
containing the otf/ directory
RouteA
Step 3:
Open a powershell terminal and run
```powershell
Get-ChildItem | Get-FileHash | Export-Csv checksum.csv
```
Step 4:
Open the csv (many forms of spreadsheet software can help with this. e.g.
Microsoft Excel, LibreOffice Calc). The SHA256 will match those in the
Font List below
(Note that I have reordered the columns)
RouteB
Step 3:
Zip the otf/ directory and run
```powershell
Get-FileHash [zip-name]
```
The SHA256 Hash is E028AAAC4EEB2B80BD5293256B3943FAD64647929A5CB595733D7ED2462EE008
------------------------------ Font List ------------------------------
Algorithm Hash Font
SHA256 6A6A829DAEEB0AB216CD89B592825F2E1293F1F274CA9F154BE622248289204A FiraCodeNF-Bold.otf
SHA256 D3CFDDF56C54EB45282F36E2E01077A0AF0699AF5578743ABDB91245F25F7CC3 FiraCodeNF-Light.otf
SHA256 7AA865190D599CED0ED77BF384E67AC75B17D0405680355F0502AC7101A224C8 FiraCodeNF-Medium.otf
SHA256 E1119A6FD1465C611B887799563A9FC11CE75AC936F71421947C95BCD6190F7B FiraCodeNF-Regular.otf
SHA256 A1152AB95933FCB7C42F4A778CB98867983165E4660C911F0F9F83DED9DE09C7 FiraCodeNF-Retina.otf
============================= Fira Code NF =============================
Log in or click on link to see number of positives.
- firaCodeNF.zip (eb1026cf4947) - ## / 63
- firacodenf.2.1.0.nupkg (0e8e78420de3) - ## / 60
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
FiraCodeNF 6.002 | 3287 | Monday, May 2, 2022 | Approved | |
Fira Code NF 5.0.0 | 3421 | Tuesday, June 9, 2020 | Approved | |
Fira Code NF 4.0.0 | 348 | Thursday, May 28, 2020 | Approved | |
Fira Code NF 3.1.0 | 171 | Tuesday, May 26, 2020 | Approved | |
Fira Code NF 3.0.0 | 125 | Tuesday, May 26, 2020 | Approved | |
Fira Code NF 2.1.0 | 443 | Wednesday, January 29, 2020 | Approved |
Copyright (c) 2014, The Fira Code Project Authors
Ground Rules:
- This discussion is only about Fira Code NF and the Fira Code NF package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or Fira Code NF, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.