about summary refs log tree commit diff
path: root/pkgs
Commit message (Collapse)AuthorAgeFilesLines
...
* pkgs/sternenseemann/scripts: widen backup ignores for ~/Videossternenseemann2023-05-141-1/+4
| | | | These are archived elsewhere and don't need to fill up the backup drive.
* pkgs/sternenseemann: use (vuizvui) pkgs.callPackagesternenseemann2023-05-142-5/+7
| | | | | This allows us to get the fix point for scripts from callPackage instead of building it ad hoc.
* pkgs/tvl: 2023-02-02 -> 2023-05-01sternenseemann2023-05-141-1/+1
|
* pkgs/sternenseemann/logbook: use dune 3 to unbreak buildsternenseemann2023-04-101-2/+2
|
* treewide: s6-test is dead, long live eltest!sternenseemann2023-04-105-9/+9
| | | | | | | | | | | | Recent versions of s6-portable-utils no longer include s6-test which was deprecated in favor of eltest which supposedly has the same interface. I've not tested this commit very thoroughly, but my system now builds again with recent nixpkgs commits (I think I dependended on s6-test via the rust writer via nman). cc @Profpatsch
* slylandro: Remove hidpi specific settings for nowaszlig2023-04-092-6/+5
| | | | | | | | | | | | | | | | | This reverts commit c88fd9eaa12c8a3c06502b09c2056d3c91421952. The hardware.video.hidpi.enable option was removed a while ago[1] because it's not clear what a single boolean option should mean, so it doesn't make sense anymore to make any of our options depend on it. Forthermore, I'm experimenting with different Wayland compositors at the moment and most of the stuff that I did here is for Xorg. I expect most of the stuff to be gone when I'm settled with a Wayland setup that works for me. [1]: https://github.com/NixOS/nixpkgs/pull/222689 Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/nvim: initdevhell2023-04-052-0/+74
| | | | | This is just a test for now. I'm sure the config is ridiculous, but it'll do for the moment.
* vim/markdown: Remove dircolors syntaxaszlig2023-03-311-2/+2
| | | | | | | | | | | | The syntax file in question queries features from the current terminal and will bring editing Markdown files to a crawl, freezing Vim for more than ten seconds. I haven't encountered a dircolors(1) file within a Markdown fenced code block yet and even if this should be the case someday it's not worth the high runtime cost. Signed-off-by: aszlig <aszlig@nix.build>
* firefox: Rebase mute-by-default patch against v111aszlig2023-03-221-8/+11
| | | | | | | | | Firefox version 111.0 has refactored AutoplayPolicy.cpp a but and there is now a handy "IsWindowAllowedToPlayByUserGesture" function that is more convenient in that we just need to patch it to *always* return false. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/mutt: Add reply_regexp for German "AW:"aszlig2023-03-151-0/+1
| | | | | | | | | | | | | Since the default reply regexp depends on the current locale and I refuse to use German localisation for mutt or even my whole system (except for a few corner cases such as time format), replying to emails with "AW: foobar" in the subject gets messy at some point when you get multiple "Re: AW: Re: AW: foobar". So allowing both "Re:" and "AW:" prefixes and stripping them should hopefully make those subjects less messy. Signed-off-by: aszlig <aszlig@nix.build>
* firefox: Update multi-account-containers to v8.1.2aszlig2023-02-021-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Upstream changes: New features: * Add ability to filter the container list * Make “default container” entry keyboard navigable * Add option to select a light/dark theme Bug fixes: * Enable proxyDNS only for supported proxies (SOCKS4/5) * Refresh the UI even when there are no proxy settings * Fix the tab sorting for custom container ordering * Allow hyphens in proxy username/password * Fix rendering for Troubleshooting info section * Tooltip renders off viewport when hovering over a container assigned to VPN. * Excluding containers from sync with RegExp * Fix empty regexp and incoming sync exclude behavior * Remove identityState when deleting containers * Account for moved aboutNetError.css in Firefox 107 * Truncate text to ensure the delete icon is visible * Update wording for sites opened in no container Developer improvements: * Use GitHub Actions for testing * Update the “new issue” template * Update issue menu * Update documentation and templates * Make Troubleshooting Information optional * Update minimal version of web-ext Full source code diff can be found here: https://github.com/mozilla/multi-account-containers/compare/8.0.9...8.1.2 Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/aszlig: Remove grandpaaszlig2023-02-022-21/+0
| | | | | | | | | | | Since Python 2 is marked insecure, we get evaluation errors for this package. The application is no longer in use and I've archived the source code repository already. I also do not intend to continue developing it, let alone port to Python 3. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/tvl: 2022-10-07 -> 2023-02-02sternenseemann2023-02-021-1/+1
|
* pkgs/sternenseemann/saneterm: fix build with recent g-i changessternenseemann2023-01-251-5/+1
| | | | | | | | gobject-introspectino in nativeBuildInputs will propagate itself (for runtime) in buildInputs and be correctly available in checkInputs. There has been a bit of back and forth in upstream with g-i, so let's hope this sticks!
* aacolorize: Convert to Python 3aszlig2023-01-172-16/+31
| | | | | | | | | | | | Python 2 was sunset a long time ago and recently got marked as insecure, so evaluation fails. Since this program is very little in size, I decided to quickly switch to Python 3 in a low-effort way. This means that I didn't switch to using pathlib or using context managers for files, only the things necessary so that it still works. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/sternenseemann/texlive: add chemistry packagessternenseemann2023-01-121-1/+1
|
* pkgs/sternenseemann/plan9port: drop upstreamed patchsternenseemann2023-01-062-163/+0
|
* devhell/vim: add swayconfig-vimdevhell2022-12-231-0/+1
| | | | | It's annoying to have vim complain about sway's config not being i3. This lets vim appreciate sway's config.
* pkgs/firefox: Update Account Containers to v8.0.9aszlig2022-12-151-2/+2
| | | | | | | | | | | | | | Changes for both version 8.0.8 and 8.0.9: * Fix new location of aboutNetError.css in Firefox 107. * Fix missing styling for "open in this container" confirmation page. Upstream changelogs: https://github.com/mozilla/multi-account-containers/releases/tag/8.0.8 https://github.com/mozilla/multi-account-containers/releases/tag/8.0.9 Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/firefox: Update Tridactyl to version 1.23.0aszlig2022-12-151-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | New features: * :back and :forward tab completions with tree style history * Local and global marks added. m[a-zA-Z] to add a mark, lowercase makes a local mark (unique to that page), uppercase makes a global mark. Global marks are preserved between browser restarts. Press backtick followed by a key to go to a mark. See the eighth page of the :tutor for more information * :tgroup* functionality added for "tab groups" for showing/hiding groups of tabs and switching between them. See :help tgroupcreate and :help tgroupswitch for usage tips * Proxy support added with :proxyadd, :set proxy and :autocontain support * :tab completions now shows whether tabs are pinned (P), audible (A), muted (M), or discarded (D) and allows filtering by these characters. :set statusstylepretty true to display emojis instead (but always use the same characters for filtering) * If bookmarking the current URL, :bmark will now use the tab's title if one is not provided, even if a folder path is provided * :gobble mode now accepts key combinations as terminators rather than just counts of key presses to accept. This lays the groundwork for making Tridactyl friendlier to more keyboard layouts * :set jsurls.[keyword] added which work like searchurls but provide js functions whose return value is called by {,tab,win}open. See :help jsurls for more information * searchurls now support array slicing with %s[n:m] * :tabopen --focus-address-bar added to open a new tab and give focus to the address bar * {search,js}url now support aliases * :autocmd now lets you modify requestHeaders and responseHeaders, for example if you want to change your User-Agent * ex.insert_space command added to insert a space in the command line, bound to <C-Space> by default Bug fixes: * visual mode will now exit erroneously less often * Hint mode will now open more links in new tabs when requested, rather than falling back to opening things in the current tab * :open should now work with bookmarklets * :find now searches from view and gains some new arguments to control its behaviour * :issue should now prefill its fields correctly * You can no longer attempt to save files to illegal filenames * Flickering when opening a new tab with dark mode enabled has been reduced * forced-color CSS support improved * :mktridactylrc doesn't make :seturls into global settings * :set tabsort mru now displays the current tab at the bottom Miscellaneous: * More :bind --mode=browser bind slots added * We've added the arg argument parsing library so excmd arguments might become more consistent one day :) * Documentation of :allowautofocus and :unfocus improved * Documentation of :native for containerised (Snap, Flatpak, etc) installations of Firefox improved * Documentation for :autocmd improved * :bind [key] now returns a valid :bind command that you can edit * :get [setting] no longer returns an equals sign so it can be more easily changed into a :set * :tutor is now viewable directly on GitHub Full upstream changelog with authors and issue numbers: https://github.com/tridactyl/tridactyl/blob/5bf126699f37e1981458c5c27b78b41dfd140af1/CHANGELOG.md#release-1230--2022-11-28 Signed-off-by: aszlig <aszlig@nix.build>
* Rename vim_configurable to vim-fullaszlig2022-12-112-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The "vim_configurable" derivation has had a long history in nixpkgs back then when there was no RFC process and where people still were figuring out better ways on how to configure compile-time flags. One of those was a composableDerivation function, which was used for "vim_configurable" and mapped attribute sets to autoconf-flags, so that for example if there was a "--enable-foo" flag you could just use something like: vim_configurable.merge { cfg.fooSupport = true; } You'd then get a Vim with "--enable-foo" passed to configureFlags. However, the composableDerivation feature was too complicated and was ultimately removed at some point. While it does allow for things such as introducing new "edf" (stands for Enable Disable Feature and maps the autoconf flags mentioned above to attribute sets) flags, the complexity that comes with that system is way too large than using something like eg.: vim-full.overrideAttrs (drv: { configureFlags = (drv.configureFlags or []) ++ [ "--enable-foo" ]; }) While this looks more verbose than the above, one can easily follow what's happening, whereas if you'd need to add and enable a new "edf" flag, you'd do something like this: vim_configurable.merge { flags = composableDerivation.edf { name = "foo"; }; cfg.fooSupport = true; } I admit that this does look a little nicer, but even I'm not sure whether it's worth adding so much complexity since in practice I rarely came across a sitation where something like the above would be really beneficial. So back then when "vim_configurable" was introduced[1], it was used as an alternative to the main vim derivation but using composableDerivation instead. Nowadays however, vim_configurable no longer uses composableDerivation and the rename also doesn't change any features, so I think it's safe to rename vim_configurable to vim-full in Vuizvui. [1]: https://github.com/NixOS/nixpkgs/commit/9a4e9e7a3b4014bb3c9f678ec22d254b85c4c98a [2]: https://github.com/NixOS/nixpkgs/commit/4e5ebcc3ed1de9c5c2001c7d5829f4566e0bde3f Signed-off-by: aszlig <aszlig@nix.build> Cc: @Profpatsch Cc: @devhell
* pkgs/sternenseemann: remove everything shaktisternenseemann2022-11-283-63/+1
| | | | | | | | | Since shakti's k9 is no longer available for download, this is quite nonsensical to keep around. When it becomes available again, I'll be better off downloading it and saving it locally somewhere. Nixified shakti will just end up being garbage collected… The k-gpp idea wasn't bad, but not great either.
* vim/default: vim-markdwon -> markdown-preview-nvimdevhell2022-11-281-1/+1
| | | | | | I'm particularly annoyed at the way `vim-markdown` handles folding, so I'm going to give `markdown-preview-nvim` a spin. It's also actively maintained and seems quite powerful.
* pkgs/profpatsch/xrandr: fix assert statementsProfpatsch2022-11-011-3/+3
|
* pkgs/profpatsch.de/talkies: add talkieProfpatsch2022-11-011-1/+3
|
* pkgs/profpatsch/deploy: print all commands to stderrProfpatsch2022-11-011-3/+8
|
* firefox: Fix path to Tridactyl native executableaszlig2022-10-271-5/+2
| | | | | | | | | | The new Tridactyl native messenger is no longer written in Python, so the path to the main executable is no longer valid. I also trimmed down the allowed_extensions attribute to just include the actual extension. Signed-off-by: aszlig <aszlig@nix.build>
* workstation: Switch to Nix-managed Firefoxaszlig2022-10-277-0/+223
| | | | | | | | | | | | | | I had this laying around locally for a year now and I'm still not really happy with some things, for example not having yet full source builds of the extensions and a few config options not yet managed by Nix (eg. search engines). However, since Firefox takes a while to build it's a bit tedious to always do it directly (and locally) after I update my machines. Having this part of my workstation profile should make sure that my version of Firefox is available at all times. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/sternenseemann/acme: set PLAN9 env varsternenseemann2022-10-151-1/+1
| | | | | | | After https://github.com/NixOS/nixpkgs/pull/183008 it seems to be necessary to set PLAN9 even with Sören's patch to resolve the font acme needs. I don't have time to debug this issue at the moment, so let's give in and set the variable.
* pkgs/tvl: 2022-10-06 -> 2022-10-07sternenseemann2022-10-071-1/+1
| | | | Fixes build (!) of my emacs on i686-linux.
* pkgs/tvl: 2022-09-29 -> 2022-10-06sternenseemann2022-10-061-1/+1
| | | | Fixes eval of my emacs on i686-linux
* pkgs/tvl: pass localSystem correctlysternenseemann2022-10-061-0/+3
| | | | | | | | | depot reimports nixpkgs, so we need to make sure it passes the correct value for `system`. As a result of how depot works, cross is unsupported at the moment. This breaks machines/sternenseemann/ludwig for the moment, which we'll be able to address separately.
* pkgs/sterneseemann/tep: unicode: 14.0 -> 15.0sternenseemann2022-10-021-2/+2
|
* pkgs/tvl: 2022-09-28 -> 2022-09-29sternenseemann2022-09-291-1/+1
| | | | | Disalbes checkMeta for depot which should prevent the odd eval failure due to extra meta attrs it uses
* channel: Fix exposing meta.isHydraChannelaszlig2022-09-281-23/+27
| | | | | | | | | | | | | | | | | | | | | The isHydraChannel meta attribute is needed in order to tell Hydra that the derivation in question should be a channel tarball. However in Nixpkgs the meta attribute is not used, so checkMeta doesn't recognise it as a valid attribute which leads to an evaluation error. Recently[1] a commit got merged, which enables shallow type checking for meta attributes by default. This led to an evaluation error for our Hydra machine channels for the reason mentioned above. I opted to work around that issue by adding meta.isHydraChannel after mkDerivation, because adding isHydraChannel as a valid meta attribute to Nixpkgs doesn't feel right to me since it's only relevant for Hydra and its apparently deprecated[2] channel feature. [1]: https://github.com/NixOS/nixpkgs/commit/6762de9a28e248f46bd0810e03c [2]: https://github.com/NixOS/hydra/blob/53335323ae79ca1a42643f58e520b376898ce641/doc/manual/src/jobs.md#meta-fields Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/tvl: fix evalsternenseemann2022-09-281-1/+1
|
* pkgs/tvl: 2022-06-03 -> 2022-09-28sternenseemann2022-09-281-1/+1
| | | | Contains adjustments for recent alias removals in nixpkgs.
* pkgs/profpatsch: fix tvl referenceProfpatsch2022-09-261-0/+2
|
* pkgs/profpatsch/show-qr-code: fix encoding with newlinesProfpatsch2022-09-261-1/+8
| | | | The Qr-code was done with a strange format that only allowed ASCII.
* pkgs/profpatsch: Fix attribute name for util-linuxaszlig2022-09-261-2/+2
| | | | | | | | | | | This attribute has been renamed a while ago[1] but recently even the alias was removed[2], which now triggers an evaluation error in Vuizvui. [1]: https://github.com/NixOS/nixpkgs/commit/bc49a0815ae860010b4d593b02f [2]: https://github.com/NixOS/nixpkgs/commit/ba3319568df2c6675dbe36478fb Signed-off-by: aszlig <aszlig@nix.build> Cc: @Profpatsch
* pkgs/vim: Add quick-scope pluginaszlig2022-09-181-0/+7
| | | | | | | | | | | | Found this thanks to @fpletz starring the repository and since I constantly use f/F and t/T when navigating, I decided to give it a try. Usually when trying things, I'd just add the Vim version with the plugin to my local Nix profile, but since I'm already irritated when other things than the cursor are highlighted in the current line, I decided to do something completely irrational and just add it to all my machines. Signed-off-by: aszlig <aszlig@nix.build>
* radare2: Add patch to default to AT&T ASM syntaxaszlig2022-09-183-1/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some personal history on this: I started to get used to AT&T syntax because it's the default in GDB and used that ever since until I one day starting to do some more reverse engineering using radare, which defaults to Intel syntax. Ever since then probably my most used command in GDB was "set disassembly-flavor intel" (because I was to lazy to add it to the config) because I constantly got confused by the source/destination operand swaps. This even happened during live reverse engineering at rC3 where I was confused about some function logic only to find out that I was viewing in AT&T syntax. Fast-forward to today: I'm debugging some application using WINE and winedbg uses AT&T syntax, which I didn't like at first. After reflecting on this for a while, I thought it would probably be better to get used to AT&T syntax again and switch everything to use AT&T for the following reasons: * Operands are more natural to read, since most libraries/APIs in higher level languages do it like this (well, except memcpy, strcpy, etc... maybe I now get confused by libc functions...) * AT&T syntax feels less verbose, for example "mov ecx, dword [eax]" is just "movl (%eax), %ecx" This very commit makes sure that radare2 now defaults to AT&T syntax instead of eg. ensuring that GDB uses Intel syntax by default. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/sandbox: Create injected target directoryaszlig2022-09-101-4/+11
| | | | | | | | | | | | | When using NIX_SANDBOX_DEBUG_INJECT_FILES (which we now call NIX_SANDBOX_DEBUG_INJECT_DIRS, because it's more accurate), I usually used it to provide fake /dev or /sys directories. I turned out, that today I was trying to use this functionality again (who'd have known) and it also turned out that I forgot to create the target directory, which wasn't needed back then for /dev or /sys because they were already existing. Signed-off-by: aszlig <aszlig@nix.build>
* Use a font point size of 10 on hidpiaszlig2022-09-052-5/+6
| | | | | | | | | With my new laptop, a font size of 12pt is rather large and given that hidpi displays usually have a quite large resolution (the name might hint at that), we don't necessarily need to use embedded bitmaps anymore which was one of the reasons why I used a point size of 12. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Remove hex and color names highlightingaszlig2022-08-231-0/+5
| | | | | | | | | | | | We only want to highlight #aabbcc-style hex colors and not every damn hex value that happens to be 3 or 4 bytes, which is very annoying when you're doing a lot of bit manipulation. Additionally, I currently have a code base where "gold" is something a player can have, so one doesn't need much imagination on how irritating that is. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/rustfmt: Use Nightly versionaszlig2022-08-231-1/+1
| | | | | | | The config we're baking in by default relies on Nightly features, so it only makes sense to actually use a rustfmt version that supports it. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/sternenseemann/saneterm: fix buildsternenseemann2022-08-161-0/+4
| | | | | Seems like something got more strict about setup hook execution and the relevant env vars for gi weren't set in checkPhase.
* pkgs/vim: Use postFetch instead of extraPostFetchaszlig2022-08-151-3/+3
| | | | | | | | | | | | | | | | We no longer need to use extraPostFetch in order to append stuff to the postFetch phase of fetchzip. Since this got fixed[1], we now get appropriate warnings during evaluation: warning: use 'postFetch' instead of 'extraPostFetch' with 'fetchzip' and 'fetchFromGitHub'. Neither do we like warnings nor do we like to use workarounds from the past that got fixed, so let's fix it on our side as well :-) [1]: https://github.com/NixOS/nixpkgs/pull/173430 Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/profpatsch/deploy: Also create system profileProfpatsch2022-06-271-4/+13
| | | | | | | | | I don’t know how I missed this, but my deploy script didn’t actually set up a system profile, so rebooting would lead to (very) old generations being activated again. Thanks to @sternenseemann for the nix-env trick (via https://code.tvl.fyi/tree/ops/nixos.nix#n55 )
* pkgs/profpatsch/deploy: fix nix ssh linkProfpatsch2022-06-261-1/+1
| | | | idk why/how this works and tbh I don’t even want to know.
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-01 12:40:43 +0000