summaryrefslogtreecommitdiffstats
path: root/2020/info
diff options
context:
space:
mode:
Diffstat (limited to '2020/info')
-rw-r--r--2020/info/25.md37
1 files changed, 36 insertions, 1 deletions
diff --git a/2020/info/25.md b/2020/info/25.md
index 5cc2cc42..c6ce6ef3 100644
--- a/2020/info/25.md
+++ b/2020/info/25.md
@@ -22,6 +22,41 @@ displayed to you in the buffer `*jq-json*`.
In this lightning talk, I'll give a quick overview on how to use
counsel-jq and how to build similar completion functionality.
-# Resources
+## Resources
<https://200ok.ch/posts/2020-11-30_emacsconf_traverse_complex_json_structures_with_live_feedback_with_counseljq.html>
+
+## Questions from the pad
+
+### Q4: Any plans for counsel-yq and/or -xq? ;-)
+
+- counsel-jq currently just shells out to jq. Adding tools build on top of jq (at least yq is afaik) would be very easy. We could employ a strategy pattern to find the right tool based on the current major-mode with a configurable fallback. Here's the place where the shellout happens: <https://github.com/200ok-ch/counsel-jq/blob/master/counsel-jq.el#L23>
+
+- Would you be interested in making a PR for that?(;
+
+### Q3: Why repository_url did not autocomplete in addition to the result (I know that it is ivy thing but possible to configure?)
+
+- There's no autocompletion for the search query, but that would be a great addition. That would theoretically be possibe by employing jq to look ahead in the current tree and providing options for autocomplete. I'm not certain if Ivy does have autocomplete for search queries, though.
+
+- If somebody has more knowledge on that and would like to ping me up or provide a (draft) PR, I'd be happy to help out in that endeavour!
+
+### Q2: is it difficult to provide autocompletion for the json query in the minibuffer?+1
+
+- Good question. I'd be curious, too. It's the same question as Q2 where I went into a possibe scenario.
+
+### Q1: Is it possible to search in arbitrary deep objects? E.g., an AST represented in JSON.
+
+- counsel-jq uses jq under the hood, so all queries that are valid queries in jq should be valid in jq. Hence, I'm inclined to say 'yes'(;
+
+## Notes from the pad
+
+- 200ok GmbH (<https://200ok.ch>)
+- Play Emacs like an instrument: <https://www.youtube.com/watch?v=gfZDwYeBlO4>
+- jq: <https://stedolan.github.io/jq/>
+- ivy supports dynamic sources. So does helm I guess.
+- counsel-jq: <https://github.com/200ok-ch/counsel-jq>
+- organice: <https://github.com/200ok-ch/organice>
+- Entire presentation inside Emacs, with a count down reminder.
+
+
+