| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
| |
I only need to run sway and the ssh-agent on a workstation (desktop or
laptop). Start these two processes when the window manager starts.
|
| | |
|
| | |
|
| |
|
|
| |
We need to start the ssh agent (if needed) before we start sway.
|
| |
|
|
|
|
|
|
| |
I keep running into issues when using fish: I'm not familiar with the
syntax and I don't use it enough that it sticks. I also need to google
stuff regularly to figure out how things are supposed to work. This is
annoying enough that the supposed benefits of fish are not worth it for
me.
|
| | |
|
| |
|
|
|
|
| |
A function to create a go project: it creates the git repository, setup
the project using a flake template, create an initial commit, push it
and ensure we can run drone on it.
|
| |
|
|
|
|
|
| |
It's easier to edit / debug / test the code that way.
This also add a new function (`find-ssh-agent') to find or start a new
ssh agent when a shell is started.
|
| |
|
|
|
| |
It's usually needed for developing some rust projects, but this should
be setup by the flake of that project.
|
| |
|
|
| |
I'm not using gerrit anymore.
|
| |
|
|
|
|
|
| |
No need to do this with Go, a python script is fine.
We also don't need to set shell aliases for this: when we install the
tool, we can create symbolic links to `ip2int` and `int2ip`.
|
| |
|
|
|
| |
I don't know why I need to do this, but otherwise I can't build rust
packages with `cargo build' if it's not set ...
|
| |
|
|
|
|
|
|
|
|
|
| |
The pre-commit hook for new lines reported and correct a number of
issues, so let's commit them now and after that we ca enable the hook
for the repository.
Change-Id: I5bb882d3c2cca870ef94301303f029acfb308740
Reviewed-on: https://cl.fcuny.net/c/world/+/592
Tested-by: CI
Reviewed-by: Franck Cuny <franck@fcuny.net>
|
| |
|
|
|
|
|
| |
Change-Id: I394d4cd05ff763aed28e91d86e2905f6ad414336
Reviewed-on: https://cl.fcuny.net/c/world/+/470
Tested-by: CI
Reviewed-by: Franck Cuny <franck@fcuny.net>
|
| |
|
|
|
|
|
| |
Change-Id: I309e378a9cd1871fc84b395a6e077757106d2628
Reviewed-on: https://cl.fcuny.net/c/world/+/463
Tested-by: CI
Reviewed-by: Franck Cuny <franck@fcuny.net>
|
| |
|
|
|
|
|
| |
Change-Id: I03a35a211c7563e65770b39b140099291efafab9
Reviewed-on: https://cl.fcuny.net/c/world/+/458
Reviewed-by: Franck Cuny <franck@fcuny.net>
Tested-by: CI
|
| |
|
|
|
|
|
|
|
|
| |
By moving the aliases to a shared module, they can be used between zsh
and fish.
Change-Id: Ifcfe0af3b90825fe3a67bc1796d4cf65a58d3ff2
Reviewed-on: https://cl.fcuny.net/c/world/+/456
Reviewed-by: Franck Cuny <franck@fcuny.net>
Tested-by: CI
|
|
|
I'm considering trying again fish, and there are a number of things that
should be common between zsh and fish (aliases, environment variables,
...).
Instead of duplicating these settings multiple time, I'm consolidating
the shell configurations under `home/shell`, and I can set the shell I
want to use with `my.home.shell.name`.
The first step is to move the modules for fish and zsh under
`home/shell`, add an interface to pick which one I want to use, and
modify the `host/home.nix` configuration to keep using zsh with the new
interface.
Change-Id: Idb66b1a6fcc11a6eeaf5fd2d32dd3698d2d85bdf
Reviewed-on: https://cl.fcuny.net/c/world/+/455
Tested-by: CI
Reviewed-by: Franck Cuny <franck@fcuny.net>
|
