home-manager-config.git - My personal home manager configurations.

	Commit message (Collapse)	Author	Age	Lines
*	feat(communication/neomutt): reworked the email syncing	Arpit Chakladar	11 days	-15/+15
\| \| \| \| \| \| \| \|	Now we have the ability to map each folder on the remote server with a folder with an arbitrary name in the local server. Each folder gets its own channel with quick and full variations where the quick only download the new emails from the remote to the local and full makes a sync both ways.
*	chore(communication/neomutt): minor file renaming	Arpit Chakladar	2026-09-24	-1/+1
\|
*	refactor(naming): use kebab-case option names and consistent gopass secret ↵	Arpit Chakladar	2026-09-24	-1/+1
\| \| \| \|	naming
*	chore: removed all raw string configurations options in favor of files	Arpit Chakladar	2026-09-19	-4/+3
\| \| \| \| \| \| \| \|	Moved all configurations which were previously raw strings chunks, for options that the home-manager options didn't provide, into files for that specific configuration and reading there contents instead (with string replacement for passing information from the rest of the configuration).
*	fix(communication/neomutt): fixed mbsync syncing with different modes	Arpit Chakladar	2026-09-18	-1/+0
\| \| \| \| \| \|	Now there are two channels created for every account quick and full variants, quick only gives new emails and full does the whole sync. neomutt-sync can now be told which channel to use to sync with.
*	feat: Rewrote neomutt keybindings, updated comments	Arpit Chakladar	2026-08-05	-1/+1
\| \| \| \| \|	- Rewriting the neomutt keybindings by hand - Updated comments to be simpler
*	feat: added example to use pgp signing of emails, fixed browserpass	Arpit Chakladar	2026-08-02	-1/+1
\| \| \| \| \| \| \| \|	- Added example on how to enable pgp signing on gmail email accounts - The programs.browserpass.enable option only used extension ids for the actual extensions not for the custom extension key we gave it. So we are updaing the com.github.browserpass.native.json file to manually add our own extension id to it
*	feat: fixed chromium extension ids, duplicate sent emails, etc	Arpit Chakladar	2026-08-02	-0/+1
\| \| \| \| \| \| \| \| \| \| \|	- Every home-manager switch had a change to change the ids of the extensions, now we get the same extension id for any build of the given extension - Sending emails from neomutt send duplicate emails, it is now fixed - Auto re-registering in usque-warp connect, as it gets deactivated in about 24 hours - Using a style.mustache.css for the waybar css configs for syntax highlighting
*	refactor(neomutt): just some whitespace formatting	Arpit Chakladar	2026-07-18	-1/+0
\|
*	refactor: standardize file-level comments, drop unused pkgs, and theme ↵	Arpit Chakladar	2026-07-17	-0/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	lazygit with base16 - Move inline comments to top of file across all modules for consistent style - Add descriptive comments to files missing them (aggregators, assertions, scripts, flake) - Remove unused `pkgs` parameter from i3/keybindings.nix and zathura/default.nix - Drop explicit `package = pkgs.zathura` (home-manager provides the default) - Delete stale meli-sync.sh (migrated to neomutt) - Remove extraneous blank lines for consistent formatting - Theme lazygit with config.scheme base16 colors instead of hardcoded names
*	feat: reworked the structure for communication/neomutt	Arpit Chakladar	2026-07-15	-0/+45
	Using neomutt as the module for email instead of just "email" as used previously. "email" was ambigious in that it was too vague on what it was supposed to do with email, now neomutt clearly specifies that we plan to use neomutt as our email client. However mbsync and notmuch are still used under the hood that is not reflected in the module name "neomutt". This is fine as they only serve the purpose of downloading and querying the emails which may be considered a background feature.