On Sat, May 6, 2017 at 2:30 AM Kaushal Modi wrote:
> +(setq body-str (replace-regexp-in-string "^[ \n\r]*\n" "\n"
> body-str)))
>
>
Just one correction to this regexp so that two or more consecutive empty
lines in the source block get retained:
(setq body-str (replace-regexp-in-string "^[ ]+
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
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
* 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
* 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
* 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
* 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
Hello,
I have this MWE:
#+TITLE: Org babel tangle and noweb
#+PROPERTY: header-args:shell :shebang "#!/usr/bin/env bash"
* Shell Script
#+BEGIN_SRC shell :noweb yes :tangle code.sh
exec emacs -Q "$@" \
--eval '(progn
<>
)' 2>/dev/null >
* 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
* 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
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 this will work han
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
* 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
Apologies for the resubmission; forgot to stage a hunk in one of the
commits.
Kind regards,
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
* 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 t
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
((org-at-item-p)
* 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
* 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
ind
* 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 b/contrib/lisp/ox-s5
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 writes:
>
> > I
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)
I get
origin or
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&D Institu
* 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(+),
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 we
25 matches
Mail list logo
