Re: [O] Block level specification for tex code html export method

[Eric S Fraga]

On Friday,  4 Sep 2015 at 15:23, Haochen Xie wrote:
> Hi Eric,
>
> It's very likely due to this problem as both Andreas and I mentioned in
> earlier mails:

Thanks.  I did notice the bits about htlatex but didn't pay much
attention.  I don't actually need svg as I use png for my web pages!

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.2, Org release_8.3.1-188-g410ea6

Re: [O] Block level specification for tex code html export method

[Alan Schmitt]

Thanks to everyone, I now have this working. Here is the final version.

--8<---cut here---start->8---
#+LATEX_HEADER: \usepackage{tikz}

First execute the second code block, to define the convenience macro
and to set the required new variables in ob-latex.el.  Then export to
HTML and to pdf to see the tree exported as an SVG image and as
embedded tikz respectively.

* Tikz test
Here's a tree, exported to both html and pdf.

#+header: :file (by-backend (html "tree.svg") (latex "tree.tikz") (t 
"tree.png"))
#+header: :imagemagick yes :iminoptions -density 600 :imoutoptions -geometry 800
#+header: :results file raw
#+header: :fit yes
#+header: :headers '("\\usepackage{tikz}")
#+begin_src latex
  \usetikzlibrary{trees}
  \begin{tikzpicture}
\node [circle, draw, fill=red!20] at (0,0) {1}
child { node [circle, draw, fill=blue!30] {2}
  child { node [circle, draw, fill=green!30] {3} }
  child { node [circle, draw, fill=yellow!30] {4} }};
  \end{tikzpicture}
#+end_src

#+results:
[[file:tree.png]]

