Hi all,

I've got a question that pertains to any of these identify-region, parse, make-expandable approaches.

The main use I'd like to use the trick for (esp. Chris's Emacs version) is to deal with large intermediate compiler ASTs.

But if a compiler produces a long stream of output to stdout, with certain Show-produced ASTs embedded in it, what's the most expedient way to identify those regions that can be collapsed in the buffer and interactively expanded?
Or is there another hack I'm not thinking of?  What's easiest?

  -Ryan



On Wed, Mar 14, 2012 at 5:01 AM, Heinrich Apfelmus <apfelmus@quantentunnel.de> wrote:
Christopher Done wrote:
Maybe an Emacs script to expand the nodes nicely:
http://www.youtube.com/watch?v=6ofEZQ7XoEA I don't find mere pretty
printing that useful compared to the “expanding” paradigm I'm used to in
Chrome and Firebug.

Great demo video. My recent GSoC project suggestions aims to make that available to non-Emacsers, via the web browser.

 http://hackage.haskell.org/trac/summer-of-code/ticket/1609


Best regards,
Heinrich Apfelmus

--
http://apfelmus.nfshost.com



_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe