0:00:00.320,0:00:03.040 good afternoon or good evening everyone 0:00:02.639,0:00:05.440 uh 0:00:03.040,0:00:07.759 today my talk is going to be on org mode 0:00:05.440,0:00:10.559 and or group for skulls and researchers 0:00:07.759,0:00:12.639 leo has talked about like the overall 0:00:10.559,0:00:15.120 picture of orgrim and or 0:00:12.639,0:00:16.240 uh bibtex or groundbreak tech I will be 0:00:15.120,0:00:19.199 talking more about 0:00:16.240,0:00:20.320 the research process itself using these 0:00:19.199,0:00:22.400 tools 0:00:20.320,0:00:25.039 all right so just to introduce that the 0:00:22.400,0:00:28.080 research process is really messy 0:00:25.039,0:00:31.039 um you're always working in like 0:00:28.080,0:00:32.960 piecemeal tasks and things move around 0:00:31.039,0:00:35.280 all the time and so 0:00:32.960,0:00:36.880 there needs to be a system where you can 0:00:35.280,0:00:39.360 organize all these tasks 0:00:36.880,0:00:41.760 all these ideas in a way that is 0:00:39.360,0:00:44.239 flexible and effective 0:00:41.760,0:00:44.960 so my motivation is that research is 0:00:44.239,0:00:47.120 hard and 0:00:44.960,0:00:49.600 writing about it is even more difficult 0:00:47.120,0:00:51.120 and my goal is to add some structure to 0:00:49.600,0:00:52.800 this whole madness 0:00:51.120,0:00:54.480 so here's a list of some of the stuff 0:00:52.800,0:00:57.199 that I've been using since I first 0:00:54.480,0:01:00.160 learned about Emacs in 2019 0:00:57.199,0:01:02.000 and what I've what I've found useful um 0:01:00.160,0:01:05.199 during my res uh like um 0:01:02.000,0:01:07.920 within my research process all right so 0:01:05.199,0:01:10.400 I've organized org mode for researchers 0:01:07.920,0:01:12.400 and scholars within the writing process 0:01:10.400,0:01:14.320 into three modules first there's like 0:01:12.400,0:01:15.759 the planning aspect of it 0:01:14.320,0:01:17.680 then you've got the writing and the 0:01:15.759,0:01:18.320 reference management which I will join 0:01:17.680,0:01:20.560 together 0:01:18.320,0:01:21.920 by looking at the example of doing your 0:01:20.560,0:01:24.720 literature review 0:01:21.920,0:01:26.479 all right so when we're talking about 0:01:24.720,0:01:27.360 planning we're talking about either task 0:01:26.479,0:01:30.880 management or 0:01:27.360,0:01:31.600 time management with task management 0:01:30.880,0:01:33.840 you've got 0:01:31.600,0:01:36.159 org modes to do's and tags and 0:01:33.840,0:01:38.479 categories these are really powerful 0:01:36.159,0:01:41.600 tools that you could use 0:01:38.479,0:01:44.799 um in your org files to just um 0:01:41.600,0:01:47.040 uh like organize your tasks and 0:01:44.799,0:01:49.040 your appointments so there are different 0:01:47.040,0:01:50.960 types of to-do's that you can either set 0:01:49.040,0:01:52.799 globally in your init file or they can 0:01:50.960,0:01:55.200 be file buffer specific 0:01:52.799,0:01:56.079 so that means based on context based on 0:01:55.200,0:01:57.759 the type of 0:01:56.079,0:01:59.280 manuscript you're working on whether 0:01:57.759,0:02:02.240 it's like a literate programming 0:01:59.280,0:02:03.759 report or your actual thesis slash 0:02:02.240,0:02:05.840 dissertation 0:02:03.759,0:02:07.759 um also these to-do's are either created 0:02:05.840,0:02:11.440 as a set tree like think of them as 0:02:07.759,0:02:14.800 headings and sections if you use latex 0:02:11.440,0:02:15.360 or inline text which are like org inline 0:02:14.800,0:02:17.760 tasks I 0:02:15.360,0:02:19.120 like organ line tasks because like I can 0:02:17.760,0:02:21.520 add 0:02:19.120,0:02:22.879 to do's between two paragraphs and that 0:02:21.520,0:02:25.360 way it doesn't show up 0:02:22.879,0:02:27.280 in the table of contents when I export 0:02:25.360,0:02:30.879 into pdf or html or 0:02:27.280,0:02:34.319 anything else all right so this is an 0:02:30.879,0:02:37.360 example of buffer specific to do's 0:02:34.319,0:02:39.120 and and this is example of like a little 0:02:37.360,0:02:40.800 programming report that I was working on 0:02:39.120,0:02:43.200 where I was like dealing with 0:02:40.800,0:02:44.080 data and like analysis and all of that 0:02:43.200,0:02:47.519 stuff and so 0:02:44.080,0:02:49.440 I needed um context specific to do's to 0:02:47.519,0:02:52.080 use them within this buffer 0:02:49.440,0:02:54.319 um and that's how I would organize it 0:02:52.080,0:02:57.200 and there's also also another example 0:02:54.319,0:02:57.920 of an org inline task where you could 0:02:57.200,0:03:01.360 see it 0:02:57.920,0:03:03.040 in the middle between the two headings 0:03:01.360,0:03:04.959 that way it wouldn't show up in the 0:03:03.040,0:03:06.480 table of contents and it would look like 0:03:04.959,0:03:09.519 nature within the 0:03:06.480,0:03:11.920 text when you export it 0:03:09.519,0:03:13.280 oh but I also added a tag of no export 0:03:11.920,0:03:16.400 so it won't show up at all 0:03:13.280,0:03:19.360 when I export it into like either pdf 0:03:16.400,0:03:21.599 which I use all the time all right so 0:03:19.360,0:03:24.159 another useful tool 0:03:21.599,0:03:25.200 um for the research and just like 0:03:24.159,0:03:27.920 general planning 0:03:25.200,0:03:29.120 is the org capture um when I first 0:03:27.920,0:03:32.080 started with Emacs 0:03:29.120,0:03:34.239 actually it was for org agenda and I 0:03:32.080,0:03:35.360 went crazy with my capture template I 0:03:34.239,0:03:37.599 created a template for 0:03:35.360,0:03:38.640 everything um because I was just so 0:03:37.599,0:03:40.720 excited 0:03:38.640,0:03:42.400 but with time I was using less and less 0:03:40.720,0:03:46.319 of them so I kept taking them out 0:03:42.400,0:03:48.239 and now this is my simplified um 0:03:46.319,0:03:49.599 capture templates that I use either for 0:03:48.239,0:03:52.159 a general to do 0:03:49.599,0:03:54.159 um for a regular appointment a fleeting 0:03:52.159,0:03:55.200 note research tasks because like those 0:03:54.159,0:03:56.959 are what I focus on 0:03:55.200,0:03:58.720 like my bread and butter and then 0:03:56.959,0:04:00.879 finally with meetings which I find 0:03:58.720,0:04:01.680 sometimes I don't use it as much because 0:04:00.879,0:04:03.519 I would just like 0:04:01.680,0:04:04.879 have the org file ready instead of 0:04:03.519,0:04:07.920 needing to capture 0:04:04.879,0:04:11.439 you know open a capture template 0:04:07.920,0:04:12.400 right or agenda um that's how I got into 0:04:11.439,0:04:15.439 Emacs 0:04:12.400,0:04:16.799 I needed to um organize my life and I 0:04:15.439,0:04:19.199 found Emacs and 0:04:16.799,0:04:20.479 it's been great ever since um it 0:04:19.199,0:04:22.720 populates all your to-do's and 0:04:20.479,0:04:25.280 appointments into a singular view so the 0:04:22.720,0:04:29.120 default view I think it's a weak view 0:04:25.280,0:04:31.919 however I use org super agenda love this 0:04:29.120,0:04:34.160 um package and I set up my agenda as a 0:04:31.919,0:04:37.360 daily view with just appointments 0:04:34.160,0:04:38.720 deadlines and a habit tracker um and 0:04:37.360,0:04:40.639 a side note you guys I'm still 0:04:38.720,0:04:42.320 struggling with organizing the perfect 0:04:40.639,0:04:45.360 agenda so it's a process 0:04:42.320,0:04:47.919 and take it easy all right 0:04:45.360,0:04:50.320 so this is just an overview of my daily 0:04:47.919,0:04:52.800 agenda as you can see they're just like 0:04:50.320,0:04:55.520 appointments that I import from gmail 0:04:52.800,0:04:57.919 using org gcal 0:04:55.520,0:04:58.880 a simple habit tracker of like daily 0:04:57.919,0:05:00.960 free writing 0:04:58.880,0:05:02.800 as you can see there are a lot of times 0:05:00.960,0:05:05.199 where I'm skipping and the asterisk is 0:05:02.800,0:05:08.479 the one where I've completed that day 0:05:05.199,0:05:10.080 so you know it's a process and then just 0:05:08.479,0:05:12.639 like regular deadlines 0:05:10.080,0:05:14.000 so what happens is that I have other 0:05:12.639,0:05:17.120 to-do's that I have 0:05:14.000,0:05:17.919 not scheduled or not added a deadline 0:05:17.120,0:05:20.560 but they're just 0:05:17.919,0:05:22.320 tasks that keep piling up when I first 0:05:20.560,0:05:24.880 started with Emacs and org agenda 0:05:22.320,0:05:26.880 I had everything in there and it got 0:05:24.880,0:05:29.680 overwhelming and then I decided no 0:05:26.880,0:05:30.800 I'm not gonna even let them show up so 0:05:29.680,0:05:33.120 what I would do 0:05:30.800,0:05:34.479 at the beginning of each week or the 0:05:33.120,0:05:36.800 night before 0:05:34.479,0:05:38.000 um I would sit down look at all my to 0:05:36.800,0:05:40.720 to-do's that I have 0:05:38.000,0:05:42.639 not assigned yet to a deadline or a 0:05:40.720,0:05:45.360 schedule or just a simple 0:05:42.639,0:05:46.320 timestamp um and I would organize them 0:05:45.360,0:05:49.520 throughout the week 0:05:46.320,0:05:51.680 so here's an example of what I did 0:05:49.520,0:05:53.039 so on that wednesday from my gmail I had 0:05:51.680,0:05:55.600 all these appointments but 0:05:53.039,0:05:56.560 one of them is I have a writing group 0:05:55.600,0:05:58.400 session 0:05:56.560,0:05:59.759 and so I looked at my tasks and I 0:05:58.400,0:06:02.639 thought okay then I will just 0:05:59.759,0:06:03.520 assign um like for example my emac 0:06:02.639,0:06:06.319 slides 0:06:03.520,0:06:07.280 or the framework diagram into that 0:06:06.319,0:06:09.600 writing session 0:06:07.280,0:06:10.800 and all I did was just add an active 0:06:09.600,0:06:12.960 timestamp 0:06:10.800,0:06:14.000 that is all I needed to do and it went 0:06:12.960,0:06:17.120 straight into my 0:06:14.000,0:06:20.080 appointment now if I miss that 0:06:17.120,0:06:21.520 it won't show up on the next day so if 0:06:20.080,0:06:24.639 you put in a deadline 0:06:21.520,0:06:26.560 it will show up as an overdue but if you 0:06:24.639,0:06:29.280 have no deadline or schedule it will not 0:06:26.560,0:06:32.960 show up in your daily org agenda 0:06:29.280,0:06:35.680 so just a star 0:06:32.960,0:06:37.520 all right another way of accessing your 0:06:35.680,0:06:40.880 to do's is that if it's 0:06:37.520,0:06:42.160 um file specific org file specific 0:06:40.880,0:06:44.160 buffer specific 0:06:42.160,0:06:46.400 and so like when we talked about like 0:06:44.160,0:06:47.680 whether to have a big ass org file or 0:06:46.400,0:06:50.720 like tiny files 0:06:47.680,0:06:54.560 it all depends and this isn't the the 0:06:50.720,0:06:55.759 um you know the way this depends 0:06:54.560,0:06:58.400 because if you're working on like a 0:06:55.759,0:06:59.680 dissertation um it's a huge manuscript 0:06:58.400,0:07:02.880 you need to like work 0:06:59.680,0:07:05.759 on that org file all the time um 0:07:02.880,0:07:07.680 then yes it might do should be in that 0:07:05.759,0:07:08.000 file specifically because every time if 0:07:07.680,0:07:09.680 I'm 0:07:08.000,0:07:12.479 if I'm visiting this org file all the 0:07:09.680,0:07:15.520 time I should be able to just look at my 0:07:12.479,0:07:18.639 tasks from uh within that buffer 0:07:15.520,0:07:21.599 and so I use org sidebar to 0:07:18.639,0:07:22.960 keep all these specific uh to do's 0:07:21.599,0:07:26.560 within that org file 0:07:22.960,0:07:28.400 I find it helpful okay 0:07:26.560,0:07:29.759 now that we're going into the writing 0:07:28.400,0:07:33.039 and reference management 0:07:29.759,0:07:35.840 we'll call it a literature review um 0:07:33.039,0:07:36.639 and this is something I've built as a 0:07:35.840,0:07:40.240 schema 0:07:36.639,0:07:43.759 I think that it works for now 0:07:40.240,0:07:45.919 um and it requires one outside pack 0:07:43.759,0:07:47.680 of outside software which is zotero what 0:07:45.919,0:07:48.720 I use it's an open source reference 0:07:47.680,0:07:51.759 management 0:07:48.720,0:07:53.599 software um it's great 0:07:51.759,0:07:55.120 but the things to keep in mind is that I 0:07:53.599,0:07:58.319 use two um 0:07:55.120,0:08:01.039 plugins that is really needed for when 0:07:58.319,0:08:03.840 we work with orgrim bibtex and orgrim 0:08:01.039,0:08:06.160 and org mode um and the zap file so 0:08:03.840,0:08:07.039 better bibtex organizes your reference 0:08:06.160,0:08:10.560 keys 0:08:07.039,0:08:13.360 um in um in a way like in a fashion that 0:08:10.560,0:08:14.240 works for you so for me all my reference 0:08:13.360,0:08:17.280 keys are like 0:08:14.240,0:08:21.120 last author and gear um and with zap 0:08:17.280,0:08:22.319 file I um I let it like rename all the 0:08:21.120,0:08:24.400 pdf files 0:08:22.319,0:08:26.000 the same way that I have for my bit of 0:08:24.400,0:08:29.360 my bib keys which is like 0:08:26.000,0:08:33.440 last name of author and year all right 0:08:29.360,0:08:37.120 once you export your entire 0:08:33.440,0:08:39.440 library as a bib file then you can work 0:08:37.120,0:08:42.880 on it within org mode and Emacs 0:08:39.440,0:08:45.040 using um the following packages 0:08:42.880,0:08:47.839 all right so with orgrim bibtex it 0:08:45.040,0:08:49.519 creates an org file for each bib entry 0:08:47.839,0:08:52.240 and you have the option of like 0:08:49.519,0:08:54.880 templating and doing other stuff with it 0:08:52.240,0:08:56.240 and then finally there's like this orb 0:08:54.880,0:08:58.800 pdf scraper 0:08:56.240,0:09:00.240 I've used it briefly but I think the 0:08:58.800,0:09:02.880 potential 0:09:00.240,0:09:05.920 with or pdf scraper is if you're gonna 0:09:02.880,0:09:08.320 do a bibliometric study or like a 0:09:05.920,0:09:10.000 systematic literature view there's 0:09:08.320,0:09:10.959 something there but I have to look 0:09:10.000,0:09:14.399 through it 0:09:10.959,0:09:16.880 anyway so once you create your you know 0:09:14.399,0:09:18.160 your reference file of reference x and 0:09:16.880,0:09:20.240 you're writing your notes 0:09:18.160,0:09:22.399 you can either go like with going 0:09:20.240,0:09:24.080 through org mode you're writing 0:09:22.399,0:09:26.080 your ideas you're writing your notes 0:09:24.080,0:09:27.839 you're assigning tasks 0:09:26.080,0:09:30.480 and then there's org transclusion which 0:09:27.839,0:09:32.240 I will mention briefly at the end 0:09:30.480,0:09:35.360 and ways to extract if you're going to 0:09:32.240,0:09:36.640 go through the orgrom 0:09:35.360,0:09:38.720 things that you're going to use within 0:09:36.640,0:09:40.000 orgrom it's a great way to build your 0:09:38.720,0:09:42.880 database you start making the 0:09:40.000,0:09:44.959 connections and you can visualize your 0:09:42.880,0:09:46.240 notes and like how these references are 0:09:44.959,0:09:48.839 linked to each other 0:09:46.240,0:09:50.240 through the organ server or or ground 0:09:48.839,0:09:53.120 graph 0:09:50.240,0:09:53.680 all right this is just notes for later 0:09:53.120,0:09:56.240 okay 0:09:53.680,0:09:57.360 so this is an example of like an orgram 0:09:56.240,0:09:59.279 file that I have 0:09:57.360,0:10:01.760 for example if I'm working on adaptation 0:09:59.279,0:10:02.560 policy I have these hyperlinks that are 0:10:01.760,0:10:04.959 linked to other 0:10:02.560,0:10:06.640 concepts and ideas such as either 0:10:04.959,0:10:08.720 climate security 0:10:06.640,0:10:10.560 um changing global environment so on and 0:10:08.720,0:10:13.920 so forth and the backlinks 0:10:10.560,0:10:15.839 are other references that talk about 0:10:13.920,0:10:17.680 this specific concept 0:10:15.839,0:10:19.920 so this is really helpful and then when 0:10:17.680,0:10:22.160 you visualize it the picture on the left 0:10:19.920,0:10:24.160 which I'm sure looks really small 0:10:22.160,0:10:25.680 um you can see the connections that it's 0:10:24.160,0:10:28.160 making with other 0:10:25.680,0:10:29.760 references so of course this is just 0:10:28.160,0:10:32.720 like a buffer 0:10:29.760,0:10:34.560 network when you look at the entire 0:10:32.720,0:10:38.000 database network it's it's 0:10:34.560,0:10:41.680 it's growing okay 0:10:38.000,0:10:44.079 so going into organ bidtech 0:10:41.680,0:10:46.000 so it utilizes a combination of the or 0:10:44.079,0:10:46.880 graph package helmbik tech candidate 0:10:46.000,0:10:50.079 completion 0:10:46.880,0:10:51.440 and it works with orgrom functionalities 0:10:50.079,0:10:54.880 and 0:10:51.440,0:10:57.440 other good stuff this is an example 0:10:54.880,0:10:58.720 of my orgrim bibtex file all right so 0:10:57.440,0:11:01.200 I've created 0:10:58.720,0:11:02.320 um the template which I pretty much use 0:11:01.200,0:11:05.920 what leo 0:11:02.320,0:11:08.640 has uh produced like in his um 0:11:05.920,0:11:10.160 tutorial so I think it's it's great it 0:11:08.640,0:11:12.880 works well for me 0:11:10.160,0:11:14.480 um and what it does is that it works 0:11:12.880,0:11:17.519 with your bib file 0:11:14.480,0:11:19.519 so if you're in your bib file you have a 0:11:17.519,0:11:21.040 sub entry that's called keywords and 0:11:19.519,0:11:23.120 usually that's within 0:11:21.040,0:11:24.560 a journal article the author would 0:11:23.120,0:11:27.519 specify these 0:11:24.560,0:11:28.160 keywords um when it gets imported into 0:11:27.519,0:11:30.399 zotero 0:11:28.160,0:11:32.399 it extracts those keywords and then it 0:11:30.399,0:11:34.959 gets populated as an org file 0:11:32.399,0:11:36.959 with orgrim bibtex so I always start 0:11:34.959,0:11:38.560 with the meta information first and then 0:11:36.959,0:11:42.480 I would write my notes 0:11:38.560,0:11:45.760 after that this is an example though 0:11:42.480,0:11:49.120 for reference of a physical book so 0:11:45.760,0:11:51.519 I don't have a pdf file for it um 0:11:49.120,0:11:53.920 so what I've figured out like a new idea 0:11:51.519,0:11:55.760 for it so if I'm writing notes on it 0:11:53.920,0:11:57.279 I would create a property that says 0:11:55.760,0:11:58.959 pages um 0:11:57.279,0:12:00.639 that way it's easier for you when you go 0:11:58.959,0:12:02.720 back to citing 0:12:00.639,0:12:04.720 um certain ideas or something that you 0:12:02.720,0:12:07.839 have the pages prepared there 0:12:04.720,0:12:11.279 it's easier that way okay 0:12:07.839,0:12:13.040 org noter which is something I 0:12:11.279,0:12:14.880 use a lot especially with journal 0:12:13.040,0:12:15.600 articles that have pdfs and stuff like 0:12:14.880,0:12:19.120 that 0:12:15.600,0:12:22.720 they're really helpful if you are gonna 0:12:19.120,0:12:23.760 if you've just started using um Emacs 0:12:22.720,0:12:26.959 and orgrim 0:12:23.760,0:12:29.519 and you have all these pdfs that have 0:12:26.959,0:12:30.079 all the annotations and highlighting and 0:12:29.519,0:12:32.639 the 0:12:30.079,0:12:33.200 all that stuff with org noter you can 0:12:32.639,0:12:36.720 just 0:12:33.200,0:12:39.519 use the org note or create skeleton 0:12:36.720,0:12:41.200 uh command and it will populate all your 0:12:39.519,0:12:43.760 notes that have already been 0:12:41.200,0:12:44.800 um entered within the pdf file if you're 0:12:43.760,0:12:48.160 using an outside 0:12:44.800,0:12:52.560 software and creates them like as a neat 0:12:48.160,0:12:55.920 org file I I highly recommend 0:12:52.560,0:12:57.920 finally org transclusion um 0:12:55.920,0:13:01.040 I think this is still in its beta phase 0:12:57.920,0:13:02.720 but I've been enjoying it so far 0:13:01.040,0:13:04.800 um I'm guessing people know what 0:13:02.720,0:13:06.480 translation mean which is sort of like 0:13:04.800,0:13:09.600 copy pasting text from 0:13:06.480,0:13:11.839 one org file to another this is helpful 0:13:09.600,0:13:12.959 I I think I I peeked at a question that 0:13:11.839,0:13:16.320 was talking about like 0:13:12.959,0:13:18.320 you know linking um to other org files 0:13:16.320,0:13:20.320 I think org transclusion could really 0:13:18.320,0:13:24.399 work okay it's 0:13:20.320,0:13:27.760 equivalent to the include 0:13:24.399,0:13:29.519 function within org mode um but I think 0:13:27.760,0:13:32.560 so like if you have other files 0:13:29.519,0:13:34.800 that you know which region that you 0:13:32.560,0:13:36.079 need in another file you could use the 0:13:34.800,0:13:38.160 include but with 0:13:36.079,0:13:39.440 org transclusion it's great I mean you 0:13:38.160,0:13:42.720 just have 0:13:39.440,0:13:43.360 um you're just linking one part to the 0:13:42.720,0:13:45.760 other 0:13:43.360,0:13:47.760 sort of like not refiling but you know 0:13:45.760,0:13:49.680 hyperlinking 0:13:47.760,0:13:51.120 so this is an example of what org 0:13:49.680,0:13:53.680 transclusion looks like 0:13:51.120,0:13:54.720 um so the highlighted problem statement 0:13:53.680,0:13:57.760 is from another 0:13:54.720,0:13:58.240 org file and then what I would do is 0:13:57.760,0:13:59.760 just like 0:13:58.240,0:14:01.440 link it to there and there was like a 0:13:59.760,0:14:05.440 transclusion command 0:14:01.440,0:14:08.399 I wish I made another screenshot of it 0:14:05.440,0:14:09.120 and so when you invoke org transclusion 0:14:08.399,0:14:12.079 mode 0:14:09.120,0:14:12.480 it turns um it prints it out like that 0:14:12.079,0:14:15.120 so 0:14:12.480,0:14:16.560 it's in view mode and then when you want 0:14:15.120,0:14:18.480 to edit it will take you back to that 0:14:16.560,0:14:21.839 buffer and you can edit the text 0:14:18.480,0:14:22.720 however you want all right so thank you 0:14:21.839,0:14:26.000 so much 0:14:22.720,0:14:29.120 um I wanted to leave room for questions 0:14:26.000,0:14:32.560 but special thanks to all the folks that 0:14:29.120,0:14:33.440 work on orgrom or ground bibtex orgrim 0:14:32.560,0:14:36.320 server or 0:14:33.440,0:14:38.240 transclusion and of course alpha papo on 0:14:36.320,0:14:42.560 or super agenda and org sidebar 0:14:38.240,0:14:42.560 that's how I got into Emacs thank you 0:14:43.440,0:14:47.120 all right and uh well thank you so yeah 0:14:45.600,0:14:49.120 this time I'll be the one asking the 0:14:47.120,0:14:51.360 question and not I'm in so 0:14:49.120,0:14:53.120 I'm feeling filling big shoes right now 0:14:51.360,0:14:54.880 so you'll have to bear with me folks 0:14:53.120,0:14:56.240 so thank you so much noora for your 0:14:54.880,0:14:57.279 presentation that is incredibly 0:14:56.240,0:14:58.959 interesting 0:14:57.279,0:15:00.800 so would you mind if I fed you questions 0:14:58.959,0:15:04.000 from the charts yeah 0:15:00.800,0:15:06.160 go ahead okay so the first one I I've 0:15:04.000,0:15:07.920 picked on my end was did you try using 0:15:06.160,0:15:10.560 ebib instead of zotero 0:15:07.920,0:15:12.079 and if so is it better than zotero in 0:15:10.560,0:15:14.880 some ways 0:15:12.079,0:15:15.680 I no I have not used eb I've only used 0:15:14.880,0:15:18.560 mendeley 0:15:15.680,0:15:20.320 and then they got bought by el savior 0:15:18.560,0:15:23.040 and so like I was like okay I'm done 0:15:20.320,0:15:25.120 I'm going to zotero um there are a lot 0:15:23.040,0:15:26.240 of plugins with zotero that you can play 0:15:25.120,0:15:28.320 around with 0:15:26.240,0:15:30.480 so I can't speak for ebit but definitely 0:15:28.320,0:15:32.079 zotero it's been a good experience so 0:15:30.480,0:15:34.880 far 0:15:32.079,0:15:35.360 yes same I also I also do research on 0:15:34.880,0:15:38.079 the site 0:15:35.360,0:15:39.360 as I told you english major and yeah I 0:15:38.079,0:15:41.839 also do zotero 0:15:39.360,0:15:43.759 some people have been using uh a 0:15:41.839,0:15:44.160 connector between zotero and Emacs which 0:15:43.759,0:15:46.000 has 0:15:44.160,0:15:47.360 they've had great success with them but 0:15:46.000,0:15:50.480 personally I haven't touched 0:15:47.360,0:15:52.240 touched it already so yeah 0:15:50.480,0:15:53.920 oh go ahead sorry all right so far I 0:15:52.240,0:15:54.880 don't have any problems with zotero but 0:15:53.920,0:15:56.320 maybe if I 0:15:54.880,0:15:58.320 run into something I might check out 0:15:56.320,0:16:00.240 ebay in the future 0:15:58.320,0:16:01.680 yeah definitely I think zotero is a very 0:16:00.240,0:16:02.560 solid project and you know the fact that 0:16:01.680,0:16:04.959 it's being used 0:16:02.560,0:16:06.560 by people outside of Emacs also ensures 0:16:04.959,0:16:07.680 that there's quite a lot of packing 0:16:06.560,0:16:09.759 behind the software 0:16:07.680,0:16:11.759 which is reassuring when your livelihood 0:16:09.759,0:16:13.519 depends on your research 0:16:11.759,0:16:15.600 right and then I think one more thing 0:16:13.519,0:16:17.519 with zotero is that you can create 0:16:15.600,0:16:18.079 groups so if you're in a collaborative 0:16:17.519,0:16:20.160 project 0:16:18.079,0:16:22.320 you can create a reference you know a 0:16:20.160,0:16:23.759 library just for your group and I think 0:16:22.320,0:16:25.279 that could help because like I 0:16:23.759,0:16:27.600 I'm going to be in a project next 0:16:25.279,0:16:29.839 semester that requires that 0:16:27.600,0:16:31.600 yeah definitely I believe the ability to 0:16:29.839,0:16:33.839 have folders inside zotero 0:16:31.600,0:16:35.360 makes it incredibly useful to manage 0:16:33.839,0:16:37.440 your different projects concurrent 0:16:35.360,0:16:39.279 projects 0:16:37.440,0:16:41.279 so moving on to the questions do you 0:16:39.279,0:16:43.440 have any suggestion on what subjects or 0:16:41.279,0:16:46.560 things should be tags or separate organ 0:16:43.440,0:16:50.320 files for cross-linking 0:16:46.560,0:16:52.720 right um so so far now like I'm having 0:16:50.320,0:16:55.360 trouble with like should I be combining 0:16:52.720,0:16:55.839 certain concepts together as one like 0:16:55.360,0:16:59.360 this is 0:16:55.839,0:17:00.959 where the the thought process you know 0:16:59.360,0:17:02.959 starts coming to fruit is that when you 0:17:00.959,0:17:04.880 start you know combining 0:17:02.959,0:17:06.480 ideas together so you won't need a 0:17:04.880,0:17:09.199 specific tag 0:17:06.480,0:17:11.280 and another one that are like similar in 0:17:09.199,0:17:12.720 ideas 0:17:11.280,0:17:14.799 I'm not sure if that answers the 0:17:12.720,0:17:15.919 question but like so far I've been using 0:17:14.799,0:17:17.919 the orgrum 0:17:15.919,0:17:19.039 you know the default way which is like 0:17:17.919,0:17:22.160 many small 0:17:19.039,0:17:24.400 um files and then just 0:17:22.160,0:17:26.319 linking them to my like either if I have 0:17:24.400,0:17:26.959 a report to write or if I have a like 0:17:26.319,0:17:32.240 you know 0:17:26.959,0:17:35.360 essay to write 0:17:32.240,0:17:37.760 I think you're muted 0:17:35.360,0:17:38.400 q and I just I did two stupid things the 0:17:37.760,0:17:40.640 first one 0:17:38.400,0:17:42.320 was filling up my water the second one 0:17:40.640,0:17:43.760 was peeking without actually turning on 0:17:42.320,0:17:45.760 my microphone 0:17:43.760,0:17:47.760 so let's just hope that nothing is going 0:17:45.760,0:17:48.320 to fry in the near vicinity of me right 0:17:47.760,0:17:49.840 now 0:17:48.320,0:17:51.440 but uh yeah I believe you've answered 0:17:49.840,0:17:53.200 the question so don't worry about it I'm 0:17:51.440,0:17:55.280 slightly wet right now which is not a 0:17:53.200,0:17:57.280 very agreeable feeling but we'll have to 0:17:55.280,0:17:59.360 carry on I suppose 0:17:57.280,0:18:01.600 another question is there a place where 0:17:59.360,0:18:04.320 people are collaborating on research 0:18:01.600,0:18:06.160 about Emacs so do you want to try to 0:18:04.320,0:18:08.559 take this one 0:18:06.160,0:18:10.559 um I don't know but I'm definitely 0:18:08.559,0:18:12.480 interested in the user experience of 0:18:10.559,0:18:14.720 Emacs so 0:18:12.480,0:18:16.400 if anyone wants to work on that I'm 0:18:14.720,0:18:18.320 happy 0:18:16.400,0:18:19.760 well you do have a a pretty good 0:18:18.320,0:18:22.080 candidate in front of you if I 0:18:19.760,0:18:22.960 should say so myself I'm incredibly 0:18:22.080,0:18:25.039 interested about 0:18:22.960,0:18:26.960 um the ability to do research in Emacs 0:18:25.039,0:18:30.480 and about the ability to 0:18:26.960,0:18:32.480 um preach the floss way 0:18:30.480,0:18:34.080 to academia and to the academe 0:18:32.480,0:18:35.280 especially because I believe there's 0:18:34.080,0:18:38.240 really something 0:18:35.280,0:18:39.919 great to be done sorry I'm just looking 0:18:38.240,0:18:41.840 at the puddle of water on the side which 0:18:39.919,0:18:45.039 is slightly oozing my way 0:18:41.840,0:18:46.880 which is not a very good feeling really 0:18:45.039,0:18:48.320 but yeah I believe I believe some work 0:18:46.880,0:18:50.000 could be done and if people are 0:18:48.320,0:18:52.320 interested in the chat right now 0:18:50.000,0:18:53.440 I mean do get in touch with us both 0:18:52.320,0:18:56.480 neuron and I 0:18:53.440,0:18:57.280 are on our slack channel yes I know 0:18:56.480,0:19:00.080 slack 0:18:57.280,0:19:01.919 the corporate hive mind that it's like 0:19:00.080,0:19:02.720 but we've decided with orgrim to use 0:19:01.919,0:19:05.520 slack 0:19:02.720,0:19:06.880 but you can find us very easily and uh 0:19:05.520,0:19:07.360 if you want to talk about these topics 0:19:06.880,0:19:08.720 yes 0:19:07.360,0:19:10.720 by all means do and we'll be very 0:19:08.720,0:19:12.640 interested to answer your questions 0:19:10.720,0:19:15.520 so I have a question here says like how 0:19:12.640,0:19:18.640 does the view for time blocking works 0:19:15.520,0:19:22.000 um I use org super agenda so 0:19:18.640,0:19:23.200 um what happens is that my active 0:19:22.000,0:19:26.960 timestamps are 0:19:23.200,0:19:29.200 only in my gmail or file 0:19:26.960,0:19:30.080 so if you use org gcal you have to 0:19:29.200,0:19:32.559 specify 0:19:30.080,0:19:34.320 a certain org file and when it you know 0:19:32.559,0:19:35.679 imports them it imports them as like 0:19:34.320,0:19:38.400 active 0:19:35.679,0:19:40.480 timestamps and I make sure whenever I 0:19:38.400,0:19:42.480 create a to-do or even a research task 0:19:40.480,0:19:45.039 that it doesn't have a time stamp on it 0:19:42.480,0:19:48.480 because what I want to do is go back 0:19:45.039,0:19:50.160 and then move around um these tags 0:19:48.480,0:19:51.919 according to my you know either weekly 0:19:50.160,0:19:52.960 schedule or monthly or however long you 0:19:51.919,0:19:56.480 want to do it 0:19:52.960,0:19:59.679 um so yeah only active timestamps or 0:19:56.480,0:20:03.280 deadlines um appear in your time grid 0:19:59.679,0:20:05.440 so that could work um that's very good 0:20:03.280,0:20:06.320 just just to uh interject for a second 0:20:05.440,0:20:07.840 about this 0:20:06.320,0:20:10.720 you know with orgrim right now we're 0:20:07.840,0:20:13.039 mostly uh focused on optimization 0:20:10.720,0:20:14.720 but we're hoping to move on to ux very 0:20:13.039,0:20:16.720 soon so all those matters about 0:20:14.720,0:20:18.159 you know having to do's in your files it 0:20:16.720,0:20:20.000 is something that we've been thinking 0:20:18.159,0:20:20.880 about with jethro kwan who is my main 0:20:20.000,0:20:23.280 commentator 0:20:20.880,0:20:24.480 or grow and we'll be working on this in 0:20:23.280,0:20:26.080 the coming months so don't worry too 0:20:24.480,0:20:29.760 much about it and stay tuned 0:20:26.080,0:20:33.200 yeah um so I've got the ebib 0:20:29.760,0:20:34.080 and what else um what subjects I think 0:20:33.200,0:20:35.919 okay 0:20:34.080,0:20:37.120 what is this question have you seen the 0:20:35.919,0:20:40.400 project papi's 0:20:37.120,0:20:41.280 I'm not sure what oh it's a zotero 0:20:40.400,0:20:43.840 alternative okay 0:20:41.280,0:20:45.919 I'll look into it thank you I don't know 0:20:43.840,0:20:49.600 I don't know about it either so 0:20:45.919,0:20:53.200 please look into it and let me know yeah 0:20:49.600,0:20:55.679 um have we covered all the questions 0:20:53.200,0:20:56.880 I believe we have and we have about 0:20:55.679,0:20:58.880 two-minute leeway 0:20:56.880,0:21:00.240 for me to move into the next talk so 0:20:58.880,0:21:01.760 we're right on time 0:21:00.240,0:21:04.159 all right thank you so much really 0:21:01.760,0:21:05.440 appreciate it and good luck everyone 0:21:04.159,0:21:07.600 well thank you and thank you so much for 0:21:05.440,0:21:08.400 coming and uh doing allowing me not to 0:21:07.600,0:21:11.440 be the only one 0:21:08.400,0:21:14.559 talking about all room today sounds good 0:21:11.440,0:21:16.799 all right thank you both very much 0:21:14.559,0:21:16.799 yes