{"action":"closed","issue":{"url":"https://api.github.com/repos/JCLiang/vim-cscope-utils/issues/2","labels_url":"https://api.github.com/repos/JCLiang/vim-cscope-utils/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/JCLiang/vim-cscope-utils/issues/2/comments","events_url":"https://api.github.com/repos/JCLiang/vim-cscope-utils/issues/2/events","html_url":"https://github.com/JCLiang/vim-cscope-utils/issues/2","id":94862325,"number":2,"title":"Tags per branch introduces some new issues","user":{"login":"martinpelikan","id":3248296,"avatar_url":"https://avatars.githubusercontent.com/u/3248296?v=3","gravatar_id":"","url":"https://api.github.com/users/martinpelikan","html_url":"https://github.com/martinpelikan","followers_url":"https://api.github.com/users/martinpelikan/followers","following_url":"https://api.github.com/users/martinpelikan/following{/other_user}","gists_url":"https://api.github.com/users/martinpelikan/gists{/gist_id}","starred_url":"https://api.github.com/users/martinpelikan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/martinpelikan/subscriptions","organizations_url":"https://api.github.com/users/martinpelikan/orgs","repos_url":"https://api.github.com/users/martinpelikan/repos","events_url":"https://api.github.com/users/martinpelikan/events{/privacy}","received_events_url":"https://api.github.com/users/martinpelikan/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-07-14T03:56:51Z","updated_at":"2015-07-23T00:50:11Z","closed_at":"2015-07-23T00:50:11Z","body":"The changes introduced in [12d5ad7a](https://github.com/JCLiang/vim-cscope-utils/commit/12d5ad7abd71036aed30ea8c3d1f44bfa0692c04) are a great idea! However, they have caused a few issues for my uses in their current implementation. Perhaps these issues can be addressed in the user configuration, so I'd like to hear what you think. \r\n\r\n1. Branch names should be sanitized to be file/directory-name safe. If, for example, your branch name has a directory separator '/' in it, such as 'username/mybranch/testing', the relevant tag files will now be nested under several sub-directories. This may be intentional (and even neat, if you want to organize your tags in this manner), but it feels somewhat unpredictable and unexpected for me.\r\n2. I like to use \"vim -t {tag}\". It seems like the plugin only loads the tags after the argument has already been parsed and attempted to be evaluated and thus this fails. However, I have been able to set the 'tags' option to point at .git/tags and get the expected behaviour. With the new branching scheme, setting this statically no longer works as the tags will live in different places.\r\n3. Some kind of LRU cleanup might be nice, although purely just final polish. Cscope databases can grow to moderate sizes with huge projects, and this can add up if they are kept for each branch. This can be cleaned up manually, and in the grand scheme of things probably won't add up to much on modern disks, but it can still be a neat feature.\r\n\r\nCheers"}}