On 22/09/2011 16:55, John Sparrow wrote: > >> I noticed that when opening the workbench always the last changeset gets >> preselected. Therefore one sees the differences of the previous > changeset, >> but not the diffs to the current working copy. >> >> When opening the workbench I'd expect that it preselects the current >> changes marked as the topmost changeset "* working directory *". >> >> Can that be configured somewhere in THg's setting?
+1 This is new in 2.1.3. in 2.1.2 the working directory status was shown when first opened, which made sense. The one annoying thing was that if you had unapplied patches, the top one of those was shown instead, which didn't make sense. > Why not use 'View file status'? > I prefer the way Workbench functions now - since it's primarily a tool > for checking the repos history. I disagree - for me the beauty of the workbench is that it's a universal tool that can do just about anything. 9 times out of 10 the first thing I want to do when I open it is to check the working directory contents; after that I might either commit, create an mq patch or shelve. I also use it to browse history, but I do that a lot less frequently than working directory operations. I pretty much never use the standalone commit or file status tools, since the workbench lets me see and do everything in one window. Latest News at: http://www.indigovision.com/index.php/en/news.html ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
