path: root/2020/subtitles/emacsconf-2020--17-org-mode-and-org-roam-for-scholars-and-researchers--noorah-alhasan-autogen.vtt

WEBVTT

00:00:00.320 --> 00:00:02.639
good afternoon or good evening everyone

00:00:02.639 --> 00:00:03.040
uh

00:00:03.040 --> 00:00:05.440
today my talk is going to be on org mode

00:00:05.440 --> 00:00:07.759
and or group for skulls and researchers

00:00:07.759 --> 00:00:10.559
leo has talked about like the overall

00:00:10.559 --> 00:00:12.639
picture of orgrim and or

00:00:12.639 --> 00:00:15.120
uh bibtex or groundbreak tech I will be

00:00:15.120 --> 00:00:16.240
talking more about

00:00:16.240 --> 00:00:19.199
the research process itself using these

00:00:19.199 --> 00:00:20.320
tools

00:00:20.320 --> 00:00:22.400
all right so just to introduce that the

00:00:22.400 --> 00:00:25.039
research process is really messy

00:00:25.039 --> 00:00:28.080
um you're always working in like

00:00:28.080 --> 00:00:31.039
piecemeal tasks and things move around

00:00:31.039 --> 00:00:32.960
all the time and so

00:00:32.960 --> 00:00:35.280
there needs to be a system where you can

00:00:35.280 --> 00:00:36.880
organize all these tasks

00:00:36.880 --> 00:00:39.360
all these ideas in a way that is

00:00:39.360 --> 00:00:41.760
flexible and effective

00:00:41.760 --> 00:00:44.239
so my motivation is that research is

00:00:44.239 --> 00:00:44.960
hard and

00:00:44.960 --> 00:00:47.120
writing about it is even more difficult

00:00:47.120 --> 00:00:49.600
and my goal is to add some structure to

00:00:49.600 --> 00:00:51.120
this whole madness

00:00:51.120 --> 00:00:52.800
so here's a list of some of the stuff

00:00:52.800 --> 00:00:54.480
that I've been using since I first

00:00:54.480 --> 00:00:57.199
learned about Emacs in 2019

00:00:57.199 --> 00:01:00.160
and what I've what I've found useful um

00:01:00.160 --> 00:01:02.000
during my res uh like um

00:01:02.000 --> 00:01:05.199
within my research process all right so

00:01:05.199 --> 00:01:07.920
I've organized org mode for researchers

00:01:07.920 --> 00:01:10.400
and scholars within the writing process

00:01:10.400 --> 00:01:12.400
into three modules first there's like

00:01:12.400 --> 00:01:14.320
the planning aspect of it

00:01:14.320 --> 00:01:15.759
then you've got the writing and the

00:01:15.759 --> 00:01:17.680
reference management which I will join

00:01:17.680 --> 00:01:18.320
together

00:01:18.320 --> 00:01:20.560
by looking at the example of doing your

00:01:20.560 --> 00:01:21.920
literature review

00:01:21.920 --> 00:01:24.720
all right so when we're talking about

00:01:24.720 --> 00:01:26.479
planning we're talking about either task

00:01:26.479 --> 00:01:27.360
management or

00:01:27.360 --> 00:01:30.880
time management with task management

00:01:30.880 --> 00:01:31.600
you've got

00:01:31.600 --> 00:01:33.840
org modes to do's and tags and

00:01:33.840 --> 00:01:36.159
categories these are really powerful

00:01:36.159 --> 00:01:38.479
tools that you could use

00:01:38.479 --> 00:01:41.600
um in your org files to just um

00:01:41.600 --> 00:01:44.799
uh like organize your tasks and

00:01:44.799 --> 00:01:47.040
your appointments so there are different

00:01:47.040 --> 00:01:49.040
types of to-do's that you can either set

00:01:49.040 --> 00:01:50.960
globally in your init file or they can

00:01:50.960 --> 00:01:52.799
be file buffer specific

00:01:52.799 --> 00:01:55.200
so that means based on context based on

00:01:55.200 --> 00:01:56.079
the type of

00:01:56.079 --> 00:01:57.759
manuscript you're working on whether

00:01:57.759 --> 00:01:59.280
it's like a literate programming

00:01:59.280 --> 00:02:02.240
report or your actual thesis slash

00:02:02.240 --> 00:02:03.759
dissertation

00:02:03.759 --> 00:02:05.840
um also these to-do's are either created

00:02:05.840 --> 00:02:07.759
as a set tree like think of them as

00:02:07.759 --> 00:02:11.440
headings and sections if you use latex

00:02:11.440 --> 00:02:14.800
or inline text which are like org inline

00:02:14.800 --> 00:02:15.360
tasks I

00:02:15.360 --> 00:02:17.760
like organ line tasks because like I can

00:02:17.760 --> 00:02:19.120
add

00:02:19.120 --> 00:02:21.520
to do's between two paragraphs and that

00:02:21.520 --> 00:02:22.879
way it doesn't show up

00:02:22.879 --> 00:02:25.360
in the table of contents when I export

00:02:25.360 --> 00:02:27.280
into pdf or html or

00:02:27.280 --> 00:02:30.879
anything else all right so this is an

00:02:30.879 --> 00:02:34.319
example of buffer specific to do's

00:02:34.319 --> 00:02:37.360
and and this is example of like a little

