| 5 Aug 2019 |
 swedneck:permaweb.io | true, but you still place scripts in some bin directory, usually | 19:37:07 |
 darnir | Hmm. Wasn't aware of that | 19:37:15 |
| swedneck:permaweb.io | maybe just add a line to the readme explaining where the files users are interested in are | 19:37:41 |
| darnir | I plan to provide an install target for make soon. Allowing you to install the scripts into /usr/bin or similar | 19:37:50 |
| darnir | I shall! Thanks for the input. | 19:38:08 |
| swedneck:permaweb.io | another bit of input: a script that wraps around curl to let you call the matrix API easily would be nice | 19:38:54 |
| darnir | In reply to @darnir:talk.go7box.xyz
I plan to provide an install target for make soon. Allowing you to install the scripts into /usr/bin or similar This just needs some refactoring to account for the location of sourced scripts. | 19:38:59 |
| darnir | In reply to @swedneck:permaweb.io
another bit of input: a script that wraps around curl to let you call the matrix API easily would be nice That's exactly what this does? | 19:39:17 |
| swedneck:permaweb.io | i mean a general script | 19:39:23 |
| darnir | To call which API? | 19:39:33 |
| swedneck:permaweb.io | not specifically for logging in etc | 19:39:38 |
| swedneck:permaweb.io | i guess the other option is to have specific scripts for each API call | 19:41:00 |
| darnir | I don't follow. You want a script that does what exactly? | 19:41:23 |
| darnir | The scripts I'm trying to provide make it easy to do common things. It's not necessarily a 1:1 mapping to the API | 19:41:54 |
| swedneck:permaweb.io | well the server-server api is definitely not needed :P | 19:42:15 |
| darnir | And it's not implemented either | 19:42:26 |
 AppAraat | darnir: on its way (actually already in my repo) just need to read up on some things before the actual MR | 21:33:24 |
| darnir | (y) | 21:53:53 |
| AppAraat | done | 23:52:15 |
 Gitlab Notifications | [Darshit Shah/Matrix Shell Suite] AppAraat opened merge request Removed "set -o pipefail" (!5) | 23:20:12 |
| 6 Aug 2019 |
| AppAraat | man, Gitlab is lacking some features IMO. First I can't see all of the MRs I started, and when I get a comment on a MR that I started, I only get an e-mail notification and no mention of it in the web UI. | 22:58:24 |
| AppAraat | oh wait I just had to filter on me as author: https://gitlab.com/dashboard/merge_requests?scope=all&utf8=%E2%9C%93&state=all&author_username=AppA | 23:05:15 |
| AppAraat | darnir: btw (and I know this is probably a pipe dream of mine), but what do you think about me attempting to replace dependency on jq ? | 23:10:26 |
| darnir | Sure. How would you approach it though? | 23:15:12 |
| darnir | I wanted the scripts to be purely POSIX. But had to settle for jq as a dependency. | 23:15:32 |
| darnir | Parsing json is quite hard. You can do it with sed and awk. But it's difficult, unmaintainable and error prone | 23:16:57 |
| AppAraat | yeah I was thinking sed & awk, since they're already present on most (all?) POSIX systems. However, doing that would indeed certainly not be easy. Perhaps add sed & awk as a fallback if jq is not found? | 23:40:23 |
| 10 Aug 2019 |
 errhammr moved to a different home server | Als Antwort auf @AppAraat:matrix.org
yeah I was thinking sed & awk, since they're already present on most (all?) POSIX systems. However, doing that would indeed certainly not be easy. Perhaps add sed & awk as a fallback if jq is not found? You mean, write a jq.sh script that does what jq does but in plain POSIX? | 11:32:55 |
| AppAraat | Or just replace singular instances of jq with custom sed & awk lines. There are not many places now where jq is used but maybe it might grow in the future. | 11:47:07 |
| darnir | More complex and interesting uses of jq are possible. And maybe we should use it. | 11:48:04 |
