oh-my-fish/pkg/omf/cli/omf.list_themes.fish

function omf.list_themes
  set -l seen ""
  for theme in (basename $OMF_PATH/db/themes/*) \
               (basename {$OMF_PATH,$OMF_CONFIG}/themes/*)
    contains $theme $seen; or echo $theme
    set seen $seen $theme
  end
end
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 02:55:29 +08:00			`function omf.list_themes`
%%% United States of the Fish → Wahoo + OMF %%% 2015-08-26 23:20:13 +08:00			`set -l seen ""`
			`for theme in (basename $OMF_PATH/db/themes/*) \`
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-28 01:56:01 +08:00			`(basename {$OMF_PATH,$OMF_CONFIG}/themes/*)`
%%% United States of the Fish → Wahoo + OMF %%% 2015-08-26 23:20:13 +08:00			`contains $theme $seen; or echo $theme`
			`set seen $seen $theme`
			`end`
			`end`