00:02:37.360 --> 00:02:39.120
programming report that I was working on

00:02:39.120 --> 00:02:40.800
where I was like dealing with

00:02:40.800 --> 00:02:43.200
data and like analysis and all of that

00:02:43.200 --> 00:02:44.080
stuff and so

00:02:44.080 --> 00:02:47.519
I needed um context specific to do's to

00:02:47.519 --> 00:02:49.440
use them within this buffer

00:02:49.440 --> 00:02:52.080
um and that's how I would organize it

00:02:52.080 --> 00:02:54.319
and there's also also another example

00:02:54.319 --> 00:02:57.200
of an org inline task where you could

00:02:57.200 --> 00:02:57.920
see it

00:02:57.920 --> 00:03:01.360
in the middle between the two headings

00:03:01.360 --> 00:03:03.040
that way it wouldn't show up in the

00:03:03.040 --> 00:03:04.959
table of contents and it would look like

00:03:04.959 --> 00:03:06.480
nature within the

00:03:06.480 --> 00:03:09.519
text when you export it

00:03:09.519 --> 00:03:11.920
oh but I also added a tag of no export

00:03:11.920 --> 00:03:13.280
so it won't show up at all

00:03:13.280 --> 00:03:16.400
when I export it into like either pdf

00:03:16.400 --> 00:03:19.360
which I use all the time all right so

00:03:19.360 --> 00:03:21.599
another useful tool

00:03:21.599 --> 00:03:24.159
um for the research and just like

00:03:24.159 --> 00:03:25.200
general planning

00:03:25.200 --> 00:03:27.920
is the org capture um when I first

00:03:27.920 --> 00:03:29.120
started with Emacs

00:03:29.120 --> 00:03:32.080
actually it was for org agenda and I

00:03:32.080 --> 00:03:34.239
went crazy with my capture template I

00:03:34.239 --> 00:03:35.360
created a template for

00:03:35.360 --> 00:03:37.599
everything um because I was just so

00:03:37.599 --> 00:03:38.640
excited

00:03:38.640 --> 00:03:40.720
but with time I was using less and less

00:03:40.720 --> 00:03:42.400
of them so I kept taking them out

00:03:42.400 --> 00:03:46.319
and now this is my simplified um

00:03:46.319 --> 00:03:48.239
capture templates that I use either for

00:03:48.239 --> 00:03:49.599
a general to do

00:03:49.599 --> 00:03:52.159
um for a regular appointment a fleeting

00:03:52.159 --> 00:03:54.159
note research tasks because like those

00:03:54.159 --> 00:03:55.200
are what I focus on

00:03:55.200 --> 00:03:56.959
like my bread and butter and then

00:03:56.959 --> 00:03:58.720
finally with meetings which I find

00:03:58.720 --> 00:04:00.879
sometimes I don't use it as much because

00:04:00.879 --> 00:04:01.680
I would just like

00:04:01.680 --> 00:04:03.519
have the org file ready instead of

00:04:03.519 --> 00:04:04.879
needing to capture

00:04:04.879 --> 00:04:07.920
you know open a capture template

00:04:07.920 --> 00:04:11.439
right or agenda um that's how I got into

00:04:11.439 --> 00:04:12.400
Emacs

00:04:12.400 --> 00:04:15.439
I needed to um organize my life and I

00:04:15.439 --> 00:04:16.799
found Emacs and

00:04:16.799 --> 00:04:19.199
it's been great ever since um it

00:04:19.199 --> 00:04:20.479
populates all your to-do's and

00:04:20.479 --> 00:04:22.720
appointments into a singular view so the

00:04:22.720 --> 00:04:25.280
default view I think it's a weak view

00:04:25.280 --> 00:04:29.120
however I use org super agenda love this

00:04:29.120 --> 00:04:31.919
um package and I set up my agenda as a

00:04:31.919 --> 00:04:34.160
daily view with just appointments

00:04:34.160 --> 00:04:37.360
deadlines and a habit tracker um and

00:04:37.360 --> 00:04:38.720
a side note you guys I'm still

00:04:38.720 --> 00:04:40.639
struggling with organizing the perfect

00:04:40.639 --> 00:04:42.320
agenda so it's a process

00:04:42.320 --> 00:04:45.360
and take it easy all right

00:04:45.360 --> 00:04:47.919
so this is just an overview of my daily

00:04:47.919 --> 00:04:50.320
agenda as you can see they're just like

00:04:50.320 --> 00:04:52.800
appointments that I import from gmail

00:04:52.800 --> 00:04:55.520
using org gcal

00:04:55.520 --> 00:04:57.919
a simple habit tracker of like daily

00:04:57.919 --> 00:04:58.880
free writing

00:04:58.880 --> 00:05:00.960
as you can see there are a lot of times

00:05:00.960 --> 00:05:02.800
where I'm skipping and the asterisk is

00:05:02.800 --> 00:05:05.199
the one where I've completed that day

00:05:05.199 --> 00:05:08.479
so you know it's a process and then just

00:05:08.479 --> 00:05:10.080
like regular deadlines

00:05:10.080 --> 00:05:12.639
so what happens is that I have other

00:05:12.639 --> 00:05:14.000
to-do's that I have

00:05:14.000 --> 00:05:17.120
not scheduled or not added a deadline

00:05:17.120 --> 00:05:17.919
but they're just

