Conversation
|
Fixes #9 |
| !URxvt.font: xft:Anonymous Pro Minus:style=Regular:dpi=109:size=12 | ||
| !URxvt.font: xft:Fantasque Sans Mono:style=light:dpi=163:size=11 | ||
| URxvt.font: xft:Roboto Mono:style=light:dpi=109::size=12 | ||
| !URxvt.font: xft:Roboto Mono:style=light:dpi=109::size=10 |
There was a problem hiding this comment.
Changed to Anonymous as Roboto Mono is on the AUR.
| urxvt.matcher.button: 3 | ||
|
|
||
| urxvt.letterSpace: -1 | ||
| urxvt.letterSpace: 0 |
There was a problem hiding this comment.
+1 This setting caused some weird rendering issues for me 😛
| tags: | ||
| - awesome | ||
|
|
||
| - name: Clone github.com/NuckChorris/assault |
| tags: | ||
| - awesome | ||
|
|
||
| - name: Clone github.com/NuckChorris/assault |
| repo: "https://github.com/majutsushi/urxvt-font-size.git" | ||
| version: master | ||
|
|
||
| - name: Link .config/awesome/lain |
| dest: "~/bin" | ||
| state: link | ||
|
|
||
| - name: Link bin/ |
There was a problem hiding this comment.
Duplicate task here as the one just above?
| xrandr --auto | ||
| xrdb ~/.Xresources | ||
|
|
||
| awesome |
There was a problem hiding this comment.
What's the difference between this file and home/xprofile ?
There was a problem hiding this comment.
I should've documented it at the time:
I was having an issue with LightDM, xprofile is executed by LightDM, but I don't think xinitrc was being executed. I should have xinitrc execute xprofile. startx will execute xinitrc and not xprofile
There was a problem hiding this comment.
Does that mean you're trying to move from LightDM to startx? Or can they coexist without any issues?
I remember briefly trying startx, but got confused quickly and gave up
| @@ -1 +1 @@ | |||
| ../../../submodules/github.com/chriskempson/base16-vim/colors/base16-tomorrow.vim No newline at end of file | |||
| /home/sgreenup/code/github.com/scottgreenup/desktop/src/github.com/chriskempson/base16-vim/colors/base16-tomorrow.vim No newline at end of file | |||
There was a problem hiding this comment.
I'm a fan of using the full path, though it does mean that sgreenup will need to be changed for other users.
Maybe it could be an ansible task to populate the top level directories with $HOME?
There was a problem hiding this comment.
Crap, it is an ansible task already, it needs to be ignored.
| .PHONY: install | ||
| install: | ||
| # TODO use vault '--ask-vault-pass' | ||
| ansible-playbook -i '127.0.0.1,' --ask-become-pass linux.yaml |
There was a problem hiding this comment.
Is -i necessary if you've declared hosts: localhost in linux.yaml?
There was a problem hiding this comment.
I am not sure, I think so.
the hosts list in linux.yaml affects which hosts are covered by that YAML file, but the flag is to specify which ones are being acted on with that command.
2 participants
Just to get feedback.