Search Criteria
Package Details: nerd-fonts-jetbrains-mono 2.1.0-1
| Git Clone URL: | https://aur.archlinux.org/nerd-fonts-jetbrains-mono.git (read-only, click to copy) |
|---|---|
| Package Base: | nerd-fonts-jetbrains-mono |
| Description: | A Nerd Font patched version of JetBrains Mono |
| Upstream URL: | https://www.nerdfonts.com |
| Licenses: | |
| Conflicts: | |
| Submitter: | yochananmarqos |
| Maintainer: | yochananmarqos |
| Last Packager: | yochananmarqos |
| Votes: | 1 |
| Popularity: | 0.37 |
| First Submitted: | 2020-02-02 16:36 |
| Last Updated: | 2020-02-02 16:36 |
Dependencies (5)
- fontconfig (fontconfig-srb, fontconfig-infinality-ultimate, fontconfig-ubuntu, fontconfig-infinality, fontconfig-infinality-remix, fontconfig-git)
- xorg-font-utils
- fontconfig (fontconfig-srb, fontconfig-infinality-ultimate, fontconfig-ubuntu, fontconfig-infinality, fontconfig-infinality-remix, fontconfig-git) (make)
- xorg-mkfontdir (xorg-mkfontscale) (make)
- xorg-mkfontscale (make)
Latest Comments
yochananmarqos commented on 2020-03-21 14:06
@Kage-Yami: No, you can have both installed at the same time as they have different filenames.
Kage-Yami commented on 2020-03-21 02:52
I'm not sure when it comes to patched fonts, but shouldn't this conflict with
ttf-jetbrains-mono?yochananmarqos commented on 2020-02-26 22:42
@Vitruvius: Well, if the
nerd-fonts-completemaintainer ever updates to 2.1.0, it will conflict.Vitruvius commented on 2020-02-26 22:41
This does not conflict with nerd-fonts-complete (I don't know about nerd-fonts). I could not find this font with nerd-fonts-complete installed, so I removed that line from the PKGBUILD, and it installed without issue.
yochananmarqos commented on 2020-02-18 15:02
@Parmigggiana: The error is completely unrelated to this package. Check your Ruby installation and
$PATHlike it suggests.Parmigggiana commented on 2020-02-18 12:00
EDIT: My bad, it's as yochananmaroq says. I didn't understand the error and wasn't able to find anything relevant before; I managed to remove that path from the PATH variable even if I still don't really get how it works but the package installed fine and the font looks great. I'll just leave this here in case anyone has a similar problem. The easiest way i found to remove that path was just copying the output from echo $PATH into export PATH= without the one that was causing problems
I'm unable to install this package because of this error message
==> Starting package()... find: The relative path ‘$(ruby -e 'puts Gem.bindir')’ is included in the PATH environment variable, which is insecure in combination with the -execdir action of find. Please remove that entry from $PATH ==> ERROR: A failure occurred in package(). Aborting...