00:05:17.919 --> 00:05:20.560
tasks that keep piling up when I first

00:05:20.560 --> 00:05:22.320
started with Emacs and org agenda

00:05:22.320 --> 00:05:24.880
I had everything in there and it got

00:05:24.880 --> 00:05:26.880
overwhelming and then I decided no

00:05:26.880 --> 00:05:29.680
I'm not gonna even let them show up so

00:05:29.680 --> 00:05:30.800
what I would do

00:05:30.800 --> 00:05:33.120
at the beginning of each week or the

00:05:33.120 --> 00:05:34.479
night before

00:05:34.479 --> 00:05:36.800
um I would sit down look at all my to

00:05:36.800 --> 00:05:38.000
to-do's that I have

00:05:38.000 --> 00:05:40.720
not assigned yet to a deadline or a

00:05:40.720 --> 00:05:42.639
schedule or just a simple

00:05:42.639 --> 00:05:45.360
timestamp um and I would organize them

00:05:45.360 --> 00:05:46.320
throughout the week

00:05:46.320 --> 00:05:49.520
so here's an example of what I did

00:05:49.520 --> 00:05:51.680
so on that wednesday from my gmail I had

00:05:51.680 --> 00:05:53.039
all these appointments but

00:05:53.039 --> 00:05:55.600
one of them is I have a writing group

00:05:55.600 --> 00:05:56.560
session

00:05:56.560 --> 00:05:58.400
and so I looked at my tasks and I

00:05:58.400 --> 00:05:59.759
thought okay then I will just

00:05:59.759 --> 00:06:02.639
assign um like for example my emac

00:06:02.639 --> 00:06:03.520
slides

00:06:03.520 --> 00:06:06.319
or the framework diagram into that

00:06:06.319 --> 00:06:07.280
writing session

00:06:07.280 --> 00:06:09.600
and all I did was just add an active

00:06:09.600 --> 00:06:10.800
timestamp

00:06:10.800 --> 00:06:12.960
that is all I needed to do and it went

00:06:12.960 --> 00:06:14.000
straight into my

00:06:14.000 --> 00:06:17.120
appointment now if I miss that

00:06:17.120 --> 00:06:20.080
it won't show up on the next day so if

00:06:20.080 --> 00:06:21.520
you put in a deadline

00:06:21.520 --> 00:06:24.639
it will show up as an overdue but if you

00:06:24.639 --> 00:06:26.560
have no deadline or schedule it will not

00:06:26.560 --> 00:06:29.280
show up in your daily org agenda

00:06:29.280 --> 00:06:32.960
so just a star

00:06:32.960 --> 00:06:35.680
all right another way of accessing your

00:06:35.680 --> 00:06:37.520
to do's is that if it's

00:06:37.520 --> 00:06:40.880
um file specific org file specific

00:06:40.880 --> 00:06:42.160
buffer specific

00:06:42.160 --> 00:06:44.160
and so like when we talked about like

00:06:44.160 --> 00:06:46.400
whether to have a big ass org file or

00:06:46.400 --> 00:06:47.680
like tiny files

00:06:47.680 --> 00:06:50.720
it all depends and this isn't the the

00:06:50.720 --> 00:06:54.560
um you know the way this depends

00:06:54.560 --> 00:06:55.759
because if you're working on like a

00:06:55.759 --> 00:06:58.400
dissertation um it's a huge manuscript

00:06:58.400 --> 00:06:59.680
you need to like work

00:06:59.680 --> 00:07:02.880
on that org file all the time um

00:07:02.880 --> 00:07:05.759
then yes it might do should be in that

00:07:05.759 --> 00:07:07.680
file specifically because every time if

00:07:07.680 --> 00:07:08.000
I'm

00:07:08.000 --> 00:07:09.680
if I'm visiting this org file all the

00:07:09.680 --> 00:07:12.479
time I should be able to just look at my

00:07:12.479 --> 00:07:15.520
tasks from uh within that buffer

00:07:15.520 --> 00:07:18.639
and so I use org sidebar to

00:07:18.639 --> 00:07:21.599
keep all these specific uh to do's

00:07:21.599 --> 00:07:22.960
within that org file

00:07:22.960 --> 00:07:26.560
I find it helpful okay

00:07:26.560 --> 00:07:28.400
now that we're going into the writing

00:07:28.400 --> 00:07:29.759
and reference management

00:07:29.759 --> 00:07:33.039
we'll call it a literature review um

00:07:33.039 --> 00:07:35.840
and this is something I've built as a

00:07:35.840 --> 00:07:36.639
schema

00:07:36.639 --> 00:07:40.240
I think that it works for now

00:07:40.240 --> 00:07:43.759
um and it requires one outside pack

00:07:43.759 --> 00:07:45.919
of outside software which is zotero what

00:07:45.919 --> 00:07:47.680
I use it's an open source reference

00:07:47.680 --> 00:07:48.720
management

00:07:48.720 --> 00:07:51.759
software um it's great

00:07:51.759 --> 00:07:53.599
but the things to keep in mind is that I

00:07:53.599 --> 00:07:55.120
use two um

00:07:55.120 --> 00:07:58.319
plugins that is really needed for when

00:07:58.319 --> 00:08:01.039
we work with orgrim bibtex and orgrim

00:08:01.039 --> 00:08:03.840
and org mode um and the zap file so

