All talks: https://emacsconf.org/2023/talks/
Why Nabokov would use Org-Mode if he were writing today
https://emacsconf.org/2023/talks/nabokov - Edmund Jorgensen - Track: General
Watch/participate: https://emacsconf.org/2023/watch/gen/
Q&A room: https://media.emacsconf.org/2023/current/bbb-nabokov.html
IRC: https://chat.emacsconf.org/#/connect?join=emacsconf,emacsconf-gen or #emacsconf-gen on libera.chat network
Guidelines for conduct: https://emacsconf.org/conduct
See end of file for license (CC Attribution-ShareAlike 4.0 + GPLv3 or later)
----------------------------------------------------------------
Notes, discussions, links, feedback:

• It looks like the Zettelkasten slipbox for nabokov
• James Howell also like the idea using small slide to convey single idea to the reader. In emacs, we have `narrow` function. Yes! I use various narrow functions to present text with Emacs. (I use narrow a bunch when editing, it really helps focus on a chapter or scene)
  • The funny thing about narrow functions, I mean the first time I saw it in the manual, there is a warning to the new user.  That would be afraid of this kind of functionality, and you have to be careful, haha...
  • I saw that warning too and avoided narrow for a long time as a result!  But it's not really that bad...
    • Exactly, I use narrow a lot, you know, every time I'm working on any single type of writing or writing a code or writing a piece of manuscript. It's really helped me to narrow down my attention and to kind of release any other thoughts that is not directly connected to the current things I'm working on. And that really is an underestimated functionality for the Emacs.
• The most valuable thing that Org will bring to the writer is the structure, how we can navigate between different structures of thoughts.
• The idea is using tag to narrow down a single person's timeline in the whole context of stories. It's something very interesting.
• ewj.io/emacs

----------------------------------------------------------------
Questions and answers go here:

• Q: Does the index really matter here? I mean, his colleague is also using some A4 paper, and do you think that the index card is the most important thing here?
  • A:
    • portbablity win!
• Q:How do you export the second level headings (scenes in this example) without the heading itself, just the content? 
  • A:3 ways for this: ox-ignore (it was visually annoying), dumb awk script, pandoc filters in lua
    • I would say the org-transclusion works very well for this kind of demand.
• Q: Slightly offtopic: where can we see your novels?
  • A: there are on Amazon: two of them, and a book of short-stories
    • Links:https://www.amazon.com/World-Enough-Time-Edmund-Jorgensen/dp/0984749233
    • https://www.amazon.com/Other-Copenhagens-Stories-Edmund-Jorgensen-ebook/dp/B00O4OQCBE
• Q: Have you looked at the Denote Signature features. The hierarchical nature of luhman IDs and index cards work well with Denote Signatures
  • A:I haven't, but I will take a look!
  • https://protesilaos.com/emacs/denote#h:f9204f1f-fcee-49b1-8081-16a08a338099
  • The part that I like with signatures is they can be optional with your zettelkasten as another way to use it.
• Q: Do you have a workflow combining hand-written index cards and org mode?
  • A:
    • Maybe just take a picture and OCR for your small index cards, but at the end of the day you always have to go back to your main Org files.
      • Ooh, I have a workflow for using Google's OCR to grab the text from my sketches (esp. the ID) so that I can link to my sketches in Org with ID and completion - sachac
        • haha, nice to see different approach, I personally didn't do that because I still most of my work is on the computer so yeah in the future if i have lots of handwriting notes in my working I will reconsider Google solution
• Q:
  • A:

----------------------------------------------------------------
Next talks:

• Development: Editor Integrated REPL Driven Development for all languages https://pad.emacsconf.org/2023-eval
• General: Collaborative data processing and documenting using org-babel https://pad.emacsconf.org/2023-collab
• Development: REPLs in strange places: Lua, LaTeX, LPeg, LPegRex, TikZ https://pad.emacsconf.org/2023-repl

Questions/comments related to EmacsConf 2023 as a whole? https://pad.emacsconf.org/2023
----------------------------------------------------------------
This pad will be archived at https://emacsconf.org/2023/talks/nabokov after the conference.
Except where otherwise noted, the material on the EmacsConf pad are dual-licensed under the terms of the Creative Commons Attribution-ShareAlike 4.0 International Public License; and the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) an later version. Copies of these two licenses are included in the EmacsConf wiki repository, in the COPYING.GPL and COPYING.CC-BY-SA files (https://emacsconf.org/COPYING/)
By contributing to this pad, you agree to make your contributions available under the above licenses. You are also promising that you are the author of your changes, or that you copied them from a work in the public domain or a work released under a free license that is compatible with the above two licenses. DO NOT SUBMIT COPYRIGHTED WORK WITHOUT PERMISSION.