about summary refs log tree commit diff
path: root/pkgs/aszlig
Commit message (Collapse)AuthorAgeFilesLines
* firefox: Update Tridactyl to version 1.24.0aszlig2024-02-021-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | New features: * A new :reader mode has been added which Tridactyl binds can run on. If you prefer the old mode, it is accessible with :reader --old. We've left gr bound to the old mode for now but you can update it with :bind gr reader * With :set tabsort mru, tab IDs within Tridactyl are now determined by recency of use almost everywhere. This means, e.g. that you can use 2gt to switch to the second most recently used tab (so identical to <C-^>), 3gt to the third most recently used tab, etc. * yq bind added to display current URL as a QR code, with q bind in visual mode. See :text2qr for details * :set keyboardlayoutforce true will now force Tridactyl to use, by default, the US keyboard layout for keybinds, even if you're using a different layout. Useful if you use multiple layouts but don't want Tridactyl binds to move, or if you use a layout such as a Cyrillic one where the default binds are difficult to use. Change the forced layout with :set keyboardlayoutbase * Experimental support for opening arbitrary pages in the sidebar has been added. See :help sidebartoggle and :help sidebaropen for more details * :autocmd and related commands now have completions * :open and related commands now have completions for searchurls and previous searches * Quality of life improvements for tab groups * -x flag added to :hint to exclude CSS selectors from hints * With the command line open, <C-o>t opens a new tab in the background for the selected completion - especially useful with :back completions * :hint -C [selectors] added for custom hint modes while including the default selectors * ;gd rapid hint mode with discarded tabs added * :undo now has fuzzy matching * :source can now read from the command line and the clipboard with --strings and --clipboard * :tab{grab,push} now respect tabopenpos Bug fixes: * :find will now find start from the current viewport * Comments now work in multiline commands in RC files * :editor now works on Gradio apps (please spare me when AI takes over the world) * :winmerge completions are more readable with many windows * :urlincrement now operates on the decoded URI so e.g. %20 doesn't become %21 * ;m and ;M for Google reverse-image search now work again * The midnight theme no longer has a white background in FF102+ * Container colours fixed for FF108+ * gi no longer goes to the start of the search box on Google * modeindicator border is now configurable * Unbindable default binds should no longer be possible * Config should no longer reset when interacting with help page Miscellaneous: * :jsua command added to preserve "user action" intent when using browser binds, needed for triggering certain Web Extension APIs such as browser.sidebarAction.open(). See :help jsua for more information * tri.hinting_content.hintElements function added for advanced usage in :js - see the source for documentation * Groundwork for multi-browser support added * All tests now run using GitHub actions * Docs are now built and hosted on our website * Native messenger now supports Arm-based Macs with :native version at least 0.4.0 * Native messenger 0.4.1 checks %XDG_CONFIG_HOME% on Windows * when_feature.sh [feature] helper script added to repo to find the earliest possible version a feature appeared in Tridactyl Signed-off-by: aszlig <aszlig@nix.build>
* firefox: Update Stylus to version 1.5.45aszlig2024-02-021-2/+2
| | | | | | | | | | | | A lot has changed between 1.5.38, but mostly around the integrated editor (which I don't use) and circumvention of content security policies on certain sites. I might want to drop this plugin at some point, since it does a whole lot more than what I personally want (which is simply: use a different CSS for a *very* small and selected amount of sites). Signed-off-by: aszlig <aszlig@nix.build>
* firefox: Update ff2mpv to version 5.1.0aszlig2024-02-021-2/+2
| | | | | | | | | | | | Most changes are about installing the native messaging app and packaging on various distributions and OS, additionally it also tries to support more browsers. In addition to that, there is now a way to set mpv arguments via the plugin's new options page. We however want to set this via Nix, so I'm completely ignoring that feature and didn't include it in our ff2mpv.py. Signed-off-by: aszlig <aszlig@nix.build>
* firefox: Enable Global Privacy Controlaszlig2024-02-021-0/+1
| | | | | | | | | | | | | | | | | This was introduced in Firefox 120.0 and essentially implements the following specification: https://privacycg.github.io/gpc-spec/ Similar to Do-Not-Track, it implements a header (Sec-GPC) that expresses the persons preference to the site of whether the site may sell/share the browsers interaction. Since Do-Not-Track pretty much is ignored on most sites that formerly adhered to it, I expect a similar fate for GPC, but maybe this time things work out differently (crossing fingers). Signed-off-by: aszlig <aszlig@nix.build>
* firefox: Disable extension updatesaszlig2024-02-021-0/+1
| | | | | | | We're managing extensions via Nix, so there is no need to check whether extension updates are available. Signed-off-by: aszlig <aszlig@nix.build>
* psi: Update to latest masteraszlig2024-01-221-8/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is mainly because of the following build failure that seems to have been fixed upstream: widgets/emojiregistry.cpp: In member function 'EmojiRegistry::Category EmojiRegistry::startCategory(QStringRef) const': widgets/emojiregistry.cpp:40:10: error: 'uint32_t' is not a member of 'std'; did you mean 'wint_t'? 40 | std::uint32_t ucs; | ^~~~~~~~ | wint_t widgets/emojiregistry.cpp:44:9: error: 'ucs' was not declared in this scope 44 | ucs = QChar::surrogateToUcs4(in[0], in[1]); | ^~~ widgets/emojiregistry.cpp:46:9: error: 'ucs' was not declared in this scope 46 | ucs = in[0].unicode(); | ^~~ widgets/emojiregistry.cpp:51:9: error: 'ucs' was not declared in this scope 51 | if (ucs == 0x200d) | ^~~ widgets/emojiregistry.cpp:53:9: error: 'ucs' was not declared in this scope 53 | if (ucs == 0xfe0f) | ^~~ widgets/emojiregistry.cpp:55:9: error: 'ucs' was not declared in this scope 55 | if (ucs <= 0x39 && in.length() > 2 && (ucs >= 0x30 || ucs == 0x2a || ucs == 0x23) && in[1].unicode() == 0xfe0f | ^~~ widgets/emojiregistry.cpp:61:38: error: 'ucs' was not declared in this scope 61 | auto lb = ranges_.lower_bound(ucs); | ^~~ Of course, the second reason is that the current version seems to be way too stable and I want to have a fresh round of new bugs. Signed-off-by: aszlig <aszlig@nix.build>
* vim: Update Nix syntax/indent to latest masteraszlig2024-01-091-2/+2
| | | | | | | | Not only were there a lot of smaller fixes in the meantime, but latest master now properly supports the (not so) new (anymore) path interpolation syntax. Signed-off-by: aszlig <aszlig@nix.build>
* firefox: Update Multi-Account Containers to 8.1.3aszlig2023-12-061-2/+2
| | | | | | | This release just includes fixes for "Firefox Accounts" rebranding, no real feature changes. Signed-off-by: aszlig <aszlig@nix.build>
* firefox: Update Stylus addon to version 1.5.38aszlig2023-12-061-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Changes since 1.5.33 minus bugfixes and CI stuff: * Added an option to use adoptedStyleSheets API (Chrome/ium 73+, Firefox 101+), instead of using DOM elements * Combine style & editor settings * Add an option to update only enabled styles * Auto-retry style finder on network failure * Faster import/undo * Highlight the Save button in unsaved styles * Improve the write-style UI a bit * Show errors when importing the backup * Show instant inject option in Firefox * Speed up opening the manager (a bit) * Speed up opening the multi-sectioned editor with lots of sections * Support fractional numbers with Alt-key increment * Use new userstyles.org API & uso-archive url * Show autosaved draft's css code prior to confirming + auto-remove the autosaved draft when saving * Apply eyedropper color immediately * Open installer for .user.less * Remember all editor options * Remember searchMode in manager The full release notes can be found at: https://github.com/openstyles/stylus/releases Signed-off-by: aszlig <aszlig@nix.build>
* firefox: Fix evaluation with newer nixpkgsaszlig2023-12-061-5/+16
| | | | | | | | | | | | | | | | | | A recent nixpkgs change[1] added an explicit requireSigning attribute, which in turn sets MOZ_REQUIRE_SIGNING to a zero-width string. The change also changed the check in the Firefox wrapper to check whether the browser derivation exposes a requireSigning attribute, which it doesn't. Since I'm busy with other things and just want my machine configuration to evaluate, I quickly worked around this by re-adding the requireSigning (and allowAddonSideload for that matter) to the derivation attributes on our side. [1]: https://github.com/NixOS/nixpkgs/commit/c4c81ac8a219e8725dae514f49c Signed-off-by: aszlig <aszlig@nix.build>
* Revert "firefox: Make FOUC less annoying"aszlig2023-08-091-7/+0
| | | | | | | | | | | | | This reverts commit e868bfeca5501c7c02f1fc1013ea6cc7e79af043. Unfortunately, this causes some sites to be outright unreadable since they seem to rely on a certain set of default colors. Given that the FOUC is already pretty minimal in Firefox, I think it's really not worth breaking a bunch of sites just to get rid of the flashing, at least until we found a better way to prevent it entirely. Signed-off-by: aszlig <aszlig@nix.build>
* pkgs/gpodder: Update to latest upstream masteraszlig2023-08-051-3/+3
| | | | | | | | The latest Git master version contains a bunch of fixes for yt-dlp integration and since most of my feeds are actually YouTube channels, it just makes sense to upgrade. Signed-off-by: aszlig <aszlig@nix.build>
* firefox: Add a few more prefs from Betterfoxaszlig2023-07-191-0/+14
| | | | | | | | | | | | | | | | | I roughly went through the preferences set by Betterfox[1] and checked whether they'd make sense for my Firefox version. While most of these options are pretty straightforward, the captive and connectivity services are features for convenience, eg. when travelling. However, since the only thing they do is giving UI hints that otherwise can be found out via a quick detour to the shell or visiting a random "http://" URL I don't think the convenience outweights repeatedly pinging detectportal.firefox.com. [1]: https://github.com/yokoffing/Betterfox Signed-off-by: aszlig <aszlig@nix.build>
* firefox: Make FOUC less annoyingaszlig2023-07-141-0/+7
| | | | | | | | | | | | | | | | | | Flash of unstyled content[1] is a common issue in browsers and happens whenever transitioning to a page without the full styles being loaded. For the most part, Firefox does a good job preventing FOUC, but in some occasions the default colors still show up. Since I do prefer a dark color scheme anyway, let's actually make sure that the default colors represent a dark color scheme. The reason why I picked the dark colors from startpage.com is purely because it was the next best to pick some colors from, rather than personal preference. [1]: https://en.wikipedia.org/wiki/Flash_of_unstyled_content Signed-off-by: aszlig <aszlig@nix.build>
* psi: Update to latest Git masteraszlig2023-06-022-12/+12
| | | | | | | | | | | | | There is no particular reason for this other than me "feeling" that my version became somewhat old. From looking at the upstream diffs the changes are mostly fixes. However, I also updated the QDarkStyle plugin, which does have quite a few changes and the overall theming now looks lighter than before but still not in a way that feels like an annoyance. We'll see and revert if necessary. Signed-off-by: aszlig <aszlig@nix.build>
* firefox: Update Stylus addon to version 1.5.33aszlig2023-06-021-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Upstream changes from 1.5.26 to 1.5.33: * Add year selector in popup search * Autocomplete fixes * CSSLint: 1.5x faster; supports nested &-selectors and nested @-rules * CSSLint: new color syntax, removed IE6-8 rules * CSSLint: new syntax for nested selectors * Ctrl-/ to toggle line comment will use the standard /* block syntax */ to avoid upstream bugs in less and stylus preprocessors * Don't open installer when browsing a non-raw .user.css URL on github * Editor: allow to change numbers via keyboard/wheel * Editor: autocomplete for less preprocessor will show @ variables * Editor: improvements and fixes for autocomplete * Editor: new option Arrow keys ↑↓ traverse sections * Fix CSP patching, color picker hue overflow, section naming, style size in manager after toggling, dark mode eye dropper * Fixed userstyles.org install button, again * Fixes for Stylus pages in Firefox + dark mode * Fixes for sync * Hide lint errors for @ vars with less preprocessor * New beautify options * New option: toggle .user.css URL installer * Properly update style preview in tab when its config changes * Show installed styles in the list of available styles in the popup finder * Style manager: added multi-column mode option * Style manager: added style size * Style manager: changed Number of applies-­to items option minimum from 1 to 0 * fix: installing github styles in subdirectory inside the repository * fix: styling of iframes in Firefox * fix: styling of same-origin iframes in Chrome * fix: styling of sandboxed iframes in Chrome before 86 * fixed installation on the redesigned userstyles.org * fixed saving of windowed editor position on a non-primary monitor * skip & report invalid styles on import Signed-off-by: aszlig <aszlig@nix.build>
* dnyarri: Switch to gpodder from Gitaszlig2023-06-023-1/+95
| | | | | | | | | I already had the latest Git version laying around in my Nix user profile, so it's battle-tested enough. The main reason why I did this is because it has much better support for yt-dlp, which I prefer to youtube-dl. Signed-off-by: aszlig <aszlig@nix.build>
* 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>
* 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>
* 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"
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-01 13:24:34 +0000