00:08:03.840 --> 00:08:06.160
better bibtex organizes your reference

00:08:06.160 --> 00:08:07.039
keys

00:08:07.039 --> 00:08:10.560
um in um in a way like in a fashion that

00:08:10.560 --> 00:08:13.360
works for you so for me all my reference

00:08:13.360 --> 00:08:14.240
keys are like

00:08:14.240 --> 00:08:17.280
last author and gear um and with zap

00:08:17.280 --> 00:08:21.120
file I um I let it like rename all the

00:08:21.120 --> 00:08:22.319
pdf files

00:08:22.319 --> 00:08:24.400
the same way that I have for my bit of

00:08:24.400 --> 00:08:26.000
my bib keys which is like

00:08:26.000 --> 00:08:29.360
last name of author and year all right

00:08:29.360 --> 00:08:33.440
once you export your entire

00:08:33.440 --> 00:08:37.120
library as a bib file then you can work

00:08:37.120 --> 00:08:39.440
on it within org mode and Emacs

00:08:39.440 --> 00:08:42.880
using um the following packages

00:08:42.880 --> 00:08:45.040
all right so with orgrim bibtex it

00:08:45.040 --> 00:08:47.839
creates an org file for each bib entry

00:08:47.839 --> 00:08:49.519
and you have the option of like

00:08:49.519 --> 00:08:52.240
templating and doing other stuff with it

00:08:52.240 --> 00:08:54.880
and then finally there's like this orb

00:08:54.880 --> 00:08:56.240
pdf scraper

00:08:56.240 --> 00:08:58.800
I've used it briefly but I think the

00:08:58.800 --> 00:09:00.240
potential

00:09:00.240 --> 00:09:02.880
with or pdf scraper is if you're gonna

00:09:02.880 --> 00:09:05.920
do a bibliometric study or like a

00:09:05.920 --> 00:09:08.320
systematic literature view there's

00:09:08.320 --> 00:09:10.000
something there but I have to look

00:09:10.000 --> 00:09:10.959
through it

00:09:10.959 --> 00:09:14.399
anyway so once you create your you know

00:09:14.399 --> 00:09:16.880
your reference file of reference x and

00:09:16.880 --> 00:09:18.160
you're writing your notes

00:09:18.160 --> 00:09:20.240
you can either go like with going

00:09:20.240 --> 00:09:22.399
through org mode you're writing

00:09:22.399 --> 00:09:24.080
your ideas you're writing your notes

00:09:24.080 --> 00:09:26.080
you're assigning tasks

00:09:26.080 --> 00:09:27.839
and then there's org transclusion which

00:09:27.839 --> 00:09:30.480
I will mention briefly at the end

00:09:30.480 --> 00:09:32.240
and ways to extract if you're going to

00:09:32.240 --> 00:09:35.360
go through the orgrom

00:09:35.360 --> 00:09:36.640
things that you're going to use within

00:09:36.640 --> 00:09:38.720
orgrom it's a great way to build your

00:09:38.720 --> 00:09:40.000
database you start making the

00:09:40.000 --> 00:09:42.880
connections and you can visualize your

00:09:42.880 --> 00:09:44.959
notes and like how these references are

00:09:44.959 --> 00:09:46.240
linked to each other

00:09:46.240 --> 00:09:48.839
through the organ server or or ground

00:09:48.839 --> 00:09:50.240
graph

00:09:50.240 --> 00:09:53.120
all right this is just notes for later

00:09:53.120 --> 00:09:53.680
okay

00:09:53.680 --> 00:09:56.240
so this is an example of like an orgram

00:09:56.240 --> 00:09:57.360
file that I have

00:09:57.360 --> 00:09:59.279
for example if I'm working on adaptation

00:09:59.279 --> 00:10:01.760
policy I have these hyperlinks that are

00:10:01.760 --> 00:10:02.560
linked to other

00:10:02.560 --> 00:10:04.959
concepts and ideas such as either

00:10:04.959 --> 00:10:06.640
climate security

00:10:06.640 --> 00:10:08.720
um changing global environment so on and

00:10:08.720 --> 00:10:10.560
so forth and the backlinks

00:10:10.560 --> 00:10:13.920
are other references that talk about

00:10:13.920 --> 00:10:15.839
this specific concept

00:10:15.839 --> 00:10:17.680
so this is really helpful and then when

00:10:17.680 --> 00:10:19.920
you visualize it the picture on the left

00:10:19.920 --> 00:10:22.160
which I'm sure looks really small

00:10:22.160 --> 00:10:24.160
um you can see the connections that it's

00:10:24.160 --> 00:10:25.680
making with other

00:10:25.680 --> 00:10:28.160
references so of course this is just

00:10:28.160 --> 00:10:29.760
like a buffer

00:10:29.760 --> 00:10:32.720
network when you look at the entire

00:10:32.720 --> 00:10:34.560
database network it's it's

00:10:34.560 --> 00:10:38.000
it's growing okay

00:10:38.000 --> 00:10:41.680
so going into organ bidtech

00:10:41.680 --> 00:10:44.079
so it utilizes a combination of the or

00:10:44.079 --> 00:10:46.000
graph package helmbik tech candidate

00:10:46.000 --> 00:10:46.880
completion

00:10:46.880 --> 00:10:50.079
and it works with orgrom functionalities

00:10:50.079 --> 00:10:51.440
and

