Re: [O] Org-agenda-leaders

[Uwe Jochum]

Dear Matt,

thanks! I'll try a fresh install of Emacs and orgmode this weekend and see 
what will happen. My Emacs is 24.3.1 on a Linux Mint machine.


Besten Dank,

Uwe Jochum

Matt Lundin schrieb am 2015-10-21 um 17:03 Uhr:


Uwe Jochum  writes:


Hi all,

when I switched to the orgmode 8.3.2 quite a lot of entries in my
weekly agenda disappeared. This seems to be related to the fact that I
renamed the agenda leaders like so:

 '(org-agenda-deadline-leaders (quote ("FRIST:  " "In %3d d.: ")))

 '(org-agenda-scheduled-leaders (quote ("TERMIN: " "TERMIN.%2dx: ")))



I cannot replicate this. The leaders above (FRIST, TERMIN) appear
properly on my machine.

Org-mode version 8.3.2 (release_8.3.2-204-g30ec97)
Emacs: "25.0.50.4"

Matt

Re: [O] Bug: LaTeX export: internal target + \autoref{} broken [8.3.2 (8.3.2-elpaplus @ /home/myq/.emacs.d/elpa/org-plus-contrib-20150929/)]

[Rasmus]

☕◦m̰̱̐y̿q̟̽  writes:


> Given the following Org document:
>
> ,
> | #+MACRO: refp \autoref{$1}, \autopageref{$1}
> |
> |
> | * section
> |
> | Please see the results in {{{refp(sec:info)}}}.
> |
> | * info<>
> |
> | The results are here.
> `
>
> When exporting to LaTex, I expect `autoref' and `autopageref' to
> correctly refer to the target `sec:info'. However, recent versions of
> Org do not do that. I now get the following when exporting to LaTeX:
>
> ,
> | % Created 2015-10-21 Wed 03:25
> | \documentclass[11pt]{article}
> | % [...]
> | \begin{document}
> | % [...]
> | \section{section}
> | \label{sec:orgheadline1}
> |
> | Please see the results in \autoref{sec:info}, \autopageref{sec:info}.
> |
> | \section{info\label{orgtarget1}}
> | \label{sec:orgheadline2}
> |
> | The results are here.
> | \end{document}
> `
>
> When compiled, the following warning is issued:
>
> ,
> | Latex failed to resolve 2 reference(s)
> `
>
>
> This did not occur in Org Mode 8.3beta.

Can you try (setq org-latex-prefer-user-labels t).

This works as expected:

 #+MACRO: refp \autoref{$1}, \autopageref{$1}

 * section

 Please see the results in {{{refp(sec:info)}}}.

 * info
 :PROPERTIES:
 :CUSTOM_ID: sec:info
 :END:

 The results are here.

Hope it helps,
Rasmus

-- 
Sådan en god dansk lagereddike kan man slet ikke bruge mere

Re: [O] [Not a] Bug : LaTeX export: internal target + \autoref{}broken [8.3.2 (8.3.2-elpaplus /home/myq/.emacs.d/elpa/org-plus-contrib-20150929/)]

[☕◦m̰̱̐y̿q̟̽]

Andreas Leha  med.uni-goettingen.de> and Rasmus  gmx.us> write:

> ☕◦m̰̱̐y̿q̟̽  gmail.com> writes:
> >
> > Given the following Org document:
> >
> > ,
> > | #+MACRO: refp \autoref{$1}, \autopageref{$1}
> > |
> > |
> > | * section
> > |
> > | Please see the results in {{{refp(sec:info)}}}.
> > |
> > | * info<>
> > |
> > | The results are here.
> > `
[...]
> > ,
> > | Latex failed to resolve 2 reference(s)
> > `
> >
> >
> > This did not occur in Org Mode 8.3beta.
> >
> 
> Please see `org-latex-prefer-user-labels'.

Andreas & Rasmus,

Thank you.

That new variable was the issue. Strangely, the documentation notes that it 
was introduced in Emacs 25.1 but I'm running 24.5.1.

Now that I know what variable to look for, I can see that other people have 
had the same problem.

