dot file for fish shell integration does not follow XDG path convention

Required information for bugs. I probably can't help you unless you include this:

• Build 2.9.20160206
• 10.11.4

shell integration for fish is installed as $HOME/.iterm2_shell_integration.fish but should be installed as $XDG_CONFIG_HOME/iterm2_shell_integration.fish

(

$XDG_CONFIG_HOME default is `$

HOME/.config/fish` )

Milestone changed to Ship 3.0

Milestone changed to Future Release

I don't know if you want me to open a new issue or if you'd rather make this one more general, but:

It would be nice if iTerm could respect $XDG_CONFIG_HOME for all its config, not just this file.

So the current ~/.iterm2/ directory should be ~/.config/iterm2/ (assuming a default or blank $XDG_CONFIG_HOME).

Then the shell integration dotfiles should probably be inside iTerm's config directory, rather than (as @db had suggested) in the directory for the relevant shell. My logic here is that these files belong to iTerm and get updated with new iTerm updates, and they are sourced by a single line in the shell's config file.

How is XDG_CONFIG_HOME normally set? Is it from a .bashrc script or something else?

I don't think this can make it into 3.0 but since it's a server-side change it can be done at any time.

XDG_CONFIG_HOME defaults to $HOME/.config

but any login shell can change it. For iTerm though, I would think that would be a setting once the app is opened. IOW, I can set the sync directory to be $HOME/Dropbox/settings/iterm

And if iterm could detect changes between dropbox versions, that would be awesome

I mean, if you want to customize it, where would you perform that customization? Would it be in .bashrc or .bash_profile?

Depends on what shell you have. I use fish, so for me that would be $HOME/.config/fish/config.fish

Milestone changed to %Feature Complete 3.1

I set XDG_CONFIG_HOME in my bash_profile file. It's not technically an OSX thing - it's a Linux thing - but if apps can support it when the environment variable is set, that is awesome.

Is this available if I upgrade to the beta 3.1?

changed milestone to %Review for next version