Max Bolingbroke wrote:

2008/9/9 Andrew Coppin :

...

Actually, now that I think about it, it would be kind of nice to have a magic package that writes out escape codes or calls the Win32 API depending on which platform your program is compiled on - in the style of System.FilePath. I don't know how to do that though... A nice idea, guys?

I wrote this package a few weeks ago: check out http://hackage.haskell.org/cgi-bin/hackage-scripts/package/ansi-terminal and it's companion http://hackage.haskell.org/cgi-bin/hackage-scripts/package/ansi-wl-pprint

Ah, so somebody has already beaten me to it, eh? Looks like the only thing it doesn't do is let you change the title on the console window. (Because, obviously, that's only possible on Windows.) And what do you know, it installed out of the box without issue on my Windows system. Now that's pretty rare... Any ideas about the build log error that's preventing Hackage from autogenerating the documentation?

On 2008 Sep 12, at 22:29, Curt Sampson wrote:

On 2008-09-12 20:29 +0100 (Fri), Andrew Coppin wrote:

...

Looks like the only thing it doesn't do is let you change the title on the console window. (Because, obviously, that's only possible on Windows.)

Right. Unless you send an ^[^H]0;foo^G sequence (^[ being ESC) to your xterm. You'll find that the title changes to "foo".

0 = both title and icon 1 = icon name 2 = titlebar text Most X11 terminal emulators use the same protocol. (ISTR that dtterm doesn't, but I don't think most people care any more.) One other gotcha is that Terminal.app on Leopard (dunno about Tiger) treats 0, 1, 2 the same way so if you set the icon name after the title you end up with the icon name in the titlebar. (OSX uses the titlebar text as the icon name when minimized.) -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery@kf8nh.com system administrator [openafs,heimdal,too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH

2008/9/13 Max Bolingbroke :

Interesting information. I'll look into adding this to my package then: cheers!

Just FYI, I have now implemented and tested this feature. The new version, 0.5.0, is available on Hackage. Cheers, Max

2008/9/13 Andrew Coppin :

...

Just FYI, I have now implemented and tested this feature. The new version, 0.5.0, is available on Hackage.

For both platforms?

Of course! My package promises to work cross-platform, after all.

Out of interest, how do you get the correct package built on each platform?

If you mean "how do I compile the ANSI emulator on Windows but the actual ANSI stuff on Unix", most of the magic is in the .cabal file: http://github.com/batterseapower/ansi-terminal/tree/master/ansi-terminal.cab.... I simply turn on the C-preprocessor (CPP) and then supply -DWINDOWS on Windows and -DUNIX on anything else. The actual use of CPP in my source is then confined to a single module (http://github.com/batterseapower/ansi-terminal/tree/master/System/Console/AN...) which either imports System.Console.ANSI.Windows or System.Console.ANSI.Unix depending on which of those two have been defined. Nothing to it, really. However, this is the stuff that is making the Hackage documentation generation choke currently because until recently Cabal forgot to supply the CPP flags to a Haddock 2 (but not Haddock 0.x) run. All the best, Max

On Sat, 2008-09-13 at 13:41 +0100, Andrew Coppin wrote:

...

If you mean "how do I compile the ANSI emulator on Windows but the actual ANSI stuff on Unix", most of the magic is in the .cabal file:

...

I simply turn on the C-preprocessor (CPP) and then supply -DWINDOWS on Windows and -DUNIX on anything else.

Anyway, that still leaves one question: how do you figure out which platform you're on so you can set the right options?

As Max suggested, look in the .cabal file. You'll find this snippet: if os(windows) Build-Depends: Win32 >= 2.0 Cpp-Options: -DWINDOWS [... other stuff ...] else -- We assume any non-Windows platform is Unix Build-Depends: unix >= 2.3.0.0 Cpp-Options: -DUNIX [... other stuff ...] Extensions: CPP Duncan