summaryrefslogtreecommitdiffstats
path: root/2022/captions/emacsconf-2022-dbus--the-wheels-on-dbus--ian-eure--main.vtt
diff options
context:
space:
mode:
Diffstat (limited to '2022/captions/emacsconf-2022-dbus--the-wheels-on-dbus--ian-eure--main.vtt')
-rw-r--r--2022/captions/emacsconf-2022-dbus--the-wheels-on-dbus--ian-eure--main.vtt34
1 files changed, 17 insertions, 17 deletions
diff --git a/2022/captions/emacsconf-2022-dbus--the-wheels-on-dbus--ian-eure--main.vtt b/2022/captions/emacsconf-2022-dbus--the-wheels-on-dbus--ian-eure--main.vtt
index 7420e30c..c824d2db 100644
--- a/2022/captions/emacsconf-2022-dbus--the-wheels-on-dbus--ian-eure--main.vtt
+++ b/2022/captions/emacsconf-2022-dbus--the-wheels-on-dbus--ian-eure--main.vtt
@@ -325,10 +325,10 @@ If you want to interact with D-Bus from Emacs,
it's fairly straightforward.
00:04:30.080 --> 00:04:33.199
-There's a collection of functions like `dbus-get-property'
+There's a collection of functions like dbus-get-property
00:04:33.200 --> 00:04:35.039
-or `dbus-call-method', et cetera,
+or dbus-call-method, et cetera,
00:04:35.040 --> 00:04:37.639
and they almost all take this same set
@@ -416,7 +416,7 @@ of mixing up which thing is what.
So this sets the endpoint to that object,
00:05:41.480 --> 00:05:43.119
-calls `debase-get-property' on it,
+calls debase-get-property on it,
00:05:43.120 --> 00:05:45.039
and you can see it works exactly the same.
@@ -472,7 +472,7 @@ you often find yourself needing to look
at a different aspect of that object.
00:06:22.480 --> 00:06:26.599
-This is supported with the built-in EIEIO `clone' method,
+This is supported with the built-in EIEIO clone method,
00:06:26.600 --> 00:06:28.279
which takes an object
@@ -548,7 +548,7 @@ You can also, if you don't want to use the object,
you can provide the raw argument list.
00:07:18.240 --> 00:07:20.919
-Under the covers, this is basically an `flet'
+Under the covers, this is basically an flet
00:07:20.920 --> 00:07:23.279
where you're currying all of these functions
@@ -624,7 +624,7 @@ Let's generate some Elisp code
for that hostname1 service we were interacting with before.
00:08:19.640 --> 00:08:23.119
-`debase-gen-class' is the generation class,
+debase-gen-class is the generation class,
00:08:23.120 --> 00:08:26.079
and it says to create a class that matches this interface,
@@ -636,16 +636,16 @@ named "hostname1", and then the rest of these arguments
are the same ones to target the endpoint,
00:08:31.000 --> 00:08:32.919
-just like with `debase-object',
+just like with debase-object,
00:08:32.920 --> 00:08:34.759
-because it extends `debase-object'.
+because it extends debase-object.
00:08:34.760 --> 00:08:37.679
-`debase-gen-code' is a generic function
+debase-gen-code is a generic function
00:08:37.680 --> 00:08:40.119
-that takes any `debase-gen' class.
+that takes any debase-gen class.
00:08:40.120 --> 00:08:42.279
There are different classes for functions,
@@ -666,7 +666,7 @@ look about like we would expect:
creates a defclass named "hostname1",
00:08:52.160 --> 00:08:53.879
-which extends `debase-object',
+which extends debase-object,
00:08:53.880 --> 00:08:56.639
has all of the slots and accessors defined,
@@ -692,7 +692,7 @@ if you like.
NOTE Debase: ObjectManager
00:09:08.680 --> 00:09:12.279
-Debase also comes with `debase-objectmanager',
+Debase also comes with "debase-objectmanager",
00:09:12.280 --> 00:09:15.399
which is convenience for the D-Bus ObjectManager interface.
@@ -722,7 +722,7 @@ and by subscribing to the signals,
you can be notified when they change.
00:09:33.000 --> 00:09:35.999
-`debase-objectmanager' keeps a local cache,
+"debase-objectmanager" keeps a local cache,
00:09:36.000 --> 00:09:38.119
and will fire a callback on any change.
@@ -829,7 +829,7 @@ of "password".
I hit Enter, and it unlocks it, and it mounts it,
00:10:51.200 --> 00:10:53.319
-and it opens `dired' looking at it.
+and it opens "dired" looking at it.
00:10:53.320 --> 00:10:54.439
And here's a little README.
@@ -882,7 +882,7 @@ you can actually get results back from the remote operation.
So here's some code.
00:11:32.000 --> 00:11:35.679
-Here's a `dbus-eval' function, which takes a string,
+Here's a dbus-eval function, which takes a string,
00:11:35.680 --> 00:11:37.359
reads it, and evaluates it,
@@ -891,7 +891,7 @@ reads it, and evaluates it,
and returns whatever that value is.
00:11:39.360 --> 00:11:41.839
-Then we have a `debase-bind' block
+Then we have a debase-bind block
00:11:41.840 --> 00:11:44.799
that sets up an object on the session bus.
@@ -915,7 +915,7 @@ And we're gonna create this interface,
org.gnu.Emacs.Eval, and then register a method called Eval
00:12:02.520 --> 00:12:04.759
-that calls that `dbus-eval' function.
+that calls that dbus-eval function.
00:12:04.760 --> 00:12:08.119
Pretty straightforward, only a handful of lines of code.