Re: Long standing annoying issue in ghci
Interesting. Would you mind reopening the issue and providing a buggy example? Amd alerting haskeline maintainers? How does it work on a 1 line prompt that is so long it wraps? On Thu, 7 Dec 2017 23:11 MarLinn, wrote: > > > Here's what I use: > > > > :set prompt "\ESC[46m\STX%s>\ESC[39;49m\STX " > > > > I believe \STX is a signal to haskeline for control sequences. > > Documentation is here: > > https://github.com/judah/haskeline/wiki/ControlSequencesInPrompt > Note: If you're using a multi-line prompt, things may be different > again. I don't know what the rules are, but I found that if I put \STX > on any but the last line of prompts I get weird characters. The same > goes for any \SOH you might want to add for some reason. > > Cheers, > MarLinn > > ___ > ghc-devs mailing list > ghc-devs@haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs > ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Re: Long standing annoying issue in ghci
Here's what I use: :set prompt "\ESC[46m\STX%s>\ESC[39;49m\STX " I believe \STX is a signal to haskeline for control sequences. Documentation is here: https://github.com/judah/haskeline/wiki/ControlSequencesInPrompt Note: If you're using a multi-line prompt, things may be different again. I don't know what the rules are, but I found that if I put \STX on any but the last line of prompts I get weird characters. The same goes for any \SOH you might want to add for some reason. Cheers, MarLinn ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
RE: Can't push to haddock
But when I try to push the GHC patch, I get this message
Ah... it worked after a while. Maybe a mirroring thing?
But in pushing to GHC I saw:
git push
Counting objects: 45, done.
Delta compression using up to 32 threads.
Compressing objects: 100% (45/45), done.
Writing objects: 100% (45/45), 27.56 KiB | 0 bytes/s, done.
Total 45 (delta 43), reused 0 (delta 0)
remote: performing commit message validations...
remote: Commit message validation passed!
remote: performing submodule-ref update validations...
remote: Submodule update(s) detected in
fa29df02a1b0b926afb2525a258172dcbf0ea460:
remote: utils/haddock => 24841386cff6fdccc11accf9daa815c2c7444d65
remote: utils/hsc2hs => 9483ad10064fbbb97ab525280623826b1ef63959
remote: OK
remote: performing whitespace validations...
remote: whitespace validation passed!
remote: mirroring ssh://g...@git.haskell.org/ghc to
ssh://g...@github.com/ghc/ghc ...
remote: To ssh://g...@github.com/ghc/ghc
remote:5f332e1..fa29df0 master -> master
remote: running notifier
To ssh://g...@git.haskell.org/ghc.git
5f332e1..fa29df0 HEAD -> master
simonpj@cam-05-unx:~/code/HEAD$
I did not intend to monkey around with hsc2hs. I can't think how that happened,
or whether it matter.
With many apologies, would a wiser person that me like to see if I've
accidentally messed up hsc2hs.
Thanks
Simon
From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of Simon Peyton
Jones via ghc-devs
Sent: 07 December 2017 17:32
To: ghc-devs@haskell.org
Subject: Can't push to haddock
I'm trying to push a patch that needs a supporting change to haddock.
I've pushed the haddock change to the ghc-head branch of
ssh://g...@github.com/haskell/haddock.git, which is (according to 'packages')
the relevant haddock upstream repo.
But when I try to push the GHC patch, I get this message
bash$ git push
Counting objects: 45, done.
Delta compression using up to 32 threads.
Compressing objects: 100% (45/45), done.
Writing objects: 100% (45/45), 27.56 KiB | 0 bytes/s, done.
Total 45 (delta 43), reused 0 (delta 0)
remote: performing commit message validations...
remote: Commit message validation passed!
remote: performing submodule-ref update validations...
remote: Submodule update(s) detected in
fa29df02a1b0b926afb2525a258172dcbf0ea460:
remote: utils/haddock => 24841386cff6fdccc11accf9daa815c2c7444d65
remote: *FAIL* commit not found in submodule repo ('../haddock.git')
remote:or not reachable from persistent branches
remote: hooklet hooks/update.secondary.d/check-submodule-refs failed
remote: hooks/update.secondary died
remote: error: hook declined to update refs/heads/master
To ssh://g...@git.haskell.org/ghc.git
! [remote rejected] HEAD -> master (hook declined)
error: failed to push some refs to 'ssh://g...@git.haskell.org/ghc.git'
simonpj@cam-05-unx:~/code/HEAD$
What's up? I have pushed the haddock commit!
THanks
Simon
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Can't push to haddock
I'm trying to push a patch that needs a supporting change to haddock.
I've pushed the haddock change to the ghc-head branch of
ssh://g...@github.com/haskell/haddock.git, which is (according to 'packages')
the relevant haddock upstream repo.
But when I try to push the GHC patch, I get this message
bash$ git push
Counting objects: 45, done.
Delta compression using up to 32 threads.
Compressing objects: 100% (45/45), done.
Writing objects: 100% (45/45), 27.56 KiB | 0 bytes/s, done.
Total 45 (delta 43), reused 0 (delta 0)
remote: performing commit message validations...
remote: Commit message validation passed!
remote: performing submodule-ref update validations...
remote: Submodule update(s) detected in
fa29df02a1b0b926afb2525a258172dcbf0ea460:
remote: utils/haddock => 24841386cff6fdccc11accf9daa815c2c7444d65
remote: *FAIL* commit not found in submodule repo ('../haddock.git')
remote:or not reachable from persistent branches
remote: hooklet hooks/update.secondary.d/check-submodule-refs failed
remote: hooks/update.secondary died
remote: error: hook declined to update refs/heads/master
To ssh://g...@git.haskell.org/ghc.git
! [remote rejected] HEAD -> master (hook declined)
error: failed to push some refs to 'ssh://g...@git.haskell.org/ghc.git'
simonpj@cam-05-unx:~/code/HEAD$
What's up? I have pushed the haddock commit!
THanks
Simon
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
