nvim-orgmode / nvim-orgmode/orgmode

Some Vimmy Enhancements

Open
#245 2 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

non-core-feature
Dominant language
Lua
Stars
3.9k
Forks
190
Avg merge
2d 13h
Merged PRs (30d)
7

Description

Does this feature exist in Emacs orgmode core?

N/A

Orgmode link

No response

Feature value

I left out the regular questions in this issue since its not relevant to orgmode or emacs behavior. Rather its some behavior tweaks that could be made to make this outstanding plugin feel more integrated into vim.

  1. . command should remember the prompt value. (so if I run <leader>ot to edit the tags, and then I go to another headline and press . it should edit the tags the same way instead of running the edit tags command and bringing up the prompt of what I would like to change the tags to. If I wanted to change them to something other than my original edit, then I would run <leader>ot again.
  2. Org agenda/task lists should be treated as a normal buffer. So that if I press enter on an agenda item and it opens it in the same window, pressing <c-o> should bring me back to the agenda. Currently it does, but then the buffer is empty.
  3. User prompts, share same history (refile headline, filter tags/categories, etc...) all share the same history, which makes it harder to reuse previous values. For example, if I'm in the agenda and I have a complex filter active. Then I do a bunch of org editing, and reopen the agenda, when I type / and then scrollback through the history to restore my filter, I may have to scroll a bunch of items back which is not intuitive.

These are some ideas that I came across that would make orgmode a little more vimmy.

Again, thank you @kristijanhusak for the amazing work!


Aside, is there a lua way to open the agenda with a filter pre-applied?

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the dot command, agenda buffer navigation, and user-prompt history entry points. Check how each currently handles repeated edits, jump-back navigation, and stored values; done means all three behaviors work consistently without breaking existing Orgmode interactions.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua, vim
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.