Re: [O] [PATCH 1/2] org-refile: escape slashes only in headline of refile target

2017-05-06 Thread Kyle Meyer
Sebastian Reuße writes: > I have a copyright assignment with FSF; the reason I’m not on the org > contributors page is that I haven’t submitted a patch before. Great, I'll add you to that page. -- Kyle

Re: [O] [PATCH 1/2] org-refile: escape slashes only in headline of refile target

2017-05-06 Thread Kyle Meyer
Sebastian Reuße writes: > Thank you, Kyle. I’ve incorporated your suggestions (after pulling the > git send-mail trigger early a few times). Thanks. Applied to the master branch. Could you send a patch that mentions the org-refile-use-outline-path change in ORG-NEWS? -- Kyle

Re: [O] [PATCH 1/2] org-refile: escape slashes only in headline of refile target

2017-05-05 Thread Sebastian Reuße
Kyle Meyer writes: > Based on the Org contributor page [*], it doesn't look like you've > signed papers with the FSF, so the commit message should label this as > a "TINYCHANGE". (I think this and the next patch would be small enough > to mark as tiny changes.) I have a copyright assignment wit

Re: [O] [PATCH 1/2] org-refile: escape slashes only in headline of refile target

2017-05-05 Thread Sebastian Reuße
Kyle Meyer writes: > Org's master branch currently supports Emacs >= 24.3, but string-join > was added in the 24.5 release. > I'm fine with the append -> cons conversion, but avoiding it would > make for a cleaner diff that's more focused on the main purpose of > this patch. Thank you, Kyle. I

[O] [PATCH 1/2] org-refile: Escape slashes only in headline of refile target

2017-05-05 Thread Sebastian Reuße
* org.el (org-refile-get-targets): Only escape slashes in headline part of refile target; leave any file-system path component (when enabled) unescaped. The reason to escape slashes in refile targets is to make it clear when a slash was part of a headline vs. part of the outline path. It makes se

[O] [PATCH 1/2] org-refile: Escape slashes only in headline of refile target

2017-05-05 Thread Sebastian Reuße
* org.el (org-refile-get-targets): Only escape slashes in headline part of refile target; leave any file-system path component (when enabled) unescaped. The reason to escape slashes in refile targets is to make it clear when a slash was part of a headline vs. part of the outline path. It makes se

[O] [PATCH 1/2] org-refile: Escape slashes only in headline of refile target

2017-05-05 Thread Sebastian Reuße
* org.el (org-refile-get-targets): Only escape slashes in headline part of refile target; leave any file-system path component (when enabled) unescaped. The reason to escape slashes in refile targets is to make it clear when a slash was part of a headline vs. part of the outline path. It makes se

Re: [O] [PATCH 1/2] org-refile: escape slashes only in headline of refile target

2017-05-05 Thread Kyle Meyer
Sebastian Reuße writes: > * org.el (org-refile-get-targets): only escape slashes in headline For style consistency, the first word following the colon should be capitalized. The same applies to the commit subject. > part of refile target; leave any file-system path component (when > enabled) u

[O] [PATCH 1/2] org-refile: escape slashes only in headline of refile target

2017-05-05 Thread Sebastian Reuße
* org.el (org-refile-get-targets): only escape slashes in headline part of refile target; leave any file-system path component (when enabled) unescaped. The reason to escape slashes in refile targets is to make it clear when a slash was part of a headline vs. part of the outline path. It makes se

[O] [PATCH 1/2] org-refile: escape slashes only in headline of refile target

2017-05-05 Thread Sebastian Reuße
* org.el (org-refile-get-targets): only escape slashes in headline part of refile target; leave any file-system path component (when enabled) unescaped. The reason to escape slashes in refile targets is to make it clear when a slash was part of a headline vs. part of the outline path. It makes se