drpyser / configs Goto Github PK

And maybe make sure restarting bspwm forces restart of other X applications(polybar, sxhkd, ...).

• htop
• root shell terminal
• nix repl
• package updates available
• other status windows?

See https://github.com/baskerville/bspwm/tree/master/examples/receptacles .

Using receptacles and rules, a script can create application windows in the right layout and desktops.

https://github.com/rycee/home-manager

Equivalent of system nix configuration, for user home management.

Currently, each top level directory is a set of files that define a set of configurations. Eventually, different (conflicting) sets of configurations could be desired, if different setups are to be experimented, or to version configurations for differnet machines.

To support different, independent sets of configurations,

• add a top layer in the file hierarchy, each root directory containing the configurations for a particular machine.

Alternative configurations for the same machine could be supported in multiple ways:

• git branches
• different roots, e.g. x86-64-nixos-bspwm, x86-64-nixos-i3, x86-64.ubuntu.gnome, ...

Alternatively, or complementary, the definition of a set of configurations for a particular machine state(the "recipe") could be managed separately from the configurations themselves, for example using a script or some declarative tooling(e.g. vagrant, foreman, ansible/chef/puppet/salt).
The configurations could be organized arbitrarily, and the build script would refer to the configuration assets it requires from the repository.

http://man7.org/linux/man-pages/man8/fstrim.8.html
Not sure how much necessary/valuable this is.

window selection is currently implemented through a small python script: https://github.com/DrPyser/configs/blob/master/home/bin/select_window.py

This uses dmenu to provide a list of all windows by title(prepended with an index to help disambiguate between windows with the same title). This works pretty well.

Alternatively, It could be interesting to support window/node selection using custom tags, as with i3's mark feature: https://i3wm.org/docs/userguide.html#vim_like_marks .
It seems to me this would require storing window tag information separately, and implementing command(s) to manipulate that data. Basically, a small wrapper around an sqlite table or equivalent storage backend(e.g. in-memory key/value store). see baskerville/bspwm#1049 .

Alternatively, using intuitively named desktops, and dynamic desktop management, could also help window selection(i.e. web browser windows always go to a web desktop, ...).

bspwm window state and flags are shown in polybar, to the right of the workspaces.
Currently, they are shown as letters:

The --dotfiles options to GNU stow doesn't work well when the target directory exist, it seems.

aspiers/stow#33

Until the issue is resolved, I'll just keep the dotfiles/dot-directories as they are and avoid using the option.

https://nixos.wiki/wiki/NixOS:extend_NixOS