Why All talks: https://emacsconf.o
rg/2023/talks/
Emacs turbo-charges my writing
https://emacsconf.org/2023/talks/writing - Jeremy Friesen - Track: General
Watch/participate: https://emacsconf.org/2023/watch/gen/
Q&A room: https://media.emacsconf.org/2023/current/bbb-writing.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:

• https://takeonrules.com (presenter's personal blog)
• When you put your thoughts on the physical world, it actually helps you to generate more. It's kind of releasing your mind and let your mind freely be free so from that kind of states you can create something new

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

• Q: Do you think the line number for writing document kind of distraction? Especially for notes.
  • A:I don't find it distracting; I've been coding for a long time and those fringes are partially invisible.  But help me orient.
    • or, what it brings to you, if we don't have that.
      • Given that I'm writing code, prose, documentation, etc, I prefer to have a common left fring…most of the time.
    • Okay. I use (avy-goto-line &optional ARG) for jumping
      • I bind C-j to jump to `avy-goto-char-timer`; My C-l is bound to `consult-goto-line`
• Q: How do you manage private and public data with your zettlekasten. One of my blockers on putting my zettlekasten on the web is I don't want everything in it to be public. expeccily fleeting notes
  • A: I explicitly export a single page at a time; this ensures the primary page is something I consider public.
  • Q: Do you have anything to prevent private links from getting accidentally being made publicaly accessible
    • The main guard is the "publish this page" function.  Under the hood, private notes are those that I don't specify a public URL.  I do this by way of the `#+ROAM_REFS:` keyword (technically there are a few other keywords I check as well; for bespoke historical reasons) on the document.  If it doesn't have that, then an internal link to that item will not export a public link.
• Q: Is there anything special you're using to go from Org to Hugo Markdown?  This looks like a really nice setup, and I'd like to give it a try!
  • A: https://github.com/jeremyf/dotemacs you'll be looking for jf-blogging.el (also jf-org-mode.el)
• Q: Another font question.   What font were you using in eww?
  • A: For fixed fonts I'm using "Iosevka Comfy Motion Fixed" and for variable "ETBembo"
• Q: What's the story behind the name "Take On Rules"?
  • A: The blog started as a game rules oriented blog; it was my time to interrogate rule systems.  But over time that drifted; and once I moved to Org-Mode for writing I settled on an everything and nothing blog.  My https://takeonrules.com/about/ has a bit more details on this
    •  "Anything and nothing." Makes sense. :-)
• Q:
  • A:

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

• Development: Improving compiler diagnostics with overlays https://pad.emacsconf.org/2023-overlay
• General: Why Nabokov would use Org-Mode if he were writing today https://pad.emacsconf.org/2023-nabokov
• Development: Editor Integrated REPL Driven Development for all languages https://pad.emacsconf.org/2023-eval

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/writing 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.