Re: [O] [BUG] R src blocks untabify literal constant TABs

On Tue, 22 Sep 2015, Charles C. Berry wrote: Just to tie this up, this is an issue with `org-src-preserve-indentation', see (info "(org) Editing source code") for the best documentation. I found the "replace sequences of spaces with tab characters" for nil values confusing. The oppos

Re: [O] a patch to org.el of git version

Hi Nicolas, Thank you for the update. But it looks like `org-show-children' is a replacement of `show-children'. Actually the key bind for `show-children' (C-c TAB in my case) is remapped to `org-show-children' as below. org.el:5733: > (define-key org-mode-map [remap show-children] 'org-show-chil

Re: [O] [BUG] R src blocks untabify literal constant TABs

Sorry, I just walked in the door and didn't put on my thinking cap... On Tue, 22 Sep 2015, Charles C. Berry wrote: On Tue, 22 Sep 2015, Grant Rettke wrote: On Tue, Sep 22, 2015 at 5:04 PM, Charles C. Berry wrote: ECM follows: I just ran it and got 10 chars like you expected: I got 10,

Re: [O] [BUG] R src blocks untabify literal constant TABs

On Tue, 22 Sep 2015, Grant Rettke wrote: On Tue, Sep 22, 2015 at 5:04 PM, Charles C. Berry wrote: ECM follows: I just ran it and got 10 chars like you expected: #+BEGIN_src R nchar("AB") #+END_src #+RESULTS: : 10 10 is not what I expected. Should be 3 characters. Be sure to run

Re: [O] [BUG] R src blocks untabify literal constant TABs

On Tue, Sep 22, 2015 at 5:04 PM, Charles C. Berry wrote: > > ECM follows: I just ran it and got 10 chars like you expected: #+BEGIN_src R nchar("AB") #+END_src #+RESULTS: : 10 --- Emacs Version: src_emacs-lisp{emacs-version} {{{results("24.4.1")}}} Org Version from Git: src_emacs-lisp

Re: [O] [PATCH v3] fix SETUPFILE pathname expansion with subdirectories

Any other feedback on this patch? Thanks, Richard On 2015-09-20 01:28, Richard Hansen wrote: > * lisp/org-macro.el (org-macro--collect-macros): cd to the directory > containing the SETUPFILE before recursing so that relative pathnames > in the SETUPFILE are expanded properly. > > * lisp/org.el

[O] [BUG] R src blocks untabify literal constant TABs

ECM follows: Make a string of three characters :'A', '', and 'B': #+BEGIN_SRC R res <- paste0("A","\t","B") nchar(res) #+END_SRC #+RESULTS: : 3 Make a src block in which the string appears literally, then execute the resulting src block: #+BEGIN_SRC R :results raw :wrap "src R" res <- p

Re: [O] inter-word space in org -> latex

