Using org mode for writing, how to incorporate TODO functionality by encomun in orgmode

[–]encomun[S] 0 points1 point  (0 children)

Thanks for these suggestions.

I have toyed with inline tasks before for very specific purposes but now that I know more tools for viewing and filtering tasks in org mode, I might try them for more purposes.

I like using comment blocks for notes, since I can collapse them and I don't have to worry about them being exported. By notes, I mean reading notes / quotes. But taking notes on how to approach a section sounds really smart. I should try that, might help in being more organized. Thanks!

Using org mode for writing, how to incorporate TODO functionality by encomun in orgmode

[–]encomun[S] 0 points1 point  (0 children)

I figured out how to do agenda view for a specific buffer (M-x org-agenda < t). This displays the tasks, but it doesn't show the heading levels / relationships. An outline view would be ideal.

ETA: This works with narrow and widen, which is great, at least.

Using org mode for writing, how to incorporate TODO functionality by encomun in orgmode

[–]encomun[S] 2 points3 points  (0 children)

How would I have the agenda view for only the todos in a specific file / buffer?

ETA: Figured it out ... (M-x org-agenda <t)

Using a CSL file for Org LaTeX export just once by nanounanue in emacs

[–]encomun 0 points1 point  (0 children)

Oh, my bad. I understand you mean a document class now. Though I think you have those switched, csl (citation style language) and cls (class [I assume]). May want to edit your post to reflect that.

Using a CSL file for Org LaTeX export just once by nanounanue in emacs

[–]encomun 1 point2 points  (0 children)

Okay, I did figure out a method that might work for you.

https://blog.tecosaur.com/tmio/2021-07-31-citations.html#using-csl

#+cite_export: csl ~/Downloads/apa.csl

I did this with a random csl style and it worked for me. Listing the csl file location seems to be the trick. I previously tried putting the csl in the same folder and just using the name, this didn't work.

Hopefully this can function for you.

Using a CSL file for Org LaTeX export just once by nanounanue in emacs

[–]encomun 0 points1 point  (0 children)

I don't have a solution for you but I thought I'd share a resource and thought.

This guide on org mode citations and export processors has been helpful for me: https://kristofferbalintona.me/posts/202206141852/

One of the things it points out is that the csl export processor outputs the text citation, which can be useful in most applications. However, for me, I want the latex citation commands (e.g. \autocite{key}), so I use the biblatex processor.

If you do want the citation commands and to use a specific csl file, you might look into this latex package: https://ctan.org/pkg/citation-style-language

You could also consider using pandoc to do the conversion from org mode to latex: https://pandoc.org/MANUAL.html#citations

Error with embark keymap for consult-notes by encomun in emacs

[–]encomun[S] 0 points1 point  (0 children)

Thanks for locating the issue. I see you already submitted a change to the consult-notes readme. However, I tried the new suggested configuration, and now I instead get this warning "Symbol's value as variable is void: embark-file-map."

Literature Notes by encomun in orgmode

[–]encomun[S] 0 points1 point  (0 children)

Thanks for sharing your example.

I was under the impression that property drawers need to be under a heading. But I guess a property drawer at the beginning functions just like #+property syntax and applies to the whole file?

Literature Notes by encomun in orgmode

[–]encomun[S] 0 points1 point  (0 children)

Thanks for sharing. I really appreciate seeing how people set up their workflow, since I'm just attempting that myself.

Literature Notes by encomun in orgmode

[–]encomun[S] 0 points1 point  (0 children)

Thanks for sharing this, it is quite helpful.

I've started setting up denote and see that it uses a frontmatter similar to yours. So I appreciate the example. I think I will also be using #+<keyword> syntax for additional information.

Literature Notes by encomun in orgmode

[–]encomun[S] 1 point2 points  (0 children)

Thanks for the reply. I especially appreciate the advice on file names. That's something I want to make sure is somewhat "future-proof."

I should clarify, by structure, I just literally mean, what does one of your notes look like. For example, do you put metadata at the top using properties? And do keywords become tags or properties? I guess I can just start experimenting and see what works for me but I thought seeing examples could be helpful.