summaryrefslogblamecommitdiffstats
path: root/2020/subtitles/emacsconf-2020--07-beyond-vim-and-emacs-a-scalable-ui-paradigm--questions--sid-kasivajhula-autogen.sbv
blob: f0f427a3b06d65cf57a78a8c615cf1c73ed10f40 (plain) (tree)







































































































































































































































































































































































                                        
0:00:00.080,0:00:03.520
for the list of questions in whatever

0:00:01.680,0:00:06.160
order you like

0:00:03.520,0:00:08.000
okay so i see what package is used um

0:00:06.160,0:00:10.400
probably cemex mode

0:00:08.000,0:00:11.360
um right so the main package that was

0:00:10.400,0:00:14.480
being demoed

0:00:11.360,0:00:16.720
um that is not yet on melpa in fact i

0:00:14.480,0:00:19.359
haven't even decided on a name for it

0:00:16.720,0:00:22.080
um i've alternately alternately called

0:00:19.359,0:00:26.000
it epistemic mode i've called it

0:00:22.080,0:00:28.560
um england i called it uh

0:00:26.000,0:00:30.240
all kinds of things but at the moment

0:00:28.560,0:00:31.439
you can find it on my github there's a

0:00:30.240,0:00:32.960
link

0:00:31.439,0:00:35.600
in the presentation itself if you go to

0:00:32.960,0:00:38.879
github slash account about

0:00:35.600,0:00:39.840
um the package there it's currently

0:00:38.879,0:00:42.879
named indra

0:00:39.840,0:00:46.800
i'm not sure um

0:00:42.879,0:00:49.920
packages actually yes the second one is

0:00:46.800,0:00:53.280
red that was the name that i selected um

0:00:49.920,0:00:53.920
last night um and that's because it

0:00:53.280,0:00:55.760
might that

0:00:53.920,0:00:57.520
there's a concept in tibetan buddhism

0:00:55.760,0:00:58.480
that seems like it might have something

0:00:57.520,0:00:59.840
to do with

0:00:58.480,0:01:01.600
the kinds of concepts we're talking

0:00:59.840,0:01:04.000
about with this package so i just

0:01:01.600,0:01:05.760
thought it would be a good name for it

0:01:04.000,0:01:09.920
so you can look up that concept

0:01:05.760,0:01:13.119
and get a sense of it on wikipedia

0:01:09.920,0:01:15.759
next question is how to deal with dwarak

0:01:13.119,0:01:16.960
dwarjak or however that's pronounced

0:01:15.759,0:01:20.400
this is always bug me

0:01:16.960,0:01:22.400
is there an x-mod map mode so the thing

0:01:20.400,0:01:23.360
with this is it's kind of surprising but

0:01:22.400,0:01:26.000
although vim

0:01:23.360,0:01:27.200
was originally developed um you know

0:01:26.000,0:01:29.520
with the idea of

0:01:27.200,0:01:32.000
the key bindings being on the home rule

0:01:29.520,0:01:33.119
it turns out that that is actually not a

0:01:32.000,0:01:36.400
major aspect

0:01:33.119,0:01:38.560
of the vim editing experience so

0:01:36.400,0:01:40.720
people who use the dvorak layout

0:01:38.560,0:01:42.640
actually end up using the same keys as

0:01:40.720,0:01:44.720
they do on the normal qwerty layout so

0:01:42.640,0:01:48.159
they don't remap anything

0:01:44.720,0:01:51.040
because the uh the the sort of

0:01:48.159,0:01:52.240
the power that vim or the the

0:01:51.040,0:01:55.600
flexibility the

0:01:52.240,0:01:56.880
spiral that bim enables on qwerty layout

0:01:55.600,0:01:58.719
keyboards is exactly

0:01:56.880,0:01:59.920
preserved even on a door jack keyboard

0:01:58.719,0:02:01.920
even though you your

0:01:59.920,0:02:04.399
fingers are not in the same positions

0:02:01.920,0:02:09.119
it's not a big deal actually

0:02:04.399,0:02:10.879
um and then i mostly use default model

