Don't implicitly convert . & .syntuxignore

[seidtgeist]

@felixge mentioned respecting contents of .gitignore, a potential .syntuxignore and also ignoring folders like node_modules

@klipstein recommended disabling the default behaviour of recursively converting the current dir

Edit: Herped the derp

[seidtgeist]

Ok, here's my personal reasoning:

Because syntux is a program which modifies files we might want to disable the implicit path = current dir behavior. Let's compare this with *nix: ls for example clearly doesn't need a path. rm on the other hand, well, what can I say, that's a stupid example. sed and awk need arguments. chmod and chown need arguments. If we changed that, to achieve the same result one could simply write syntux . instead of syntux. I think that's bearable.

Additionally I think a .syntuxignore file would make sense. Maintaining an internal list of common folders might be a never ending task. Maybe rather provide/create an example .syntuxignore in a syntux --init command which would create syntax.json, too?

[felixge]

I'm ok with not assuming the CWD as the path. Lets change that.

[seidtgeist]

Might as well make this an stdin to stdout mode.

[felixge]

Either that, or a REPL.

[seidtgeist]

+1

Can we detect how syntux_cli is being used from the outside? Thinking "pipe vs repl mode".

[felixge]

Can we detect how syntux_cli is being used from the outside? Thinking "pipe vs repl mode".

I think so. If not we'll have a switch for the repl. Piping should be given more importance.