pretty-print
Here are 196 public repositories matching this topic...
-
Updated
May 6, 2020 - Clojure
-
Updated
Nov 22, 2018 - JavaScript
-
Updated
Jun 29, 2018 - Swift
-
Updated
Dec 31, 2018 - JavaScript
It would be nice to have a website that could be used interactively to show how pretty-simple formats things.
This could be done in the following steps:
- Figure how to compile
pretty-simplewith GHCJS. - Create a small frontend application in either Haskell with GHCJS or just plain JavaScript. The frontend application should roughly look like this: https://jsoneditoronline.org/. It s
-
Updated
May 18, 2020 - Erlang
-
Updated
May 29, 2020 - Scala
-
Updated
Sep 8, 2017 - JavaScript
-
Updated
May 24, 2020 - PHP
-
Updated
Apr 2, 2020 - Python
-
Updated
Apr 10, 2020 - JavaScript
-
Updated
Nov 23, 2019 - JavaScript
-
Updated
Jun 4, 2019 - JavaScript
from https://metacpan.org/pod/Data::Printer
Changing output targets
By default, p() will be set to use STDERR. As of version 0.27, you can set up the 'output' property so Data::Printer outputs to several different places:
output => 'stderr' - Standard error. Same as *STDERR output => 'stdout' - Standard output. Same as *STDOUT output => $filename - Append
-
Updated
May 27, 2020 - Python
HTTPony is not a real workhorse server (yeah, I'm milking this pun for all its worth). It might be nice to provide some kind of route manifest with canned responses if a user wants to simulate something more than 200 OK.
I think they should be called pony shows.
A frequent complaint about R documentation is that the examples are at the very end of the documentation, and often people learn best by example.
Perhaps rdoc could move the examples section to just below the description? Maybe controllable by an option if people want to preserve the default ordering.
-
Updated
Jul 12, 2019 - Go
-
Updated
Sep 12, 2019 - JavaScript
-
Updated
Jul 9, 2018 - Lua
-
Updated
Feb 19, 2019 - JavaScript
-
Updated
Apr 4, 2020 - JavaScript
-
Updated
May 30, 2020 - OCaml
Add Benchmarks
As Rust is so strong performance-wise it'd be cool to be among the fastest json pretty printers out there.
Maybe as a start three files with ~1Kb, ~1MB and ~1GB..
I'd accept a PR anytime!
src/parsing.c: In function ‘parse_object_close’:
src/parsing.c:80:5: warning: ‘strncat’ specified bound depends on the length of the source argument [-Wstringop-overflow=]
80 | strncat(value, to_append, strlen(to_append));
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CC gcc -c src/tokens.c -o lib/tokens.o -O3 -g -std=gnu99 -fstack-protector-all -Wstack-protector -Wall
Improve this page
Add a description, image, and links to the pretty-print topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the pretty-print topic, visit your repo's landing page and select "manage topics."
becomes
stuff [/some/path].stuff [/some/path].but it should have spacing after the first period.
And when I'm using `preserveNewlines' set to true, shouldn't it be like this?
But instead it puts it on one line and ignores preserveNewlines.