0:02:09.119,0:02:12.319
provided by vanilla emacs and work and

0:02:10.879,0:02:13.840
org mode for text editing can you give

0:02:12.319,0:02:15.920
me some examples

0:02:13.840,0:02:17.280
of how the user can use the concept of

0:02:15.920,0:02:20.840
mode mode

0:02:17.280,0:02:24.640
to do some interesting

0:02:20.840,0:02:25.120
um so probably the main thing would be

0:02:24.640,0:02:27.920
the

0:02:25.120,0:02:28.959
the keystrokes would be less uh

0:02:27.920,0:02:32.080
contrived

0:02:28.959,0:02:36.560
so they the the fewer modes you have

0:02:32.080,0:02:39.840
the more modifiers you need

0:02:36.560,0:02:41.280
in order to um do whatever it is that

0:02:39.840,0:02:44.800
you're trying to do because you've got

0:02:41.280,0:02:47.840
essentially with a max model you've got

0:02:44.800,0:02:47.840
a completely flat

0:02:48.080,0:02:52.160
keyboard structure and so all of the

0:02:50.959,0:02:55.680
different things that you might

0:02:52.160,0:02:58.720
want to express are all mapped to a flat

0:02:55.680,0:03:02.840
keyboard uh set of keys

0:02:58.720,0:03:06.400
so with um with this kind of

0:03:02.840,0:03:09.200
modal structure the more modes you have

0:03:06.400,0:03:10.400
the more the individual keystrokes

0:03:09.200,0:03:13.200
become

0:03:10.400,0:03:14.959
shorter and shorter so that could be one

0:03:13.200,0:03:17.519
benefit that would be provided

0:03:14.959,0:03:18.000
with many modes your keystrokes would

0:03:17.519,0:03:20.080
generally

0:03:18.000,0:03:22.080
be a single keystroke long for even

0:03:20.080,0:03:24.159
relatively complex tasks

0:03:22.080,0:03:25.440
because you're setting the context

0:03:24.159,0:03:27.200
beforehand

0:03:25.440,0:03:30.840
so you already say oh i'm going to be

0:03:27.200,0:03:33.440
talking about this org buffer

0:03:30.840,0:03:36.319
agenda and then

0:03:33.440,0:03:39.599
um the all the keystrokes that you do at

0:03:36.319,0:03:42.159
that point would be in relation to that

0:03:39.599,0:03:44.080
um okay i think we have time for like

0:03:42.159,0:03:46.879
one more short question

0:03:44.080,0:03:48.879
one more short question okay let's see

0:03:46.879,0:03:50.400
how do new modes come into existence you

0:03:48.879,0:03:53.040
can make them yourself

0:03:50.400,0:03:53.760
um and you can specify them in emacs

0:03:53.040,0:03:56.159
lisp

0:03:53.760,0:03:59.040
if you like but there's also simple you

0:03:56.159,0:04:02.720
can also do it visually as we did

0:03:59.040,0:04:04.799
um but the yeah defining them

0:04:02.720,0:04:07.519
is essentially built on top of hydra but

0:04:04.799,0:04:09.120
it could also be built on top of evil or

0:04:07.519,0:04:12.400
any other modal interface provider

0:04:09.120,0:04:12.400
there's an abstraction layer

0:04:12.840,0:04:17.919
okay thank you so much for your talk and

0:04:15.920,0:04:21.440
for the live q a

0:04:17.919,0:04:22.880
sure thank you yes feel free to um take

0:04:21.440,0:04:23.759
up the rest of the questions either via

0:04:22.880,0:04:25.680
irc or

0:04:23.759,0:04:26.960
on the pad on on your own time off the

0:04:25.680,0:04:28.639
stream

0:04:26.960,0:04:30.000
perfect yeah i'll go ahead and put in

0:04:28.639,0:04:32.240
some answers there

0:04:30.000,0:04:33.120
awesome thank you all right thank you

0:04:32.240,0:04:36.880
have a good one

0:04:33.120,0:04:36.880
thanks you too