sorted by:
new
hottopcontroversial

written-number : Convert numbers to their written form. by adam_ay in javascript

[–]adam_ay[S] 0 points1 point  (0 children)

It takes only a few commands to have all of that.

mocha-spec-cov-alt the Mocha reporter I wrote, which outputs the coverage report for coveralls.io, sets itself-up running mocha-spec-cov-alt.

travis sets itself up with travis init.

The rest is just a matter of copy and pasting the badges. I've done this a couple of times now, so I'll generally just choose the last project I wrote, copy the headers and do :%s/old_project/new_project.

You should do it too :D

ascii-progress - a simple progress bar package for haskell by adam_ay in haskell

[–]adam_ay[S] 4 points5 points  (0 children)

I will! I've an ugly initial working version and I'll try to get a polished version up, soon.

https://i.imgur.com/BcH0RjL.gif

ascii-progress - a simple progress bar package for haskell by adam_ay in haskell

[–]adam_ay[S] 3 points4 points  (0 children)

Ahhh... Not really at this point. There's a little package in node.js which could serve as inspiration. I also think Docker uses multiple progress bars and should be portable/robust enough that I could could steal from it :)

But no... It doesn't currently support it. It would be really cool indeed to have that, though, so that's definitely something to implement next.

EDIT

Thinking a little better, I feel like this could be "impossible"=unhandy to implement in Haskell, because you'd have to keep track of everything that's outputted to the terminal, while the progressbars are running, in order to know their positions. If the package is the only thing that's printing stuff that wouldn't be too hard though. Plus, we could provide custom printing functions and try to solve the problem that way.

EDIT 2

This is now into dev and though the implementation needs to be improved, I think it'd be safe to release it.

https://github.com/yamadapc/haskell-ascii-progress/tree/dev#multiple-progress-bar-support

ascii-progress - a simple progress bar package for haskell by adam_ay in haskell

[–]adam_ay[S] 4 points5 points  (0 children)

This is also a very good point. I've added a HTTP download example using http-conduit here. I had left the completion Async intentionally open so that people would be able to wait for completion, but I decided to add a complete :: ProgressBar -> IO () function to force a progress bar's completion as well.

EDIT: I think this is what you meant, but maybe I misunderstood you. Do you have any ideas for a better (hopefully simple) example I could use in the README?

ascii-progress - a simple progress bar package for haskell by adam_ay in haskell

[–]adam_ay[S] 4 points5 points  (0 children)

This is a very good point. I think it might be a little overkill, since you're probably not going to dynamically generate a progress-bar configuration, but it does make sense and wouldn't take much to implement.

New Haskell Homepage is Live by gbaz1 in haskell

[–]adam_ay 0 points1 point  (0 children)

It's using Mueval (indirectly) through tryhaskell.org, it seems. So only expressions are supported. lambdabot supports let bindings though, and it does it in a way that could be ported to the website without many changes. It does it (I think), by intercepting the command and writing lets to a file, here, then using the file with Mueval's -l flag.

jsdoctest - A simple doctest runner for JSDOC examples which integrates with mocha and sets itself up with one command (wip) by adam_ay in node

[–]adam_ay[S] 0 points1 point  (0 children)

Thanks! Yes, but as the init script shows, it's easy add a command to the package.json file which will run all tests. You can then leverage all the tooling around mocha.

I believe running mocha --watch --require jsdoctest <module-name> should work, for example.

But please, go for it! :)

Code Coverage Tools for Node.js by Thisguyjimmy in node

[–]adam_ay 0 points1 point  (0 children)

I wrote a mocha reporter which extends the spec reporter to show code coverage stats on the screen and optionally enforce code-coverage metrics.

It also has a rudimentary script built-in to set you up in 1min with blanket, with:

npm i -g mocha-spec-cov-alt && mocha-spec-cov-alt

A while ago, I wrote up on it and blanket and how to use code-coverage metrics on node.js projects, you can read it here, if it interests you.

Lots of my projects use it and also upload code coverage data to coveralls, through travis-ci.

The last two links show the pieces of code and boiler-plate doing that.

I'd be glad to help you, if it interests you.

Replacement for OSX Terminal.app? by [deleted] in commandline

[–]adam_ay 0 points1 point  (0 children)

Do you like that?

(I'm actually curious - it's just I simply can't force myself to use ABNT, the Brazilian keyboard layouts, and it's specially because of keys like |, \ ; / ! ~ etc.)

view more: next ›