about summary refs log tree commit diff
path: root/pkgs/aszlig
Commit message (Collapse)AuthorAgeFilesLines
* 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/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-111-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* 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/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>
* 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/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/vim: Fix elflord color themeaszlig2022-06-222-7/+108
| | | | | | | | | | | | | I know, I know, people don't like the color scheme I use, but I got so used to it and with the new version generated via ColorTemplates it messes with me being used to elflord with 16 terminal colors instead of the GUI colors. So this patches elflord in such a way that it's consistent with what I want but still uses the new ColorTemplates version, which for example comes with nicer colors for vimdiff. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/rustfmt: Fix patching in default configaszlig2022-04-132-4/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | The patch file was relative to the rustfmt crate within the rustc source tree, so I added "-d src/tools/rustfmt" as patchFlags to apply the patch against that subdirectory. Unfortunately, patchFlags also applies to other patches as well and I didn't account for that. With current rustfmt from rustc 1.59.0 we have a patch in nixpkgs, which now fails to apply because of this: applying patch /nix/store/...-rustfmt-fix-self-tests.patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/src/tools/rustfmt/src/ignore_path.rs |+++ b/src/tools/rustfmt/src/ignore_path.rs -------------------------- File to patch: Skip this patch? [y] Skipping patch. 1 out of 1 hunk ignored To fix this, I changed the paths in config.patch to be relative to the rustc tree rather than just the rustfmt crate, so the patch should now apply regardless of whether there are other patches. Signed-off-by: aszlig <aszlig@nix.build>
* gopass: Rebase color patch against version 1.14.0aszlig2022-04-011-4/+4
| | | | | | | The patch no longer applies because some of the imports got changed in the context of the diff. Signed-off-by: aszlig <aszlig@nix.build>
* psi: Update to latest upstream masteraszlig2022-03-242-23/+23
| | | | | | | | | | | The version from 2021 certainly is way too old for my desire to crave new bugs, so let's update it for no particular reason other than gut feeling. Oh, well and of course I saw a bunch of OMEMO plugin fixes, so maybe if you search hard enough you'll find compelling reasons... :-D Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Add rustfmt with custom default configaszlig2022-02-094-1/+63
| | | | | | | | | | | | | | | | | | | | | | | | Since I do have a lot of projects where I use rustfmt, it gets pretty tedious to manually run "cargo fmt". Using g:rustfmt_autosave should make this less tedious but it might annoy me in the future, let's see. In addition to setting rustfmt I also added a default path for rustc, which is used whenever there is no rustc in path. This is because I usually switch between several projects which use different Rust versions and this way it will use the rustc version that is in PATH during "nix develop". For the rustfmt part I also added a small default configuration which represents my opinion on how I think Rust code should be formatted. The file is used whenever a project doesn't have a "rustfmt.toml" or ".rustfmt.toml". Unfortunately, RustFmt is broken in Vim right now[1], so I'm using the upstream project until the issue has been resolved. [1]: https://github.com/rust-lang/rust.vim/issues/446 Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/psi: Fix reference to libgpg-erroraszlig2021-10-101-2/+2
| | | | | | | | | | This has been renamed[1] to reflect the upstream name and since there is no alias for the old name, we need to rename it as well to avoid evaluation errors. [1]: https://github.com/NixOS/nixpkgs/commit/41574158a07f3c6ab5853b316c2fe7ed18e6354b Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Update tlib plugin to latest masteraszlig2021-09-301-2/+2
| | | | | | | | | | | | | Since Vim version 8.2.3141, the following error is raised during startup: Error detected while processing .../share/vim/vim82/plugin/02tlib.vim: line 109: E1208: -complete used without allowing arguments The latest version of the tlib plugin provides a fix for the above error, so I'm updating it to latest master. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Fix color for LightBlue in color schemeaszlig2021-07-271-0/+1
| | | | | | | | | | | | If we use 256 color mode in XTerm, using LightBlue in Vim results in 0x5fd7ff but LightBlue in GUI mode will use 0xadd8e6 which has a low contrast to the default color (0xbebebe). Since my eyes are not getting better with age, I decided to go with the old color code that provides better contrast even though I'm quite happy with the rest of the "more nuanced" colors. Signed-off-by: aszlig <aszlig@nix.build>
* 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>
* 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>
* treewide: Replace pkgconfig with pkg-configaszlig2021-06-161-2/+2
| | | | | | | | | | | | | | 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"
* 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>
* treewide: stdenv.lib -> pkgs.libProfpatsch2021-02-052-4/+4
| | | | Upstream is deprecating `stdenv.lib`, so let’s do the same.
* Revert "aszlig/gopass: Downgrade to version 1.9.2"aszlig2021-01-272-45/+12
| | | | | | | | | | | | | | | | | | | | | | | This reverts commit 7b8164be35c9d82d6e7389a407150a9128f7fb0c. From the upstream changelog: > This is an important bugfix release that should resolve several > outstanding issues and concerns. Since 1.10.0 was released was engaged > in a lot of discussions and realized that compatibility is more > important than we first thought. So we're rolling back some breaking > changes and revise some parts of our roadmap. We will strive to remain > compatible with other password store implementations - but remember > this is a goal, not a promise. This means we'll continue using > compatible secrets formats as well as GPG and Git. As mentioned in the original commit, I'm still not entirely convinced that my use case has a future with gopass, their decision to roll back some of the breaking changes at least makes it possible for me to upgrade to the latest upstream version without the fear of being locked in into some gopass-specific format. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/psi: Keep urgency hint indefinitelyaszlig2020-12-202-0/+14
| | | | | | | | | | | | | | | | | | | | | | One thing that has annoyed me since quite a while but ultimately didn't fix yet, was that the urgency hint was only set for one millisecond. I don't know how this would look like in a desktop environment, but in my environment the corresponding workspace only flashes red and then turns back to blue (the default color) whenever I get a new message. Since I do not constantly switch to Psi to check whether there is something new, I sometimes responded very late to messages even though I didn't want to (eg. not actively working on something). Of course, I also don't want to be interrupted when I'm actually in zone, but luckily the way urgency hints are displayed in my environment is pretty unobtrusive and there is no flashing, blinking or even sounds. So the only difference is that I do not need to switch to Psi anymore, to check whether there are new messages. Signed-off-by: aszlig <aszlig@nix.build>
* profiles/base: Add helper for showing last Nix logaszlig2020-12-102-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | | This is a common pattern I encounter on a daily basis, which involves copy & pasting the store path of a failed build to "nix log". Now the same is just a matter of running "nlast" and we get rid of the useless copy & paste. The way we do this does have a small goof: Using mtime (or really any time, other than atime, which commonly is disabled) is not going to work if we *repeat* an older Nix build, since this will only change the log file but the prefix directory will be unchanged. Since addressing this goof would most likely result in iterating through *all* log files, I'm not doing it since I think it doesn't occur very often in practice. If I happen to be wrong on that, we could still go for the heavyweight solution. Also, I went for implementing this in Python instead of a shell script, because the latter would not only be less readable but also way slower since we need to either fork out for every stat command or use ls and head to figure out the newest file. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/psi: Update to latest upstream masteraszlig2020-12-041-5/+20
| | | | | | | | | | | No particular reason, other than current Psi version "feeling" too old and I'm feeling somewhat adventurous. The usrsctp library is now needed for Jingle, so I added a small build of it directly from master as well. Who wants old release versions, right? Signed-off-by: aszlig <aszlig@nix.build>
* programs/vim: Add syntax highlighting for GDScriptaszlig2020-12-041-0/+7
| | | | | | | | | Added this when contributing to a GDScript project and since I know a few persons who implement their games using Godot, I might need to write GDScript at some point in the future again, so the syntax highlighting plugin comes in handy. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/librxtx-java: Fix build with newer JDKaszlig2020-10-221-2/+8
| | | | | | | | | | | | | | This is actually needed to build the axbo program, which I have rarely used during the past years. However, I'm not absolutely sure that I won't be using this again so I decided to fix it, since all that needed to be done is take an additional patch from Debian that fixes compatibility with newer JDK versions. Since the patch changes configure.in and Makefile.am, we need to regenerate all the files for autotools as well and since there were old m4 files laying around I deleted them in preAutoreconf. Signed-off-by: aszlig <aszlig@nix.build>
* aszlig/gopass: Downgrade to version 1.9.2aszlig2020-09-171-5/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Version 1.10.X switches the default to new MIME-based format which breaks interoperability with pass and other implementations. I'd gladly switch to that format, but the 1.10.0 changelog also announces plans to remove support for GnuPG and Git in the long term: > The goal is to remove the support for multiple backends and any > external dependencies, including git and gpg binaries. GnuPG and Git support is the reason why I started using pass and ultimately switched to gopass. If the latter stops being a viable password manager, switching back to pass will be much harder with the new MIME format. There is also an upstream issue[1] about this and while I haven't read through *all* the comments, other people seem to have similar reasons for switching to gopass. So far however I'm not convinced that my use case will have a future with gopass, so I'll stay at 1.9.x until I've had the time to properly research other options or maybe even stay with gopass (and go all-in with the new MIME format). [1]: https://github.com/gopasspw/gopass/issues/1365 Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/vim: Add syntax/indent plugin for Fluentaszlig2020-08-141-0/+7
| | | | | | | | | | | | For translations there is a nice web interface called Pontoon[1], which should it make conventient to edit translations. However, for developers like me I'd call this quite inconvenient, so I need a Vim plugin to make it at least more pleasing to look at :-) [1]: https://github.com/mozilla/pontoon Signed-off-by: aszlig <aszlig@nix.build>
* vim: Update Nix addon to latest masteraszlig2020-08-081-2/+2
| | | | | | | | | | | | While being at it, let's bump the Nix syntax/indentation plugin to the latest version, since there are a few quirks that were annoying me since quite a while but I was too lazy to actually fix. I haven't checked whether the latest version fixes these quirks since I don't know them on top of my head, but if it doesn't I surely will stumble on them soon enough. Signed-off-by: aszlig <aszlig@nix.build>
* vim: No longer set termencoding to "ascii"aszlig2020-08-081-1/+0
| | | | | | | | | | So far I had termencoding set to "ascii", because my terminal was only really able to display ASCII characters and nothing else. Since this is no longer the case, we can also get rid of this restriction in my Vim configuration. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/aszlig: Add Mutt configurationaszlig2020-08-082-1/+224
| | | | | | | | | | | | | | | | | | I've been using this configuration since years already but so far it has been residing in ~/.muttrc and I copied to new machines accordingly. The reason why I didn't add it here was because the config was too ugly and I never got so far as to properly re-do it. Unfortunately, the config is still ugly as hell, but at least we now generate it from a structured Nix format and also the IMAP/SMTP user and server infos are now retrieved via gopass instead. This also includes my small prank multipart/alternative filter, which should hopefully "encourange" recipients to disable HTML parsing/rendering. Signed-off-by: aszlig <aszlig@nix.build>
* gopass: Drop patch for using ASCII symbols onlyaszlig2020-08-082-18/+0
| | | | | | | | With the switch to a proper Unicode capable font, we no longer need to patch gopass and simply can now enjoy a proper tree view and also one less patch to maintain. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/psi: Increment date in version numberaszlig2020-08-071-1/+1
| | | | | | | | | | | | | | | I really don't have a lot of other things to blame for forgetting this in the first place, but let's just assume that the temperatures here right now are higher than I'm used[TM] to and thus my brain wasn't working. On the other hand while writing this I also took a peek and aparently it's around 20 degree celsius right now, which would be... well... ... okay, I just forgot about that and I feel ashamed now. Go on! Nothing to read here! Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/psi: Update to latest upstream masteraszlig2020-08-073-55/+22
| | | | | | | | | | | | | | | | The latest master version no longer crashes on Jingle file transfer requests. So alongside updating to the latest Git version, I also dropped the patch disabling Jingle. Another reason for updating is simply because the client version already feels old (heck, it's been February since the last update) and I'm really craving for fresh new bugs. I rebased the patch for the default configuration against current master with no changes in configuration (only obsolete stuff removed) and fixed the move of the src/plugins directory to the project's root directory. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/aszlig/xournal: Switch to xournal++aszlig2020-05-213-90/+1
| | | | | | | | | | | | | The patch I added to xournal was for keeping the aspect ratio when annotating PDFs with images. However, looking at xournal++ the aspect ratio is kept by default when resizing via corners so the patch is not needed. Since I don't really care a lot whether it's xournal or xournal++ and as long as it does the very little things I intend to use it for, I don't mind if it has too many features for my taste. Signed-off-by: aszlig <aszlig@nix.build>
* gopass: Rebase pager colour patch against v1.9.0aszlig2020-05-081-9/+9
| | | | | | | | The import list of list.go has changed upstream, so the rebase of this patch doesn't change anything in its functionality but just makes sure that it applies against gopass version 1.9.0. Signed-off-by: aszlig <aszlig@nix.build>
* vim: Add vim-css-color pluginaszlig2020-05-081-1/+12
| | | | | | | | | | | | | This is quite useful in CSS files and others to directly highlight the colours in the actual colour value rather than with the generic colour of the syntax file. To make sure we don't break the after/syntax files for Haskell and HTML, I also changed the way we install those files in the output directory so that if a file already exists, it is appended to rather than overwritten. Signed-off-by: aszlig <aszlig@nix.build>
* vim: Remove file artifacts for ATS syntax pluginaszlig2020-05-081-2/+3
| | | | | | | | | | | We essentially only want to have the ftdetect and syntax files, everything else is just cruft that is not in any way related to Vim. Ideally we want to do a whitelist approach instead of the "remove everything unneeded" we're doing right now, but since I don't want to refactor the whole Vim expression I'll leave it the dirty[TM] way. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/psi: Temporarily disable Jingle sessionsaszlig2020-02-102-0/+13
| | | | | | | | | | | | | | | When getting an incoming file transfer, Psi has crashed a while ago and I unfortunately don't remember the exact details. However, since those stanzas are going to be re-delivered every time we start Psi again, I'd like to debug this in an isolated environment rather than being more or less forced to stay unavailable (especially annoying if someone is trying to send a file and then you stay offline for hours). So until I get to debugging this and ideally also test this in an automated fashion, I'll disable it for now since I'm not using Jingle sessions at the moment. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/psi: Update to latest upstream masteraszlig2020-02-104-50/+50
| | | | | | | | | | | Updating to latest master fixes one of the most annoying theming issue where the chat message input box text will turn black on dark background for my custom Qt theme. There are also quite a lot of fixes in master (which is still unreleased), which we want to have as well. Signed-off-by: aszlig <aszlig@nix.build>
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-01 19:29:02 +0000