{"action":"opened","issue":{"url":"https://api.github.com/repos/scop/bash-completion/issues/47","repository_url":"https://api.github.com/repos/scop/bash-completion","labels_url":"https://api.github.com/repos/scop/bash-completion/issues/47/labels{/name}","comments_url":"https://api.github.com/repos/scop/bash-completion/issues/47/comments","events_url":"https://api.github.com/repos/scop/bash-completion/issues/47/events","html_url":"https://github.com/scop/bash-completion/issues/47","id":156701817,"number":47,"title":"Conflicts with CLICOLOR_FORCE","user":{"login":"defjaf","id":799252,"avatar_url":"https://avatars.githubusercontent.com/u/799252?v=3","gravatar_id":"","url":"https://api.github.com/users/defjaf","html_url":"https://github.com/defjaf","followers_url":"https://api.github.com/users/defjaf/followers","following_url":"https://api.github.com/users/defjaf/following{/other_user}","gists_url":"https://api.github.com/users/defjaf/gists{/gist_id}","starred_url":"https://api.github.com/users/defjaf/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/defjaf/subscriptions","organizations_url":"https://api.github.com/users/defjaf/orgs","repos_url":"https://api.github.com/users/defjaf/repos","events_url":"https://api.github.com/users/defjaf/events{/privacy}","received_events_url":"https://api.github.com/users/defjaf/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-05-25T09:20:41Z","updated_at":"2016-05-25T09:20:41Z","closed_at":null,"body":"(_The following has to do with the version of `bash-completion` that ships with OS X homebrew; apologies if it's not relevant to current versions._)\r\n\r\nVarious aspects of the completion scripts conflict with `CLICOLOR_FORCE`, an environment variable which forces `ls` to output terminal colour codes even when not obviously running interactively (useful for piping through `less', etc). \r\n\r\nThe most glaring issue is in the `have()` function, which fails so that none of the completions get set up, but this only needs to happen when the `bash-completion` script is run, so can be fixed by setting the variable later on in the startup. But some of the scripts (e.g., for `ssh`) seem to rely on `ls` to generate filename lists on-the-fly which means that they come out mangled. For example:\r\n\r\n    $ scp .bas\r\n    ^[\\[34m.bash_sessions^[\\[39\\;49m^[\\[0m/\r\n    .bashrc \r\n\r\n"}}
{"actor":{"display_login":"defjaf"}}