I just noticed that suddenly MacHg started producing something like the following when trying to open up a terminal from MacHg:

That not clearing of the terminal commands happens due to clear no longer working. If you do some googling it turns out the culprit seems to be an XCode 4 update for me. It handily blew away some of the files in /usr/share/terminfo/78 specifically it removed the configuration file xterm-256color. Restoring this file from time machine or another Lion install will restore the clear command and will stop some other funkiness I was seeing in the terminal.

Or if you have pacifist and the Lion Installer application you can open the specific package and extract the file:

1. Find the Install Mac OS X Lion application and Right click it and choose Show Package Contents
2. Inside the package contents mount the .dmg located at Install Mac OS X Lion.app/Contents/SharedSupport/InstallESD.dmg
3. From the disk image open Mac OS X Install ESD/Packages/BaseSystemResources.pkg in pacifist
4. In pacifist navigate to and extract the file /usr/share/terminfo/78/xterm-256color to the same place on your hard drive.

All fixed!

I just wanted to drop a quick note about the event “Beers with BitBucket…” that the bitbucket team sponsored this last Tuesday the 25th of October in Chicago.

I went along and scored some bitbucket bling: Two free t-shirts and a bottle opener as well as of course far too much free beer (The beer was quite good.) In fact there was enough free beer that by the end of the night after I had left the two t-shirts at a table at one of the after function bar’s there was only one t-shirt left after I picked up my stuff. So obviously the bling was really popular! Still I guess that’s what happens in Chicago “after hours”.

Still in any case I met some really cool people. The bitbucket guys were really chilled. I pronounced “Atlassian” totally wrong and they still liked me Anyway thanks to Atlassian and the bitbucket crew I have a much better idea of their strategic direction and that they are really in this for the long haul and push.

In fact after I came back at around 2am (I know, I know, wandering around downtown Chicago at 2am fending off all the hmm… people who were trying to sell me “stuff”, maybe wasn’t the brightest thing to do…) But in any case I went to subway for some food and one of the bitbucket system administrators was there and of course we got to talking again and he insisted on personally paying for my subway sandwich… It’s just one detail, but I just got the feeling the team of engineers were just genuienly nice people. I get the feeling they really want to do good things for developers everywhere! So in any case personal thanks to Justin and the others!

I should also say the other people who attended were really interesting. Eg I met one of my MacHg users Sean Farley, and he was a really neat guy (He has a really strange Gravitar image, but I gave him some friendly grief over it. (Scraws!)) . Anyway, it turns out he was also a physicist and he knew a lot about Mathematica (my day job), and knew a lot about well a lot of other really interesting technologies. We got along famously…) But in any case I got some extra impetuous to add an annotation view to MacHg… I really have to get onto this.

But all in all it was a really fun night! Thanks to the bitbucket crowd for hosting it. You guys rock!

Cheers, Jas

Michael Degusta writes:

In other words, Apple’s way of getting you to buy a new phone is to make you really happy with your current one, whereas apparently Android phone makers think they can get you to buy a new phone by making you really unhappy with your current one…

The full article is really interesting and you can read it here: Historical support of android phones

Man, that’s not such good support… (Let’s hope this really improves…)

The only thing worse than managing multiple windows is managing multiple panes… – Brent Simmons

I feel like this all the time in Xcode 4. I have been using XCode 4 for quite a while now and while I love the fact that Clang and all the back end smarts are much nicer, the interface has really taken a retro-grade step in my opinion. I recently had to go back to XCode 3 to do some stuff and wow it was soooo much faster to get around and do stuff. There is now so much pane management in XCode 4.

For instance lets consider doing a find across your project. In XCode 4 you hit cmd-shift-F, enter your find text and hit return. Then you have to go drag the find results sub-pane bigger… then look through all your results. Then when you find something interesting you have to double click on a result to look at the find instance (being very careful not to single click it or else the main bit of code you were looking at to provide context to your find disappears). Then when you finally found what you want you have to dismiss the new windows you created, then resize the find column back to something you use for eg a stack trace / build results / whatever (Debug Navigator / Log Navigator) and then go on your way.

In XCode 3 you just hit cmd-shift-F, enter the find and hit return, look through the results, and then close the window. Sooo much quicker and simpler. Its things like this which just made XCode 3 so much smoother…

Apple please, please, please, also allow a more windowed approach like there used to be which was so much more flexible and quicker…

I am happy to announce that I have just released MacHg 0.9.24.

You can get the latest MacHg from the downloads, and you can view the latest release notes here.

MacHg 0.9.24 updates MacHg to fix Lion compatibility issues, and also updates the underlying Mercurial to the latest version, 1.9.2. There are a number of other nice fixes in MacHg 0.9.24. Take a look at the full change log for details!

As a personal note, sorry for the 3 month delay in development here. My real world job has been very busy and demanding, and I haven’t had as much time to devote to MacHg as I would have liked. However, the roadmap is still very much in progress…

Cheers, Jason

Update: I have changed the name of this extension from ExcludeChangests to BanChangesets. (9-Oct-2011)

