chrishill89

7 ms·

61.
by chrishill89 2y ago
You can disallow those metacharacters in the data proper. Then you have a format that can store any utf8 or whatever except the non-whitespace control codes without any escaping. That solves a problem in an opinionated way. Just like how js
62.
by chrishill89 2y ago
You can use ASCII-separated values in qsv.[1] For the unlikely event that you are dealing with data with the metacharacters: qsv will use some other control character as the “quote” character to deal with that.
63.
by chrishill89 2y ago
I’ve made my own software keyboard using Xkb (Linux). Based on a standard (ISO/European) keyboard. It’s qwerty but I’ve made changes in order to (first motivation) more easily be able to write all kinds of symbols. So the number row is
64.
Cookbook AI: Bridging Culinary Arts and AI Technology(christianek.io)
1 points by chrishill89 2y ago|0 comments
65.
by chrishill89 3y ago
I recently wanted to split and iterate on a String (`char *`) in the Git project. I was not feeling good that it had come to this point since I'm not a C programmer. ChatGPT told me that I wanted `strtok`. So I tried that but then the
66.
by chrishill89 3y ago
They don’t require a space around them. That’s a French thing. They don’t require that in Swiss German. Also not in Norwegian and probably others.
67.
by chrishill89 3y ago
I’ve started using a sort of hanging quotation style for block quotes in commit messages. From commit 3927bbe9a4: “ This matches the behavior of COMMIT_EDITMSG, which stays around in case of error. Two spaces, one q
68.
by chrishill89 3y ago
Thanks, that makes sense. :)
69.
by chrishill89 3y ago
> if it is an octal escape it’s four; I just figured out that 1. `\0` and octal numbers share the same prefix 2. Octal numbers can have 1-3 digits (not fixed) So maybe it’s more tricky than I thought.
70.
by chrishill89 3y ago
I don’t see the issue. If it’s a literal character it’s one character; if it’s `\n` or or `\0` then it’s two; if it is an octal escape it’s four; and so on. You have to parse them the same way in a character literal as in a string literal,
71.
by chrishill89 3y ago
> Multi-character constants I asked on SO why C characters use `'` on both ends instead of just one (e.g. why not just `'a` instead of `'a'`?). This seems to have been the biggest reason.
72.
by chrishill89 3y ago
> The fact that the whole file is then non-portable is a feature, not a bug; if you need to pack an entire table into a field, encode it in some portable encoding (eg base64) and add a decoder field. I guess you could: 1. Use unit-separa
73.
by chrishill89 3y ago
That deals with commas but (since AWK is line-oriented) I doubt that deals with multi-line fields?
74.
by chrishill89 3y ago
I agree. And some tools support it, e.g. Miller.[1] There are a lot of power tools for CSV. All they need to do to support this format is to support it as input and output. It should be possible for example to add support to Csvkit[2] as in