Please ignore my bug report.

Myq

Re: [O] ox-html HOWTO? exporting #+RESULTS inside div

[Cook, Malcolm]

Charles, 

Excellent - that is precisely what I needed.

Additionally, I can avoid having to include the :wrap keyword on every header 
by specifying a single  buffer-wide  header arguments, such as

#+PROPERTY: header-args :wrap org-results-container

Thanks,

~ malcolm_c...@stowers.org


From: Charles C. Berry 
Sent: Wednesday, October 21, 2015 9:18 PM
To: Cook, Malcolm
Cc: emacs-orgmode@gnu.org
Subject: Re: ox-html HOWTO? exporting #+RESULTS inside div

On Wed, 21 Oct 2015, Cook, Malcolm wrote:

> Hi,
>
> I would like to contrive for the contents of results blocks to be
> embedded in a new div with a common class of org-results-container.

Try this:

--8<---cut here---start->8---
#+BEGIN_SRC shell :exports both :wrap org-results-container
echo "org results here"
#+END_SRC
--8<---cut here---end--->8---

which html export renders as

--8<---cut here---start->8---


org results here



--8<---cut here---end--->8---

You can add a special-block filter if the  ...  is unwanted.

HTH,

Chuck

Re: [O] Bug: `org-timestamp-format' does not return correct time [8.2.10 (8.2.10-41-g42228a-elpa @ /home/gk/.emacs.d/packages/org-20150601/)]

[Kyle Meyer]

Göktuğ Kayaalp  writes:

> The function `org-timestamp-format' returns bad values:
>
> (org-timestamp-format "<2015-10-07 Wed>" "%d %B %Y")
> "30 November -001"
> (org-timestamp-format "[2015-10-07 Wed]" "%d %B %Y")
> "30 November -001"
> (org-timestamp-format "[2015-10-07]" "%d %B %Y")
> "30 November -001"
> (org-timestamp-format "<2015-10-07>" "%d %B %Y")
> "30 November -001"
> (org-timestamp-format "2015-10-07" "%d %B %Y")
> "30 November -001"
> (org-timestamp-format (current-time) "%d %B %Y")
> "30 November -001"
> (org-timestamp-format (org-parse-time-string "[2015-10-07 Wed]")
>   "%d %B %Y")
> "30 November -001"

I think this is because org-timestamp-format works with timestamp
objects, as returned by org-element-context, rather than strings.

-- 
Kyle

Re: [O] Rescheduling timestamps on a headline (not the next line)

[Matt Lundin]

Michael Hoffman  writes:

> I am using org-mode 8.2.10. I often like to keep SCHEDULED and
> DEADLINE timestamps on the headline so they are more compact and show
> up even when I have collapsed that tree. Unfortunately, in this case,
> (org-schedule) and (org-deadline) add a new timestamp on the second
> line instead of replacing the previous schedule.

Org-syntax requires planning info (SCHEDULED, DEADLINE) to be on its own
line. Anything can be arbitrarily entered into an org file, but only
certain syntax will work properly.

See http://orgmode.org/worg/dev/org-syntax.html

Best,
Matt

Re: [O] ox-html HOWTO? exporting #+RESULTS inside div

[Charles C. Berry]

On Wed, 21 Oct 2015, Cook, Malcolm wrote:


Hi,

I would like to contrive for the contents of results blocks to be 
embedded in a new div with a common class of org-results-container.


Try this:

--8<---cut here---start->8---
#+BEGIN_SRC shell :exports both :wrap org-results-container
echo "org results here"
#+END_SRC
--8<---cut here---end--->8---

which html export renders as

--8<---cut here---start->8---


org results here



--8<---cut here---end--->8---

You can add a special-block filter if the  ...  is unwanted.

HTH,

Chuck

Re: [O] Bizarre C-c ' error

[John Kitchin]

I think that is normal. The comma is some way that org escapes the * so
it cannot be mistaken for a headline. The comma should have no effect on
running the code with C-c C-c, and it should go away when you run C-c ' in the
src-block, and reappear when you exit that. If you get rid of the
leading *, the comma will disappear.

