summaryrefslogtreecommitdiffstats
path: root/2020/subtitles/emacsconf-2020--31-lakota-language-and-emacs--questions--grant-shangreaux-autogen.vtt
blob: 164d8d8d4dc80c1934cdbcdb018a17d589bd569d (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
WEBVTT

00:00:05.120 --> 00:00:05.680
hello

00:00:05.680 --> 00:00:10.080
can you hear me yes I can awesome

00:00:10.080 --> 00:00:12.400
all right so we have a couple minutes

00:00:12.400 --> 00:00:13.200
and

00:00:13.200 --> 00:00:15.200
uh it seems a couple questions as well

00:00:15.200 --> 00:00:17.680
so take it away

00:00:17.680 --> 00:00:20.000
okay I won't share my screen unless

00:00:20.000 --> 00:00:22.640
needed um

00:00:22.640 --> 00:00:25.439
looks like question one advantages

00:00:25.439 --> 00:00:27.599
advantages of using Emacs input methods

00:00:27.599 --> 00:00:31.119
over something like x compose

00:00:31.119 --> 00:00:32.559
well there's a there's a couple things

00:00:32.559 --> 00:00:34.320
there one is

00:00:34.320 --> 00:00:37.360
um Emacs is cross platform so

00:00:37.360 --> 00:00:39.520
writing this input mode for Emacs means

00:00:39.520 --> 00:00:41.520
if I do end up using

00:00:41.520 --> 00:00:44.559
a non-free operating system I can still

00:00:44.559 --> 00:00:46.480
use Emacs I can still type

00:00:46.480 --> 00:00:49.920
in the way that I would like to um

00:00:49.920 --> 00:00:52.800
I did look in I don't I actually don't

00:00:52.800 --> 00:00:54.640
know what x compose is

00:00:54.640 --> 00:00:56.719
I tried looking for it on my system I

00:00:56.719 --> 00:00:59.680
could not find it anywhere

00:00:59.680 --> 00:01:02.399
I did actually go and figure out how to

00:01:02.399 --> 00:01:02.879
write a

00:01:02.879 --> 00:01:06.080
x11 keyboard layout so that's also

00:01:06.080 --> 00:01:07.040
available

00:01:07.040 --> 00:01:09.840
in the repository that has the Emacs

00:01:09.840 --> 00:01:11.920
package as well

00:01:11.920 --> 00:01:14.720
and it is handy to be able to have that

00:01:14.720 --> 00:01:15.920
so I can type in

00:01:15.920 --> 00:01:21.200
other applications besides Emacs

00:01:21.200 --> 00:01:24.479
but the main advantages for Emacs was it

00:01:24.479 --> 00:01:25.119
was actually

00:01:25.119 --> 00:01:27.439
much easier to discover and much easier

00:01:27.439 --> 00:01:28.560
to

00:01:28.560 --> 00:01:31.439
manipulate and get feedback you know as

00:01:31.439 --> 00:01:33.040
I was developing it like I could just

00:01:33.040 --> 00:01:35.360
evaluate the coil package

00:01:35.360 --> 00:01:37.200
try it out and see if it works when I

00:01:37.200 --> 00:01:39.680
was trying to do the x11 inputs I'd have

00:01:39.680 --> 00:01:40.560
to log out

00:01:40.560 --> 00:01:42.799
read and and relog in again to get

00:01:42.799 --> 00:01:43.759
things read and

00:01:43.759 --> 00:01:46.240
it was you know it doesn't have that

00:01:46.240 --> 00:01:46.799
beautiful

00:01:46.799 --> 00:01:50.560
interactivity the way that Emacs does so

00:01:50.560 --> 00:01:53.040
for me it was a good place to start um

00:01:53.040 --> 00:01:54.960
especially because

00:01:54.960 --> 00:01:56.640
I had never done anything like this

00:01:56.640 --> 00:01:58.079
before like developing

00:01:58.079 --> 00:02:00.079
something that felt low level you know

00:02:00.079 --> 00:02:04.320
like a keyboard input

00:02:04.320 --> 00:02:06.399
I hope that answers your question

00:02:06.399 --> 00:02:08.479
question two can you give us a demo of

00:02:08.479 --> 00:02:09.280
you typing in

00:02:09.280 --> 00:02:12.400
either lakota and input method sure

00:02:12.400 --> 00:02:19.599
um share my screen now

00:02:19.599 --> 00:02:21.520
of course I always have to select which

00:02:21.520 --> 00:02:32.239
one

00:02:32.239 --> 00:02:36.560
okay so control backslash opens the

00:02:36.560 --> 00:02:37.840
input modes

00:02:37.840 --> 00:02:40.000
although when you've selected one you

00:02:40.000 --> 00:02:41.920
have it already so

00:02:41.920 --> 00:02:45.680
uh yeah wash day

00:02:45.680 --> 00:02:48.319
that's it is good washed it so this is

00:02:48.319 --> 00:02:50.000
the suggested lakota

00:02:50.000 --> 00:02:53.360
orthography or otherwise known as the

00:02:53.360 --> 00:02:56.560
standard lakota orthography

00:02:56.560 --> 00:02:58.800
another benefit of doing it in Emacs is

00:02:58.800 --> 00:03:00.640
that I now get

00:03:00.640 --> 00:03:06.800
completion on lakota words so

00:03:06.800 --> 00:03:08.800
so I'm you know it's a second language

00:03:08.800 --> 00:03:10.560
for me and as I'm trying to learn it

00:03:10.560 --> 00:03:11.440
it's actually

00:03:11.440 --> 00:03:13.760
quite useful to have company mode as a

00:03:13.760 --> 00:03:15.599
bonus um

00:03:15.599 --> 00:03:19.680
for typing things

00:03:19.680 --> 00:03:22.239
I can show the other orthography so to

00:03:22.239 --> 00:03:23.599
to get another one you do

00:03:23.599 --> 00:03:27.200
the universal input control u backslash

00:03:27.200 --> 00:03:30.560
and I can try the white hat orthography

00:03:30.560 --> 00:03:36.239
oh yeah lost

00:03:36.239 --> 00:03:39.760
what's the command for that you are now

00:03:39.760 --> 00:03:41.440
unmuted

00:03:41.440 --> 00:03:44.720
yeah okay you are now muted

00:03:44.720 --> 00:03:48.000
thank you

00:03:48.000 --> 00:03:52.080
you are now unmuted you are now muted

00:03:52.080 --> 00:03:55.680
oops not quite as slick as that other

00:03:55.680 --> 00:03:58.879
demo we saw the other day

00:03:58.879 --> 00:04:02.799
okay so control u control backslash I

00:04:02.799 --> 00:04:04.239
can select a different

00:04:04.239 --> 00:04:07.200
input method um from the default so if I

00:04:07.200 --> 00:04:10.560
select white hat I can type

00:04:10.560 --> 00:04:14.480
wash day like that

00:04:14.480 --> 00:04:18.000
so it's a different orthography here um

00:04:18.000 --> 00:04:19.919
I won't go too deeply into that it's

00:04:19.919 --> 00:04:21.440
hard to think and talk and type all at

00:04:21.440 --> 00:04:23.120
the same time

00:04:23.120 --> 00:04:26.320
um I hope that's good

00:04:26.320 --> 00:04:28.560
I'm happy to do more maybe I'll put up a

00:04:28.560 --> 00:04:31.840
video of of demonstrating that sometimes

00:04:31.840 --> 00:04:36.479
why did I just go ahead

00:04:36.479 --> 00:04:39.520
um time about for like one more question

00:04:39.520 --> 00:04:42.880
okay on live yeah thank you

00:04:42.880 --> 00:04:45.280
um well real quick did I write the

00:04:45.280 --> 00:04:46.240
company back end

00:04:46.240 --> 00:04:48.880
no that's just the automatic company

00:04:48.880 --> 00:04:50.639
completion based on other things I've

00:04:50.639 --> 00:04:51.280
typed

00:04:51.280 --> 00:04:55.440
why did I decide on the the input method

00:04:55.440 --> 00:04:58.080
that's a good question um I just did it

00:04:58.080 --> 00:04:58.880
based on

00:04:58.880 --> 00:05:03.120
my experience um in the x input mode you

00:05:03.120 --> 00:05:04.000
type it first

00:05:04.000 --> 00:05:06.160
and honestly I would love any input on

00:05:06.160 --> 00:05:07.120
what's more

00:05:07.120 --> 00:05:09.280
usual for these type of combining

00:05:09.280 --> 00:05:10.960
letters

00:05:10.960 --> 00:05:13.919
and really what I would like to do is

00:05:13.919 --> 00:05:15.360
kind of confer with other

00:05:15.360 --> 00:05:17.600
people from the tribe and talk to elders

00:05:17.600 --> 00:05:19.440
and see

00:05:19.440 --> 00:05:21.440
what feels right what what is the best

00:05:21.440 --> 00:05:23.600
way to go about this

00:05:23.600 --> 00:05:24.800
I don't think that it should be an

00:05:24.800 --> 00:05:26.960
individual decision and in this case it

00:05:26.960 --> 00:05:27.919
is because

00:05:27.919 --> 00:05:30.880
I created it for myself but now that

00:05:30.880 --> 00:05:32.320
I've released it to the world I think

00:05:32.320 --> 00:05:34.639
there's more to think about

00:05:34.639 --> 00:05:37.680
okay I guess I have to go now so we can

00:05:37.680 --> 00:05:38.800
get to the next talk

00:05:38.800 --> 00:05:42.320
thank you for listening okay

00:05:42.320 --> 00:05:44.320
thank you very much grant for your

00:05:44.320 --> 00:05:45.759
awesome talk and for

00:05:45.759 --> 00:05:50.720
the questions and answers