Bruno Pinto
2222db74d8
Change theme when creating a new theme
...
We already change the current directory to the theme dir, to make it
easier for development, we also change the current theme.
2015-08-28 13:15:31 +01:00
Jorge Bucaran
d107b2ec1e
simplify color setters
2015-08-28 18:35:50 +09:00
Bruno Pinto
0767b2a72f
Fish < 2.2 does not support argument for set_color
...
The second argument (background) was added on fish 2.2
2015-08-28 18:33:31 +09:00
Wes Morgan
c6e72863bd
centralize pkg / theme installation
2015-08-28 18:28:47 +09:00
Bruno Pinto
bfe77b6273
Handle scenarios where colors are not defined.
...
Fish should set default colors:
b32f770a69/share/functions/__fish_config_interactive.fish
2015-08-28 18:24:57 +09:00
Bruno Pinto
20ed43983b
Naming functions with omf. namespace.
...
Having a clear namespace `omf.` improves the readability of the code as
we clarify what is the function name and what is the namespace.
2015-08-28 18:24:56 +09:00
Bruno Pinto
2ecc1fc100
Use fish's colors
...
Instead of using custom colors, reuse fish's colors.
Original fish colors here:
4d628d5f43/functions/restore_original_fish_colors.fish
2015-08-28 18:21:03 +09:00
Wes Morgan
2564e7446c
refresh after installing package or theme
...
The functions themselves no longer do that.
2015-08-28 18:21:03 +09:00
Wes Morgan
718ba2fc10
don't refresh in omf_theme
...
Leave that up to the caller.
2015-08-28 18:21:03 +09:00
Wes Morgan
4809687b52
don't refresh in omf_install_package
...
Leave that up to the caller.
2015-08-28 18:21:03 +09:00
Bruno Pinto
b5591c97d0
Improve template README
...
Layout and links
2015-08-28 18:21:03 +09:00
Justin Hileman
0359ba047c
Merge $OMF_CONFIG and $OMF_CUSTOM.
...
Per conversation with @bpinto in Gitter.
There's no need for two separate directories. You don't have a `.git` and `.git-custom` folder, you just put your config in `.git` :)
The most straightforward interpretation of XDG basedir spec is that user configuration for omf would go in `~/.config/omf`, so let's put it there. The only question is whether omf-generated config (i.e. the `theme` file) should go there as well. By analogy with git, programmatically generated config should probably be merged in with user config. This also makes it so when a user clones their dotfiles to a new machine, both kinds of settings come with it.
2015-08-27 11:02:30 -07:00
Jorge Bucaran
a1c319db73
fix template generator using incorrect variable USERNAME → USER
2015-08-27 10:28:00 +09:00
Jorge Bucaran
fa46c0118e
Merge pull request #519 from fish-shell/get-renamed-to-install
...
Rename 'get' to 'install'
2015-08-27 07:24:02 +09:00
Jorge Bucaran
c855e0024c
fix omf new theme and remove default theme
2015-08-27 06:04:24 +09:00
Bruno Pinto
24ab9a991b
Rename 'get' to 'install'
...
We already use 'install' on the command description: 'Install one or
more packages.'
Also call update using 'u' instead of 'p'.
2015-08-26 21:19:40 +01:00
Bruno Pinto
7f53f59ee6
Remove unused code
...
`default` was doing nothing.
2015-08-26 20:14:23 +01:00
Jorge Bucaran
c480308889
remove references to wa
2015-08-27 03:58:35 +09:00
Jorge Bucaran
ed688aac2d
fix use of older omf_use in omf_remove_package
2015-08-27 03:15:05 +09:00
Bruno Pinto
a9df3e1e98
Rename omf use to omf theme.
...
The first time I saw `use`, I thought I could use the command for
everything, including packages, but it's only used for themes. So, it's
better to have a clearer name.
2015-08-26 19:09:11 +01:00
Jorge Bucaran
e68f83ffeb
fix omf_get_package typo
2015-08-27 02:06:18 +09:00
Jorge Bucaran
2693a2fd18
%%% United States of the Fish → Wahoo + OMF %%%
2015-08-27 00:20:13 +09:00
