Re: Editing Git projects in BBEdit (Branch awareness)
I use git via SourceTree, a local GUI app. When I switch branches, open (and closed) BBEdit documents change to the versions in the last commit of the switched-to branch. Since SourceTree just issues git commands (switching is checkout), I don't know why it doesn't happen for you. Steve On Feb 29, 9:36 am, Pete Walker crayzeep...@gmail.com wrote: Hi, I currently use BBEdit alongside GitHub for Mac to manage our projects. One of Git's killer features is the ease with which you can create new branches and then switch between them - it would be great if BBEdit had some awareness of the branch you're currently working on. The main feature I'm looking for is for the currently open files of a project to be branch-aware. For example, if I switch branches in git, it would be useful if BBEdit would change the currently open files to a set specific to that branch. That means if I have to create a new branch to deal with a specific issue, I can have a clean slate to work with, and then when I switch back, I can carry on from where I left off. Does this make sense? Thanks, Pete -- You received this message because you are subscribed to the BBEdit Talk discussion group on Google Groups. To post to this group, send email to bbedit@googlegroups.com To unsubscribe from this group, send email to bbedit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/bbedit?hl=en If you have a feature request or would like to report a problem, please email supp...@barebones.com rather than posting to the group. Follow @bbedit on Twitter: http://www.twitter.com/bbedit
Re: Editing Git projects in BBEdit (Branch awareness)
Good morning, On 29/02/12 at 6:36 AM -0800, Pete Walker crayzeep...@gmail.com wrote: The main feature I'm looking for is for the currently open files of a project to be branch-aware. For example, if I switch branches in git, it would be useful if BBEdit would change the currently open files to a set specific to that branch. That means if I have to create a new branch to deal with a specific issue, I can have a clean slate to work with, and then when I switch back, I can carry on from where I left off. Sounds like you want project files. Create a different project for each branch and then you can have just the files you want to work on. If that doesn't quite do it then try Workspaces; create a different one for each branch. With a bit of scripting and projects/workspaces you should be able to get BBEdit to 'change' when you change branches. And that type of flexibility is one of the things that makes BBedit not suck. Charlie -- Ꮚ Charlie Garrison ♊ garri...@zeta.org.au O ascii ribbon campaign - stop html mail - www.asciiribbon.org 〠 http://www.ietf.org/rfc/rfc1855.txt -- You received this message because you are subscribed to the BBEdit Talk discussion group on Google Groups. To post to this group, send email to bbedit@googlegroups.com To unsubscribe from this group, send email to bbedit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/bbedit?hl=en If you have a feature request or would like to report a problem, please email supp...@barebones.com rather than posting to the group. Follow @bbedit on Twitter: http://www.twitter.com/bbedit