* COMMENT setup
#+begin_src emacs-lisp :results silent
  (setq org-babel-latex-htlatex "htlatex")
  (defmacro by-backend (&rest body)
`(case org-export-current-backend ,@body))
#+end_src
--8<---cut here---end--->8---

The header line that says to use the package tikz right before the
source block is only necessary to generate the png when evaluating the
block (“C-c C-c” on it), but as it does not prevent the export to work,
I leave it there.

I had to change my systems pgfsys-tex4ht.def as described in
http://tex.stackexchange.com/questions/185349/error-using-pgfsysdriver-with-tex4ht-only-shows-up-with-texlive-2014-ok-with-t/232739#232739
(having a local copy and modifying it as suggested on the site did not
work).

Thanks again,

Alan

-- 
OpenPGP Key ID : 040D0A3B4ED2E5C7
Last week athmospheric CO₂ average (Updated August 31, 2015, Mauna Loa Obs.):
377.82 ppm


signature.asc
Description: PGP signature

[O] ob-R ignores ess-eval-visibly?

[Tamas Papp]

Hi,

I prefer ESS not to wait for results of evaluating R code, especially if
it takes a longer time (eg estimating a model in RStan, 1-2 minutes), so
I have

(setq ess-eval-visibly 'nowait)

But I find that ob-R ignores this, eg evaluating

#+BEGIN_SRC R :results none
  Sys.sleep(10)
#+END_SRC

I looked at the source and I think I understand why this is: the results
need to be inserted into the buffer. However, could there be an
exception for :results none, when they are not needed? Then I could put
code which takes a long time into these blocks, and they would not block
my Emacs.

Best,

Tamas

Re: [O] emacs & org mode for scholars questions

[Rasmus]

Christian Wittern  writes:

> $> pip --freeze > requirements   and
> $> pip install -r 
> might provide both a flexible and extensible way to maintain meta packages. 
> Or is there already a better way in the Emacs universe?

Why make it so hard?  Just use the facilities built into Emacs, namely
init.el and package.el and put something like this in your init.

(setq package-selected-packages
  '(auctex ess
company
js2-mode
magit
nyan-mode
pdf-tools
paredit
visual-regexp))

(package-initialize)
(when (fboundp 'package-install-selected-packages) ; Emacs-v25 
  (package-install-selected-packages))


Rasmus

-- 
Dobbelt-A

[O] SOLVED: Error when tangling subtree - but works for whole document

[Rainer M Krug]

The problem is that tangling in an indirect buffer does not work.

I'll post another email concerning this.

Thanks,

Rainer

Rainer M Krug  writes:

> Hi
>
> I get an error #(wrong-type-argument stringp nil)# when I tangle a
> subtree, but tangling the whole document works.
>
> ,
> | GNU Emacs 24.5.1 (x86_64-apple-darwin14.5.0, Carbon Version 157
> | AppKit 1348.17) of 2015-08-28 on Rainers-MacBook-Pro.local
> | Org-mode version 8.3.1 (release_8.3.1-166-g5bfdfc @ 
> /Users/rainerkrug/.emacs.d/org-mode/lisp/)
> `
>
> The backtrace is below
>
> Let me know if you need any further info
>
> Thanks,
>
> Rainer
>

[snip: Long Backtrace (11 lines)]

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug

PGP: 0x0F52F982


signature.asc
Description: PGP signature

[O] Tangling from indirect buffer

[Rainer M Krug]

Hi

it seems that tangling from an indirect buffer does not work. Is this by
design or a bug?

Would it be possible to make this possible? I am working a lot in
indirect buffers (one subfolder R packages, another analysis of data, a
third one results) and would very much like to tangle from them instead of
having to go back to the actual buffer.

Thanks,

Rainer

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug

PGP: 0x0F52F982


signature.asc
Description: PGP signature

Re: [O] Org Babel blocks exports dollar signs to LaTeX verbatim

[Alan Schmitt]

(Still catching up on orgmode mail … sorry if you already found a way to
address the issue)

On 2015-08-18 18:13, Matthew MacLean  writes:

> When working with Org Babel source code blocks, if I have a dollar sign in my
> code and export it to PDF using LaTeX, it appears to parse as an internal
> link. (Maybe?)
>
> This is what it looks like:
> Inline image 1
> That comes from the following source code block:
>
> #+BEGIN_SRC sql :eval no :var id=1
> SELECT * FROM blah
> WHERE id=$id
> #+END_SRC
>
> The resulting LaTeX from the source code block is:
>
> \begin{minted}[]{sql}
> SELECT * FROM blah
> WHERE id=$id
> \end{minted}
>
> I have verified that SQL is not the only block type to do this by having a
> Ruby block with nothing except a "$" in it, and got the same result.

These red boxes often come from signaling a syntax error from pygments,
which I confirmed by putting the code in a test.sql file and running:

% pygmentize -f latex test.sql
\begin{Verbatim}[commandchars=\\\{\}]
\PY{k}{SELECT} \PY{o}{*} \PY{k}{FROM} \PY{n}{blah}
\PY{k}{WHERE} \PY{n}{id}\PY{o}{=}\PY{err}{\PYZdl{}}\PY{n}{id}
\end{Verbatim}

You can see the “\PY{err}” that signals a parser error around the dollar
sign.

There are some solutions to hide these boxes here:
http://tex.stackexchange.com/questions/14166/red-box-drawn-around-question-mark-operator-in-minted-erlang-code

Best,

Alan

-- 
OpenPGP Key ID : 040D0A3B4ED2E5C7
Last week athmospheric CO₂ average (Updated August 31, 2015, Mauna Loa Obs.):
377.82 ppm


signature.asc
Description: PGP signature

Re: [O] Block level specification for tex code html export method

[Andreas Leha]

Hi Nicolas,

Nicolas Goaziou  writes:
> Hello,
>
> Andreas Leha  writes:
>
>> This macro is from Eric Schulte initially.  And I guess I would be out
>> of luck adapting it to new Org mode versions as well.
>
> What about
>
>   (defmacro by-backend (&rest body)
> `(case org-export-current-backend ,@body))
> ?
>
> Regards,

Thanks for this!  One reason less not to upgrade Org mode.

Seems to work fine!

Just note, that it works for me only after exporting
 (when tested under emacs -Q).

What about including that into org?

Regards,
Andreas

[O] Bug: org-shitmeta(up/down) does not seem to handle subtrees and items properly [8.3.1 (8.3.1-95-g1dbb25-elpa @ /home/fvaresi/.emacs.d/elpa/org-20150831/)]

[Fernando Varesi]

Hi. First of all I apologize if this report does not comply in any way to the 
standards, since it's my first report.

Steps to reproduce:
1. Create an outline with 2 headlines, each of them having their own drawers.
2. Move the pointer to the headline.
3. Hit M-S-down.

Expected Behavior:
M-S-up/down should move the subtree/item up/down when pointer is in a 
headline/item.

Current Behavior:
Only the headline is moved, even inside a drawer if it's present.

Debugging:
I checked the functions org-shiftmetaup and org-shiftmetadown, and the cond 
does not check for org-at-heading-p nor org-at-item-bullet.

Fix:
You'll notice in my configuration I added hooks for org-shiftmetaup-hook and 
org-shiftmetadown-hook. This produces the expected behavior, but I think these 
conds should be added to the function itself. I'm not sure org-at-item-bullet 
is the right predicate, but it worked for me.

Thanks,

Fernando.




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.




Emacs  : GNU Emacs 24.5.1 (x86_64-pc-linux-gnu, GTK+ Version 3.16.4)
 of 2015-06-28 on trouble, modified by Debian
Package: Org-mode version 8.3.1 (8.3.1-95-g1dbb25-elpa @ 
/home/fvaresi/.emacs.d/elpa/org-20150831/)

current state:
==
(setq
 org-src-lang-modes '(("http" . "ob-http") ("ocaml" . tuareg) ("elisp" . 
emacs-lisp) ("ditaa" . artist) ("asymptote" . asy)
  ("dot" . fundamental) ("sqlite" . sql) ("calc" . 
fundamental) ("C" . c) ("cpp" . c++) ("C++" . c++)
  ("screen" . shell-script) ("shell" . sh) ("bash" . sh))
 org-tab-first-hook '(org-hide-block-toggle-maybe 
org-babel-hide-result-toggle-maybe org-babel-header-arg-expand)
 org-shiftmetadown-hook '((lambda nil
   (cond ((org-at-heading-p) (org-move-subtree-down)) 
((org-at-item-bullet-p) (org-move-item-down
  )
 org-speed-command-hook '(org-speed-command-default-hook 
org-babel-speed-command-hook)
 org-notmuch-search-open-function 'org-notmuch-search-follow-link
 org-occur-hook '(org-first-headline-recenter)
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-clock-mode-line-total 'today
 org-confirm-shell-link-function 'yes-or-no-p
 org-default-notes-file "~/org/notes.org"
 org-agenda-include-diary t
 org-after-todo-state-change-hook '(org-clock-out-if-current)
 org-from-is-user-regexp "\\"
 org-src-mode-hook '(org-src-babel-configure-edit-buffer 
org-src-mode-configure-edit-buffer)
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-babel-pre-tangle-hook '(save-buffer)
 org-mode-hook '(#[nil "\300\301\302\303\304$\207" [org-add-hook 
change-major-mode-hook org-show-block-all append local] 5]
 #[nil "\300\301\302\303\304$\207" [org-add-hook 
change-major-mode-hook org-babel-show-result-all append local] 5]
 org-babel-result-hide-spec org-babel-hide-all-hashes)
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-shiftmetaup-hook '((lambda nil (cond ((org-at-heading-p) 
(org-move-subtree-up)) ((org-at-item-bullet-p) (org-move-item-up)
 org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point 
org-babel-execute-safely-maybe)
 org-enforce-todo-dependencies t
 org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers 
org-cycle-show-empty-lines
  org-optimize-window-after-visibility-change)
 org-notmuch-open-function 'org-notmuch-follow-link
 org-enforce-todo-checkbox-dependencies t
 org-todo-keywords '((sequence "TODO(t)" "IN_PROGRESS(p)" "|" "DONE(d)"))
 org-confirm-elisp-link-function 'yes-or-no-p
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 org-log-into-drawer t
 org-blocker-hook '(org-block-todo-from-checkboxes 
org-block-todo-from-children-or-siblings-or-parent)
 org-babel-load-languages '((emacs-lisp . t) (http . t))
 org-agenda-files '("~/org/notes.org")
 org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
 org-clock-out-remove-zero-time-clocks t
 )
-- 
Ing. Fernando Varesi

Re: [O] Block level specification for tex code html export method

[Nicolas Goaziou]

Andreas Leha  writes:

> Seems to work fine!
>
> Just note, that it works for me only after exporting
>  (when tested under emacs -Q).

`org-export-current-backend' is set when exporting a document, much like
`backend'.

> What about including that into org?

Wrong namespace. It should be prefixed with "org". 

Also, it might be better to include it directly in :file directive
handling if that is its sole purpose.


Regards,

Re: [O] shell scripts in yasnippet?

[John Kitchin]

This is kind of close:

#+BEGIN_SRC emacs-lisp
(yas-global-mode)
(with-temp-buffer
  (insert "# name : my-fortune
# key: myf
# expand-env: ((yas-indent-line nil)
# --

#+BEGIN_QUOTE:
${1:`(shell-command-to-string \"fortune\")`}
#END_QUOTE

$0
")
  (yas-load-snippet-buffer-and-close 'org-mode))
#+END_SRC

For some reason it is inserting some extra spaces before # for me, and I
cannot figure out why.

Tobias Frischholz writes:

> Hi there,
>
> right now I’m tinkering around with yasnippet.
> I was wondering if there’s a possibility to run a shell script and write its 
> results in the text file.
>
> Specifically, I’m want to run “fortune” and put the results in a 
> #+BEGIN_QUOTE…#+END_QUOTE block.
> Would that be possible?
> Best regards,
> Tobias Frischholz
>
> PGP PUBLIC KEY: http://pgp.mit.edu/pks/lookup?search=0xCD463AC1&op=index

--
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] Block level specification for tex code html export method

[Andreas Leha]

Nicolas Goaziou  writes:
> Andreas Leha  writes:
>
>> Seems to work fine!
>>
>> Just note, that it works for me only after exporting
>>  (when tested under emacs -Q).
>
> `org-export-current-backend' is set when exporting a document, much like
> `backend'.
>

The same protection as in the previous version seems to take effect
here:

  (defmacro by-backend (&rest body)
`(case (if (boundp 'org-export-current-backend) org-export-current-backend 
nil) ,@body))

Are there any issues with this?

>> What about including that into org?
>
> Wrong namespace. It should be prefixed with "org". 
>

Easy to fix.

> Also, it might be better to include it directly in :file directive
> handling if that is its sole purpose.

Could you elaborate why that might be better?  Including it as a macro
like this has the up-side to be more general.n

I think that also other header arguments would benefit from such a
(org-)by-backend switch.

In former versions (pre-dating the handling of *.tikz 'images' by
ox-latex) of the tikz code in this thread, for example, the :results
argument needed to be set according to the backend as well


Regards,
Andreas

Re: [O] Tangling from indirect buffer

[Kyle Meyer]

Rainer M Krug  writes:

> Hi
>
> it seems that tangling from an indirect buffer does not work. Is this by
> design or a bug?

I don't think that's by design.

> Would it be possible to make this possible?

Does the below patch work for you?  If so, I can test it more thoroughly
and send a proper patch.

diff --git a/lisp/ob-tangle.el b/lisp/ob-tangle.el
index d20c2b3..cf48db3 100644
--- a/lisp/ob-tangle.el
+++ b/lisp/ob-tangle.el
@@ -242,7 +242,7 @@ (defun org-babel-tangle (&optional arg target-file lang)
 			 (base-name (cond
  ((string= "yes" tangle)
   (file-name-sans-extension
-   (buffer-file-name)))
+   (nth 1 spec)))
  ((string= "no" tangle) nil)
  ((> (length tangle) 0) tangle)))
 			 (file-name (when base-name
@@ -427,7 +427,7 @@ (defun org-babel-tangle-single-block
 	 (start-line
 	  (save-restriction (widen)
 			(+ 1 (line-number-at-pos (point)
-	 (file (buffer-file-name))
+	 (file (buffer-file-name (buffer-base-buffer)))
 	 (src-lang (nth 0 info))
 	 (params (nth 2 info))
 	 (extra (nth 3 info))

--
Kyle

[O] (no subject)

[Eduardo Mercovich]

Hello everbody. 

I'm an emacs/org-mode newbie but I'm learning, so please forgive me if
this is obvious for you.

A couple days ago I updated org from the packages-list. 

Now, when I'm trying to use a simple org table (typing TAB, for
example), I get: 
"org-get-limited-outline-regexp: Variable binding depth exceeds
max-specpdl-size"

Also, while trying to export a document to html, I get: 
"Variable binding depth exceeds max-specpdl-size"

Looking up, I saw that this is a mechanisms to protect against infinite
recursions, so I tried to increase the limit -just to get the exporting
done- putting in my .emacs this:

(setq max-specpdl-size 15000)
(setq max-lisp-eval-depth 15000)

But, no luck. 

Any pointer about what could be happening, or how to solve it? 
Thanks a lot in advance... :)

-- 
e

Re: [O] (no subject)

[thomas]

you could revert to your working org installation (if you did not delete 
that folder)  by deleting / moving the folder with the faulty 
installation (say "org-201508XX") from your .emacs.d/elpa directory.


If this solves your problems, then I would recommend starting a "bare" 
emacs


 emacs -q

and install org from elpa again. A few days ago I ran into that same 
issue :-)


 - thomas


On 04.09.2015 16:51, Eduardo Mercovich wrote:

Hello everbody.

I'm an emacs/org-mode newbie but I'm learning, so please forgive me if
this is obvious for you.

A couple days ago I updated org from the packages-list.

Now, when I'm trying to use a simple org table (typing TAB, for
example), I get:
"org-get-limited-outline-regexp: Variable binding depth exceeds
max-specpdl-size"

Also, while trying to export a document to html, I get:
"Variable binding depth exceeds max-specpdl-size"

Looking up, I saw that this is a mechanisms to protect against infinite
recursions, so I tried to increase the limit -just to get the exporting
done- putting in my .emacs this:

(setq max-specpdl-size 15000)
(setq max-lisp-eval-depth 15000)

But, no luck.

Any pointer about what could be happening, or how to solve it?
Thanks a lot in advance... :)

Re: [O] Org Babel blocks exports dollar signs to LaTeX verbatim

[Matthew MacLean]

Ah, thanks! So it was configuration then...

I initially figured it was language-dependant, which was why I tried it in
Ruby, since "$" is a valid character in that language... What I didn't
anticipate was that the boxes came from intelligent-syntax checking--I
figured that it was just some sort of fancy character I was unfamiliar with
that needed to be escaped.

So, the way I fixed the issue in my Org file was to add the following to
override the syntax error checking:

#+LATEX_HEADER: \expandafter\def\csname PY@tok@err\endcsname{}

It was recommended on that Stack Exchange answer not to do this, but we
aren't writing code directly in LaTeX, we're using Org mode..! That means
we don't really need error highlighting in our exporting, since that sort
of thing is already covered by existing language support.

On Fri, Sep 4, 2015 at 5:57 AM, Alan Schmitt  wrote:

> (Still catching up on orgmode mail … sorry if you already found a way to
> address the issue)
>
> On 2015-08-18 18:13, Matthew MacLean  writes:
>
> > When working with Org Babel source code blocks, if I have a dollar sign
> in my
> > code and export it to PDF using LaTeX, it appears to parse as an internal
> > link. (Maybe?)
> >
> > This is what it looks like:
> > Inline image 1
> > That comes from the following source code block:
> >
> > #+BEGIN_SRC sql :eval no :var id=1
> > SELECT * FROM blah
> > WHERE id=$id
> > #+END_SRC
> >
> > The resulting LaTeX from the source code block is:
> >
> > \begin{minted}[]{sql}
> > SELECT * FROM blah
> > WHERE id=$id
> > \end{minted}
> >
> > I have verified that SQL is not the only block type to do this by having
> a
> > Ruby block with nothing except a "$" in it, and got the same result.
>
> These red boxes often come from signaling a syntax error from pygments,
> which I confirmed by putting the code in a test.sql file and running:
>
> % pygmentize -f latex test.sql
> \begin{Verbatim}[commandchars=\\\{\}]
> \PY{k}{SELECT} \PY{o}{*} \PY{k}{FROM} \PY{n}{blah}
> \PY{k}{WHERE} \PY{n}{id}\PY{o}{=}\PY{err}{\PYZdl{}}\PY{n}{id}
> \end{Verbatim}
>
> You can see the “\PY{err}” that signals a parser error around the dollar
> sign.
>
> There are some solutions to hide these boxes here:
>
> http://tex.stackexchange.com/questions/14166/red-box-drawn-around-question-mark-operator-in-minted-erlang-code
>
> Best,
>
> Alan
>
> --
> OpenPGP Key ID : 040D0A3B4ED2E5C7
> Last week athmospheric CO₂ average (Updated August 31, 2015, Mauna Loa
> Obs.):
> 377.82 ppm
>

Re: [O] File local circular links

[Michael Brand]

Hi Nicolas

On Thu, Sep 3, 2015 at 4:06 PM, Nicolas Goaziou  wrote:
> Can't you simply do
>
>   (org-link-search ":file local circular link:" (point))
>
> ?

In my previous example the

  (org-link-search "[[:file local circular link:]]" (point))

to get enough from the org-link-search argument AVOID-POS would work
to jump between the two links. But when the second link is in a
headline

-
[[:file local circular link:]]
some text
* [[:file local circular link:]]
-

the second link jumps only to itself with the new org-link-search. I
understand that this is desired behavior because the headline gets
priority over the target on line 1. Before your change the target on
line 1 was the match when following the link on line 3, which was a
bug that I wrongly relied on to jump backwards. My conclusion is that
org-link-search is the wrong function for my purpose and I will have
to implement something with re-search-forward on my own.

> You could also use target-links

My main requirement is that the link has to be also the target, not a
link and a target side by side. How could that be fulfilled with
target-links?

Michael

[O] org-entry-get behaviour

[Martin Kaffanke]

Hi there,

I can see now, that (org-entry-get (point) "foo") is nil, if
:PROPERTIES: follows the CLOCK: entry.  Has it changed to be that
:PROPERTIES: now must be the first thing of the entry?  If so, how can I
change all my entries at once instead of going through all my items and
do it by hand?

Thanks,
Martin

Re: [O] org-entry-get behaviour

[Kyle Meyer]

Hi,

Martin Kaffanke  writes:

> Hi there,
>
> I can see now, that (org-entry-get (point) "foo") is nil, if
> :PROPERTIES: follows the CLOCK: entry.  Has it changed to be that
> :PROPERTIES: now must be the first thing of the entry?

Yes.

> If so, how can I
> change all my entries at once instead of going through all my items and
> do it by hand?

There is a function here:

http://orgmode.org/Changes.html

--
Kyle

Re: [O] Bug: org-shitmeta(up/down) does not seem to handle subtrees and items properly [8.3.1 (8.3.1-95-g1dbb25-elpa @ /home/fvaresi/.emacs.d/elpa/org-20150831/)]

[Nicolas Goaziou]

Hello,

Fernando Varesi  writes:

> Steps to reproduce:
> 1. Create an outline with 2 headlines, each of them having their own drawers.
> 2. Move the pointer to the headline.
> 3. Hit M-S-down.
>
> Expected Behavior:
> M-S-up/down should move the subtree/item up/down when pointer is in a 
> headline/item.
>
> Current Behavior:
> Only the headline is moved, even inside a drawer if it's present.

M-S-down mostly ignores structure. It moves current line down, whatever
it is. Check its docstring, in particular first and last sentences:

  Drag the line at point down.
  In a table, insert an empty row at the current line.
  On a clock timestamp, update the value of the timestamp like `S-'
  but also adjust the previous clocked item in the clock history.
  Everywhere else, drag the line at point down.


Regards,

-- 
Nicolas Goaziou

Re: [O] Bug: org-shitmeta(up/down) does not seem to handle subtrees and items properly [8.3.1 (8.3.1-95-g1dbb25-elpa @ /home/fvaresi/.emacs.d/elpa/org-20150831/)]

[Fernando Varesi]

Hi, Nicolas. Thanks for replying

Given the documentation in
http://orgmode.org/manual/Structure-editing.html#Structure-editing, I would
expect it to still use org-move-subtree-down.

Anyway, my desired behavior can be easily achieved with hooks so I don't
mind it keeping it  as is, but I thought that somehow the functionality
described in the manual was lost unintentionally.

Regards,

Fernando Varesi.

On Fri, Sep 4, 2015 at 2:33 PM Nicolas Goaziou 
wrote:

> Hello,
>
> Fernando Varesi  writes:
>
> > Steps to reproduce:
> > 1. Create an outline with 2 headlines, each of them having their own
> drawers.
> > 2. Move the pointer to the headline.
> > 3. Hit M-S-down.
> >
> > Expected Behavior:
> > M-S-up/down should move the subtree/item up/down when pointer is in a
> headline/item.
> >
> > Current Behavior:
> > Only the headline is moved, even inside a drawer if it's present.
>
> M-S-down mostly ignores structure. It moves current line down, whatever
> it is. Check its docstring, in particular first and last sentences:
>
>   Drag the line at point down.
>   In a table, insert an empty row at the current line.
>   On a clock timestamp, update the value of the timestamp like `S-'
>   but also adjust the previous clocked item in the clock history.
>   Everywhere else, drag the line at point down.
>
>
> Regards,
>
> --
> Nicolas Goaziou
>

Re: [O] (no subject)

[Eduardo Mercovich]

Dear Thomas. 

> you could revert to your working org installation (if you did not delete 
> that folder)  by deleting / moving the folder with the faulty 
> installation (say "org-201508XX") from your .emacs.d/elpa directory.
> If this solves your problems, then I would recommend starting a "bare" 
> emacs
>   emacs -q
> and install org from elpa again.

I did it, with some hiccups in the middle, and now I have a working
Org-mode version 8.3.1 (8.3.1-95-g1dbb25-elpaplus) 
in 
~/.emacs.d/elpa/org-20150831/

Thank you! :)

> A few days ago I ran into that same  issue :-)

Even while upgrading is not yet perfect, the packaging system is
becoming better by each version. 

As I'm not a bleeding edge developer, I may enjoy this version for a
while, but for those who may step on the same rock: 

1 . I uninstalled org from the package manager (M-x list-packages, there
mark with "D" and execute with "x")
2 . unloaded every org file (this is important, close all org buffers
before installation), 
3. . and installed again org from the package manager; 
4. . after, installed org-plus-contrib. 

Now it seems it's working fine, and I hope it may serve others too.
Don't forget to unload org buffers before install! (is upgrading the
same?).

Thanks a lot Thomas! :)

Best... 

-- 
e

Re: [O] Bug: org-shitmeta(up/down) does not seem to handle subtrees and items properly [8.3.1 (8.3.1-95-g1dbb25-elpa @ /home/fvaresi/.emacs.d/elpa/org-20150831/)]

[Nicolas Goaziou]

Fernando Varesi  writes:

> Given the documentation in
> http://orgmode.org/manual/Structure-editing.html#Structure-editing, I would
> expect it to still use org-move-subtree-down.

This is bound to M-down, isn't it? It probably is a documentation bug.

Regards,

Re: [O] Question about todo subheadings and logbook

[Nicolas Goaziou]

Hello,

Keith M Swartz  writes:

> I often want to add a subheading (sub-task) to this todo item, so I'll hit
> Alt-Enter to do this. When I do, it creates the subheading /between/ the
> original todo and the drawer. Is that correct?

It is.

> My preference - and what I would have assumed to be the correct behavior -
> would be to have the subheadings appear /after/ the logbook drawer, as each
> subtask can also have a todo state and its own logbook.

The logbook drawer can be anywhere in the entry. So creating headline
after the drawer is fuzzy. Also, it is to smart. What if I want to
create a new headline that would use this logbook?

Sometimes, the simpler is the better.


Regards,

-- 
Nicolas Goaziou

Re: [O] [PATCH] org-mime: make plain/text mime export a choice

[Nicolas Goaziou]

Jon Miller  writes:

> At this point, I'm not sure if there is any further hacking left to be done
> to the original patch I sent? Are we okay with just leaving the two options
> of 'ascii and 'org?

I don't think we're at a conclusion yet. In addition to providing ascii
and org, we might also

 - provide org, ascii, latin-1 and utf8
 - provide any symbol that will be understood as an export back-end

WDYT?

Regards,

Re: [O] [PATCH] org-mime: make plain/text mime export a choice

[Jon Miller]

Nicolas Goaziou writes:

> Jon Miller  writes:
>
>> At this point, I'm not sure if there is any further hacking left to be done
>> to the original patch I sent? Are we okay with just leaving the two options
>> of 'ascii and 'org?
>
> I don't think we're at a conclusion yet. In addition to providing ascii
> and org, we might also
>
>  - provide org, ascii, latin-1 and utf8
>  - provide any symbol that will be understood as an export back-end
>
> WDYT?

I'm willing to help hack out a solution. I just need a hint to help me
along.

- I specifically do not know how to produce a latin1 or utf8 export via the
  existing `org-export-string-as' function call that is being used.

- As for updating the parameter to support any valid back-end, I assume that
  means updating the defcustom from a choice list to a symbol that is then
  later checked as a valid back-end and defaults to a simple choice when it
  is non-valid?

-- 
Jon Miller

Re: [O] Question about todo subheadings and logbook

[Keith M Swartz]

Thank you, Nicolas.

I think this behavior is wrong, then, or else I have some configuration
setting that's messing things up. Problem is, if you create sub-level
todos, and change their state, the updates all get muddled, and you can't
tell which one's state changed. It also creates multiple logbooks if you go
back and change the state of the main heading at some point. (I also can't
help but wonder if this is partly due to changes in org-mode 8.3 regarding
property drawer syntax.)

Here is an example to reproduce some questionable results:

0. Create a set of TODO labels, like so:
#+SEQ_TODO: TODO(!) PEND(!) DONE(!)

1. Create an item, make it a todo. (Creates a logbook.)

2. Create a subheading. (Alt-Enter, shift-right) Make it a todo. (This adds
a line to the logbook saying the state changed to TODO, even though the
previous line says the state already is TODO. You can't tell which state
changed.)

3. Cycle the state on your sub-todo to PEND. (Changes the state in the
logbook.)

4, Go back to the main heading and cycle the state to PEND. (This creates
ANOTHER logbook right underneath the heading showing the state change. The
original record for when it was marked TODO is in the other logbook, but
there are two such entries, and it's not obvious which one is which. You
could probably infer logically that the older entry is for the main
heading, but if states keep going back and forth, you'll lose track
quickly.)

This can't be a desired behavior for anyone -- you either want multiple
logbooks for each item and subitem, OR you want a single logbook the whole
time. And if someone wants the latter, I don't see how it can be at all
useful if you can't tell whether the main item's state was changed or one
of the sub-items.

I could debate whether this is a bug, but my emacs is nothing if not
versatile, so bug or not, I'm fairly confident there's a way to get the
behavior I DO want. To that end, I was hoping somebody could offer a
suggestion.

However, the more I dive into this, I think the easiest fix is to define
org-metareturn-hook to call org-cycle (to collapse the drawer) and
org-end-of-line (so it's positioned after where the drawer would be) BEFORE
invoking org-metareturn to add the subheading. Actually, I'd probably want
something more specific than org-cycle, since I don't want it to expand the
drawer or some other tree node.

Any thoughts on this approach as a solution to my issue?

Thanks,
Keith


On Fri, Sep 4, 2015 at 11:52 AM, Nicolas Goaziou 
wrote:

> Hello,
>
> Keith M Swartz  writes:
>
> > I often want to add a subheading (sub-task) to this todo item, so I'll
> hit
> > Alt-Enter to do this. When I do, it creates the subheading /between/ the
> > original todo and the drawer. Is that correct?
>
> It is.
>
> > My preference - and what I would have assumed to be the correct behavior
> -
> > would be to have the subheadings appear /after/ the logbook drawer, as
> each
> > subtask can also have a todo state and its own logbook.
>
> The logbook drawer can be anywhere in the entry. So creating headline
> after the drawer is fuzzy. Also, it is to smart. What if I want to
> create a new headline that would use this logbook?
>
> Sometimes, the simpler is the better.
>
>
> Regards,
>
> --
> Nicolas Goaziou
>



-- 

Keith M Swartz
oneroad...@gmail.com

Re: [O] latest org from Elpa error: Invalid function: org-babel-header-args-safe-fn

[Mikhail Titov]

On Sat, Aug  8, 2015 at  8:54 AM, Ista Zahn  wrote:
> Unfortunately I now can't reproduce the problem, so I can't check if
> my suggestion to byte compile ob-R.el works or not.

For those still having this issue.

I do confirm this solves the problem that occurred upon upgrading Org
via ELPA on 64-bit MS Windows build of Emacs 24.5.1 maintained by Chris
Zheng.

I deleted and recompiled both ob-core.elc and ob-R.elc .

-- 
Mikhail

Re: [O] Question about todo subheadings and logbook

[Nicolas Goaziou]

Keith M Swartz  writes:

> Here is an example to reproduce some questionable results:
>
> 0. Create a set of TODO labels, like so:
> #+SEQ_TODO: TODO(!) PEND(!) DONE(!)
>
> 1. Create an item, make it a todo. (Creates a logbook.)

OK.

> 2. Create a subheading. (Alt-Enter, shift-right)

>From where?

> Make it a todo. (This adds a line to the logbook saying the state
> changed to TODO, even though the previous line says the state already
> is TODO. You can't tell which state changed.)
>
> 3. Cycle the state on your sub-todo to PEND. (Changes the state in the
> logbook.)
>
> 4, Go back to the main heading and cycle the state to PEND. (This creates
> ANOTHER logbook right underneath the heading showing the state change. The
> original record for when it was marked TODO is in the other logbook, but
> there are two such entries, and it's not obvious which one is which. You
> could probably infer logically that the older entry is for the main
> heading, but if states keep going back and forth, you'll lose track
> quickly.)

I cannot reproduce this. It creates the following document:

  #+SEQ_TODO: TODO(!) PEND(!) DONE(!)

  * PEND test
:LOGBOOK:
- State "PEND"   from "TODO"   [2015-09-04 ven. 21:37]
- State "TODO"   from  [2015-09-04 ven. 21:33]
:END:

  ** PEND test2
 :LOGBOOK:
 - State "PEND"   from "TODO"   [2015-09-04 ven. 21:35]
 - State "TODO"   from  [2015-09-04 ven. 21:34]
 :END:


Regards,

[O] org-mac-iCal: "Import diary from iCal in agenda" doesn't work

[Tobias Frischholz]

I have a small problem with a key binding for the agenda, which should import 
my iCal.app appointments into the diary.

I have the following code from this page:

(setq org-agenda custom-commands
  '(("I" "Import diary from iCal" agenda ""
 ((org-agenda-mode-hook
   (lambda ()
 (org-mac-iCal)))
When I start Emacs I get this warning:

Warning (initialization): An error occurred while loading 
`/Users/friolz/.emacs.d/init.el':

Symbol's value as variable is void: custom-commands


Manually importing the dates via M-x org-mac-iCal is working fine.

Best regards,
Tobias Frischholz

PGP PUBLIC KEY: http://pgp.mit.edu/pks/lookup?search=0xCD463AC1&op=index



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [O] Tangling from indirect buffer

[Martin Carlé]

Indirect buffers are of immense help but I had the same issue.

Can confirm that the hack referring to spec instead to the
buffer-file-name and getting the buffer-base-buffer respectively, does
the trick.

Great!

On 2015-09-04 Fri 17:49, Kyle Meyer wrote:

> Rainer M Krug  writes:
>
>> Hi
>>
>> it seems that tangling from an indirect buffer does not work. Is this by
>> design or a bug?
>
> I don't think that's by design.
>
>> Would it be possible to make this possible?
>
> Does the below patch work for you?  If so, I can test it more thoroughly
> and send a proper patch.

-- 
Fetch my gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 7E3CA33F


smime.p7s
Description: S/MIME cryptographic signature

Re: [O] Question about todo subheadings and logbook

[Keith M Swartz]

I was creating the sub-heading from the exact same spot where I stopped
typing and hit C-c C-t. Didn't move the cursor, just went straight from one
step to the next.

After step

Here is what that set of steps created for me:

* PEND First item
:LOGBOOK:
- State "PEND"   from "TODO"   [2015-09-04 Fri 13:23]
:END:
*** PEND Second item
:LOGBOOK:
- State "PEND"   from "TODO"   [2015-09-04 Fri 13:23]
- State "TODO"   from  [2015-09-04 Fri 13:23]
- State "TODO"   from  [2015-09-04 Fri 13:22]
:END:

Step-by-step -- after step 1 [note: the logbook is collapsed initially, but
I expanded it here to show the contents. Expanding the logbook before
creating a sub-item may alter the results; I haven't tried that.]

* TODO First item
:LOGBOOK:
- State "TODO"   from  [2015-09-04 Fri 13:25]
:END:

after step 2:

* TODO First item
*** TODO Second item
:LOGBOOK:
- State "TODO"   from  [2015-09-04 Fri 13:26]
- State "TODO"   from  [2015-09-04 Fri 13:25]
:END:

Looks like our experiences already differ. (BTW, are you on the same org
version?)

after step 3:

* TODO First item
*** PEND Second item
:LOGBOOK:
- State "PEND"   from "TODO"   [2015-09-04 Fri 13:26]
- State "TODO"   from  [2015-09-04 Fri 13:26]
- State "TODO"   from  [2015-09-04 Fri 13:25]
:END:

And after step 4, it's as you saw above.

Keith


On Fri, Sep 4, 2015 at 12:38 PM, Nicolas Goaziou 
wrote:

> Keith M Swartz  writes:
>
> > Here is an example to reproduce some questionable results:
> >
> > 0. Create a set of TODO labels, like so:
> > #+SEQ_TODO: TODO(!) PEND(!) DONE(!)
> >
> > 1. Create an item, make it a todo. (Creates a logbook.)
>
> OK.
>
> > 2. Create a subheading. (Alt-Enter, shift-right)
>
> From where?
>
> > Make it a todo. (This adds a line to the logbook saying the state
> > changed to TODO, even though the previous line says the state already
> > is TODO. You can't tell which state changed.)
> >
> > 3. Cycle the state on your sub-todo to PEND. (Changes the state in the
> > logbook.)
> >
> > 4, Go back to the main heading and cycle the state to PEND. (This creates
> > ANOTHER logbook right underneath the heading showing the state change.
> The
> > original record for when it was marked TODO is in the other logbook, but
> > there are two such entries, and it's not obvious which one is which. You
> > could probably infer logically that the older entry is for the main
> > heading, but if states keep going back and forth, you'll lose track
> > quickly.)
>
> I cannot reproduce this. It creates the following document:
>
>   #+SEQ_TODO: TODO(!) PEND(!) DONE(!)
>
>   * PEND test
> :LOGBOOK:
> - State "PEND"   from "TODO"   [2015-09-04 ven. 21:37]
> - State "TODO"   from  [2015-09-04 ven. 21:33]
> :END:
>
>   ** PEND test2
>  :LOGBOOK:
>  - State "PEND"   from "TODO"   [2015-09-04 ven. 21:35]
>  - State "TODO"   from  [2015-09-04 ven. 21:34]
>  :END:
>
>
> Regards,
>



-- 

Keith M Swartz
oneroad...@gmail.com

Re: [O] org-mac-iCal: "Import diary from iCal in agenda" doesn't work

[Josiah Schwab]

Hello Tobias,

On  4 September 2015 at 12:49 PDT, Tobias Frischholz wrote:

> I have a small problem with a key binding for the agenda, which should import 
> my iCal.app appointments into the diary.
>
> I have the following code from this page:
>
> (setq org-agenda custom-commands
>   '(("I" "Import diary from iCal" agenda ""
>  ((org-agenda-mode-hook
>(lambda ()
>  (org-mac-iCal)))
> When I start Emacs I get this warning:
>
> Warning (initialization): An error occurred while loading 
> `/Users/friolz/.emacs.d/init.el':
>
> Symbol's value as variable is void: custom-commands

I think there's a "-" missing.  The variable name is

  org-agenda-custom-commands
^
Best,
Josiah

[O] org-mobile-push and MobileOrg compatibility issue

[Vamsi Vytla]

M-x 'org-mobile-push', with the latest org-mode leaves the files
incompatible with MobileOrg Android application. There have been no changes
in MobileOrg for over a year.

I bisected the latest org-mobile related changes and noticed that reverting
this one line below "fixes" the issue (at least for me). Since there aren't
any tests, it's hard to validate changes and understand things easily.

If anybody can point me in the right direction, I would love to look into
it further.

Cheers!

diff --git a/lisp/org-mobile.el b/lisp/org-mobile.el
index 6c7c8d0..7e1127c 100644
--- a/lisp/org-mobile.el
+++ b/lisp/org-mobile.el
@@ -446,7 +446,7 @@ agenda view showing the flagged items."
 x))
   (cdr entry)))
(insert "#+TODO: " (mapconcat 'identity kwds " ") "\n")
-   (setq dwds (or (member "|" kwds) (last kwds))
+   (setq dwds (member "|" kwds)
  twds (org-delete-all dwds kwds)
  todo-kwds (org-delete-all twds todo-kwds)
  done-kwds (org-delete-all dwds done-kwds)))

Re: [O] Question about todo subheadings and logbook

[Nicolas Goaziou]

Keith M Swartz  writes:

> Step-by-step -- after step 1 [note: the logbook is collapsed initially, but
> I expanded it here to show the contents. Expanding the logbook before
> creating a sub-item may alter the results; I haven't tried that.]
>
> * TODO First item
> :LOGBOOK:
> - State "TODO"   from  [2015-09-04 Fri 13:25]
> :END:
>
> after step 2:
>
> * TODO First item
> *** TODO Second item
> :LOGBOOK:
> - State "TODO"   from  [2015-09-04 Fri 13:26]
> - State "TODO"   from  [2015-09-04 Fri 13:25]
> :END:

So you insert sub-heading between the first one and its logbook. Well,
this is to be expected. I don't see why Org should prevent you to do
that.

You may use, e.g., C-RET to insert new heading past contents of the
first one.

Regards,

Re: [O] org-mac-iCal: "Import diary from iCal in agenda" doesn't work

[Josiah Schwab]

On  4 September 2015 at 13:35 PDT, Josiah Schwab wrote:

> I think there's a "-" missing.  The variable name is
>
>   org-agenda-custom-commands
> ^

This is also now fixed on the website (worg commit 60c0b12).

Best,
Josiah

Re: [O] Question about todo subheadings and logbook

[Keith M Swartz]

I think there's some misunderstanding here regarding my initial question.

I do NOT want the subheading to go between the first one and the logbook.
When I hit Ctrl-Enter at the end of the line, that's where it goes. I
didn't choose to do that, and I would like it not to. To get what I want
now, I have to collapse the drawer and go to the end of the line (past the
"..." denoting the drawer) before adding a subheading. That's unnecessary
work that I shouldn't have to do.

I want the behavior to be such that after I type in the todo text, hit C-c
C-t (to label it as a todo), and hit ctrl-enter -- right there, without
moving the cursor again -- it should create a subheading BELOW the drawer.

When you created your test case, where did you position the cursor before
creating a subheading? Did you move the cursor between C-c C-t and
Ctrl-Enter? If so, I think that shouldn't be necessary, but right or wrong,
I'm trying to modify the behavior so I don't have to do that. If you didn't
move the cursor, then can you suggest why my org-mode is behaving that way?
I tried with a vanilla install (no custom settings at all) and got the same
thing.

Keith

On Fri, Sep 4, 2015 at 3:35 PM, Nicolas Goaziou 
wrote:

> Keith M Swartz  writes:
>
> > Step-by-step -- after step 1 [note: the logbook is collapsed initially,
> but
> > I expanded it here to show the contents. Expanding the logbook before
> > creating a sub-item may alter the results; I haven't tried that.]
> >
> > * TODO First item
> > :LOGBOOK:
> > - State "TODO"   from  [2015-09-04 Fri 13:25]
> > :END:
> >
> > after step 2:
> >
> > * TODO First item
> > *** TODO Second item
> > :LOGBOOK:
> > - State "TODO"   from  [2015-09-04 Fri 13:26]
> > - State "TODO"   from  [2015-09-04 Fri 13:25]
> > :END:
>
> So you insert sub-heading between the first one and its logbook. Well,
> this is to be expected. I don't see why Org should prevent you to do
> that.
>
> You may use, e.g., C-RET to insert new heading past contents of the
> first one.
>
> Regards,
>



-- 

Keith M Swartz
oneroad...@gmail.com

Re: [O] emacs & org mode for scholars questions

[John Kitchin]

Thanks. org-ref has been pretty stable lately, and given my fall
schedule it is likely to stay that way ;)

It might be ready for MELPA. I don't have a lot of experience packaging
for MELPA. Is there a set of instructions on how to do that somewhere?

Erik Hetzner writes:

> Thanks, John.
>
> I was really blown away by org-ref. It’s a great package. I love, for
> instance, the citation displayed in the minibuffer when the cursor is
> on a cite. If you need help with the MELPA packaging process, let me
> know.
>
> best, Erik
>
> On Wed, 02 Sep 2015 03:40:42-0700,
> John Kitchin  wrote:
>>
>> Cool! Thanks for the shout out to org-ref!
>>
>> my jmax starter package (http://github.com/jkitchin/jmax) is basically
>> designed for the last point you described. I use it with students (41
>> this semester!) as a standalone "package". It isn't as polished as
>> prelude or others, but it allows them to do things like I do out of the
>> box.
>>
>> The conference sounds like it was fun! Best wishes,
>>
>> Erik Hetzner writes:
>>
>> > Hi all,
>> >
>> > Thanks for all your responses! They were a great help when putting
>> > together my talk. I’ve posted my slides from EmacsConf 2015 here:
>> >
>> >   http://www.e6h.org/talks/emacsconf-2015/index.html
>> >
>> > I think the planners are planning to post videos as soon as they can
>> > get them edited to
>> >
>> >   http://emacsconf2015.org/
>> >
>> > EmacsConf 2015 was a lot of fun. Almost everyone there was an Org mode
>> > user, which was no great surprise.
>> >
>> > One thing that I came out of the conference thinking was that a
>> > curated meta-package for Emacs (like elpy) that brought together tools
>> > for scholarly writers (in LaTeX and markdown and org-mode) might be a
>> > great help for Emacs beginners.
>> >
>> > best, Erik
>> >
>> > On Mon, 24 Aug 2015 22:38:30 -0700,
>> > Erik Hetzner  wrote:
>> >>
>> >> Hi all,
>> >>
>> >> I am going to be giving a talk on how Emacs can help support scholars,
>> >> especially those who are using plain text and doing reproducible
>> >> research, at “Emacsconf 2015” in San Francisco this Saturday (the
>> >> 29th).
>> >>
>> >> I have done some work on managing references using Emacs & pandoc, but
>> >> what I’d like to focus on in this talk is why Emacs is a great tool
>> >> for scholarly writers (both scientists and humanists) and what Emacs
>> >> developers should be concentrating on to make it an even better tool
>> >> for the scholarly community.
>> >>
>> >> I’m wondering if you any of you might have any suggestions about what
>> >> you would like to see Emacs do better to support the scholarly writing
>> >> community.
>> >>
>> >> Thanks for any help you can provide!
>> >>
>> >> best, Erik Hetzner
>> >> --
>> >> Sent from my free software system .
>> >>
>> >>
>>
>> --
>> 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

--
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] using dates as property?

[John Kitchin]

thanks. that also works for me.

Samuel Wales writes:

> i always put inactive timestamps in headlines, and sort both the
> outline and agenda using them.  for example:
>
> * CONVERSATION [2015-08-31 Mon 14:41] john
> * CONVERSATION [2015-09-01 Tue 15:02] rms
>
> or newest first.  they are visible and binary-searchable.
> works perfectly for me.

--
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

[O] subtreep option in export stopped working propery

[Joon Ro]

Hi,
I have been using a link containing elisp:(org-beamer-export-to-pdf nil t) to 
export the subtree as a beamer pdf. It used to work well, but after a certain 
update a couple of months ago (I'm using 8.3beta and I regularly update it), it 
stopped working properly. For example, when I click on the following Beamer 
link:
* Export Test:PROPERTIES: :EXPORT_FILE_NAME: ./Test:EXPORT_TITLE: Export 
Test:EXPORT_SUBTREE: [[elisp:(org-beamer-export-to-pdf%20nil%20t)][Beamer]] 
:END:
Subtree Contents.

I get a tex file with one page with properties written on it.
Again, I used to use this link to generate subtree-only beamer pdf. Also, 
exporting manually (C-c C-e C-s l P) works well as well.
Best,Joon