Is there an actual problem running the code?

Lawrence Bottorff writes:

> I found this bizarre thing while doing some babel coding. I start by
> putting this template together
>
> #+name: leibniz_3
> #+begin_src lisp :session :exports code :results silent
>
> #+end_src
>
> Then from this page
>  I copy this code
> (some 40 lines down)
>
> . . .
>   (push (make-rule :goal (first r)
>:pattern (second r)
>:action (third r)
>:name (fourth r))
> *rules*) )
>
> into a C-c ' buffer. But when I return to my org buffer (with an additional
> C-c '), it has done this:
>
> #+name: leibtest
> #+begin_src lisp :session :exports code :results silent
>   (push (make-rule :goal (first r)
>:pattern (second r)
>:action (third r)
>:name (fourth r))
> ,*rules*) )
> #+end_src
>
> Can you spot the difference? Subtle bug as it is, the code now has a comma
> thrown in on the last line. At first I thought this was some copying crud
> -- for example, if I simply highlight my code directly off this email (in
> Chrome/gmail) and try to XWinows-paste (middle wheel mouse click) it in, it
> throws in weird white-space crud -- but no, this comma add thing is only
> from doing a C-c ' round trip! And no, it's not an issue of how I put in
> the code: copy or type -- into the original org buffer or into the C-c '
> buffer. Again, just a C-c ' round trip throws in this comma. Odd
> coincidence, but this might have been legitimate CL code, except the list
> needs a backquote too. This has been a hair-pulling, all-time-top-ten bug,
> to be sure. And diff shows only this problem on the whole LEIBNIZ.CL file.
> Any ideas what's causing this?
>
> Lb

--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu

Re: [O] preparing a R course in org for slides..can i link back to org document?

[John Kitchin]

I use org-show (https://github.com/jkitchin/jmax/tree/master/org) which
is similar to these other solutions, but runs in emacs in a slide show
mode. It is an adaptation of some of Sacha's code. You can see it in
action here: https://www.youtube.com/watch?v=JZ8RK-R9O_g




Ista Zahn writes:

> On Mon, Oct 19, 2015 at 7:29 AM, Eric S Fraga  wrote:
>> On Monday, 19 Oct 2015 at 11:05, Xebar Saram wrote:
>>> Also if people are using other alternative to org-reveal that can do that i
>>> also wouldnt mind to try it out (a long as its as simple as org-revel :-))
>>
>> You might want to try org-treeslide [1].
>
> I believe the canonical repository is https://github.com/takaxp/org-tree-slide
>
>  List of alternatives can be
>> found on Worg [2].
>>
>> I'm suggesting org-treeslide because it runs within Emacs so you have
>> the full power of Emacs at hand.  It should be easy to use babel in the
>> presentation although I've never tried.  I'm a beamer person (with
>> org-reveal as a useful quick'n'dirty backup).
>>
>> HTH,
>> eric
>>
>> Footnotes:
>> [1]  https://github.com/avdi/org-tree-slide
>>
>> [2]  http://orgmode.org/worg/org-tutorials/non-beamer-presentations.html
>>
>> --
>> : Eric S Fraga (0xFFFCF67D), Emacs 24.5.1, Org release_8.3beta-1229-ge900eb
>>

--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu

Re: [O] preparing a R course in org for slides..can i link back to org document?

[Ista Zahn]

On Mon, Oct 19, 2015 at 7:29 AM, Eric S Fraga  wrote:
> On Monday, 19 Oct 2015 at 11:05, Xebar Saram wrote:
>> Also if people are using other alternative to org-reveal that can do that i
>> also wouldnt mind to try it out (a long as its as simple as org-revel :-))
>
> You might want to try org-treeslide [1].

I believe the canonical repository is https://github.com/takaxp/org-tree-slide

 List of alternatives can be