00:10:51.440 --> 00:10:54.880
other good stuff this is an example

00:10:54.880 --> 00:10:57.440
of my orgrim bibtex file all right so

00:10:57.440 --> 00:10:58.720
I've created

00:10:58.720 --> 00:11:01.200
um the template which I pretty much use

00:11:01.200 --> 00:11:02.320
what leo

00:11:02.320 --> 00:11:05.920
has uh produced like in his um

00:11:05.920 --> 00:11:08.640
tutorial so I think it's it's great it

00:11:08.640 --> 00:11:10.160
works well for me

00:11:10.160 --> 00:11:12.880
um and what it does is that it works

00:11:12.880 --> 00:11:14.480
with your bib file

00:11:14.480 --> 00:11:17.519
so if you're in your bib file you have a

00:11:17.519 --> 00:11:19.519
sub entry that's called keywords and

00:11:19.519 --> 00:11:21.040
usually that's within

00:11:21.040 --> 00:11:23.120
a journal article the author would

00:11:23.120 --> 00:11:24.560
specify these

00:11:24.560 --> 00:11:27.519
keywords um when it gets imported into

00:11:27.519 --> 00:11:28.160
zotero

00:11:28.160 --> 00:11:30.399
it extracts those keywords and then it

00:11:30.399 --> 00:11:32.399
gets populated as an org file

00:11:32.399 --> 00:11:34.959
with orgrim bibtex so I always start

00:11:34.959 --> 00:11:36.959
with the meta information first and then

00:11:36.959 --> 00:11:38.560
I would write my notes

00:11:38.560 --> 00:11:42.480
after that this is an example though

00:11:42.480 --> 00:11:45.760
for reference of a physical book so

00:11:45.760 --> 00:11:49.120
I don't have a pdf file for it um

00:11:49.120 --> 00:11:51.519
so what I've figured out like a new idea

00:11:51.519 --> 00:11:53.920
for it so if I'm writing notes on it

00:11:53.920 --> 00:11:55.760
I would create a property that says

00:11:55.760 --> 00:11:57.279
pages um

00:11:57.279 --> 00:11:58.959
that way it's easier for you when you go

00:11:58.959 --> 00:12:00.639
back to citing

00:12:00.639 --> 00:12:02.720
um certain ideas or something that you

00:12:02.720 --> 00:12:04.720
have the pages prepared there

00:12:04.720 --> 00:12:07.839
it's easier that way okay

00:12:07.839 --> 00:12:11.279
org noter which is something I

00:12:11.279 --> 00:12:13.040
use a lot especially with journal

00:12:13.040 --> 00:12:14.880
articles that have pdfs and stuff like

00:12:14.880 --> 00:12:15.600
that

00:12:15.600 --> 00:12:19.120
they're really helpful if you are gonna

00:12:19.120 --> 00:12:22.720
if you've just started using um Emacs

00:12:22.720 --> 00:12:23.760
and orgrim

00:12:23.760 --> 00:12:26.959
and you have all these pdfs that have

00:12:26.959 --> 00:12:29.519
all the annotations and highlighting and

00:12:29.519 --> 00:12:30.079
the

00:12:30.079 --> 00:12:32.639
all that stuff with org noter you can

00:12:32.639 --> 00:12:33.200
just

00:12:33.200 --> 00:12:36.720
use the org note or create skeleton

00:12:36.720 --> 00:12:39.519
uh command and it will populate all your

00:12:39.519 --> 00:12:41.200
notes that have already been

00:12:41.200 --> 00:12:43.760
um entered within the pdf file if you're

00:12:43.760 --> 00:12:44.800
using an outside

00:12:44.800 --> 00:12:48.160
software and creates them like as a neat

00:12:48.160 --> 00:12:52.560
org file I I highly recommend

00:12:52.560 --> 00:12:55.920
finally org transclusion um

00:12:55.920 --> 00:12:57.920
I think this is still in its beta phase

00:12:57.920 --> 00:13:01.040
but I've been enjoying it so far

00:13:01.040 --> 00:13:02.720
um I'm guessing people know what

00:13:02.720 --> 00:13:04.800
translation mean which is sort of like

00:13:04.800 --> 00:13:06.480
copy pasting text from

00:13:06.480 --> 00:13:09.600
one org file to another this is helpful

00:13:09.600 --> 00:13:11.839
I I think I I peeked at a question that

00:13:11.839 --> 00:13:12.959
was talking about like

00:13:12.959 --> 00:13:16.320
you know linking um to other org files

00:13:16.320 --> 00:13:18.320
I think org transclusion could really

00:13:18.320 --> 00:13:20.320
work okay it's

00:13:20.320 --> 00:13:24.399
equivalent to the include

00:13:24.399 --> 00:13:27.760
function within org mode um but I think

00:13:27.760 --> 00:13:29.519
so like if you have other files

00:13:29.519 --> 00:13:32.560
that you know which region that you

00:13:32.560 --> 00:13:34.800
need in another file you could use the

00:13:34.800 --> 00:13:36.079
include but with

00:13:36.079 --> 00:13:38.160
org transclusion it's great I mean you

00:13:38.160 --> 00:13:39.440
just have

00:13:39.440 --> 00:13:42.720
um you're just linking one part to the

00:13:42.720 --> 00:13:43.360
other

