about summary refs log tree commit diff
path: root/pkgs
Commit message (Collapse)AuthorAgeFilesLines
* pkgs/profpatsch/text-letter: file from stdinProfpatsch2021-07-191-1/+0
|
* pkgs/sternenseemann/saneterm: update to e91ae2bsternenseemann2021-07-151-2/+2
|
* pkgs/vim: Replace vim-css-color with vim-hexokinasedevhell2021-07-101-1/+11
| | | | | | | As @aszlig mentioned earlier, this looks like a better plugin. It does everything I need it to. This commit also enables `termguicolors` which wasn't the case prior, and without it `vim-hexokinase` cannot function properly.
* workstation: Patch XTerm to set $COLORTERMaszlig2021-07-093-1/+20
| | | | | | | | | | While ncurses already has support for detecting direct color terminals, a lot of applications out there do not yet query terminfo but instead rely on some shady COLORTERM environment variable. While I don't really like that approach, patching XTerm to set that variable currently is better than patching all the applications to query terminfo. Signed-off-by: aszlig <aszlig@nix.build>
* vim: Replace vim-css-color by hexokinaseaszlig2021-07-091-6/+31
| | | | | | | | | | | | | | | | | | So far vim-css-color worked quite well for what I wanted, but after talking to @devhell about possible alternatives, I stumbled upon hexokinase and tried it a bit. One of the gripes I had with things such as colorizer is that it highlights colors regardless of the file types we're in, which in turn will also highlight things where the hash character is not a hex value, for example in Erlang's base notation for integers. Hexokinase also highlights all file types but first of all, it only highlights things separated by word boundary and also it's way less obtrusive because the way I've configured it only the hash character is highlighted, not the whole color value. Signed-off-by: aszlig <aszlig@nix.build>
* workstation: Advertise XTerm true color capabilityaszlig2021-07-091-2/+13
| | | | | | | | | | | | | | | | | | So far, the TERM environment variable has been set to xterm-256color, but in reality newer XTerm versions already supported 24bit colors so setting this to xterm-direct results in using the right terminfo entry for our terminal. To make sure this is really the case, let's explicitly set directColor to true, because while it is enabled in nixpkgs by default it is however a compile-time option and could possibly be disabled. Additionally, Vim is now looking pretty gruesome because my colorscheme so far has used colors for 16-color terminals and I don't particularly like the GUI colors. I added a few fixups for the color scheme to address that. Signed-off-by: aszlig <aszlig@nix.build>
* vim: Add highlighting for Markdown code blocksaszlig2021-07-091-1/+116
| | | | | | | | | | | | | | | | | | | | | | While I could have done this simply by setting the g:markdown_fenced_languages variable, I instead decided it would be a better idea to use the same language names that GitHub recognises via their GitHub Flavored Markdown syntax. Since they're using Linguist, I decided to simply import the YAML file and try to match them against existing Vim syntax files. That way, we only need to maintain a blacklist of languages we do not want and should pretty much get highlighting for all supported languages. Unfortunately, the "markdown.vim" syntax file sources all of the syntax files for these languages and so the more languages we include there, the slower it gets when opening a Markdown file. Right now, I mostly use this for editing textareas, so let's see how annoying the slower load time will get and blacklist more languages later if it bugs me too much. Signed-off-by: aszlig <aszlig@nix.build>
* vim: Fix Fish syntax fileaszlig2021-07-091-5/+5
| | | | | | | | | | | | The file in question actually was a ZIP file, which instead of being unpacked got directly moved to syntax/fish.vim and in turn caused errors whenever the filetype was set to "fish". Instead of just fixing up the ZIP file I switched to a GitHub repository that seemed to be maintained a lot more (last commit in 2020) than the one we had so far (last change 2013). Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Switch to vim-css-color from colorizerdevhell2021-07-081-1/+1
| | | | | | The `colorizer` plugin doesn't produce accurate results, so I'll try `vim-css-colors`. It's also looking more maintained than the previous plugin.
* aszlig/vim: Switch to dedicated plugin for Jinja2aszlig2021-07-021-7/+5
| | | | | | | | | | | | | | | | The Vim syntax highlighting plugin file is no longer[1] shipped with Jinja2 version 3.x, so the build fails accordingly with: install: cannot stat 'ext/Vim/jinja.vim': No such file or directory In another upstream pull request[2] one of the project members mentioned another syntax plugin which apparently seems to be more up to date. This is what I'm hereby switching to as a replacement. [1]: https://github.com/pallets/jinja/pull/1196 [2]: https://github.com/pallets/jinja/issues/1007 Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Add mucomplete plugindevhell2021-06-301-0/+7
| | | | | | I've been looking for a good, lightweight, and fast completion engine that also has little or no dependencies. The `mucomplete` plugin seems to fit the bill as I also don't have any fancy requirements.
* pkgs/sternenseemann/saneterm: update to 21577c3sternenseemann2021-06-301-2/+2
|
* pkgs/vim: Add vim-tomldevhell2021-06-271-0/+1
| | | | | | I find myself working more and more with TOML files these days. Unfortunately neither `vim` nor `neovim` upstream have added support for syntax highlighting of TOML files yet.
* pkgs/sternenseemann/pass: remove unused patch filesternenseemann2021-06-231-50/+0
|
* Revert "sternenseemann/pass: Revert changes for pass 1.7.4"sternenseemann2021-06-231-8/+3
| | | | | | | This reverts commit 8ee2e8ee99e566f007051b9d1b51f6a14eb7b5f0. pass 1.7.4 is in nixos-unstable now, so these changes are necessary to fix the build of pass.
* devhell/vim: Add colorizer plugindevhell2021-06-201-0/+1
| | | | This helps quite a lot when working with colors.
* sternenseemann/pass: Revert changes for pass 1.7.4aszlig2021-06-161-3/+8
| | | | | | | | | | | | | | | | | | This reverts commit 88f3e07f175c813cd33469e426f76d7815dd1389. Since https://github.com/NixOS/nixpkgs/pull/126616 still isn't merged and also not in the current NixOS unstable channel, we run into the following evaluation error: assertion '(dmenuSupport -> (((dmenu != null) && (xdotool != null)) && x11Support))' failed at: (17:1) in file: .../pkgs/tools/security/pass/default.nix I decided to re-revert this change, because the commit in question (which undid the revert) did not specify a good reason for doing so and right now the eval error breaks all machine channels on Hydra. Signed-off-by: aszlig <aszlig@nix.build> Cc: @sternenseemann
* treewide: Replace xvfb_run with xvfb-runaszlig2021-06-163-6/+6
| | | | | | | | | | | | Another alias that has been introduced not too long ago[1] and now more closely resembles the actual command name. Since NixOS VM tests no longer allow aliases, our sandbox tests did not evaluate anymore. While at it, I also renamed all the other uses of the alias. [1]: https://github.com/NixOS/nixpkgs/commit/726306003af21ade95b1908d1920ce9a0f9815bb Signed-off-by: aszlig <aszlig@nix.build>
* treewide: Replace pkgconfig with pkg-configaszlig2021-06-168-16/+16
| | | | | | | | | | | | | | This is another alias which got introduced in 2018, because the actual command is "pkg-config" and so the package name containing a dash is more reasonable. The reason why I'm doing this is because NixOS VM tests now disallow aliases and while the evaluation error in question only affected the "gnupg" test, I decided to change all occurences in the event that we might want to disallow aliases for things other than VM tests. Signed-off-by: aszlig <aszlig@nix.build> Cc: @sternenseemann for "opam-env"
* pkgs/profpatsch: Replace s6PortableUtils aliasaszlig2021-06-161-2/+2
| | | | | | | | | | | | | | | | | | Similar to 4701a995cb865c5d7178f574a3eae5872595e768, where I replaced the libtidy alias for html-tidy because it broke evaluation of the PSI test, I found another test for nman which uses an alias. The background is that aliases are now[1] no longer allowed in NixOS VM tests and since "s6PortableUtils" is indirectly referenced, we get an evaluation error on Hydra. Using the unaliased name fixes evaluation and should not change anything in functionality. [1]: https://github.com/NixOS/nixpkgs/commit/3edde6562e19698da69a499881e0a2e4f5a497a2 Signed-off-by: aszlig <aszlig@nix.build> Cc: @Profpatsch
* psi: Update to latest upstream masteraszlig2021-06-151-8/+8
| | | | | | | | | | | | This is mainly to incorporate my latest fix[1] for OMEMO, so in theory updating the plugins would have been sufficient. However, since I like to eat the freshest set of new bugs, I also updated everything else except the theme. The latter seems to be a bit more complicated, since it changed the way they're building it so I skipped that for now. [1]: https://github.com/psi-im/plugins/pull/91 Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/psi: Replaced aliased use of html-tidyaszlig2021-06-151-2/+2
| | | | | | | | | | | | | | | | | | | | A recent change[1] disabled aliases by default in VM tests and since libtidy actually has been an alias of html-tidy since 2014 it's a good idea to use the actual non-aliased packaged. Since I added my PSI build in 2019, I probably didn't check for whether the package name in nixpkgs would be different while packaging and only used the name as reported by CMake, thinking it would work (which it did). Disallowing aliases in VM tests however is a good change, so let's use the real package name. This should fix the evaluation of the Hydra jobset. [1]: https://github.com/NixOS/nixpkgs/commit/3edde6562e19698da69a499881e0a2e4f5a497a2 Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/profpatsch/dhall-flycheck: remove due to eval errorsternenseemann2021-06-131-7/+9
| | | | | | | | | Since this package is introduced via an overlay expression pulled in via IFD, I can't really fix it. Since dhall-flycheck has already been removed from all machines it was a part of, just remove it completely to migitate this issue. cc @Profpatsch
* Revert "Revert "pkgs/sternenseemann/pass: adjust for pass 1.7.4""sternenseemann2021-06-131-8/+3
| | | | This reverts commit c11bd9ec702c71e731cb14c26ff235ea1956a613.
* Revert "pkgs/sternenseemann/pass: adjust for pass 1.7.4"sternenseemann2021-06-131-3/+8
| | | | | | This reverts commit 1987f2d9a4b185dfa319763a67d527fd7ade4d83. This is not even merged into master yet, pushed by mistake.
* pkgs/sternenseemann/pass: adjust for pass 1.7.4sternenseemann2021-06-131-8/+3
|
* pkgs/sternenseemann/saneterm: update to 0288f74sternenseemann2021-06-131-2/+2
|
* pkgs/sternenseemann/mandoc: use builtins.storeDirsternenseemann2021-06-131-1/+1
|
* pkgs/sternenseemann/saneterm: needs python >= 3.9sternenseemann2021-06-131-1/+1
|
* pkgs/profpatsch/backup: more backup stuffProfpatsch2021-06-071-8/+16
|
* pkgs/profpatsch/xrandr: exit(1) on errorProfpatsch2021-06-071-0/+1
|
* pkgs/profpatsch/xdg-open: display short message on xdg-openProfpatsch2021-06-071-1/+3
|
* pkgs/profpatsch/xdg-open: fix text/html oversightProfpatsch2021-06-071-1/+1
|
* pkgs/sternenseemann/saneterm: update to 154481sternenseemann2021-06-021-2/+2
|
* machines/sternenseemann/wolfgang: install sanetermsternenseemann2021-05-312-0/+46
|
* pkgs/profpatsch: init text-letterProfpatsch2021-05-183-0/+158
| | | | A simple text letter formatter (A4) for printing.
* pkgs/profpatsch/xdg-open: Remove UriGlobHandlerProfpatsch2021-05-133-42/+12
| | | | | | The concept of a transparent handler wasn’t actually used anywhere and now that we want to generate the firefox json as well, it just hinders us from doing that in an easy way.
* pkgs/profpatsch/importDhall: allow referencing files in the typeProfpatsch2021-05-131-1/+4
| | | | | | The type string would blow up too much if you can’t reference any dhall file in the sources list. This all feels a bit hacky, but at least semantically it seems to work out?
* pkgs/profpatsch/xdg-open: directly pass MimeMatch to xdg-open scriptProfpatsch2021-05-123-19/+29
| | | | | | | No use in passing through the mime type now that we can just directly render the commands in the protocol handlers. This gives us the base for generating the Firefox handlers.json.
* pkgs/profpatsch/xdg-open: use the new matcher listProfpatsch2021-05-124-79/+10
| | | | Removes the duplication of command handlers.
* pkgs/profpatsch/xdg-open: prepare for adding firefox handler supportProfpatsch2021-05-124-218/+374
| | | | | | | | | This diff is a bit bad cause of whitespace changes, but effectively this copies all handlers into the mime handler definitions and duplicates them for now. We want to use the same config to generate a firefox mime handler file.
* pkgs/profpatsch/xdg-open: add lagrange as gemini & gopher handlerProfpatsch2021-05-081-0/+12
|
* pkgs/profpatsch/write-rust: alwyas run tests by defaultProfpatsch2021-04-236-22/+27
| | | | | | testRustSimple wouldn’t work with all the rust functions, so let’s just use it internally and expose the tests via the conventional `doCheck` attribute instead.
* pkgs/profpatsch: add xrandr two monitor setupProfpatsch2021-04-232-0/+205
| | | | Just to prove I can.
* pkgs/profpatsch/write-rust: fix ln invocationsternenseemann2021-04-201-1/+1
| | | | | | | | The -T flag is GNU coreutils specific, for s6-ln and POSIX ln, the equivalent seems to be -L which mandates behavior like linkat(3) with the AT_SYMLINK_FOLLOW flag. cc @Profpatsch
* devhell/vim: Add packages, remove textwidthdevhell2021-04-151-1/+2
| | | | | | The textwidth limit is getting annoying on certain files, and while I'm sure there's an elegant 'vim-way' of doing this without plugins, I'm just gonna go ahead and see if `vim-sleuth` does the trick.
* factorio: Fix patcher to work with Radare2 5.xaszlig2021-04-141-2/+10
| | | | | | | | | | | | | | | Version 5.0.0 of Radare2 introduced a few changes in symbol naming, which causes our patcher to fail because it's unable to find the "/usr/share/factorio" string and the getSystemWriteData() method. The upstream change[1] in question for example now uses underscores for certain characters in the symbol/comment name, so for us to be backwards-compatible I added a check against the major version of Radare2 to determine whether we should add underscores when needed. [1]: https://github.com/radareorg/radare2/commit/aaa930ab261a31e58b1257df06db02481cd3bd55 Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/sternenseemann: add release tarball toolingsternenseemann2021-04-133-0/+104
| | | | | | | | | | | | | | The following nix functions allow easily creating derivations for building a signed releases directory for project(s) to be served via e. g. HTTP. * buildGitTarball: builds a reproducible .tar.gz for a given git revision or tag (similar to git archive, but we don't actually reuse it in favor of fetchgit). * bundleSignedReleases: symlinks tarballs generated using buildGitTarball and accompanying (manually provided) signatures into a directory and verifies the signatures to ensure buildGitTarball is donig what it's supposed to.
* pkgs/sternenseemann: add schmecgit, a cgit about / source filtersternenseemann2021-04-133-0/+146
| | | | | | | | | Only does very simple dispatching to pkgs.lowdown and pkgs.chroma, but is at least significantly faster than the default source and about filters bundled with cgit (which is not really a challenge as they use python and pygments). Added to enable my cgit setup until we can have TVL's //tools/cheddar.
* pkgs/sternenseemann/shakti: fix hashsternenseemann2021-04-131-4/+5
| | | | Ugh.
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-11 13:17:37 +0000