> found on Worg [2].
>
> I'm suggesting org-treeslide because it runs within Emacs so you have
> the full power of Emacs at hand.  It should be easy to use babel in the
> presentation although I've never tried.  I'm a beamer person (with
> org-reveal as a useful quick'n'dirty backup).
>
> HTH,
> eric
>
> Footnotes:
> [1]  https://github.com/avdi/org-tree-slide
>
> [2]  http://orgmode.org/worg/org-tutorials/non-beamer-presentations.html
>
> --
> : Eric S Fraga (0xFFFCF67D), Emacs 24.5.1, Org release_8.3beta-1229-ge900eb
>

[O] Bizarre C-c ' error

[Lawrence Bottorff]

I found this bizarre thing while doing some babel coding. I start by
putting this template together

#+name: leibniz_3
#+begin_src lisp :session :exports code :results silent

#+end_src

Then from this page
 I copy this code
(some 40 lines down)

. . .
  (push (make-rule :goal (first r)
   :pattern (second r)
   :action (third r)
   :name (fourth r))
*rules*) )

into a C-c ' buffer. But when I return to my org buffer (with an additional
C-c '), it has done this:

#+name: leibtest
#+begin_src lisp :session :exports code :results silent
  (push (make-rule :goal (first r)
   :pattern (second r)
   :action (third r)
   :name (fourth r))
,*rules*) )
#+end_src

Can you spot the difference? Subtle bug as it is, the code now has a comma
thrown in on the last line. At first I thought this was some copying crud
-- for example, if I simply highlight my code directly off this email (in
Chrome/gmail) and try to XWinows-paste (middle wheel mouse click) it in, it
throws in weird white-space crud -- but no, this comma add thing is only
from doing a C-c ' round trip! And no, it's not an issue of how I put in
the code: copy or type -- into the original org buffer or into the C-c '
buffer. Again, just a C-c ' round trip throws in this comma. Odd
coincidence, but this might have been legitimate CL code, except the list
needs a backquote too. This has been a hair-pulling, all-time-top-ten bug,
to be sure. And diff shows only this problem on the whole LEIBNIZ.CL file.
Any ideas what's causing this?

Lb

[O] ox-html HOWTO? exporting #+RESULTS inside div

[Cook, Malcolm]

Hi,

I would like to contrive for the contents of results blocks to be embedded in a 
new div with a common class of org-results-container.

Can this be accomplished through configuring ox-html somehow?  Or must I 
contrive to modify ox-html.el source? Or is this "Just A Bad Idea" (tm).

My use case is to be able to be able to hide all (or selected) results blocks 
using javascript in service of an html presentation used as a tutorial where 
RESULTS are revealed when clicking on, say, the previous source code block.

Thanks,

Malcolm Cook

Re: [O] order in agenda

[Andreas Leha]

Hi Nick,

Nick Dokos  writes:
> Andreas Leha  writes:
>
>> I am aware, that overlapping events cannot be displayed really well in
>> the (linear) agenda view.  But if I have two events starting at the same
>> (day and) time, I'd prefer the one with the later end time to appear
>> always below the other one.  Is that already achievable?
>>
>> Here is an excerpt of my current agenda for next week showing
>> sub-optimal (IMO) ordering:
>> ,
>> |   work: 16:00-18:00 Meeting with XXX :work::ATTACH:
>> |   work: 16:00-16:45 Event 2 :work::
>> `
>>
>
> C-h v org-agenda-sorting-strategy RET
>
> Maybe you can do something with user-defined-{up,down}?
>

Thanks for the pointer.  Indeed, user-defined-{up,down} seem to be the
way to go.  I'll look into that.

Thanks,
Andreas

Re: [O] Org-agenda-leaders

[Matt Lundin]

Uwe Jochum  writes:

> Hi all,
>
> when I switched to the orgmode 8.3.2 quite a lot of entries in my
> weekly agenda disappeared. This seems to be related to the fact that I
> renamed the agenda leaders like so:
>
>  '(org-agenda-deadline-leaders (quote ("FRIST:  " "In %3d d.: ")))
>
>  '(org-agenda-scheduled-leaders (quote ("TERMIN: " "TERMIN.%2dx: ")))
>

I cannot replicate this. The leaders above (FRIST, TERMIN) appear
properly on my machine.

Org-mode version 8.3.2 (release_8.3.2-204-g30ec97)
Emacs: "25.0.50.4"

Matt

Re: [O] order in agenda

[Nick Dokos]

Andreas Leha  writes:

> I am aware, that overlapping events cannot be displayed really well in
> the (linear) agenda view.  But if I have two events starting at the same
> (day and) time, I'd prefer the one with the later end time to appear
> always below the other one.  Is that already achievable?
>
> Here is an excerpt of my current agenda for next week showing
> sub-optimal (IMO) ordering:
> ,
> |   work: 16:00-18:00 Meeting with XXX :work::ATTACH:
> |   work: 16:00-16:45 Event 2 :work::
> `
>

