Hi all,
I've just started learning haskell.
I encountered a strange behaviour in ghci.
1. ghci doesn't seem to do pruning of duplicate expressions. If the same
expression is entered twice, both of them are stored in the history instead
of just one. Bash uses environmental variables (HISTCONTROL
2008/8/21 Venkat Ramanan <[EMAIL PROTECTED]>:
> Hi all,
>
> I've just started learning haskell.
>
> I encountered a strange behaviour in ghci.
>
> 1. ghci doesn't seem to do pruning of duplicate expressions. If the same
> expression is entered twice, both of them are stored in the history instead
>
On Thu, Aug 21, 2008 at 5:13 PM, Judah Jacobson <[EMAIL PROTECTED]>wrote:
> I don't think there currently is; but you should feel free to submit a
> feature request with the desired behavior at:
> http://hackage.haskell.org/trac/ghc/
>
OK. I just submitted a feature request there. (#2531)
Is thi
On Tue, Aug 12, 2008 at 03:17:59PM -0400, Isaac Dupree wrote:
> Thomas Schilling wrote:
> > I encourage everyone to add useful tips and examples both from users who
> > already use Git and later on, once we have gathered more experience. I
> > believe that Git has some features which can improv
Isaac see third
> FWIW, I started a wiki page that tries a direct comparison between Darcs and
> Git:
>
>http://hackage.haskell.org/trac/ghc/wiki/GitForDarcsUsers
>
> Some mappings are simple, some are more complicated and will require
> adopting a different workflow. I still recommen
> I personally don't know Git, and while I'm sure I'll be learning at
> some point, I'm always nervous about learning a VCS on something I
> care about, as mistakes can go quite wrong.
If I can lend you (or someone else) a hand don't hesitate to contact me.
(I'm not a git guru though..)
With git y
> Using merge you also get a more accurate reflection of the project
> history, i.e. you can see that the two branches were being developed
> independently.
Timestamps will be preserved so not all information is lost..
Marc
___
Glasgow-haskell-users mail
> Sorry for being a git n00b, but does using merge mean that we need to use
> in-place branch switching (which you earlier said won't work well for ghc
> anyways)?
You have to kind of "branches" : local ones and remote ones.
remote ones represent the state of remote ones. The only way I know
On Mon, Aug 18, 2008 at 12:21:47PM +1000, Manuel M T Chakravarty wrote:
> From what you are saying, it seems that one "advantage" of git (in-place
> branch switching) is not going to be useful to GHC in any case (because we
> use nested repositories).
> Manuel
I don't agree. I feel it's convi
