The template includes the orb-process-file-field function to allow selecting the pdf to be used with org-noter. ![]() To break-down aspects of the configuration snippet above: To make life easier, there is a tinyġ ( setq 2 bibtex-completion-notes-path "/home/haozeke/Git/Gitlab/Mine/Notes/" 3 bibtex-completion-bibliography "/home/haozeke/GDrive/zotLib.bib" 4 bibtex-completion-pdf-field "file" 5 bibtex-completion-notes-template-multiple-files 6 ( concat 7 "#+TITLE: $\n" 19 ":END:\n\n" 20 ) 21 )ĭoom-emacs users like me might want to wrap the above in a nice after! org-ref expression, but it doesn’t really matter. ![]() Without getting too deep into the weeds here, the basic requirements are: This guide complete, I will also describe the Zotero settings I have. ![]() Venerable helm-bibtex ( repo here) and org-ref ( repo here). The basic tools of bibliographic management from the emacs end are the Thus this section is actually doom agnostic. Since I will be using org-ref, it makes no sense to load or work with the The otherĪspect of interacting with the notes is via the org-roam interface and will be downcase ))) 15 :config 16 ( add-to-list 'deft-extensions "tex" ) 17 )įor more about the doom-emacs defaults, check the Github repo. Given the packages we will be using, some variable settings are in order, namely:ġ ( use-package deft 2 :commands deft 3 :init 4 ( setq deft-default-extension "org" 5 de-couples filename and note title: 6 deft-use-filename-as-title nil 7 deft-use-filter-string-for-filename t 8 disable auto-save 9 deft-auto-save-interval -1.0 10 converts the filter string into a readable file-name using kebab-case: 11 deft-file-naming-rules 12 ' (( noslash. Interpolate smoothly with org-roam, org-ref, helm-bibtex, and The basic idea is to ensure meaningful templates which ConceptĬovers websites, bibliographies, and pdfs respectivelyĪ key component in this workflow is actually facilitated by the fabulous The concepts above will be handled by the following packages. Storage Not actually part of the workflow in the same way, since it will be handled at the system level, it is worth nothing, that in this workflow Zotero is used to export a master bib file and keeps it updated, while the notes themselves are version controlled 5. Backlinks In particular, by backlinks at this point we are referring to the ability to link to a pdf or a website with a unique key such that notes can be added or removed at will. In particular, it would be nice to be able to visualize the flow of ideas, each represented by a note. Contextual Representation This aspect of the workflow deals with representations, which should transcend the usage of tags or categories. The search interface must then simply allow us to narrow down our candidates in a meaningful manner. It is assumed that there will be many notes, and that they will have a wide variety of content. This then requires a separate system forĮach which is described by: Search Engine The search engine is key, both in terms of accessibility and scalability. The idea is to be able to create notes for all kinds of content. Zotero This is what I personally use and recommend. ![]() The fact that it is Java based was a major issue for me. Jabref This is fun, but really more of a per-project management system, but it works well for that. Sadly, the price tiers aren’t very friendly so I have to give it a hard pass. The options most commonly seen are: Mendeley This is a great option, and the most mobile friendly of the bunch. Reference management is one of the main reasons to consider a plain-text setup, and mine is no different. So the basics of the ideology are listed below. Workflow I want, and then implement it, instead of relying on the cannedĪpproaches of each package. While working through ideas, it actually was more useful to describe the
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |