Chrome works well. The "file://" portion at the beginning has got to
do with windows namespace [1] and browser conventions.
On 26 May 2012 02:40, Antoine Latter wrote:
> Also 'cabal' doesn't track executables, only libraries.
It does update your cabal package binaries, if the package generates
o
On Fri, May 25, 2012 at 6:28 PM, Nicu Ionita wrote:
>
>
> I have Haskell Platform 2011.2.0.1 and I assumed that haddock comes with it.
> Now I checked the version - it is 2.9.2 and cabal info tells me that the
> last version is 2.10.0 and that I don't have the package installed (?).
>
> Ok, now I
Am 25.05.2012 06:49, schrieb Magnus Therning:
On Fri, May 25, 2012 at 01:19:11AM +0200, Nicu Ionita wrote:
Hi cafe,
I have a problem with haddock documentation created when installing
new packages with cabal on windows.
The generated html files have all links in the form
j:\Users\...\doc\...\xx
I’m having the same problem on my Windows 7 laptop. The solution I’ve
found is to use Internet Explorer — it isn’t perfect, but for some reason
it is the only browser capable of handling these links.
On Fri, May 25, 2012 at 01:19:11AM +0200, Nicu Ionita wrote:
Hi cafe,
I have a problem wit
On Fri, May 25, 2012 at 01:19:11AM +0200, Nicu Ionita wrote:
> Hi cafe,
>
> I have a problem with haddock documentation created when installing
> new packages with cabal on windows.
> The generated html files have all links in the form
> j:\Users\...\doc\...\xxx.html, but firefox says, it cannot o
Hi cafe,
I have a problem with haddock documentation created when installing new
packages with cabal on windows.
The generated html files have all links in the form
j:\Users\...\doc\...\xxx.html, but firefox says, it cannot open that link.
Actually all links should be prefixed by "file:///".