Just a quick note to say I uploaded my first published Mercurial extension!

BanChangesets can be used to ensure that certain changesets which are determined to be “bad” by a team can be banned from being repushed to a central repository.

Imagine that you have a team of people working on a mercurial repository. One of the members of the team pushes a changeset or group of changesets to the central repository but these changesets are “bad” for one reason or another. (Maybe some branch was merged when it should not have been, etc. Maybe some nuclear launch codes were accidentally committed, etc.). Ideally this should never happen. In practice it happens all too frequently.

So typically the leader of the project will send out an email saying something like: Please strip the following revisions from your repositories:

162a93e027fdcc6f037c80d185eb201e346da0b0
69cc2b0e47158d1a571a35ec89c5524b084944c9
a4988662d998b8d986bdaec43079475827aa31d0

The problem is of course that in a team of say 20 people someone might have already pulled the “bad” revisions and they may accidentally miss the email, and re-push these bad revisions back to the central server.

The extension ban-changesets is intended to prevent such a re-push of these “bad” changesets.

See the full details here and on the wiki page

I am happy to announce that I have just released MacHg 0.9.22.

You can get the latest MacHg from the downloads, and you can view the latest release notes here.

MacHg 0.9.22 is primarily a bug fix release. There was an issue where if you double clicked on a file without changes in the last version MacHg would crash. This is now fixed. There are a number of other nice fixes in MacHg 0.9.22 but nothing critical. Take a look at the full change log for details!

Cheers, Jason

I am happy to announce that I have just released MacHg 0.9.21.

You can get the latest MacHg from the downloads, and you can view the latest release notes here.

In MacHg 0.9.21 I think I have finally fixed the various NSTask related problems. Previously NSTask would intermittently hang, or just drop tasks. But only fairly occasionally. I had gotten to the stage where I could reproduce the problems in small code samples and had sent these small projects to the cocoa-dev list. Finally I have managed to fix things by switching to a drop in replacement of NSTask called TLMTask written by Adam R. Maxwell (who writes the TeX Live Utility) (Adam has been extremely helpful in private emails about issues to do with TLMTask,)

So this completes the promise in the last blog post. There are currently no critical bugs I am aware of stopping me releasing MacHg 1.0.0. I will see if any problems crop up in the wild with MacHg 0.9.21 and if not this latest version will become version 1.0.0!

Cheers, Jason

[Update : fixed Adam's name as Adam pointed out]

I am happy to announce that I have just released MacHg 0.9.20.

You can get the latest MacHg from the downloads, and you can view the latest release notes here.

MacHg 0.9.20 now continually reports the progress of long running operations such as clone, push, pull, incoming, and outgoing; adds an ‘Open With…’ menu item; adds a ‘Scroll to Changeset…’ menu in all log views; updates the bundled Mercurial to 1.8.2; and includes a number of other fixes and enhancements.

I really like the new ‘Scroll to Changeset’ feature. You can just hit cmd-L to go to any changeset and it’s available anywhere you see a list of changesets. Having progress for long running operations is also something that has been requested for a long time. With the NSTask changes in recent versions of MacHg this has now been possible.

Unfortunately, MacHg is still having very occasional and intermittent quirks with NSTask. After several posts to cocoa-dev and some examples posted there where NSTask is just dropping tasks I am investigating other options in ernest. I can’t go MacHg 1.0.0 until I fix this, but happily I have another option on the horizon right now.

In my testing this new alternative is working almost perfectly. I haven’t seen any dropped NSTask’s at all. However, the progressive progress updates that I just added in MacHg 0.9.20 are not yet working with this alternative method. Once I have this last kink ironed out, I will hopefully be releasing another version of MacHg very shortly (within the week) which fixes the very occasional and intermittent missing or hung NSTasks.

Cheers, Jason

Darn… Well release 0.9.17 almost went off without a hitch…

However, in making the changes in MacHg 0.9.17 so that everyone would get the latest enhancements to the diffing and merging tools as well as the speedup for the extension handling in Mercurial I choose to upgrade the support folder for MacHg. MacHg would detect when run if the most advanced version previously run was before 0.9.17 and if so it moved ~/Library/Application Support/MacHg to the trash and of course just regenerated this folder. This worked fine for me, but it turns out that I made a decision (a bad one), way back at the start, to store the default location of the repository list in ~/Library/Application Support/MacHg/Repositories.mchg. So for users who just used the defaults, I had moved their list of repositories to the trash. !!Opps… Not good!!

Anyway MacHg 0.9.18 fixes this by moving only ~/Library/Application Support/MacHg/hgrc to the trash. In a future update I’ll make sure Repositories.mchg is handled either in the documents folder or in a better way.

MacHg 0.9.19 is also a small point fix to make the amend option to commits work again for those people who don’t have the mercurial queues extension turned on by default.

Sorry about letting this slip through…

(This brings up the point. I think I need a list of beta testers. I’ll send out a message about this to the news group, or send me an email at jason@jasonfharris.com about being a beta tester.)

Cheers! Jas