Migrate to chezmoi

Move config files from config to chezmoi
Add script to auto install packages with DNF and Cargo

chezmoi/dot_config/tmux/plugins/tmux-continuum/docs/automatic_start.md

@@ -0,0 +1,47 @@
+# Automatic Tmux start
+
+Tmux is automatically started after the computer/server is turned on.
+
+### OS X
+
+To enable this feature:
+- put `set -g @continuum-boot 'on'` in `.tmux.conf`
+- reload tmux config with this shell command: `$ tmux source-file ~/.tmux.conf`
+
+Next time the computer is started:
+- `Terminal.app` window will open and resize to maximum size
+- `tmux` command will be executed in the terminal window
+- if "auto restore" feature is enabled, tmux will start restoring previous env
+
+Config options:
+- `set -g @continuum-boot-options 'fullscreen'` - terminal window
+  will go fullscreen
+- `set -g @continuum-boot-options 'iterm'` - start [iTerm](https://www.iterm2.com) instead
+  of `Terminal.app`
+- `set -g @continuum-boot-options 'iterm,fullscreen'` - start `iTerm`
+  in fullscreen
+- `set -g @continuum-boot-options 'kitty'` - start [kitty](https://sw.kovidgoyal.net/kitty) instead
+  of `Terminal.app`
+- `set -g @continuum-boot-options 'kitty,fullscreen'` - start `kitty`
+  in fullscreen
+- `set -g @continuum-boot-options 'alacritty'` - start [alacritty](https://github.com/alacritty/alacritty) instead of `Terminal.app`
+- `set -g @continuum-boot-options 'alacritty,fullscreen'` - start `alacritty`
+  in fullscreen
+
+Note: The first time you reboot your machine and activate this feature you may be prompted about a script requiring
+access to a system program (i.e. - System Events). If this happens tmux will not start automatically and you will need
+to go to `System Preferences -> Security & Privacy -> Accessability` and add the script to the list of apps that are
+allowed to control your computer.
+
+### Linux
+
+Help with this would be greatly appreciated. Please get in touch.
+
+#### Systemd
+
+##### this will only start the tmux server, it will *not* start any terminal emulator
+
+To enable automatic start with systemd:
+- Put `set -g @continuum-boot 'on'` in `.tmux.conf`
+- reload tmux config with this shell command: `$ tmux source-file ~/.tmux.conf`
+- see [systemd](/docs/systemd_details.md) for more details about how this is implemented

chezmoi/dot_config/tmux/plugins/tmux-continuum/docs/continuum_status.md

@@ -0,0 +1,17 @@
+## Continuum status in tmux status line
+
+There is an option to display current status of tmux continuum in tmux status
+line. This is done via `#{continuum_status}` interpolation and it works with
+both `status-right` and `status-left` tmux native options.
+
+Example usage:
+
+    set -g status-right 'Continuum status: #{continuum_status}'
+
+When running, `#{continuum_status}` will show continuum save interval:
+
+    Continuum status: 15
+
+or if continuous saving is disabled:
+
+    Continuum status: off

chezmoi/dot_config/tmux/plugins/tmux-continuum/docs/faq.md

@@ -0,0 +1,45 @@
+### FAQ
+
+> Will a previous save be overwritten immediately after I start tmux?
+
+No, first automatic save starts 15 minutes after tmux is started. If automatic
+restore is not enabled, that gives you enough time to manually restore from a
+previous save.
+
+> I want to make a restore to a previous point in time, but it seems that save
+is now overwritten?
+
+Read how to [restore a previously saved environment](https://github.com/tmux-plugins/tmux-resurrect/blob/master/docs/restoring_previously_saved_environment.md)
+
+> Will this plugin fill my hard disk?
+
+Most likely no. A regular save file is in the range of 5Kb. And `tmux-resurrect` already has a `remove_old_backups()` routine that will ["remove resurrect files older than 30 days, but keep at least 5 copies of backup."](https://github.com/tmux-plugins/tmux-resurrect/blob/da1a7558024b8552f7262b39ed22e3d679304f99/scripts/save.sh#L271-L277)
+
+> How do I change the save interval to i.e. 1 hour?
+
+The interval is always measured in minutes. So setting the interval to `60`
+(minutes) will do the trick. Put this in `.tmux.conf`:
+
+    set -g @continuum-save-interval '60'
+
+and then source `tmux.conf` by executing this command in the shell
+`$ tmux source-file ~/.tmux.conf`.
+
+> How do I stop automatic saving?
+
+Just set the save interval to `0`. Put this in `.tmux.conf`
+
+    set -g @continuum-save-interval '0'
+
+and then source `tmux.conf` by executing this command in the shell
+`$ tmux source-file ~/.tmux.conf`.
+
+> I had automatic restore turned on, how do I disable it now?
+
+Just remove `set -g @continuum-restore 'on'` from `tmux.conf`.
+
+To be absolutely sure automatic restore doesn't happen, create a
+`tmux_no_auto_restore` file in your home directory (command:
+`$ touch ~/tmux_no_auto_restore`). Automatic restore won't happen if this file
+exists.
+

chezmoi/dot_config/tmux/plugins/tmux-continuum/docs/multiple_tmux_servers.md

@@ -0,0 +1,20 @@
+### Behavior when running multiple tmux servers
+
+(This is safe to skip if you're always running a single tmux server.)
+
+If you're an advanced tmux user, you might be running multiple tmux servers at
+the same time. Maybe you start the first tmux server with `$ tmux` and then
+later another one with e.g. `$ tmux -S/tmp/foo`.
+
+You probably don't want to "auto restore" the same environment in the second
+tmux that uses `/tmp/foo` socket. You also probably don't want two tmux
+environments both having "auto save" feature on (think about overwrites).
+
+This plugin handles multi-server scenario by giving precedence to the tmux
+server that was first started.
+
+In the above example, the server started with `$ tmux` will do "auto
+restore" (if enabled) and will start "auto saving".
+"Auto restore" or "auto saving" **will not** happen for the second server that
+was started later with the `$ tmux -S/tmp/foo` command. The plugin will
+detect the presence of another server (`$ tmux`) and give it precedence.

chezmoi/dot_config/tmux/plugins/tmux-continuum/docs/systemd_details.md

@@ -0,0 +1,13 @@
+# Systemd automatic start for tmux
+
+The first time tmux starts when `@continuum-boot` is set to 'on' tmux-continuum will generate a user level systemd unit file which it will save to `${HOME}/.config/systemd/user/tmux.service` and enable it. From then on when that user logs in, either through a GUI session or on the console or via ssh, Systemd will start the tmux server.
+
+The command used to start the tmux server is determined via the `@continuum-systemd-start-cmd` option that can be set in .tmux.conf. (Remember to reload your configuration with `tmux source ~/.tmux.conf` afterwards.
+
+The default command to use is `new-session -d`. If you want more control over what sessions get started then you should set up your sessions in tmux.conf and set `@continuum-systemd-start-cmd = 'start-server'`. As this will be executed as part of systemd's ExecStart statement there will be no shell parsing. See [Systemd manual](http://www.freedesktop.org/software/systemd/man/systemd.service.html#Command%20lines) for more details.
+
+To control the tmux service you can use all the standard `systemctl` commands using the `--user` argument. eg to see if the tmux server has started:
+
+  systemctl --user status tmux.service
+
+