On Aug 30, 2011, at 1:15 PM, Christopher Done wrote: > 1) You put all your source files on the server, too and then run the > GHCi process under tramp and access the files via tramp. > > 2) Sounds like you'd prefer to keep your files local, which, I suppose > means you want to send code to the server when you trigger a compile? > > Could be done, could be done. I'll ponder it.
Actually, 1. is what happens, which seems like the easier thing. The folder does exist locally (ie, on the host), but it is shared with the virtualmachine, so it can be edited in either place. The sharing is either done through a a special mechanism provided by the virtualmachine (ie, in virtualbox, "shared folders"), or with plain old NFS (the latter is faster, for unknown reasons). My normal workflow is to have an editor open that edits the files on the "host". Then with a ssh connection to the "client" (the virtualmachine), I build and/or run ghci through that. I'm not sure if this is how other people do work with virtualmachines, but I would imagine it was relatively common. I'd be pretty excited about that working. As an added benefit, the same strategy could be used to jump into a project on an actually remote host. _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