00:13:43.360 --> 00:13:45.760
sort of like not refiling but you know

00:13:45.760 --> 00:13:47.760
hyperlinking

00:13:47.760 --> 00:13:49.680
so this is an example of what org

00:13:49.680 --> 00:13:51.120
transclusion looks like

00:13:51.120 --> 00:13:53.680
um so the highlighted problem statement

00:13:53.680 --> 00:13:54.720
is from another

00:13:54.720 --> 00:13:57.760
org file and then what I would do is

00:13:57.760 --> 00:13:58.240
just like

00:13:58.240 --> 00:13:59.760
link it to there and there was like a

00:13:59.760 --> 00:14:01.440
transclusion command

00:14:01.440 --> 00:14:05.440
I wish I made another screenshot of it

00:14:05.440 --> 00:14:08.399
and so when you invoke org transclusion

00:14:08.399 --> 00:14:09.120
mode

00:14:09.120 --> 00:14:12.079
it turns um it prints it out like that

00:14:12.079 --> 00:14:12.480
so

00:14:12.480 --> 00:14:15.120
it's in view mode and then when you want

00:14:15.120 --> 00:14:16.560
to edit it will take you back to that

00:14:16.560 --> 00:14:18.480
buffer and you can edit the text

00:14:18.480 --> 00:14:21.839
however you want all right so thank you

00:14:21.839 --> 00:14:22.720
so much

00:14:22.720 --> 00:14:26.000
um I wanted to leave room for questions

00:14:26.000 --> 00:14:29.120
but special thanks to all the folks that

00:14:29.120 --> 00:14:32.560
work on orgrom or ground bibtex orgrim

00:14:32.560 --> 00:14:33.440
server or

00:14:33.440 --> 00:14:36.320
transclusion and of course alpha papo on

00:14:36.320 --> 00:14:38.240
or super agenda and org sidebar

00:14:38.240 --> 00:14:43.440
that's how I got into Emacs thank you

00:14:43.440 --> 00:14:45.600
all right and uh well thank you so yeah

00:14:45.600 --> 00:14:47.120
this time I'll be the one asking the

00:14:47.120 --> 00:14:49.120
question and not I'm in so

00:14:49.120 --> 00:14:51.360
I'm feeling filling big shoes right now

00:14:51.360 --> 00:14:53.120
so you'll have to bear with me folks

00:14:53.120 --> 00:14:54.880
so thank you so much noora for your

00:14:54.880 --> 00:14:56.240
presentation that is incredibly

00:14:56.240 --> 00:14:57.279
interesting

00:14:57.279 --> 00:14:58.959
so would you mind if I fed you questions

00:14:58.959 --> 00:15:00.800
from the charts yeah

00:15:00.800 --> 00:15:04.000
go ahead okay so the first one I I've

00:15:04.000 --> 00:15:06.160
picked on my end was did you try using

00:15:06.160 --> 00:15:07.920
ebib instead of zotero

00:15:07.920 --> 00:15:10.560
and if so is it better than zotero in

00:15:10.560 --> 00:15:12.079
some ways

00:15:12.079 --> 00:15:14.880
I no I have not used eb I've only used

00:15:14.880 --> 00:15:15.680
mendeley

00:15:15.680 --> 00:15:18.560
and then they got bought by el savior

00:15:18.560 --> 00:15:20.320
and so like I was like okay I'm done

00:15:20.320 --> 00:15:23.040
I'm going to zotero um there are a lot

00:15:23.040 --> 00:15:25.120
of plugins with zotero that you can play

00:15:25.120 --> 00:15:26.240
around with

00:15:26.240 --> 00:15:28.320
so I can't speak for ebit but definitely

00:15:28.320 --> 00:15:30.480
zotero it's been a good experience so

00:15:30.480 --> 00:15:32.079
far

00:15:32.079 --> 00:15:34.880
yes same I also I also do research on

00:15:34.880 --> 00:15:35.360
the site

00:15:35.360 --> 00:15:38.079
as I told you english major and yeah I

00:15:38.079 --> 00:15:39.360
also do zotero

00:15:39.360 --> 00:15:41.839
some people have been using uh a

00:15:41.839 --> 00:15:43.759
connector between zotero and Emacs which

00:15:43.759 --> 00:15:44.160
has

00:15:44.160 --> 00:15:46.000
they've had great success with them but

00:15:46.000 --> 00:15:47.360
personally I haven't touched

00:15:47.360 --> 00:15:50.480
touched it already so yeah

00:15:50.480 --> 00:15:52.240
oh go ahead sorry all right so far I

00:15:52.240 --> 00:15:53.920
don't have any problems with zotero but

00:15:53.920 --> 00:15:54.880
maybe if I

00:15:54.880 --> 00:15:56.320
run into something I might check out

00:15:56.320 --> 00:15:58.320
ebay in the future

00:15:58.320 --> 00:16:00.240
yeah definitely I think zotero is a very

00:16:00.240 --> 00:16:01.680
solid project and you know the fact that

00:16:01.680 --> 00:16:02.560
it's being used

00:16:02.560 --> 00:16:04.959
by people outside of Emacs also ensures

00:16:04.959 --> 00:16:06.560
that there's quite a lot of packing

00:16:06.560 --> 00:16:07.680
behind the software

00:16:07.680 --> 00:16:09.759
which is reassuring when your livelihood

