Vcsh does support branches.
That being said, if you switch from branch zsh to branch vim, you will
delete the copies of your zsh config in $HOME.
That is most likely not what you want...
Richard
Sent by mobile; excuse my brevity.
___
vcs-home mailing
On 06/26/2015 10:44 PM, Richard Hartmann wrote:
Vcsh does support branches.
That being said, if you switch from branch zsh to branch vim, you will delete
the copies of your zsh config in $HOME.
Is that a documented feature or an accidental one and might it change in
future?
That is most
Hi Sitaram,
This is tricky. vcsh’s approach to overlaying fundamentally relies on having
multiple git indexes available, one for each separate *working directory*.
This implies a separate .git directory (or in vcsh’s case, a separate bare
repo, e.g. “vim.git”) for each overlay. It doesn’t
On Fri, Jun 26, 2015 at 7:32 PM, Sitaram Chamarty sitar...@gmail.com wrote:
That being said, if you switch from branch zsh to branch vim, you will
delete the copies of your zsh config in $HOME.
Is that a documented feature or an accidental one and might it change in
future?
This is a
On Fri, 26 Jun 2015 12:07:37 +0530
Sitaram Chamarty sitar...@gmail.com wrote:
Hi,
(I couldn't find this
on a quick google search, or on github issues search)
Would it be possible to use a single repo, with each configuration (vim,
zsh, etc) being a *branch* in that repo, rather than each
Thanks for your reply! (thanks to madduck, RichiH, Antonio also).
On 06/27/2015 12:17 AM, John Whitley wrote:
Hi Sitaram,
This is tricky. vcsh’s approach to overlaying fundamentally relies on
having multiple git indexes available, one for each separate *working
Yes; my mistake was asking
On Sat, Jun 27, 2015 at 4:40 AM, Sitaram Chamarty sitar...@gmail.com wrote:
[1]: https://github.com/sitaramc/gaf
gaf expands to gitify arbitrary files; out of interest, where did
you pick up the term gitify?
Richard
___
vcs-home mailing list
