summaryrefslogtreecommitdiffstats
path: root/2022/talks/buttons.md
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--2022/talks/buttons.md73
1 files changed, 73 insertions, 0 deletions
diff --git a/2022/talks/buttons.md b/2022/talks/buttons.md
index 262bafd9..dc4e9a39 100644
--- a/2022/talks/buttons.md
+++ b/2022/talks/buttons.md
@@ -26,7 +26,80 @@ Outline:
3. Description of how Hyperbole supports creating new implicit buttons using the Hyperbole defil macro
4. Examples of applying the defil macro together with different personal data structures
+# Discussion
+- Hyperbole - <https://www.gnu.org/software/hyperbole/>
+- <https://savannah.gnu.org/projects/hyperbole/>
+- Get a lot of power and put buttons everywhere without having to
+ learn a lot of syntax. This is what is cool about hyperbole. 
+- You can expand and collapse trees if you export hyperbole kotl-files
+ (unlike exporting from org-mode)
+- These hyperbole buttons looks quite cool!
+- the mapping is agnostic if you are looking at the code or any other document, that is quite powerful, thanks for the presentation!
+- I was in the other room and just came in at the last moment to hear about hyperbole for the first time!
+
+## Questions
+
+- Q: So with one line of code you can create custom hyperbutton types
+ that are live in any Emacs buffer.  Is that right?
+ - A: Yes.
+- Q:Is there a good way to share common patterns for links other than
+ the ones that you shared? shall those be PRs to your repository?
+ - A: 
+ - No, I view these buttons first as specific for your
+ application or supporting your way of working so would have
+ less value in sharing. On sharing is that they could be used
+ for collabration between different users where each user
+ would define their own mapping to work in their environment.
+ In the file example in the presentation each users could
+ have has stored the data in different local folders but use
+ the same pattern to link to the data.
+ - Thinking about it again now I realize that you mean sharing
+ as examples or for inspiration. That is a good idea. We
+ don't have any example section but we could add that. You
+ can also post ideas and examples to the Hyperbole user
+ mailing list.
+- Q: I liked the link to evaluate Calc expressions. Any way to get the
+ outcome into the buffer and not just in the message window? It could replace embedded calc mode with more control... I guess any elisp code can be used for the target evaluation.
+ -ericsfraga
+ - A: You can mix Hyperbole buttons with Org source blocks too, so
+ you could get things in a buffer that way too.
+ - The example uses a lambda expression to get the result
+ displayed. To get the result inserted in the buffer would just
+ require a function to do that instead of displaying it in the
+ message window.
+ - This would be a simple example of this (It will insert the
+ result after the button, removing rest of the line but keep the
+ point in the button allowing you to change it to calculate a new
+ result.)
+ ````
+ (defil demo-do-math "<<" ">>" ".*"
+ '(lambda (x) (save-excursion (search-forward ">>")
+ (kill-line) (insert " " (calc-eval x) " "))))
+ ````
+- Q: How did you present the right buffer with shortcuts at the right
+ of your buffer? -- a lot of people are wondering.
+ - A:  interaction-log mode -
+ <https://github.com/michael-heerdegen/interaction-log.el>
+ - In combination with displaying it in a separate frame.
+- Q:What kind of cool actions do you use in Hyperbole?
+ - A: Among other things... 
+ - You can expand and collapse trees if you export hyperbole
+ kotl-files (unlike exporting from org-mode) kotl-files are
+ Hyperbole outliner files.
+ - I use implicit button defined with the defib macro that
+ allows me to match to text with no start and stop 
+ delimiters. That way I can match on identifiers used in
+ other systems verbatim, such as identifiers in ticketing
+ systems. Much like the in Hyperbole built in debbugs for the
+ pattern "bug#id-number"
+- Q: Does the links/buttons created in hyperbole (like that one with
+ the url) get exported on org-mode files too? (like when exported to
+ html).
+ - A: There is currently no support for turning the implicit
+ buttons into html-links on export. In practice I would think
+ that to be hard and would only support parts of the
+ functionality but is an interesting idea.
[[!inline pages="internal(2022/info/buttons-after)" raw="yes"]]