News for hackers. Stuff that matters.

ingy

https://github.com/gloathub/glojure is the actively maintained fork.
Try out this Wasm browser REPL https://gloathub.org/repl/

Gloat is a Glojure AOT automation tool. I worked with James Hamlin to get Glojure AOT going last summer and have been moving it forward since. I've also been working with marcingas (nooga) to get Gloat/Glojure/let-go all cooperating.

> "YAML documents can't start with a tab while JSON documents can, making JSON not a strict subset of YAML"

But YAML can start with tabs. Tabs are allowed as separating whitespace in most of the spec productions but are not allowed as indentation. Even though those tabs look like indentation, the spec productions don't interpret them as such.

See my comment above and esp see https://play.yaml.io/main/parser?input=CXsKCQkibGlzdCI6IFsKC...

Note: the YAML spec maintainers (I am one) have identified many issues with YAML which we are actively working on, but (somewhat surprisingly) we have yet to find a case where valid JSON is invalid YAML 1.2.

This is completely valid YAML.

YAML does not allow tabs in indentation, but the tabs in your example are not indentation according to the YAML spec productions.

You can see it clearly here against many YAML parsers: https://play.yaml.io/main/parser?input=CXsKCQkibGlzdCI6IFsKC...

As tinita points out, sadly PyYAML and libyaml implement this wrong.

See https://matrix.yaml.info/

I'm one of the authors of the YAML specification. https://yaml.org/spec/1.2.2/

To date we honestly have not identified a case where where valid JSON is not valid YAML 1.2.

If anyone can point out a case where this is true, please file an issue here: https://github.com/yaml/yaml-spec/issues/

Re:Git 2.0 release notes on Wednesday March 12, 2014 @10:29AM (#7385789)
You may want to take a look at https://github.com/ingydotnet/git-subrepo#readme (and join #git-commands on freenode).
Re:Exploring an alternative to git-subtree on Monday February 24, 2014 @04:39PM (#7293570)
Serendipitously, I've been working on a new Git command called `git-subrepo` for the last 3 months that deals with all these concerns and more. The command became fully usable about a week ago.

The https://github.com/ingydotnet/git-subrepo addresses all the known concerns of the project owner, project collaborators, and end users. It keeps state in `path/subdir/.gitrepo` which means that git commands like `git mv` just work.

It also has squeaky clean history, which I've documented here: https://github.com/ingydotnet/git-subrepo/blob/master/doc/in...

Feel free to contact me by GitHub, IRC [email protected] or email [email protected].