C-h v org-agenda-sorting-strategy RET

Maybe you can do something with user-defined-{up,down}?

--
Nick

Re: [O] preparing a R course in org for slides..can i link back to org document?

[Matt Lundin]

Xebar Saram  writes:
>
> I am building an introduction to R course using org (and now
> org-reveal!). in some slide i show code blocks and would like to show
> the students the actual run of the code.

> I was wondering if anyone knew if there is a way to press a link in my
> reveal slide show that would take me to the corresponding org header
> where i could actually run the code in R+ESS.

I don't know anything about org-reveal (since I write my reveal.js
slides in html). But you could possibly get something working with
org-protocol. Or you could perhaps hack an emacs web server (elnode,
Eric Schulte's web server, etc.) to respond to links such as
localhost:port/do-something-in-emacs.

Probably the simplest solution is to have the org buffers queued up in
Emacs and to switch to them with ye olde "Alt Tab" (or whatever key
combination your window manager uses).

Best,
Matt

Re: [O] multi letter agenda commands

[Matt Lundin]

Subhan Michael Tindall  writes:

> It's already built in to custom agendas. See
> http://pages.sachachua.com/.emacs.d/Sacha.html#unnumbered-80 for
> excellent agenda examples. Sacha is a great resource for most things
> org

And there's also the manual. ;)

"The initial string in each entry defines the keys you have to press
after the dispatcher command C-c a in order to access the command.
Usually this will be just a single character, but if you have many
similar commands, you can also define two-letter combinations where the
first character is the same in several combinations and serves as a
prefix key." 

http://orgmode.org/manual/Storing-searches.html

Matt

[O] order in agenda

[Andreas Leha]

Hi all,

I am aware, that overlapping events cannot be displayed really well in
the (linear) agenda view.  But if I have two events starting at the same
(day and) time, I'd prefer the one with the later end time to appear
always below the other one.  Is that already achievable?

Here is an excerpt of my current agenda for next week showing
sub-optimal (IMO) ordering:
,
|   work: 16:00-18:00 Meeting with XXX :work::ATTACH:
|   work: 16:00-16:45 Event 2 :work::
`

Regards,
Andreas

Re: [O] Bug: LaTeX export: internal target + \autoref{} broken [8.3.2 (8.3.2-elpaplus @ /home/myq/.emacs.d/elpa/org-plus-contrib-20150929/)]

[Andreas Leha]

Hi ☕◦m̰̱̐y̿q̟̽,


☕◦m̰̱̐y̿q̟̽  writes:
>
> Given the following Org document:
>
> ,
> | #+MACRO: refp \autoref{$1}, \autopageref{$1}
> |
> |
> | * section
> |
> | Please see the results in {{{refp(sec:info)}}}.
> |
> | * info<>
> |
> | The results are here.
> `
>
> When exporting to LaTex, I expect `autoref' and `autopageref' to
> correctly refer to the target `sec:info'. However, recent versions of
> Org do not do that. I now get the following when exporting to LaTeX:
>
> ,
> | % Created 2015-10-21 Wed 03:25
> | \documentclass[11pt]{article}
> | % [...]
> | \begin{document}
> | % [...]
> | \section{section}
> | \label{sec:orgheadline1}
> |
> | Please see the results in \autoref{sec:info}, \autopageref{sec:info}.
> |
> | \section{info\label{orgtarget1}}
> | \label{sec:orgheadline2}
> |
> | The results are here.
> | \end{document}
> `
>
> When compiled, the following warning is issued:
>
> ,
> | Latex failed to resolve 2 reference(s)
> `
>
>
> This did not occur in Org Mode 8.3beta.
>

Please see `org-latex-prefer-user-labels'.

Best,
Andreas

[O] Bug: LaTeX export: internal target + \autoref{} broken [8.3.2 (8.3.2-elpaplus @ /home/myq/.emacs.d/elpa/org-plus-contrib-20150929/)]

[☕◦m̰̱̐y̿q̟̽]

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

 http://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org-mode mailing list.


Given the following Org document:

,
| #+MACRO: refp \autoref{$1}, \autopageref{$1}
|
|
| * section
|
| Please see the results in {{{refp(sec:info)}}}.
|
| * info<>
|
| The results are here.
`

When exporting to LaTex, I expect `autoref' and `autopageref' to
correctly refer to the target `sec:info'. However, recent versions of
Org do not do that. I now get the following when exporting to LaTeX:

,
| % Created 2015-10-21 Wed 03:25
| \documentclass[11pt]{article}
| % [...]
| \begin{document}
| % [...]
| \section{section}
| \label{sec:orgheadline1}
|
| Please see the results in \autoref{sec:info}, \autopageref{sec:info}.
|
| \section{info\label{orgtarget1}}
| \label{sec:orgheadline2}
|
| The results are here.
| \end{document}
`

When compiled, the following warning is issued:

,
| Latex failed to resolve 2 reference(s)
`


This did not occur in Org Mode 8.3beta.

 --

Emacs  : GNU Emacs 24.5.1 (i686-pc-linux-gnu, GTK+ Version 3.10.8)
 of 2015-06-01 on toshiba
Package: Org-mode version 8.3.2 (8.3.2-elpaplus @
/home/myq/.emacs.d/elpa/org-plus-contrib-20150929/)

current state:
==
(setq
 org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point
org-babel-execute-safely-maybe)
 org-latex-format-headline-function 'org-latex-format-headline-default-function
 org-pretty-entities t
 org-latex-packages-alist '(("" "booktabs" t) ("" "minted" t) ("" "color" nil))
 org-html-format-inlinetask-function
'org-html-format-inlinetask-default-function
 org-drill-optimal-factor-matrix '((1 (2.6 . 4.14) (1.7002
. 3.44) (1.96 . 3.58)
(2.1797 . 3.72) (2.36 . 3.86))
   )
 org-tab-first-hook '(org-hide-block-toggle-maybe
org-babel-hide-result-toggle-maybe
  org-babel-header-arg-expand)
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-modules '(org-bbdb org-bibtex org-docview org-gnus org-info
org-inlinetask org-irc org-mhe org-rmail
   org-w3m org-drill)
 org-cycle-hook '(org-inlinetask-hide-tasks
org-cycle-hide-archived-subtrees org-cycle-hide-drawers
  org-cycle-show-empty-lines
org-optimize-window-after-visibility-change)
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
 org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
 org-fontify-done-headline t
 org-babel-pre-tangle-hook '(save-buffer)
 org-occur-hook '(org-first-headline-recenter)
 org-font-lock-hook '(org-inlinetask-fontify)
 org-src-lang-modes '(("ocaml" . tuareg) ("elisp" . emacs-lisp)
("ditaa" . artist) ("asymptote" . asy)
  ("dot" . fundamental) ("sqlite" . sql) ("calc" .
fundamental) ("C" . c)
  ("cpp" . c++) ("C++" . c++) ("screen" .
shell-script) ("bash" . sh))
 org-html-format-headline-function 'org-html-format-headline-default-function
 org-log-done t
 org-use-sub-superscripts '{}
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-confirm-elisp-link-function 'yes-or-no-p
 org-hide-leading-stars t
 org-log-into-drawer t
 org-default-notes-file "notes.org"
 org-latex-classes '(("beamer" "\\documentclass[presentation]{beamer}"
  ("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
  ("\\subsubsection{%s}" . "\\subsubsection*{%s}"))
 ("article" "\\documentclass[11pt]{article}"
("\\section{%s}" . "\\section*{%s}")
  ("\\subsection{%s}" . "\\subsection*{%s}")
  ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
  ("\\paragraph{%s}" . "\\paragraph*{%s}")
  ("\\subparagraph{%s}" . "\\subparagraph*{%s}"))
 ("report" "\\documentclass[11pt]{report}"
("\\part{%s}" . "\\part*{%s}")
  ("\\chapter{%s}" . "\\chapter*{%s}")
("\\section{%s}" . "\\section*{%s}")
  ("\\subsection{%s}" . "\\subsection*{%s}")
  ("\\subsubsection{%s}" . "\\subsubsection*{%s}"))
 ("book" "\\documentclass[11pt]{book}"
("\\part{%s}" . "\\part*{%s}")
  ("\\chapter{%s}" . "\\chapter*{%s}")
("\\section{%s}" . "\\section*{%s}")
  ("\\subsection{%s}" . "\\subsection*{%s}")
  ("\\subsubsection{%s}" . "\\subsubsection*{%s}"))
 )
 org-latex-format-drawer-function '(lambda (name contents) contents)
 org-src-tab-acts-natively t
 org-export-backends '(ascii beamer html

[O] subject tree listing from publish

[Greg O'Keefe]

Hi,

I keep a directory of notes as .org files, and use publish to generate
.html from them.  This produces sitemap.html - a table of the #+TITLEs, and
theindex.html built from #+INDEX entries I have added.

I would like a third summary .html page which lists the notes organised in
a tree by subject classification, where the subject classification is
something like the ACM Computing Subject Classification or the Dewey
Decimal system, or some cut-down version of these.

The result would look a bit like this, where the _underlined_ items are
links to notes.

Information Technology
Software and its Engineering
Modelling Languages
_Dynamic Logic for UML Sequence Diagrams_
Computing Methodologies
Knowledge Representation
_Translating ACL to FOL_

Reading the  manual, it looks like I could use TAGS to give the notes
subjects, and use these to do searches over the whole project in emacs.
This, and the way theindex.html is produced by including a simple looking
theindex.inc text file makes me think that the solution may not be very
hard. However, my lisp is very weak :-(

Any suggestions or code most welcome!

Cheers,

Greg

[O] Bug: `org-timestamp-format' does not return correct time [8.2.10 (8.2.10-41-g42228a-elpa @ /home/gk/.emacs.d/packages/org-20150601/)]

[Göktuğ Kayaalp]

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

 http://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org-mode mailing list.


The function `org-timestamp-format' returns bad values:

(org-timestamp-format "<2015-10-07 Wed>" "%d %B %Y")
"30 November -001"
(org-timestamp-format "[2015-10-07 Wed]" "%d %B %Y")
"30 November -001"
(org-timestamp-format "[2015-10-07]" "%d %B %Y")
"30 November -001"
(org-timestamp-format "<2015-10-07>" "%d %B %Y")
"30 November -001"
(org-timestamp-format "2015-10-07" "%d %B %Y")
"30 November -001"
(org-timestamp-format (current-time) "%d %B %Y")
"30 November -001"
(org-timestamp-format (org-parse-time-string "[2015-10-07 Wed]")
  "%d %B %Y")
"30 November -001"


I tried this for my latex export filter, and got the same output for the
timestamp in the second example:

(defun gk-ox-latex-format-inactive-timestamp (text backend info)
  (when (org-export-derived-backend-p backend 'latex)
(org-timestamp-format text "%d %B %Y")))

I get the expected result from this piece of code:

(format-time-string
 "%d %B %Y"
 (apply #'encode-time
(org-parse-time-string
 text)))
"07 November 2015"

I see two commits that affect this function, visible here:

http://orgmode.org/cgit.cgi/org-mode.git/log/?qt=grep&q=org-timestamp-format&showmsg=1

One of them adds it, the other one refactors it, without changing the logic.

Emacs  : GNU Emacs 24.5.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.16.6)
 of 2015-09-10 on foutrelis
Package: Org-mode version 8.2.10 (8.2.10-41-g42228a-elpa @ 
/home/gk/.emacs.d/packages/org-20150601/)

Re: [O] org-agenda-scheduled-leaders and repeating tasks

[Matt Lundin]

Nicolas Goaziou  writes:

> cesar mena  writes:
>
>> i tracked this down to the function org-time-string-to-absolute.  when
>> rendering the agenda it gets called with today as its DAYNR argument,
>> which causes "org-closest-date" to return "today" for the case of
>> repeating timestamps.
>>
>> i can understand why it is done this way, and i find it useful.
>> however for some tasks, i'd rather the counter not reset lest i miss
>> something for longer than i should have (the smoke alarm case for
>> example).
>
> I fixed the issue with a rather opinionated change.
> `org-agenda-repeating-timestamp-show-all' no longer applies on ".+" and
> "++" repeaters.
>

While I agree in principe with this change, I wonder if we could make an
exception for habits. Habits (org-habit.el) customarily use a notation
like this:

--8<---cut here---start->8---
* Go for a run
  :PROPERTIES:
  :STYLE:habit
  :END:
  <2015-10-16 Fri 16:00 .+1d/2d>
--8<---cut here---end--->8---

This will appear in the agenda with a consistency graph indicating the
last n days of completion (depending on org-habit-preceding-days).
Before the change in commit a427098b57c747ecc76feb0593f32922a1e12f67,
these would appear in my daily agenda at their scheduled time,
regardless of whether I had missed a day or two. Now, if I miss a day,
the habit drops to the bottom of the agenda (it no longer appears at the
scheduled time). IMO, this is undesired behavior; I want to be reminded
of the habit at the same time each day regardless of whether I have done
it on previous days, especially since the consistency graph gives me all
the information I need about past completions.

Changing the timestamp to +1d/2d will is not an option, since the
timestamp only advances one day upon completion. This leads to an
incoherent consistency graph. The graph color remains red, which
indicates incompletion, and the habit stays on the daily agenda, even
though I have just completed it.

In short, org-habit seems to want a + notation for the purposes of the
agenda display and a .+ notation for the purposes of resetting the
timestamp. What is the best solution?

Thanks,
Matt

[O] Agenda to iCal not working

[Ken Mankoff]

I'm using the examples from 
https://www.gnu.org/software/emacs/manual/html_node/org/Exporting-Agenda-Views.html

Specifically,

(setq org-agenda-custom-commands
  '(("X" agenda "" nil ("agenda.html" "agenda.ps"))
("Y" alltodo "" nil ("todo.html" "todo.txt" "todo.ps"))
("h" "Agenda and Home-related tasks"
 ((agenda "")
  (tags-todo "home")
  (tags "garden"))
 nil
 ("~/views/home.html"))
("o" "Agenda and Office-related tasks"
 ((agenda)
  (tags-todo "work")
  (tags "office"))
 nil
 ("~/views/office.ps" "~/calendars/office.ics"

But the HTML, PS, and ICS files are not being created. If I'm visiting an Org 
file and run (org-icalendar-export-to-ics) then the ICS is generated.

Can someone offer advice why the ICS isn't generated when I generate a specific 
agenda view?

Thanks,

  -k.
  

Re: [O] Export datetree item subtree with its date, not the file's

[Eric S Fraga]

On Tuesday, 20 Oct 2015 at 17:49, Göktuğ Kayaalp wrote:
> Hello,
>
> Thanks for your response.  As you suggest, I switched to using the
> EXPORT_DATE property.  It works as expected.
>
> Now a little problem that I have is that I cannot have timestamps like
> «10 September 2015» in my exports, but a literal inactive timestamp.

If I understand you correctly, this is now a formatting issue for the
PDF export?  If so, look at

,[ C-h v org-latex-inactive-timestamp-format RET ]
| org-latex-inactive-timestamp-format is a variable defined in `ox-latex.el'.
| Its value is "\\textit{%s}"
| 
| Documentation:
| A printf format string to be applied to inactive timestamps.
| 
| You can customize this variable.
`

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 24.5.1, Org release_8.3.2-164-g50a182