summaryrefslogtreecommitdiffstats
path: root/2020/info/25.md
diff options
context:
space:
mode:
authorSacha Chua <sacha@sachachua.com>2020-12-01 00:34:46 -0500
committerSacha Chua <sacha@sachachua.com>2020-12-01 00:34:46 -0500
commitb49d5383ffb9ad3ae75c0963d16a29587a5c2a98 (patch)
tree28a7b3af4a99b1d7d004cab84c998ea598af7b42 /2020/info/25.md
parenta5359499330bab9a3b4dc3c98b8e52e65ece8c49 (diff)
downloademacsconf-wiki-b49d5383ffb9ad3ae75c0963d16a29587a5c2a98.tar.xz
emacsconf-wiki-b49d5383ffb9ad3ae75c0963d16a29587a5c2a98.zip
Tweak pad formatting
Diffstat (limited to '2020/info/25.md')
-rw-r--r--2020/info/25.md12
1 files changed, 6 insertions, 6 deletions
diff --git a/2020/info/25.md b/2020/info/25.md
index 74abfee6..5c7cf27c 100644
--- a/2020/info/25.md
+++ b/2020/info/25.md
@@ -33,23 +33,23 @@ counsel-jq and how to build similar completion functionality.
### 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>
+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?(;
+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.
+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!
+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.
+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'(;
+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