This is just a friendly reminder that if you have any issues with
Haddock that you would like to get looked at, you should probably be
making your way to the Haddock Trac[1] now.
If you already have open tickets, you can probably get them looked at if
you reply to this thread. Unfortunately there
, do tell us what you need doing for the writer. Best way to do
this is to file a ticket on Haddock Trac
http://trac.haskell.org/haddock/ . If the ticket exists already, let me
know (here or on Trac) and I'll see whether I could prioritise it a bit
more.
John
+++ Mateusz Kowalczyk [Aug 30 13 02
On 01/09/13 07:02, yi lu wrote:
I want to know if it is possible that I use strings without .
If I type
*Preludefoo bar*
which actually I mean
*Preludefoo bar*
However I don't want to type s.
I have noticed if *bar* is predefined or it is a number, it can be used as
arguments. But can
On 01/09/13 13:59, Niklas Hambüchen wrote:
On 01/09/13 04:27, Mateusz Kowalczyk wrote:
It doesn't have to be 1-to-1 but the features have to be expressible in
both: it's useless if we have different features with one syntax but not
the other.
I don't find that useless. Markdown does not have
:30 PM, Mateusz Kowalczyk wrote:
Greetings café,
Perhaps some saddening news for Markdown fans out there. As you might
remember, there was a fair amount of push for having Markdown as an
alternate syntax for Haddock.
This is a little off-topic, but the Haddock website apparently is years
On 31/08/13 19:14, Niklas Hambüchen wrote:
Hello,
I disagree.
That's fine, that's why the thread is here.
While none of your detail points are wrong, they mainly focus on the
fact that there is no 1-to-1 mapping between the existing haddock markup
and Markdown. I don't think there needs
Greetings café,
Perhaps some saddening news for Markdown fans out there. As you might
remember, there was a fair amount of push for having Markdown as an
alternate syntax for Haddock.
Unfortunately, this is probably not going to happen for reasons listed
on the post I just published at [1].
Greetings café,
There are some problems in Haddock to do with Template Haskell that I
believe are being caused by Cabal. These were apparently addressed in
1.18 which came out recently. ‘Great!’, I thought.
My problem is that I'm unsure how to use 1.18. I'm using GHC HEAD (well,
3 days old now)
On 23/08/13 14:57, jabolo...@google.com wrote:
It's a bit pointless, if I have to know the package, where I want to
search in.
Yeah! It does sound a bit pointless. Hoogle should search everything
by default, and then you can refine your search by clicking on the '+'
or '-' on the packages
On 22/08/13 19:30, jabolo...@google.com wrote:
Hi,
I noticed Hayoo appears as a link in the toolbox of
http://hackage.haskell.org and also that Hayoo seems to display better
results than Hoogle. For example, if you search for 'PublicKey' in
Hayoo, you will get several results from Hackage
On 20/08/13 09:48, Niklas Hambüchen wrote:
Nice!
I hope that haskell-suite will eventually become awesome and solve most
of our automation-on-Haskell-code needs.
Two questions:
1) My most desired feature would be a syntax tree that does not pluck
pluck comments out and make me treat
On 20/08/13 11:02, JP Moresmau wrote:
BuildWrapper has some code that tries to link back the comments to the
declaration from the AST generated by haskell-src-exts and the comments.
See
https://github.com/JPMoresmau/BuildWrapper/blob/master/src/Language/Haskell/BuildWrapper/Src.hs.
The unit
On 20/08/13 11:56, Dag Odenhall wrote:
Good stuff!
Is there any way, or plans for a way, to parse a file based on its LANGUAGE
pragmas? Last I checked e.g. HSP simply enabled all extensions when
parsing, which can cause code to be parsed incorrectly in some cases.
Can you give any
On 17/08/13 10:11, Christopher Done wrote:
Anyone ever needed this? Me and John Wiegley were discussing a decent
name for it, John suggested inv as in involution. E.g.
First thing I thought was ‘inverse’…
inv reverse (take 10)
inv reverse (dropWhile isDigit)
trim = inv reverse (dropWhile
On 15/08/13 23:07, jabolo...@google.com wrote:
Hi,
I cannot find a similar ticket, so it seems that no one has filed this
issue before. As a general comment, I think this issue is a good
example that perhaps docstrings should go in the AST.
In any case, I would ask someone with a trac
On 16/08/13 08:16, Mateusz Kowalczyk wrote:
In the future, please try with more recent version of GHC.
This is no longer a parse error with HEAD or 7.6.3. Instead, given
-- | 'y' and 'x' are here
(x, y) = (1, 2)
you get documentation generated for ‘x’ and Haddock doesn't seem to
have
On 16/08/13 11:08, Roman Cheplyaka wrote:
* Mateusz Kowalczyk fuuze...@fuuzetsu.co.uk [2013-08-16 08:16:35+0100]
In the future, please try with more recent version of GHC.
This is no longer a parse error with HEAD or 7.6.3.
Uhm, actually there is, with 7.6.3.
% cat haddock.hs
-- Main
I'm writing a small tool to help to analyse Haddock comments in
Haskell source files to help me to indicate any potential breakage to
documentation in existing source files.
Currently I'm doing the parsing with the GHC's ‘parser’ function with
Opt_Haddock set and I filter out everything I don't
On 14/08/13 19:02, Niklas Broberg wrote:
Hi Mateusz,
haskell-src-exts is not haddock-aware I'm afraid, so I don't have any real
solution for you. The one you mention, i.e. going through the whole parse
result and stiching things together manually seems like the best bet if you
want to use
a parse error. It's
up to the developer to visually inspect
that their markup produced what they wanted – we can't read minds (and
frankly, the rules are fairly simple).
Roman
* Mateusz Kowalczyk fuuze...@fuuzetsu.co.uk [2013-07-30 23:35:45+0100]
Greetings cafe,
As some of you might know, I'm
On 31/07/13 08:21, Mats Rauhala wrote:
Is Data.Text as an extra dependency really that bad? Remember that you
are parsing comments, prose, human produced text, where Data.Text is way
more useful than ByteString.
It has to come with GHC boot packages and it currently doesn't. I have
updated my
Greetings cafe,
As some of you might know, I'm hacking on Haddock as part of Google
Summer of Code. I was recently advised to create a blog and document
some of what I have been doing recently. You can find the blog at [1] if
you're interested. The first post goes over the work from the last
On 29/07/13 18:39, Paul Koerbitz wrote:
Dear list,
I am not sure if this is the right place to post this, but I just went
to haskell.org and got a
Sorry! This site is experiencing technical difficulties.
error message.
cheers
Paul
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/07/13 22:08, Micah Cowan wrote:
So, just for fun, I came up with a way to abuse the language in
order to define a function whose argument is optional:
-- dirty-trick.hs - A sneaky way to do var args fns in Haskell
{-# LANGUAGE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/07/13 19:50, Chaddaï Fouché wrote:
On Fri, Jul 5, 2013 at 11:03 PM, Ömer Sinan A?acan
omeraga...@gmail.comwrote:
There's an implicit quantifier in type of `f`, like this: `f ::
forall a. a - ListF a a`. When I add `ScopedTypeVariables` and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/06/13 23:13, Maksymilian Owsianny wrote:
Hmm... I'll have to look into it, but it looks promising. Now if
we could make hackage run such fixes automatically whilst sending
pull requests to authors... then maybe we could even fix The Great
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/06/13 19:10, Omari Norman wrote:
Hi all,
rainbow is a simple package to help you print colored text on
UNIX-like systems. It's different from packages like terminfo (upon
which it is based) and ansi-terminal in two ways. First, rainbow
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/06/13 13:15, Roman Cheplyaka wrote:
I am happy to announce the first release of standalone-haddock.
http://feuerbach.github.io/standalone-haddock/
standalone-haddock generates standalone haddock Haskell
documentation.
When you simply
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greetings,
I'm attempting to build lifted-base (as a dependency for ghc-mod) but
cabal-install fails every time during the linking phase. I pasted the
full log of `cabal install lifted-base --verbose' to hpaste at [1].
I'm attempting to build it with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/05/13 04:15, Kazu Yamamoto () wrote:
Hi Niklas,
Just one note: The emacs link on the left is not found.
Fixed. Thank you.
--Kazu
___ Haskell-Cafe
mailing list Haskell-Cafe@haskell.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18/05/13 17:25, Roman Cheplyaka wrote:
I am observing a non-deterministic behaviour of aeson's parser.
I'm writing here in addition to filing a bug report [1] to draw
attention to this (pretty scary) problem.
To try to reproduce this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/05/13 16:59, John wrote:
is'nt it possible, to write it in one line without any nested
functions in WHERE? If it's possible I'd prefer that...
any idea?
Thanks
-- View this message in context:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/05/13 17:53, John wrote:
thanks for your tips.
As I said, I'm at the very beginning of Haskell. I try it to
understand as much as I can, however the topic is very new to me.
Sorry about my silly questions...
You said, their is a mailing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/05/13 18:18, Jerzy Karczmarczuk wrote:
MATEUSZ,
There is nothing wrong with sending beginner questions to h-café!
After all, a FRIENDLY community is for whom? For Simon PJ only?
Notice that John got more than a dozen answers, people TRY
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greetings,
We can currently do something like
class (Num a, Eq a) = Foo a where bar :: a - a - Bool bar =
(==)
This means that our `a' has to be an instance of Num and Eq. Apologies
for a bit of an artificial example.
Is there a way however to do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/05/13 06:57, Ben wrote:
sorry, i was only trying to make a helpful suggestion!
just to clarify: i'm not championing asciitext (or any other
format) -- i only heard about it recently in a comment on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/05/13 09:26, Andrew Butterfield wrote:
My 2c (before such coins disappear...)
On 2 May 2013, at 09:14, Petr Pudlák wrote:
Hi,
Personally I'd incline to choose some existing, well-established
markup language with formal specification
, 2013 at 4:46 AM, Mateusz Kowalczyk
fuuze...@fuuzetsu.co.ukwrote:
On 02/05/13 09:26, Andrew Butterfield wrote:
My 2c (before such coins disappear...)
On 2 May 2013, at 09:14, Petr Pudlák wrote:
Hi,
Personally I'd incline to choose some existing,
well-established markup language
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30/04/13 03:05, Christopher Howard wrote:
Hey guys, this probably isn't the official GHC mailing list, but
I've been trying to build and install a new GHC on an old RHEL5
system, as mentioned in my previous Cafe thread. I was able to make
some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/04/13 00:08, Joe Nash wrote:
Managed not to send to all:
I think the reason markdown was the original suggestion was due to
the fact it is a very widespread and popular syntax, and as Johan
commented in the original thread, has to an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/04/13 11:57, Joe Nash wrote:
On 28 Apr 2013 11:33, Mateusz Kowalczyk fuuze...@fuuzetsu.co.uk
wrote:
If the flexibility of having it pandoc compatible is a desired
feature, can this not be achieved through implementing markdown
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/04/13 10:23, Alistair Bayley wrote:
How's about Creole? http://wikicreole.org/
Found it via this:
http://www.wilfred.me.uk/blog/2012/07/30/why-markdown-is-not-my-favourite-language/
If you go with Markdown, I vote for one of the Pandoc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/04/13 22:18, John MacFarlane wrote:
I agree with Chris that it would be better to have a standard
syntax for Haskell documentation. Especially if the alternative is
ten different markup languages. (Remember, all of these need to be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greetings,
In light of fairly recent discussion, on this mailing list, I decided
to investigate the topic of Markdown support for Haddock. The archives
of the recent discussion can be seen at [1]. This post aims to
summarise the current state of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/04/13 21:50, Johan Tibell wrote:
On Tue, Apr 9, 2013 at 12:40 PM, Joe Nash joen...@blackvine.co.uk
wrote:
I would be interested in discussing this project with a potential
mentor if one happens to be reading. I'm a second year Computer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/04/13 12:35, Ketil Malde wrote:
Hi,
I proposed a bioinformatics GSoC project involving Haskell using
OSC as the mentoring organization. Typically, haskell.org projects
concern infrastructure rather than applications, and I don't know
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
About two weeks ago we got an email (at ghc-users) mentioning that
comparing to 7.6, 7.7.x snapshot would contain (amongst other things),
type level natural numbers.
I believe the package used is at [1].
Can someone explain what use is such package
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/04/13 20:42, Mateusz Kowalczyk wrote:
About two weeks ago we got an email (at ghc-users) mentioning that
comparing to 7.6, 7.7.x snapshot would contain (amongst other
things), type level natural numbers.
I believe the package used
Greetings,
It seems that the Haskell community consistently participates in the
Google Summer of Code project. I (and probably many others) am
interested in taking part in one of such projects but I have a question
in regards to the expertise. I know that this year's projects aren't up
yet but by
On 19/02/13 13:39, Daniel Trstenjak wrote:
On Tue, Feb 19, 2013 at 02:15:33PM +0100, Vo Minh Thu wrote:
Screenshots obviously ;)
Hurray!
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
wrote:
Mateusz Kowalczyk fuuzetsu at fuuzetsu.co.uk writes:
I don't know about xml-conduit but I know that such thing is possible in
HXT. See the `Modifying a Node' section at [1] for a trivial example.
You probably will have to read the whole page to somewhat understand
what's going
I don't know about xml-conduit but I know that such thing is possible in
HXT. See the `Modifying a Node' section at [1] for a trivial example.
You probably will have to read the whole page to somewhat understand
what's going on though.
[1] -
You don't reason about the bits churned out by a compiler but about the
actual code you write. If you want to preserve such information during
the compilation process, you probably want to run the compiler without
any optimization flags at all.
At the moment, with the way you are thinking about
I don't understand why you're putting it in your .cabal file. Isn't
something like 3.8.5 over at [1] what you're trying to achieve?
...
I had a look at a package ([2]) that I know uses a multi-line code block
example. Here's what I found in its cabal file:
An example:
.
runShpider $
Quite informative, thank you. It was nice to see how to combine the
suites together as most places only show how to use one.
The mention about Travis CI is also much appreciated; it seems like a
really good project and I will definitely be using it in the future.
Mateusz Kowalczyk
On 21/01
Ah, zeroArrow looks exactly like what I need here!
Thanks, this helps.
Mateusz Kowalczyk
On 01/01/13 01:08, dag.odenh...@gmail.com wrote:
( is my GHCi prompt, might be a bit confusing for an arrow example.)
On Tue, Jan 1, 2013 at 2:05 AM, dag.odenh...@gmail.com
mailto:dag.odenh
.
Is this the right approach? Is there a built-in that already does what I
want? It
seems like a common task...
Mateusz Kowalczyk
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
love to hear whether you find any other people though. It would be
nice if some Haskell talks could be held in the area if there are enough
people.
Good luck on your search,
Mateusz Kowalczyk
On 30/12/12 14:38, Alfredo Di Napoli wrote:
Morning Cafe,
I've been living in Manchester for 1 month now
58 matches
Mail list logo
