<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">I would whole heartedly agree that Apple’s versioning is not a replacement for code versioning systems and because I commit a lot during the day I don’t have much of any use case for Apple’s versions but as long as it this functionality were “in addition to” then I see no harm as it would provide the ability to move back and forth between recent versions of the file within the commit cycle. I have had situations where it would be nice to go back in time 4 hours to remind myself what the state of this file was then (assuming I haven’t committed these changes during the timeframe). So there is a use-case for it I think and if it’s easy to “turn on” then I think it would be better with than without but if there’s a lot of effort in making it work I personally think it would be a waste of time.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Ken</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">p.s. another use-case would be that people do use textmate for document processing (it’s a great markdown editor when paired with <i>marked</i>) … in this situation you might be back in the more individual (versus team) and non-developer workflows that Apple is primarily catering to</div> <div class="bloop_sign" id="bloop_sign_1413563439946695936"><div style="font-family:helvetica,arial;font-size:13px"><br></div></div><p style="color:#000;">On 17 October 2014 at 17:10:40, Caio Fernando Bertoldi Paes de Andrade (<a href="mailto:caiofbpa@icloud.com">caiofbpa@icloud.com</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>I agree.
<br>
<br>Apple’s versioning system works fine for documents, spreadsheets and keynotes, but isn’t anywhere near as complete as what source code demands.
<br>
<br>Caio
<br>
<br>> On 17 of Oct, 2014, at 12:08, Berend Hasselman <bhh@xs4all.nl> wrote:
<br>>
<br>>
<br>> On 16-10-2014, at 17:03, Igor K <me@igorkozlov.me> wrote:
<br>>
<br>>> OS X has support for auto save and reverting to older file versions since Lion.
<br>>>
<br>>> Are there any plans to support this in TextMate?
<br>>>
<br>>> Is it hard to implement or there’s some other reason why it’s not supported?
<br>>> Maybe it’s just not on the priority list?
<br>>
<br>>
<br>> I regard Apple’s “versions” as quite useless.
<br>>
<br>> Version control a la Mercurial, Git, svn is much te be preferred.
<br>> Especially if you have a project that consists of several separate files.
<br>> Apple will treat each file separately so versions of different files can easily be unsynchronised.
<br>>
<br>> In addition Apple versions do not show highlighted differences between a current version and a previous version in the way that e.g. Changes, BBEdit and others do (for text files).
<br>>
<br>> I much prefer proper version control (I mainly use Mercurial).
<br>>
<br>> BTW: I’m not starting a flame war.
<br>>
<br>> Berend
<br>>
<br>>
<br>> _______________________________________________
<br>> textmate mailing list
<br>> textmate@lists.macromates.com
<br>> http://lists.macromates.com/listinfo/textmate
<br>
<br>
<br>_______________________________________________
<br>textmate mailing list
<br>textmate@lists.macromates.com
<br>http://lists.macromates.com/listinfo/textmate
<br></div></div></span></blockquote></body></html>