CUPS VS nixos

Apple should be more open about their removals. It isn't clear how this affects their CUPS implementation or PostScript printers https://www.cups.org

CUPS printing server

Apple literally invented CUPS, the most common Unix printing framework in use today. CUPS is the engine for iOS, MacOS, iPadOS, AirPrint, etc. I am really not interested in a debate about whether AirPrint and Apple are crappy systems or are the things to blame with my printer. I know for a fact they are not - because I am a developer and I know how mDNS works, and I know the specific problem my printer has. My Canon printer's operating system has an old, unpatched version of AVAHI that has a lot of problems playing nice with dns-sd and has a known issue with name collisions on it's own interfaces. It's no surprise it doesn't work well with AirPrint for anyone who's familiar with AVAHI.

apple currently maintains CUPS fyi: www.cups.org

With CUPS (http://www.cups.org/) being adopted by main stream companies, I think the software issue will become less glitchy. Hopefully.

In December 2019, Michael left Apple to start Lakeside Robotics. In September 2020 he teamed up with the OpenPrinting developers to fork Apple CUPS to continue its development. Today Apple CUPS is the version of CUPS that is provided with macOS® and iOS® while OpenPrinting CUPS is the version of CUPS being further developed by OpenPrinting for all operating systems.

I noticed that there was an update to Big Sur — the newest OS that this machine can run — which I had missed, so I installed it, and the files went away!

I also noticed that there has been issues, like https://github.com/apple/cups/issues/5538, related to spool file clean-up. (The fix to that one leaves some decidedly fishy-looking parentheses, but they were fixed in a later commit.)

... or unless Apple shipped a buggy version of CUPS: https://github.com/apple/cups/issues/5747

This isn’t entirely true. There’s Apple CUPS (which is now focused on macOS/iOS) and OpenPrinting CUPS, which is used by Linux/other systems.

I don't know. Have been using colorbuddy for ages now and it has always done exactly what I want. I don't need the "instant reaload" that lush advertices, doing :source on the colorscheme file, does the same for me to preview changes instantly. This is my theme, in case you need something to start with: - https://github.com/pinpox/nixos/blob/main/home-manager/modules/nvim/lua/config/pinpox-colors.lua

I use this to serve a directory temporarily.

I can't remember why I put that workaround in there, might not be needed any more. The above config is part of my dotfiles, I use my Bose blueutooth headphones by connecting them via the blueman-applet if the don't pair automatically

Yep, I have two different modules with defaults for server and for desktop. Host-specific settings are set in the according /machines//configuration.nix file. Most stuff is modularized into modules that can be reuesed and enabled at will.

You can find all my configs here

Yep, I'm using the toJSON function already. The problem I had, was that not all applications use JSON as configuration format. Also the nix code gets very long, if you have to write the whole template as a string, which I find quite unreadable. Mustache is a pretty simple frequently used templating language, here is an example template that get's rendered by the nix code above.

https://github.com/pinpox/nixos/blob/main/home-manager/modules/awesome.nix https://github.com/pinpox/dotfiles-awesome

My system uses a uniform colorscheme defined here. Configs for all applications I use read that and use the same colors. The wallpapers are randomly generated by a tool I wrote, it also automatically matches the colorscheme. Icons and symbols are colored the same way for awesomeWM.

In case you are interested I use this and this to generate colorschemes, awesome config and a matching wallpaper

Check out wezterm it has replaced tmux for me. Very active development, fast and just the right amount of features for my taste. It is configured in Lua, so if you are doing that for neovim already, it's another plus. I use it in combination with awesomeWM. My (not very special) config is here if you need something to start with.