eliasnorrby / dotfiles

:computer: Dotfiles for development on MacOS and Manjaro

Hi 👋, I'm Elias

I like building applications & automating chores.

I'm excited about...

kubernetes openshift tekton terraform quarkus zsh
argocd kafka ansible maven react gatsby typescript manjaro
tmux bspwm sxhkd git alacritty

---

dotfiles's Issues

Switch to GitHub actions for CI

I don't understand what the deal is with MacOS builds on travis-ci.com any more.

Make use of config imports for Alacritty

There are a number of settings in Alacritty that are platform specific (e.g. window.decorations: buttonless). I can make use of the config imports feature (to be released in 0.6.0) to source a alacritty.local.yml file with overrides. I may even be able to externalise font, theme and opacity settings to a file outside of version control, with defaults contained in the main file...

Make topic tasks aware of topic state

vscode's complete and utter lack of configuration as to where to put
the user settings files forces its tasks to be run before linking
files. To be specific, linking settings.json to
~/Library/Application Support/Code/User fails, becuase that directory
does not exist, so I set up a topic.tasks.yaml that ensures the
directory exists - but as of now, topic tasks are run as the last step
of the playbook.

In order to remedy this, I have experimented with running topic tasks
(known as 'post provision tasks') before the linking stage. In order
for this to work reliably, the tag do_post_provision, that at this
moment is required to trigger topic task execution, should be removed.

This in turn questions the connotations 'post provisioning' has.
Existing tasks (namely for zsh and emacs) are not per se required
to run post provision - they can just as well be run before the
linking stage. They are merely "tasks that need to be run for the
topic to function properly".

Removing the tag also highlights an issue with the topic task execution
in general: tasks are not available of topic state. If topic execution
is enabled with the tag, all topic.tasks.yaml files are sourced, and
all tasks are executed, regardless of their corresponding topic's state.
Removing the tag makes this issue even more prevalent - every run
of the playbook (every boom deploy) will include these tasks.

I suggest removing the notion of post_provision_tasks altogether.
Topic tasks may be tied to topic state using a when clause for
topics.<group>.<name>.state = 'present'. This is a bit awkward, but
the best I can think of now.

This would require a change or deprecation in
[https://github.com/eliasnorrby/dotfiles-cli](the dotfiles cli) as well.

Issue tracking vscode config file location setup:
microsoft/vscode#3884

Spicetify config

On arch, I have used Spicetify to customize the spotify UI. The settings are not yet under version control.

Varmilo Fn keys always trigger media keys

With Varmilo keyboards (on Arch, at least), hitting function keys (F1-F12) will always register as media keys.

This stackoverflow post describes the problem

The solution linked seems to work.

However, at this moment, I'm more interested in using the media keys than the function keys, so I'll stick with it.

Dependabot couldn't find a package.json for this project

Dependabot couldn't find a package.json for this project.

Dependabot requires a package.json to evaluate your project's current JavaScript dependencies. It had expected to find one at the path: /package.json.

If this isn't a JavaScript project, or if it is a library, you may wish to disable updates for it from within Dependabot.

View the update logs.

Set up a Python virtual environment

Updates to python and dependencies installed with pip often break the build. Can I set up a virtual environment to solve these issues?

• molecule
• docker
• ansible-lint
• flake8

Use editorconfig for shfmt configuration

Background

shfmt will ignore settings specified in .editorconfig when run using input from stdin (as is the case when formatting a buffer in vim using coc and diagnostic-languageserver). This issue is described in detail in mvdan/sh#577.

A -filename flag is planned for release in version 3.2.0. Until it is released, settings for shmft are duplicated in .editorconfig and coc-settings.json.

To do

When the new version is released, update coc-settings.json to pass the new flag, i.e.

"diagnostic-languageserver.formatters": {
  "shfmt": {
    "command": "shfmt",
-   "args": ["-i", "2", "-bn", "-ci", "-kp"]
+   "args": ["-filename", "script.sh"]
  }
},

nvm prefix incompatibility

nvm is incompatible with setting a prefix for npm.

I want to set a prefix to allow global package installations for my user without admin privileges.

Can I use the path parameter of the ansible module to get the best of both worlds?

Make post-install script aware of topic state

The post-install.zsh does some one-off tasks related to certain topics, as of now:

• zsh plugins
• vim plugins
• doom emacs refresh
• vscode plugins

It would best if each step could run conditionally based on each topic's state.

I could use yq to parse the root config before each step. But since these are very core modules, I don't expect I'll be disabling them any time soon, so this is not a priority.

Add OS filtering option to links

Which files to link where may depend on the OS (e.g. VSCode configs), or I may want to use a different source on different platforms.

links:
  - src: somefile.sh
    os: "MacOSX"

Todo:

• Update link-topic.yml
• Check if unlink-topic.yml will require updates as well

Set up coc-pyright

coc-python is no longer actively maintained. I should set up coc-pyright instead. But I rarely write python, so no rush.

Put GTK theme config under version control

Steps:

• clone https://github.com/EliverLara/Juno @ branches for selected themes
• unzip to ~/.themes or alternative
• link gtk-3.0/settings.ini