Re: Thread behavior in 7.8.3

2015-01-21 Thread Bas van Dijk
Hi Michael, Are you already using usb-1.3.0.0? If not, could you upgrade and test again? That release fixed the deadlock that Ben and Carter where talking about. Good luck, Bas ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org

Re: How to remove a cabal package from the local system?

2015-01-21 Thread Herbert Valerio Riedel
On 2015-01-21 at 16:36:08 +0100, Volker Wysk wrote: I have installed/registered a new version of a package with cabal by accident. How can I remove it again? Not sure if this is what you want, but the `cab` tool has an `uninstall` sub-command to unregister and remove installed packages.

Re: Found hole

2015-01-21 Thread Brandon Allbery
On Wed, Jan 21, 2015 at 9:53 AM, Stephen Paul Weber singpol...@singpolyma.net wrote: This is very concening for me. Extensions should *never* be enabled by default! If you read on, you'll find that I was working from an older proposal that was never implemented. It is instead a modified

Re: How to remove a cabal package from the local system?

2015-01-21 Thread Evan Laforge
I use a shell script. It's really useful, surely there's some official way to do this? #!/bin/zsh package=$1 if ! ghc-pkg describe $package /dev/null; then echo no such package: $package exit 1 fi ghcdir=$(ghc --print-libdir) function field() { ghc-pkg field $package $1 | cut -d'

How to remove a cabal package from the local system?

2015-01-21 Thread Volker Wysk
Hi! I have installed/registered a new version of a package with cabal by accident. How can I remove it again? There is something in ~/.cabal/packages/hackage.haskell.org, but the defective version isn't included. bye V.W. ___ Glasgow-haskell-users

Re: How to remove a cabal package from the local system?

2015-01-21 Thread Brandon Allbery
On Wed, Jan 21, 2015 at 11:19 AM, Volker Wysk vertei...@volker-wysk.de wrote: I'm also missing a command to set the Default available version. You don't set that; it's specified in the downloaded package index in the package repo. -- brandon s allbery kf8nh sine

Re: How to remove a cabal package from the local system?

2015-01-21 Thread Volker Wysk
Am Mittwoch, 21. Januar 2015, 23:56:53 schrieben Sie: I use a shell script. It's really useful, surely there's some official way to do this? It looks like a remove command to cabal has been forgotten... This would be a feature request. I'm also missing a command to set the Default available

Re: Thread behavior in 7.8.3

2015-01-21 Thread Michael Jones
Bas, I have not upgraded, mainly because my problems manifest without enabling USB. However, I think I can upgrade in a few days and move forward. Are you using ghc 7.8.10 these days or something older? Mike On Jan 21, 2015, at 12:52 PM, Bas van Dijk v.dijk@gmail.com wrote: Hi Michael,

Re: Thread behavior in 7.8.3

2015-01-21 Thread Michael Jones
Bas, I checked my cabal file and I was already using 1.3.0.0. Mike On Jan 21, 2015, at 12:52 PM, Bas van Dijk v.dijk@gmail.com wrote: Hi Michael, Are you already using usb-1.3.0.0? If not, could you upgrade and test again? That release fixed the deadlock that Ben and Carter where

Re: Found hole

2015-01-21 Thread Merijn Verstraaten
Typed holes is not an extension, because it's considered a warning/error. The reason for this is that code with typed holes is NOT valid haskell to begin with, therefore the behaviour doesn't conflict with any description in the report. Additionally, the ability to disable the typed holes

Re: Thread behavior in 7.8.3

2015-01-21 Thread Simon Marlow
On 21/01/2015 03:43, Michael Jones wrote: Simon, The code below hangs on the frameEx function. But, if I change it to: f - frameCreate objectNull idAny linti-scope PMBus Scope Tool rectZero (frameDefaultStyle .|. wxMAXIMIZE) it will progress, but no frame pops up, except once in

Re: Thread behavior in 7.8.3

2015-01-21 Thread Carter Schonwald
woops, forgot to attach the relevant links, (i shouldn't email late at night :) ) https://github.com/basvandijk/usb/issues/7 is the lib usb matter https://phabricator.haskell.org/D347 point being: on ghc 7.8, certain hanging behavior from libusb (at least as of a few months ago) was due to one

Re: Found hole

2015-01-21 Thread Stephen Paul Weber
The leading underscore invokes the typed holes extension. If you want to use such names, you'll need {-# LANGUAGE NoTypedHoles #-} as the first line of the source file. (I am not sure why this extension was enabled by default.) This is very concening for me. Extensions should *never* be

Re: Found hole

2015-01-21 Thread Stephen Paul Weber
Typed holes is not an extension, because it's considered a warning/error. The reason for this is that code with typed holes is NOT valid haskell to begin with, therefore the behaviour doesn't conflict with any description in the report. Well, now I feel very silly about my last email to this

Re: Thread behavior in 7.8.3

2015-01-21 Thread Michael Jones
Simon, I went back and retested my non-GUI version and it seems to work fine. But here is what is strange, the non-GUI version is really just a client server version of what I have problems with. I have a non-GUI app running the USB and streaming data to a server. The client app (the one that

Re: Found hole

2015-01-21 Thread David Feuer
On Jan 21, 2015 9:53 AM, Stephen Paul Weber singpol...@singpolyma.net wrote: Having them on by default mean that valid Haskell2010 programs might get rejected by GHC by default, which is a pretty bad state of affairs. It would be if it were true. But it's not. All that changes is that you get

Re: Found hole

2015-01-21 Thread David Feuer
If such verbiage is added, it should probably read more like If you did not intend to insert a typed hole, _foo may have been misspelled. On Jan 21, 2015 9:11 AM, Volker Wysk vertei...@volker-wysk.de wrote: Am Mittwoch, 21. Januar 2015, 11:03:38 schrieben Sie: If there's any comments on how

Re: Found hole

2015-01-21 Thread Volker Wysk
Am Mittwoch, 21. Januar 2015, 11:03:38 schrieben Sie: If there's any comments on how to improve the warning message to be less confusing I'd be interested to hear them. What about Found hole _foo with type: bar. This can also mean that _foo is not in scope. Bye V.W.

Re: Found hole

2015-01-21 Thread Volker Wysk
Am Mittwoch, 21. Januar 2015, 09:42:05 schrieben Sie: If such verbiage is added, it should probably read more like If you did not intend to insert a typed hole, _foo may have been misspelled. What about If you did not intend to insert a typed hole, _foo may have been misspelled or out of