Commit Graph

6 Commits (5d4b9098fc3783464da826a1215ec555c4cb6018)

Author SHA1 Message Date
Bruno Pinto af49d6f1c2 Replace `omf.util_sync` with `omf.repo.pull`
Based on
https://github.com/Homebrew/homebrew/blob/master/Library/Homebrew/cmd/update.rb#L175-L221
9 years ago
Bruno Pinto 2a0e5ba7cc Remove unused `util_fork_repo` function. 9 years ago
Bruno Pinto 7dad917436 Make `default` theme the default theme for omf.
* On clean install, configure and download `default` theme.
* Do not allow `default` theme to be removed.
* When the current theme is removed, fallback to `default`.
9 years ago
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.
9 years ago
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.
9 years ago
Jorge Bucaran 2693a2fd18 %%% United States of the Fish → Wahoo + OMF %%% 9 years ago