I can't easily type that out - and once the format can't be read / editing in a simple text editor, I'm starting to lean towards a nice binary format like protobuf.
There is a standard, and it is very simple and easy to use.
Different software uses different variants because we're not allowed to have nice things and devs are too lazy to use something slightly more complicated than .split(',')
Though if you're going to ban some common characters anyway like TSV, you might as well use CSV and ban commas, newlines, and quotation marks.
> Any escaping or encoding of these characters would make the format less human-readable, harder to parse and could introduce ambiguity and consistency problems.
Found the wording of "could introduce ambiguity and consistency problems" a bit odd, but guess they mean that even if things are specified precisely (so there's no ambiguity) not everyone would follow the rules or something? And they want to play nice with other tools following the TSV "standard"
Please. I wrote a csv parser a couple weeks ago in an hour or two. It's not that hard to handle the quoting and edge cases. Yes, maybe different parsers will handle them differently, but just document your choices and that's that. How is ambiguity better than completely disallowing certain chars? That's a non-starter
If you could pipe the ripgrep output into an editor, make changes, and have them applied, that would be great. Once you get all the text you want to change in one buffer, it should be easy to make repetitive changes quickly in your editor of choice.
I think you can. You pipe to `vim`, and it will open a buffer with the contents. I am not sure if it will pipe out, though.
Edit: I've now tried it myself with `rep`.
It's not automatic, unfortunately. You can use `vipe` (part of moreutils on my machine) to pipe into vim (or any `$EDITOR`) and to pipe the result out.
However, `rep` wants a pager. If you run `vim` with `rep` at the end of the pipeline, everything gets garbled because `rep` (well, the pager) is the one taking key presses.
To get around this, you can pipe `rep` to something else. I piped it to `cat -`, which forced it into outputting to `stdout`.
> Additionally, a subset of low entropy variations are included in network requests sent to Google. The combined state of these variations is non-identifying, since it is based on a 13-bit low entropy value (see above).
Author doesn't actually know what this information is being used for. Sure there can be a discussion about whether this information should be recorded at all (say, to determine if your site doesn't work on certain hardware), but claiming it _is_ fingerprinting is baseless.
> It probably also helps that extending Atom is much more approachable given that it's all Javascript...
I've heard this said before, I've had the opposite experience. ST offers a small api and it was easy for me to make something work with a single .py file.
I gave up trying the same thing in Atom; the api is larger and lower-level. Admission: I don't know coffeescript.
ST of course isn't nearly as flexible, there are many things you just can't do.
It's not about the limits of the language but the limits of the ST API itself. However, given Will Bond's background, this might just change for the better now that he's officially working for ST, so this is good news for all ST users obviously.
No high ranking USG official should be using insecure communication channels, as it will inevitably lead to leaks that could damage the state (secret information).
What Clinton did was dumb, but no one should have sent her classified emails in the first place. If the people sending the 'classified' documents were doing it through the right channels, it wouldn't be getting to her email server.
From a human rights, civil rights, universal rights, and transparency perspective all USG communications, and communications of all government officials everywhere should be public knowledge available to anyone on the planet at any time. At the end of the day what we find is how much all of these people conspire behind each other's backs to screw each other over and get the upper hand.
If citizens are not allowed to do this for fear of damaging society and government, politicians should be held to the same standards. For fear of damaging human rights of non-citizens, their livelihoods, economies of other countries, etc.
It's funny how government does not trust anyone below them, and yet expects everyone below to trust them when we know that they do not do the right thing most of the time (tm).