Marcin Borkowski writes: > ;; Convert single spaces after periods etc. to "\ " when exporting to LaTeX > > (defun my-latex-filter-nonfrenchspacing (text backend info) > "Convert single spaces after dots to \"\ \"." > (when (and (org-export-derived-backend-p backend 'latex) >senten

Re: [O] inter-word space in org -> latex

On 2015-09-22, at 22:17, Marcin Borkowski wrote: > On 2015-09-14, at 16:42, Dan Griswold wrote: > >> How should I mark in org mode that I want a space following a period >> concluding an abbreviation to be seen by LaTeX as an interword space? > > #+LATEX_HEADER: \frenchspacing > > and never wor

[O] standardizing slideshow outpout, a la pandoc

Hi everyone, I'm co-teaching a class this term and my co-instructor is a markdown user, so I am getting to know a little bit about pandoc. One feature I really love is the unified slideshow export: http://pandoc.org/demo/example19/Producing-slide-shows-with-Pandoc.html All the export filters us

Re: [O] inter-word space in org -> latex

On 2015-09-14, at 16:42, Dan Griswold wrote: > Dear org-mode community, > > In LaTeX, a space after a period is treated as an inter-sentence space, > which is wider than an inter-word space. This can lead to overly wide > spacing after a period that ends an abbreviation rather than a space. The

Re: [O] Bug: The headers' anchors from custom ids should be at the beginning, and not at the end, of these headers [8.3.1 (8.3.1-129-ga7c8d2-elpa @ /home/bitouze/.emacs.d/elpa/org-20150921/)]

Le 22/09/15 à 22h01, Nicolas Goaziou a écrit : > Denis Bitouzé writes: > >> I don't see your point. >> >> 1. What is less readable: the anchor or, if the anchor is at its >>beginning, the heading ? > > The latter. > >> 2. At what level is it less readable: .org or .md or .html, etc.? > > .

Re: [O] Bug: The headers' anchors from custom ids should be at the beginning, and not at the end, of these headers [8.3.1 (8.3.1-129-ga7c8d2-elpa @ /home/bitouze/.emacs.d/elpa/org-20150921/)]

Denis Bitouzé writes: > I don't see your point. > > 1. What is less readable: the anchor or, if the anchor is at its >beginning, the heading ? The latter. > 2. At what level is it less readable: .org or .md or .html, etc.? .md Regards,

Re: [O] Bug: The headers' anchors from custom ids should be at the beginning, and not at the end, of these headers [8.3.1 (8.3.1-129-ga7c8d2-elpa @ /home/bitouze/.emacs.d/elpa/org-20150921/)]

Le 22/09/15 à 21h39, Nicolas Goaziou a écrit : > Hello, Hello, >> As you can see, the anchor in the .md file is at the end of the header and, >> in >> case this header contains long text, clicking on a link to this anchor would >> lead us to the end, eventually not at the first line, of this h

Re: [O] Bug: The headers' anchors from custom ids should be at the beginning, and not at the end, of these headers [8.3.1 (8.3.1-129-ga7c8d2-elpa @ /home/bitouze/.emacs.d/elpa/org-20150921/)]

Hello, dbito...@wanadoo.fr (Denis Bitouzé) writes: > The following org file: > > #+begin_src org > * Heading with custom id > :PROPERTIES: > :CUSTOM_ID: custom-id-heading > :END: > > * Heading bis with custom id and very very very very very very very very very > very very very very very very ver

Re: [O] a patch to org.el of git version

Hello, Tokuya Kameshima writes: > This is a tiny patch to `org-show-children' which shoule be an > interactive function but not. Thank you. However, `org-show-children' is not meant to be interactive, because its functionality is incomplete within Org. It also needs `org-show-entry'. In any ca

Re: [O] funny bug if shifting scheduled items

Hello, Detlef Steuer writes: > Met this funny bug in the morning. > > (orgmode version: git from today) > > Given the file > > * Testappointment > SCHEDULED: <2015-09-21 Mo 23:00-23:55> > > If I now shift the *starttime* using shift-uparrow > the *endtime* goes to 24:00, 24:05 etc. > > If I ke

Re: [O] Show presence of zero width spaces using overlay

Hi, (this is my first post on this list, to a message that I don't have in my inbox, so I don't know if it will thread correctly) Kaushal Modi writes: > The suggestion to use zero width spaces to sort of "escape" stuff in org > mode has come up many times. I have started using it a lot and sugg

Re: [O] Avoiding open buffers when clocking in

Thanks Kyle, I did not knew this one. I was manually using this function (defun only-current-buffer () (interactive) (mapc 'kill-buffer (cdr (buffer-list (current-buffer) to kill all buffers after clocking in, but you

Re: [O] [PATCH] ox-latex: Add scrartcl LaTeX class

Eric S Fraga writes: >> Some people might hate the margin choices to the extend that they'd >> need geometry to make KOMA-script bearable. Now we have two new >> dependencies... > > yes. The real question is not the dependencies but what would we like > new users to when they try exporting a do

Re: [O] Avoiding open buffers when clocking in

Actually, the solution is obvious... I should think before posting. (defun my-org-clock-in () "Clock in and close all unmodified buffers." (interactive) (org-clock-in) (mapc 'kill-buffer (cdr (buffer-list (current-buffer ) Julian M. Burgos writes: > Thanks Kyle, I did not knew this

Re: [O] [PATCH] ox-latex: Add scrartcl LaTeX class

On Tuesday, 22 Sep 2015 at 13:21, Rasmus wrote: > Key word being 'arguably'. indeed! > Some people might hate the margin choices to the extend that they'd > need geometry to make KOMA-script bearable. Now we have two new > dependencies... yes. The real question is not the dependencies but what

Re: [O] PROPERTIES attached to results blocks - Was: Set or update timestamp after evaluation of code block?

On Tue, 22 Sep 2015, Rainer M Krug wrote: Grant Rettke writes: Might be nice to have properties attached to result blocks. That is a nice idea. True. These could be used for in the long run many purposes, like formating for export. If the formating would be defined in the properties of the

[O] Avoiding open buffers when clocking in

Dear list, When clocking in at some particular task, org-mode opens all my agenda files (I assume to check if there are dangling clocks). I have many agenda files, and I rather avoid opening tons of new buffers. Is there any way to make org-mode not check for dangling clocks in other agenda file

Re: [O] Avoiding open buffers when clocking in

"Julian M. Burgos" writes: > When clocking in at some particular task, org-mode opens all my agenda > files (I assume to check if there are dangling clocks). I have many > agenda files, and I rather avoid opening tons of new buffers. Is there any > way to make org-mode not check for dangling cl

Re: [O] [PATCH] ox-latex: Add scrartcl LaTeX class

On Tue, Sep 22, 2015 at 2:20 AM, Eric S Fraga wrote: > On Monday, 21 Sep 2015 at 21:46, Nicolas Goaziou wrote: > Only that the koma-script classes are arguably better defaults than the > actual defaults... Personally, I cannot see any reason to use the > standard article/report/letter classes!

Re: [O] A book produced using Org

Suvayu Ali writes: > After this patch from Rasmus: > > > > it's as simple as adding a > > #+latex_program: xelatex It's not pushed yet, though. I have to add documentation before this can happen. I will hopefully do so one of these nights... Ra

Re: [O] [PATCH] ox-latex: Add scrartcl LaTeX class

Eric S Fraga writes: >> Thank you. But can't users needing a non-default class customize their >> own `org-latex-classes? Or is there an entitling reason to offer it out >> of the box? > > Only that the koma-script classes are arguably better defaults than the > actual defaults... Personally, I

Re: [O] Set or update timestamp after evaluation of code block?

Rainer M Krug writes: > John Kitchin writes: > >> so picky ;) > > Jup - aren't all org users like that? > >> Maybe something like this will put that stamp in a comment >> that won't export. >> >> #+BEGIN_SRC emacs-lisp >> (defun j-add-ts () >> (save-excursion >> (re-search-forward "#\\+END

Re: [O] Agenda Tag filtering - has the behaviour changed?

On Thu, Sep 17, 2015 at 12:16:44PM -0400, Bernt Hansen wrote: > Nicolas Goaziou writes: > > > Hello, > > > > Robert Klein writes: > > > >> Looking through the commit messages this may come from commit > >> 6c6ae990c10dbe7f96b24fccf840fe9f6d81a3b8 > > > > Indeed. It seems related to this NEWS ent

[O] PROPERTIES attached to results blocks - Was: Set or update timestamp after evaluation of code block?

Grant Rettke writes: > Might be nice to have properties attached to result blocks. That is a nice > idea. True. These could be used for in the long run many purposes, like formating for export. If the formating would be defined in the properties of the result block, it would make it easy to hav

Re: [O] Set or update timestamp after evaluation of code block?

John Kitchin writes: > so picky ;) Jup - aren't all org users like that? > Maybe something like this will put that stamp in a comment > that won't export. > > #+BEGIN_SRC emacs-lisp > (defun j-add-ts () > (save-excursion > (re-search-forward "#\\+END_SRC") > (forward-line) > (begi

Re: [O] [PATCH] ox-latex: Add scrartcl LaTeX class

On Monday, 21 Sep 2015 at 21:46, Nicolas Goaziou wrote: [...] > Thank you. But can't users needing a non-default class customize their > own `org-latex-classes? Or is there an entitling reason to offer it out > of the box? Only that the koma-script classes are arguably better defaults than the a