00:16:09.759 --> 00:16:11.759
depends on your research

00:16:11.759 --> 00:16:13.519
right and then I think one more thing

00:16:13.519 --> 00:16:15.600
with zotero is that you can create

00:16:15.600 --> 00:16:17.519
groups so if you're in a collaborative

00:16:17.519 --> 00:16:18.079
project

00:16:18.079 --> 00:16:20.160
you can create a reference you know a

00:16:20.160 --> 00:16:22.320
library just for your group and I think

00:16:22.320 --> 00:16:23.759
that could help because like I

00:16:23.759 --> 00:16:25.279
I'm going to be in a project next

00:16:25.279 --> 00:16:27.600
semester that requires that

00:16:27.600 --> 00:16:29.839
yeah definitely I believe the ability to

00:16:29.839 --> 00:16:31.600
have folders inside zotero

00:16:31.600 --> 00:16:33.839
makes it incredibly useful to manage

00:16:33.839 --> 00:16:35.360
your different projects concurrent

00:16:35.360 --> 00:16:37.440
projects

00:16:37.440 --> 00:16:39.279
so moving on to the questions do you

00:16:39.279 --> 00:16:41.279
have any suggestion on what subjects or

00:16:41.279 --> 00:16:43.440
things should be tags or separate organ

00:16:43.440 --> 00:16:46.560
files for cross-linking

00:16:46.560 --> 00:16:50.320
right um so so far now like I'm having

00:16:50.320 --> 00:16:52.720
trouble with like should I be combining

00:16:52.720 --> 00:16:55.360
certain concepts together as one like

00:16:55.360 --> 00:16:55.839
this is

00:16:55.839 --> 00:16:59.360
where the the thought process you know

00:16:59.360 --> 00:17:00.959
starts coming to fruit is that when you

00:17:00.959 --> 00:17:02.959
start you know combining

00:17:02.959 --> 00:17:04.880
ideas together so you won't need a

00:17:04.880 --> 00:17:06.480
specific tag

00:17:06.480 --> 00:17:09.199
and another one that are like similar in

00:17:09.199 --> 00:17:11.280
ideas

00:17:11.280 --> 00:17:12.720
I'm not sure if that answers the

00:17:12.720 --> 00:17:14.799
question but like so far I've been using

00:17:14.799 --> 00:17:15.919
the orgrum

00:17:15.919 --> 00:17:17.919
you know the default way which is like

00:17:17.919 --> 00:17:19.039
many small

00:17:19.039 --> 00:17:22.160
um files and then just

00:17:22.160 --> 00:17:24.400
linking them to my like either if I have

00:17:24.400 --> 00:17:26.319
a report to write or if I have a like

00:17:26.319 --> 00:17:26.959
you know

00:17:26.959 --> 00:17:32.240
essay to write

00:17:32.240 --> 00:17:35.360
I think you're muted

00:17:35.360 --> 00:17:37.760
q and I just I did two stupid things the

00:17:37.760 --> 00:17:38.400
first one

00:17:38.400 --> 00:17:40.640
was filling up my water the second one

00:17:40.640 --> 00:17:42.320
was peeking without actually turning on

00:17:42.320 --> 00:17:43.760
my microphone

00:17:43.760 --> 00:17:45.760
so let's just hope that nothing is going

00:17:45.760 --> 00:17:47.760
to fry in the near vicinity of me right

00:17:47.760 --> 00:17:48.320
now

00:17:48.320 --> 00:17:49.840
but uh yeah I believe you've answered

00:17:49.840 --> 00:17:51.440
the question so don't worry about it I'm

00:17:51.440 --> 00:17:53.200
slightly wet right now which is not a

00:17:53.200 --> 00:17:55.280
very agreeable feeling but we'll have to

00:17:55.280 --> 00:17:57.280
carry on I suppose

00:17:57.280 --> 00:17:59.360
another question is there a place where

00:17:59.360 --> 00:18:01.600
people are collaborating on research

00:18:01.600 --> 00:18:04.320
about Emacs so do you want to try to

00:18:04.320 --> 00:18:06.160
take this one

00:18:06.160 --> 00:18:08.559
um I don't know but I'm definitely

00:18:08.559 --> 00:18:10.559
interested in the user experience of

00:18:10.559 --> 00:18:12.480
Emacs so

00:18:12.480 --> 00:18:14.720
if anyone wants to work on that I'm

00:18:14.720 --> 00:18:16.400
happy

00:18:16.400 --> 00:18:18.320
well you do have a a pretty good

00:18:18.320 --> 00:18:19.760
candidate in front of you if I

00:18:19.760 --> 00:18:22.080
should say so myself I'm incredibly

00:18:22.080 --> 00:18:22.960
interested about

00:18:22.960 --> 00:18:25.039
um the ability to do research in Emacs

00:18:25.039 --> 00:18:26.960
and about the ability to

00:18:26.960 --> 00:18:30.480
um preach the floss way

00:18:30.480 --> 00:18:32.480
to academia and to the academe

00:18:32.480 --> 00:18:34.080
especially because I believe there's

00:18:34.080 --> 00:18:35.280
really something

00:18:35.280 --> 00:18:38.240
great to be done sorry I'm just looking

00:18:38.240 --> 00:18:39.919
at the puddle of water on the side which

00:18:39.919 --> 00:18:41.840
is slightly oozing my way

