[O] [PATCH 2/2] org-refile: Optionally prefix refile targets with buffer name

* org.el (org-refile-get-targets): Add case to optionally prefix refile targets with the buffer name. (org-refile-use-outline-path): Add new option setting and document. Having an option to use the buffer name as a prefix is convenient, since this will work hand in hand with uniquify to only show

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

* 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

Re: [O] [PATCH 2/2] org-refile: optionally prefix refile targets with buffer name

Sebastian Reuße writes: > * org.el (org-refile-get-targets): Add case to optionally prefix > refile targets with the buffer name. > (org-refile-use-outline-path): Add new option setting and document. > > Having an option to use the buffer name as a prefix is convenient, > since

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

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

[O] [PATCH 2/2] org-refile: optionally prefix refile targets with buffer name

* org.el (org-refile-get-targets): Add case to optionally prefix refile targets with the buffer name. (org-refile-use-outline-path): Add new option setting and document. Having an option to use the buffer name as a prefix is convenient, since this will work hand in hand with uniquify to only show

Re: [O] [PATCH 2/2] org-refile: optionally prefix refile targets with buffer name

Apologies for the resubmission; forgot to stage a hunk in one of the commits. Kind regards, Sebastian Reuße

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

* 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

[O] [PATCH 2/2] org-refile: optionally prefix refile targets with buffer name

* org.el (org-refile-get-targets): Add case to optionally prefix refile targets with the buffer name. (org-refile-use-outline-path): Document new option. Having an option to use the buffer name as a prefix is convenient, since this will work hand in hand with uniquify to only show those parts of

[O] About org-sort -> org-sort-list with custom sort function

Hi All, I think there is a bug in org-sort or org-sort-list function. If you call org-sort (C-c ^) on list items, this function will call org-sort-list. However, org-sort calls org-sort-list with only one argument, i.e., the with-case (see the code below) #+BEGIN_SRC emacs-lisp

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

* 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

[O] [PATCH] ox-s5: Update to work with refactored html backedn

* contrib/lisp/ox-s5.el (org-s5-template): Adapt to changes introduced by c9ca0b6d in the way :html-divs/org-html-divs are passed to ox-html. --- contrib/lisp/ox-s5.el | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/contrib/lisp/ox-s5.el b/contrib/lisp/ox-s5.el

[O] [PATCH v1.1] ox-s5: update to work with refactored html backedn

* contrib/lisp/ox-s5.el: adapt to changes introduced by c9ca0b6d in the way :html-divs/org-html-divs are passed to ox-html --- Now it should be ready. contrib/lisp/ox-s5.el | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/contrib/lisp/ox-s5.el

Re: [O] Push rights for repository

Thank you Bastien, indeed, it is fixed now - apparently I had cloned with $ git clone git://orgmode.org/org-mode.git instead of $ git clone orgm...@orgmode.org:org-mode.git - Carsten On Fri, May 5, 2017 at 11:19 AM, Bastien wrote: > Hi Carsten, > > Carsten Dominik

Re: [O] Push rights for repository

Hi Carsten, Carsten Dominik writes: > I seem to have lost my push privilege to the git repository.  Does > anyone know why that might be the case? > > $ git remote -v shows > >     origin git://orgmode.org/org-mode.git (fetch) >     origin git://orgmode.org/org-mode.git (push)

Re: [O] [PATCH] ox-s5: update to work with refactored html backedn

It was <2017-05-04 czw 17:39>, when Łukasz Stelmach wrote: > * contrib/lisp/ox-s5.el: adapt to changes introduced by c9ca0b6d in the > way :html-divs/org-html-divs are passed to ox-html Please don't apply this patch. I'll send it from another e-mail account. -- Łukasz Stelmach Samsung R

[O] [PATCH] ox-s5: update to work with refactored html backedn

* contrib/lisp/ox-s5.el: adapt to changes introduced by c9ca0b6d in the way :html-divs/org-html-divs are passed to ox-html --- It appears that for some reason the patch didn't make it to the list the first time I sent it. contrib/lisp/ox-s5.el | 12 ++-- 1 file changed, 6 insertions(+),

[O] Push rights for repository

Hi, I seem to have lost my push privilege to the git repository. Does anyone know why that might be the case? $ git remote -v shows origin git://orgmode.org/org-mode.git (fetch) origin git://orgmode.org/org-mode.git (push) and I believe that my ssh settings are OK - I did push a few