nvim-orgmode / nvim-orgmode/orgmode

Support for org-refile-use-outline-path

Open
#645 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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?

Yes

Orgmode link

While the manual mentions the variable, I can't actually find manual documentation on its values. There are multiple website discussions such as stackexchange that provide examples of the options, though.

image
Feature value

No response

Additional context

Suppose I want to have an org file named work.org that looks like this:

* Project 1
** Tasks
* Project 2
** Tasks 

I can only refile today using a destination like work.org/Tasks, which will place under the first heading that matches. I'd like to have a singular file where I can file tasks into different headings without either

a. Making them top-level and distinct such as Project 1 Tasks and Project 2 Tasks
b. Breaking out into separate files such as project_1.org/Tasks and project_2.org/Tasks when refiling

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

Begin with the linked Org manual entry for org-refile-use-outline-path and the linked discussion to understand the supported destination forms. Then trace the orgmode refile handling for work.org/Tasks; done means duplicate headings such as Project 1/Tasks and Project 2/Tasks can be selected without renaming headings or splitting files.

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.