00:18:41.840 --> 00:18:45.039
which is not a very good feeling really

00:18:45.039 --> 00:18:46.880
but yeah I believe I believe some work

00:18:46.880 --> 00:18:48.320
could be done and if people are

00:18:48.320 --> 00:18:50.000
interested in the chat right now

00:18:50.000 --> 00:18:52.320
I mean do get in touch with us both

00:18:52.320 --> 00:18:53.440
neuron and I

00:18:53.440 --> 00:18:56.480
are on our slack channel yes I know

00:18:56.480 --> 00:18:57.280
slack

00:18:57.280 --> 00:19:00.080
the corporate hive mind that it's like

00:19:00.080 --> 00:19:01.919
but we've decided with orgrim to use

00:19:01.919 --> 00:19:02.720
slack

00:19:02.720 --> 00:19:05.520
but you can find us very easily and uh

00:19:05.520 --> 00:19:06.880
if you want to talk about these topics

00:19:06.880 --> 00:19:07.360
yes

00:19:07.360 --> 00:19:08.720
by all means do and we'll be very

00:19:08.720 --> 00:19:10.720
interested to answer your questions

00:19:10.720 --> 00:19:12.640
so I have a question here says like how

00:19:12.640 --> 00:19:15.520
does the view for time blocking works

00:19:15.520 --> 00:19:18.640
um I use org super agenda so

00:19:18.640 --> 00:19:22.000
um what happens is that my active

00:19:22.000 --> 00:19:23.200
timestamps are

00:19:23.200 --> 00:19:26.960
only in my gmail or file

00:19:26.960 --> 00:19:29.200
so if you use org gcal you have to

00:19:29.200 --> 00:19:30.080
specify

00:19:30.080 --> 00:19:32.559
a certain org file and when it you know

00:19:32.559 --> 00:19:34.320
imports them it imports them as like

00:19:34.320 --> 00:19:35.679
active

00:19:35.679 --> 00:19:38.400
timestamps and I make sure whenever I

00:19:38.400 --> 00:19:40.480
create a to-do or even a research task

00:19:40.480 --> 00:19:42.480
that it doesn't have a time stamp on it

00:19:42.480 --> 00:19:45.039
because what I want to do is go back

00:19:45.039 --> 00:19:48.480
and then move around um these tags

00:19:48.480 --> 00:19:50.160
according to my you know either weekly

00:19:50.160 --> 00:19:51.919
schedule or monthly or however long you

00:19:51.919 --> 00:19:52.960
want to do it

00:19:52.960 --> 00:19:56.480
um so yeah only active timestamps or

00:19:56.480 --> 00:19:59.679
deadlines um appear in your time grid

00:19:59.679 --> 00:20:03.280
so that could work um that's very good

00:20:03.280 --> 00:20:05.440
just just to uh interject for a second

00:20:05.440 --> 00:20:06.320
about this

00:20:06.320 --> 00:20:07.840
you know with orgrim right now we're

00:20:07.840 --> 00:20:10.720
mostly uh focused on optimization

00:20:10.720 --> 00:20:13.039
but we're hoping to move on to ux very

00:20:13.039 --> 00:20:14.720
soon so all those matters about

00:20:14.720 --> 00:20:16.720
you know having to do's in your files it

00:20:16.720 --> 00:20:18.159
is something that we've been thinking

00:20:18.159 --> 00:20:20.000
about with jethro kwan who is my main

00:20:20.000 --> 00:20:20.880
commentator

00:20:20.880 --> 00:20:23.280
or grow and we'll be working on this in

00:20:23.280 --> 00:20:24.480
the coming months so don't worry too

00:20:24.480 --> 00:20:26.080
much about it and stay tuned

00:20:26.080 --> 00:20:29.760
yeah um so I've got the ebib

00:20:29.760 --> 00:20:33.200
and what else um what subjects I think

00:20:33.200 --> 00:20:34.080
okay

00:20:34.080 --> 00:20:35.919
what is this question have you seen the

00:20:35.919 --> 00:20:37.120
project papi's

00:20:37.120 --> 00:20:40.400
I'm not sure what oh it's a zotero

00:20:40.400 --> 00:20:41.280
alternative okay

00:20:41.280 --> 00:20:43.840
I'll look into it thank you I don't know

00:20:43.840 --> 00:20:45.919
I don't know about it either so

00:20:45.919 --> 00:20:49.600
please look into it and let me know yeah

00:20:49.600 --> 00:20:53.200
um have we covered all the questions

00:20:53.200 --> 00:20:55.679
I believe we have and we have about

00:20:55.679 --> 00:20:56.880
two-minute leeway

00:20:56.880 --> 00:20:58.880
for me to move into the next talk so

00:20:58.880 --> 00:21:00.240
we're right on time

00:21:00.240 --> 00:21:01.760
all right thank you so much really

00:21:01.760 --> 00:21:04.159
appreciate it and good luck everyone

00:21:04.159 --> 00:21:05.440
well thank you and thank you so much for

00:21:05.440 --> 00:21:07.600
coming and uh doing allowing me not to

00:21:07.600 --> 00:21:08.400
be the only one

00:21:08.400 --> 00:21:11.440
talking about all room today sounds good

00:21:11.440 --> 00:21:14.559
all right thank you both very much

00:21:14.559 --> 00:21:16.799
yes