Re: [O] view only tags related topics

[Eric Fraga]

Mohamad Atef Radwan  writes:

just beginner in org mode how could i view topics only that tags 
is assigned to when i searched for certain tag and hide the 
others ...  for example i want to  view  / print only topics 
that have :linux: tag Thanks 


Maybe this is what you are looking for:

,[ C-h f org-sparse-tree RET ] | org-sparse-tree is an 
interactive compiled Lisp function in `org.el'.  |  | 
(org-sparse-tree &optional ARG TYPE) |  | Create a sparse tree, 
prompt for the details.  | This command can create sparse 
trees.  You first need to select the type | of match used to 
create the tree: |  | t  Show all TODO entries.  | T  Show 
entries with a specific TODO keyword.  | m  Show entries 
selected by a tags/property match.  | p  Enter a property name 
and its value (both with completion on existing | 
names/values) and show entries with that property.  | r  Show 
entries matching a regular expression (`/' can be used as 
well).  | b  Show deadlines and scheduled items before a 
date.  | a  Show deadlines and scheduled items after a 
date.  | d  Show deadlines due within 
`org-deadline-warning-days'.  | D  Show deadlines and 
scheduled items between a date range.  |  | [back] `  It is 
usually bound to =C-c /=.


--
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_7.9.2-632-gd344fd

Re: [O] Export a weekly calendar view from org-agenda

[Eric Fraga]

Torsten Wagner  writes:

Hey Kyle, thanks for the info I will look into it.  Maybe I 
should say more specific, I am looking for a typical calendar 
view (sort of table) as you know them from paper-based 
organizers.  If I understood your solution, I would get a plain 
list of all events. 


I used to use the built-in export of diaries in Emacs to print off 
Filofax (tm) pages:


Info -> emacs -> Calendar/Diary -> Writing Calendar Files

How you get org to diary format is another question, however...

--
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_7.9.2-632-gd344fd

Re: [O] [new exporter] empty lines in LaTeX header

[Eric Fraga]

Andreas Leha  writes:
> Eric S Fraga  writes:
>> #+latex_header: \par
>
> Thanks for that.  It works fine!

Excellent!

>> By the way, you may also wish to check out the progressbar beamer theme:
>>
>> https://github.com/cedricmauclair/beamer-progressbar
>
> Thanks for the pointer.  Thing is, that I would like to stick to a
> corporate design layout that I hacked together to mimic a Powerpoint
> template.  And that snippet was the easiest to just add there.

And, having looked at your example, it's quite appealing.  I like the
inconspicuous nature of your progress bar.  I may have to look at using
it...

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.2.50.1 and Org release_7.9.2-561-g6e31cf

Re: [O] Bug: source code editing using C-c ' (org-edit-special) eats characters

[Eric Fraga]

Eric Schulte  writes:

[...]

> In any Org-mode buffer create and enter an empty code block, I like to
> do this with " cursor at C
>
> #+begin_src sh
> C
> #+end_src
>
> Then "C-'" into edit mode type "foo bar" do *not* type enter, and then
> do a "C-'" again to go back to the Org-mode buffer.  You are left with
> the following in the Org-mode buffer, which is not valid Org.
>
> #+begin_src sh
>   foo bar#+end_src
>
> This is a relatively new problem which I only begun to notice in the
> last month or so.

I was hit by this the other day.  Not a serious issue but it hadn't
happened to me before.

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.2.50.1 and Org release_7.9.2-561-g6e31cf

Re: [O] From latest maint/master, no need to (require 'org-install)

[Eric Fraga]

Sebastien Vauban  writes:

> Hi Eric,
>
> Eric Fraga wrote:
>> (add-to-list 'load-path "~/git/org-mode")
>
> Why that one?

Ahh, that's a bit of historical garbage.  There was a point a while back
where org-install seemed to have lisp/org-xxx paths and the easiest fix
was to add the root to the list of paths.  The problem was fixed fairly
quickly but I forgot to remove my temporary fix.

>> What should I or could I remove from this?
>
> What I do is:
>
> #+begin_src emacs-lisp
>   (when (locate-library "org-install")
> (require 'org-install))
> #+end_src

Actually, I now have

#+begin_src emacs-lisp
(add-to-list 'load-path "~/git/org-mode/lisp")
(add-to-list 'load-path "~/git/org-mode/contrib/lisp/")
(require 'org)
#+end_src

with a number of other =require= calls for specific ob- and org-e-
packages.  This seems to work just fine.

My question now is whether I should replace the =(require 'org)= by
=(require 'org-loaddefs)= which seems to be the way that Emacs is moving
for packages?

Thanks,
eric

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.2.50.1 and Org release_7.9.2-406-g2c78ca

Re: [O] From latest maint/master, no need to (require 'org-install)

[Eric Fraga]

Bastien  writes:

> Hi all again,
>
> Bastien  writes:
>
>> there is no need to (require 'org-install) anymore from the maint
>> and master branches.
>
> ... and you should actually remove (require 'org-install) from your
> configuration, since this file is not automatically created anymore.
>
> Thanks,

Okay but with what should I replace this, if anything?

Specifically, I currently have (in my organically grown customisation
file ;-):

--8<---cut here---start->8---
(add-to-list 'load-path "~/git/org-mode")
(add-to-list 'load-path "~/git/org-mode/lisp")
(add-to-list 'load-path "~/git/org-mode/contrib/lisp/")
(require 'org-install)
(require 'org-e-latex)
(require 'org-e-odt)
(require 'org-latex)
(require 'org-mime)
(require 'ob-jacaranda)
(require 'ob-python)
(require 'ob-R)
(require 'ob-sh)
(require 'org-crypt) (org-crypt-use-before-save-magic)
(require 'org-inlinetask)   ;binding C-c C-x t
(require 'org-protocol)
(require 'org-wc) 
;; customisations follow
--8<---cut here---end--->8---

What should I or could I remove from this?

Thanks,
eric

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.2.50.1 and Org release_7.9.2-350-g934208

Re: [O] [bug] org-agenda-diary-entry fails on redisplay of the agenda

[Eric Fraga]

Hi Bastien,

I tracked the problem down!

There was a change, in commit b508ff69 two or so weeks ago, to the
argument sequence of org-agenda-format-item which I was using to extract
the time information from the diary entry so that I could sent that to
my Outlook calendar!  This meant that I was passing t for the TAGS
argument whereas I had intended t for DOTIME.

Arg.  There's probably an easier way to do what I want but what I
have works; obviously fragile but anything to do with Outlook (and MS in
general) is fraught with danger... :(

Again, my apologies for the noise.

Thanks again,
eric

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.2.50.1 and Org release_7.9.2-350-g934208

Re: [O] [bug] org-agenda-diary-entry fails on redisplay of the agenda

[Eric Fraga]

Bastien  writes:

> Hi Eric,
>
> Eric Fraga  writes:
>
>> I am not entirely sure what you mean but I have tested this now with an
>> empty diary.org file (i.e. no tags at all in that file at least) and I
>> get:
>
> I've pushed a fix, please let me know if it solves your problem.

Hi Bastien,

Thanks for this.  Unfortunately, it does not fix the problem.  I have
updated to latest org version and get the same error, as near as I can
tell.

However, I have bitten the bullet and gone through my customisations to
remove all diary related entries.  After some bisecting, I have found
that one of my /advices/ was affecting org's diary entry process.  I
have disabled the advice (specifically, one used to propagate new diary
entries to my Outlook and Google calendars automatically) and the
problem has disappeared.

I must not be preserving the state as well as I expected in the advice
function.Why it worked before and not now, I have no
idea.  Yet.

Apologies for the noise.

Thanks,
eric

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.2.50.1 and Org release_7.9.2-350-g934208

Re: [O] [bug] org-agenda-diary-entry fails on redisplay of the agenda

[Eric Fraga]

Bastien  writes:

> Hi Eric,
>
> Eric Fraga  writes:
>
>> I should note that
>> I have set org-agenda-diary-file to point to an org file instead of the 
>> default
>> Emacs diary file and that file is based on a date-tree layout.
>
> Can you get this error with a limited set of (tagged) items?

Hello Bastien,

I am not entirely sure what you mean but I have tested this now with an
empty diary.org file (i.e. no tags at all in that file at least) and I
get:

--8<---cut here---start->8---
Debugger entered--Lisp error: (wrong-type-argument sequencep t)
  mapcar((lambda (tg) (if (or (and hide-re (string-match hide-re tg)) (and (not 
add-inherited) (get-text-property 0 (quote inherited) tg))) nil tg)) t)
  (delq nil (mapcar (function (lambda (tg) (if (or (and hide-re (string-match 
hide-re tg)) (and (not add-inherited) (get-text-property 0 ... tg))) nil tg))) 
tags))
  (setq tags (delq nil (mapcar (function (lambda (tg) (if (or (and hide-re ...) 
(and ... ...)) nil tg))) tags)))
  (progn (if (string-match "\\([]+\\)\\(:[[:alnum:]_@#%:]+:\\)[ 
]*$" txt) (setq txt (substring txt 0 (match-beginning 0 (setq tags (delq 
nil (mapcar (function (lambda (tg) (if (or ... ...) nil tg))) tags))) (if tags 
(progn (let ((have-i (get-text-property 0 (quote inherited) (car tags))) i) 
(setq txt (concat txt " :" (mapconcat (function ...) tags ":") (if have-i "::" 
":")))
  (if (or add-inherited hide-re) (progn (if (string-match "\\([ 
]+\\)\\(:[[:alnum:]_@#%:]+:\\)[ ]*$" txt) (setq txt (substring txt 0 
(match-beginning 0 (setq tags (delq nil (mapcar (function (lambda (tg) (if 
... nil tg))) tags))) (if tags (progn (let ((have-i (get-text-property 0 ... 
...)) i) (setq txt (concat txt " :" (mapconcat ... tags ":") (if have-i "::" 
":"
  org-agenda-fix-displayed-tags(#("test 5" 0 6 (org-heading t)) t t nil)
  (setq txt (org-agenda-fix-displayed-tags txt tags 
org-agenda-show-inherited-tags org-agenda-hide-tags-regexp))
  (progn (setq txt (org-trim txt)) (setq txt (org-agenda-fix-displayed-tags txt 
tags org-agenda-show-inherited-tags org-agenda-hide-tags-regexp)) (let* 
((category (or category (if (stringp org-category) org-category (and 
org-category (symbol-name org-category))) (if buffer-file-name 
(file-name-sans-extension (file-name-nondirectory buffer-file-name)) ""))) 
(category-icon (org-agenda-get-category-icon category)) (category-icon (if 
category-icon (propertize " " (quote display) category-icon) "")) (tag (if tags 
(nth (1- (length tags)) tags) "")) time effort neffort (ts (if dotime (concat 
(if (stringp dotime) dotime "") (and org-agenda-search-headline-for-time 
txt (time-of-day (and dotime (org-get-time-of-day ts))) stamp plain s0 s1 
s2 rtn srp l duration thecategory) (and (derived-mode-p (quote org-mode)) 
buffer-file-name (add-to-list (quote org-agenda-contributing-files) 
buffer-file-name)) (if (and dotime time-of-day) (progn (if (or (setq stamp 
(string-match org-stamp-time-of-day-regexp ts)) (setq plain (string-match 
org-plain-time-of-day-regexp ts))) (progn (setq s0 (match-string 0 ts) srp (and 
stamp ...) s1 (match-string ... ts) s2 (match-string ... ts)) (if (and 
org-prefix-has-time org-agenda-remove-times-when-in-prefix ... ... ... ...) 
(setq txt ... (if s1 (setq s1 (org-get-time-of-day s1 (quote string) t))) 
(if s2 (setq s2 (org-get-time-of-day s2 (quote string) t))) (if (and s1 (not 
s2) org-agenda-default-appointment-duration) (progn (setq s2 
(org-minutes-to-hh:mm-string ... (if s2 (progn (setq duration (- ... 
...)) (if (string-match "\\([ ]+\\)\\(:[[:alnum:]_@#%:]+:\\)[   
  ]*$" txt) (progn (if (or (eq org-agenda-remove-tags t) (and 
org-agenda-remove-tags org-prefix-has-tag)) (setq txt (replace-match "" t t 
txt)) (setq txt (replace-match (concat ... ...) t t txt) (if 
(derived-mode-p (quote org-mode)) (progn (setq effort (condition-case nil 
(org-get-effort (or ... ...)) (error nil))) (if effort (progn (setq neffort 
(org-duration-string-to-minutes effort) effort (setq effort ...)) (or 
effort (setq effort "")) (if remove-re (progn (while (string-match remove-re 
txt) (setq txt (replace-match "" t t txt) (add-text-properties 0 (length 
txt) (quote (org-heading t)) txt) (setq time (cond (s2 (concat 
(org-agenda-time-of-day-to-ampm-maybe s1) "-" 
(org-agenda-time-of-day-to-ampm-maybe s2) (if org-agenda-timegrid-use-ampm " 
"))) (s1 (concat (org-agenda-time-of-day-to-ampm-maybe s1) (if 
org-agenda-timegrid-use-ampm " " ".."))) (t "")) extra (or (and 
(not habitp) extra) "") category (if (symbolp category) (symbol-name category) 
category) thecat

[O] [bug] org-agenda-diary-entry fails on redisplay of the agenda

[Eric Fraga]

Hello,

sometime in the past few weeks, something has changed that has led
to problems inserting items in my diary from the agenda view, using
"i d" (org-agenda-diary-entry).  The traceback is

--8<---cut here---start->8---
Debugger entered--Lisp error: (wrong-type-argument sequencep t)
  mapcar((lambda (tg) (if (or (and hide-re (string-match hide-re tg)) (and (not 
add-inherited) (get-text-property 0 (quote inherited) tg))) nil tg)) t)
  (delq nil (mapcar (function (lambda (tg) (if (or (and hide-re (string-match 
hide-re tg)) (and (not add-inherited) (get-text-property 0 ... tg))) nil tg))) 
tags))
  (setq tags (delq nil (mapcar (function (lambda (tg) (if (or (and hide-re ...) 
(and ... ...)) nil tg))) tags)))
  (progn (if (string-match "\\([]+\\)\\(:[[:alnum:]_@#%:]+:\\)[ 
]*$" txt) (setq txt (substring txt 0 (match-beginning 0 (setq tags (delq 
nil (mapcar (function (lambda (tg) (if (or ... ...) nil tg))) tags))) (if tags 
(progn (let ((have-i (get-text-property 0 (quote inherited) (car tags))) i) 
(setq txt (concat txt " :" (mapconcat (function ...) tags ":") (if have-i "::" 
":")))
  (if (or add-inherited hide-re) (progn (if (string-match "\\([ 
]+\\)\\(:[[:alnum:]_@#%:]+:\\)[ ]*$" txt) (setq txt (substring txt 0 
(match-beginning 0 (setq tags (delq nil (mapcar (function (lambda (tg) (if 
... nil tg))) tags))) (if tags (progn (let ((have-i (get-text-property 0 ... 
...)) i) (setq txt (concat txt " :" (mapconcat ... tags ":") (if have-i "::" 
":"
  org-agenda-fix-displayed-tags(#("test 3" 0 6 (org-heading t)) t t nil)
  (setq txt (org-agenda-fix-displayed-tags txt tags 
org-agenda-show-inherited-tags org-agenda-hide-tags-regexp))
  ...
  org-agenda-format-item(nil #("test 3" 0 6 (org-heading t)) nil nil t)
  org-agenda-add-entry-to-org-agenda-diary-file(day #("test 3" 0 6 (org-heading 
t)) (9 30 2012))
  ...
  org-agenda-diary-entry-in-org-file()
  ...
  org-agenda-diary-entry()
  call-interactively(org-agenda-diary-entry nil nil)
--8<---cut here---end--->8---

I've cut out some of the lines.

I cannot reproduce this with a minimal emacs so there is something in my
configuration that is causing the problem, I guess.  I should note that
I have set org-agenda-diary-file to point to an org file instead of the default
Emacs diary file and that file is based on a date-tree layout.

The actual entry does get inserted in the diary; it is the redisplay of
the agenda that fails.

Inserting into this diary has worked for yonks.

>From vc-annotate, I can see that some lines near where the error occurs
were changed in the past month with commit 8365b738.  However, these
don't appear to be anything relevant; not that I can really say this
with any certainty, mind you :(.  Further searching doesn't highlight
anything obvious either.

Any advice or help would be welcome!

Thanks,
eric

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.2.50.1 and Org release_7.9.1-452-g7d8a0c

Re: [O] [bug] COMMENT alone on heading ignored by new exporter

[Eric Fraga]

Nicolas Goaziou  writes:

> Hello,
>
> Eric Fraga  writes:
>
>> I often use COMMENT in headlines to block out text that I don't want
>> exported.  This works generally very well.  However, sometimes I comment
>> a headline that has no headline text, as in "* COMMENT" alone.  These
>> sections are ignored properly by the old exporter but not the new one.
>
> This is fixed. Thank you for the report.

Thanks.  Works fine now!
-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.2.50.1 and Org release_7.9.1-412-g75820c

Re: [O] Remembrance Agent and Orgmode

[Eric Fraga]

Hi,

sorry I am coming late to this thread.  I use the Remembrance Agent.  It
works great for me, trawling both emails and all my text (org, latex,
etc.) documents automatically for similarities in text while I
write.  It's ideal for academic writing (papers, proposals).

The agent is not intrusive at all, assuming you have a large enough
display and works particularly well if you use a display in portrait
orientation, as I do for writing.

There are two elements to setting this up: the emacs side and the
remembrance agent itself.  For emacs, my settings are straightforward:

#+begin_src emacs-lisp
(setq hilit-background-mode 'dark) ; if you have a dark background, obviously 
;-)
(require 'remem)
(setq remem-database-dir "/home/ucecesf/s/share/remembrance-agent"
  remem-load-original-suggestion t
  remem-prog-dir "/usr/bin"
  remem-scopes-list '(("documents" 4 5 500)
  ("mail" 4 10 500)
  ))
#+end_src

For the agent itself, I use cron to update the databases every night
with an entry that looks like this:

,
| 12 4 * * * sh /home/ucecesf/s/bin/ra-buildindices.sh
`

The contents of that shell script are:

#+begin_src sh
#!/bin/sh -f
B="/home/ucecesf/s/share/remembrance-agent"
ra-index ${B}/mail ${HOME}/s/News/agent/nnimap/ucl > /dev/null
ra-index ${B}/documents ${HOME}/s/notes ${HOME}/s/grants ${HOME}/s/talks 
${HOME}/s/papers ${HOME}/s/projects > /dev/null
#+end_src

In all of the above, you will need to change all the appropriate paths
for the location of the databases and the places to search.  The two
index commands trawl my emails and my relevant documents respectively.

I hope this helps.

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.2.50.1 and Org release_7.9.1-412-g75820c

[O] [bug] COMMENT alone on heading ignored by new exporter

[Eric Fraga]

Hello,

I often use COMMENT in headlines to block out text that I don't want
exported.  This works generally very well.  However, sometimes I comment
a headline that has no headline text, as in "* COMMENT" alone.  These
sections are ignored properly by the old exporter but not the new one.

This is a minor bug; all you have to do is add any text after the
COMMENT.  I thought it would be easy to figure out where this is going
wrong but I was unable to.  Sorry!

Example org and exported tex files attached.

Thanks,
eric

PS - I've been silent on this list for months now; it's annoying how
work can interfere with what I would rather be doing... :(

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.2.50.1 and Org release_7.9.1-225-ga5756f
* first
  some text
* second
  some text which should appear in the new exporter
*** second first
some text which should appear
*** COMMENT second third
some text which should not appear
*** COMMENT 
some text which should not appear *but* does actually appear unfortunately in the new exporter, although not in the old one.
* COMMENT third
  some text which should not appear
% Created 2012-09-29 Sat 01:04
\documentclass{scrartcl}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{fixltx2e}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{float}
\usepackage{wrapfig}
\usepackage{soul}
\usepackage{textcomp}
\usepackage{marvosym}
\usepackage[integrals]{wasysym}
\usepackage{latexsym}
\usepackage{amssymb}
\usepackage{hyperref}
\tolerance=1000
\usepackage{xcolor}
\usepackage{listings}
\usepackage{amsmath}
\author{Eric Fraga}
\date{\today}
\title{comment}
\hypersetup{
  pdfkeywords={},
  pdfsubject={},
  pdfcreator={Generated by Org mode 7.9.1 in Emacs 24.2.50.1.}}
\begin{document}

\maketitle
\tableofcontents
\vspace*{1cm}

\section{first}
\label{sec-1}
some text

\section{second}
\label{sec-2}
some text which should appear in the new exporter
\subsection{second first}
\label{sec-2-1}
some text which should appear

\subsection{COMMENT}
\label{sec-2-2}
some text which should not appear \textbf{but} does actually appear unfortunately in the new exporter, although not in the old one.
% Generated by Org mode 7.9.1 in Emacs 24.2.50.1.
\end{document}

Re: [O] essentially turn off font-lock except for headings

[Eric Fraga]

Enda  writes:

> Is there a way to do this on a per-file setting?

Not that I am aware of.
Sorry.

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.1.50.1 and Org release_7.8.11-14-g4b0121

Re: [O] LaTeX export -- Table with align option

[Eric Fraga]

Sebastien Vauban  writes:

> Hello,
>
> I want to customize a bit the layout of a table, using the =align= parameter 
> as
> explained on http://orgmode.org/manual/Tables-in-LaTeX-export.html.
>
> That works well for the first two common usages (see ECM) but not with
> @-expressions (see, for example, on

Actually, it's not the @ expressions as such that cause the problems,
it's the spaces you are trying to introduce within them, causing the org
parser to terminate the alignment term too soon.  Two solutions below.

[...]

> #+ATTR_LaTeX: align=r@{ : }r@{ }l

[...]

> gets INCORRECTLY translated to:
>
> #+begin_src latex
> \begin{tabular}{r@{}

[...]


I know this isn't pretty but you could use

  #+ATTR_LaTeX: align=r@{\hspace{1em}:\hspace{1em}}r@{\hspace{1em}}l

changing the 1em to whatever amount of space you actually want; probably
1ex is more likely...

The following also works but although it looks simpler here (in an
email), I don't like how Org hides the ~s in the first column
specification as it (incorrectly) interprets them as a verbatim style.

  #+ATTR_LaTeX: align=r@{~:~}r@{~}l

HTH,
eric

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org release_7.8.11-14-g4b0121

Re: [O] [bug] org-e-html reference to undefined org-export-coding-system

[Eric Fraga]

Nicolas Goaziou  writes:

> Hello,
>
> Eric S Fraga  writes:
>
>> with org from git as of a few minutes ago, I cannot load org.  I get the
>> following backtrace when I start emacs with --debug-init:
>>
>> ,
>> | Debugger entered--Lisp error: (void-variable org-export-coding-system)
>> |   eval(org-export-coding-system)

[...]

> I fixed it (with a temporary kludge) a few minutes ago. Could you pull
> again and tell me if it's ok?

Confirmed!  Works fine now.  Thanks.

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1 + Ma Gnus v0.6

Re: [O] org-export-preprocess-hook and the new exporter (was Re: Using Org for a dissertation)

[Eric Fraga]

Nicolas Goaziou  writes:

> Hello,
>
> Eric S Fraga  writes:
>
>> This is probably more for Nicolas... and apologies for hijacking the
>> thread slightly!
>>
>> I was intrigued by the comment above regarding the ignoreheading
>> tag.  Sounded just like what I needed.  However, it doesn't do anything
>> with org /out-of-the-box/.  A little searching led to Suvayu's posting
>> in stackoverflow [1] and that does the job nicely, but only for the
>> standard (read: old) export engine.
>>
>> The question is: is there an equivalent hook for the new exporter?
>
> For heavy structure modifications (like headlines removal), there is
> `org-export-before-parsing-hook' and the dynamically bound variable
> `org-export-current-backend'.
>
> Another way to solve the problem could be to implement your own headline
> parser:
>
> #+BEGIN_SRC emacs-lisp
> (defun my-e-latex-headline (headline contents info)
>   (if (member "ignoreheading" (org-element-property :tags headline)) contents
> (org-e-latex-headline headline contents info)))
> #+END_SRC
>
> Then you can either install it in the current `e-latex' back-end:
>
> #+BEGIN_SRC emacs-lisp
> (add-to-list 'org-e-latex-translate-table '(headline . my-e-latex-headline))
> #+END_SRC

Nicolas,

I tried this but I get:

,
| Warning (initialization): An error occurred while loading 
`/home/ucecesf/.emacs':
| 
| Symbol's value as variable is void: org-e-latex-translate-table
| 
| To ensure normal operation, you should investigate and remove the
| cause of the error in your initialization file.  Start Emacs with
| the `--debug-init' option to view a complete error backtrace.
`

I think it should be 

#+BEGIN_SRC emacs-lisp
 (add-to-list 'org-e-latex-translate-alist '(headline . my-e-latex-headline))
#+END_SRC

i.e. =alist= instead of =table=.

In any case, with this change, it works like a charm!  Many thanks.

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org release_7.8.09-527-gc2aac5

Re: [O] Babel, gnuplot, post processing

[Eric Fraga]

skip  writes:

> How can I perform post processing on eps files produced by gnuplot
> source blocks? I want to take out the extra white space margins in the
> eps file by running eps2eps utility on the eps file produced by
> gnuplot.

The easiest solution (although maybe not the most elegant) is to do this
from within gnuplot.  I do something similar in that I process the eps
to create a pdf.

#+begin_src gnuplot :file xxx.pdf
  reset
  clear
  set output 'xxx.eps'
  set terminal postscript eps enhanced 18
  ...
  plot ...
  ! epstopdf xxx.eps
#+end_src

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org release_7.8.09-527-gc2aac5

Re: [O] taskjuggler (tj3) export issues and proposals

[Eric Fraga]

Bastien  writes:

> Hi Eric,
>
> Eric S Fraga  writes:
>
>> However, I am again starting to write some proposals that will need
>> GANTT charts so maybe I can justify looking at this again.
>
> good to know you are back on this!  No matter how far you go, Org 
> will always find you :)
>
> Best,

Thanks.  Despite being quiet on the list for a few months, I can assure
you that org was with me the whole time!  I would have a hard time
functioning any longer without it.

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org release_7.8.09-527-gc2aac5

Re: [O] orgstuct++ does not lurk silently in the shadow

[Eric Fraga]

Bastien  writes:

> Hi Nicolas,
>
> Nicolas Goaziou  writes:
>
>> ((adaptive-fill-function (quote nil)) (adaptive-fill-regexp (quote \(\([
>
> [...]
>
> This looks good.
>
>> It's the same as the previous bug: when I try to debug
>> `org-indent-line-function', the problem disappears.
>
> I pushed another fix: I now rely on the existing org-let
> function, which safely evaluate let constructs.

Bastien,

unfortunately, I still have problems.  I am using org completely up to
date (a few minutes ago).  I do not turn orgstruct++-mode on
automatically at all any more but instead turn it on manually by

  M-x orgstruct++-mode RET

once I'm in a Message buffer.

I tried it just now, replying to your email as my test.  Turned on the
mode, tried to fill the quoted text and it all got mixed up.  Undid
that.  Then went to the bottom and tried to insert a new line and got:

  org-indent-line-function: Lisp nesting exceeds `max-lisp-eval-depth'

Turned off orgstruct++-mode (by M-x ... RET again) and filling of quoted
text works fine as does normal writing.

I will try (tomorrow) to isolate this with emacs -Q but my problem is
that my gnus configuration is really really messy and difficult to
isolate.

Thanks,
eric

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org release_7.8.09-489-g541288

Re: [O] [bug] new exporter fails on read only files

[Eric Fraga]

Nicolas,

unfortunately, I have immediately run into another problem with the new
exporter (to latex) when going back to my long document (a project
proposal).

I have a minimal example which illustrates the problem.  The attached
are a simple org file with the resulting latex file.  The key problem is
that the =tabular= command has an empty argument, the argument that is
meant to specify the table alignments.

Specifically,  the new exporter generates:

,
| \begin{center}
| \begin{tabular}{}
| \hline
| Task & Q1 & Q2 & Q3 & Q4 & Q5 & Q6 & Q7 & Q8 & Q9 & Q10 & Q11 & Q12\\
`

whereas the old one generates

,
| \begin{center}
| \begin{tabular}{l}
| \hline
|  Task&  Q1  &  Q2  &  Q3 [...]
`

(last line truncated by me as it was too long)

This is with org up to date from a few minutes ago (see signature).  For
the new exporter, I started emacs with -Q and then:

#+begin_src emacs-lisp
(add-to-list 'load-path "~/git/org-mode")
(add-to-list 'load-path "~/git/org-mode/lisp")
(add-to-list 'load-path "~/git/org-mode/contrib/lisp/")
(require 'org-install)
(require 'org-export)
(require 'org-e-latex)
#+end_src

Thanks,
eric

#+TITLE: examplebug.org
#+AUTHOR:Eric S Fraga
#+EMAIL: e.fr...@ucl.ac.uk
#+DATE:  2012-01-09 Mon

#+latex_header: \newcommand{\deliverable}[1]{D\ref{deliverable:#1}}

* new exporter
  <>

  This section illustrates a simple bug in the new exporter, I think.

  The project has the following deliverables:

  1. \label{deliverable:evaporative-model} The evaporative model
  2. \label{deliverable:system-model} The system model
  3. \label{deliverable:control-model} The control model
  4. \label{deliverable:control-model-recycle} ... and with a recycle
  5. \label{deliverable:preprocessing-system} ... and with preprocessing

 
  The work plan for this project is shown in the following table:

  #+latex: \renewcommand{\arraystretch}{1.5}
 
  |+++-++++-+-++-+-+|
  | Task   | Q1 | Q2 | Q3  | Q4 | Q5 | Q6 | Q7  | Q8  | Q9 | Q10 | Q11 | Q12|
  |+++-++++-+-++-+-+|
  | \ref{sec:evaporative}  | XX | XX | XX  |||| | || | ||
  | \ref{sec:systems}  ||| | XX | XX || | || | XX  ||
  | \ref{sec:control}  ||| ||| XX | XX  | XX  || | | XX |
  | \ref{sec:desalination} ||| |||| | | XX | XX  | ||
  |+++-++++-+-++-+-+|
  | Deliverables   ||| \deliverable{evaporative-model} || \deliverable{system-model} || \deliverable{control-model} | \deliverable{control-model-recycle} || | | \deliverable{preprocessing-system} |
  |+++-++++-+-++-+-+|
 


% Created 2012-05-06 Sun 23:21
\documentclass[11pt]{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{fixltx2e}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{float}
\usepackage{wrapfig}
\usepackage{soul}
\usepackage{textcomp}
\usepackage{marvosym}
\usepackage{wasysym}
\usepackage{latexsym}
\usepackage{amssymb}
\usepackage{hyperref}
\tolerance=1000
\newcommand{\deliverable}[1]{D\ref{deliverable:#1}}
\providecommand{\alert}[1]{\textbf{#1}}
\author{Eric S Fraga}
\date{2012-01-09 Mon}
\title{examplebug.org}
\hypersetup{
  pdfkeywords={},
  pdfsubject={},
  pdfcreator={Generated by Org mode 7.8.09 in Emacs 24.1.50.1.}}
\begin{document}

\maketitle
\tableofcontents
\vspace*

Re: [O] orgstuct++ does not lurk silently in the shadow

[Eric Fraga]

Bastien  writes:

> Hi Christopher,
>
> I've now fixed orgstuct++-mode so that you can turn it on and off
> safely.  Some Org filling functions fall back on the major-mode
> filling functions through a new defmacro.
>
> Please test and report any problem.
>
> Thanks!

Ummm, doesn't work well for me at all.  If I try to fill your main
paragraph above, the whole quoted text is filled into one
mess.  Without orgstuct++-mode, it works.

Further, with orgstuct++-mode, trying to add a new line (i.e. my
response), I get the following error message:

,
| org-indent-line-function: Lisp nesting exceeds `max-lisp-eval-depth' [3 times]
`

with the following backtrace:

,
| Debugger entered--Lisp error: (error "Lisp nesting exceeds 
`max-lisp-eval-depth'")
|   org-indent-line-function()
|   org-indent-line-function()
|   org-indent-line-function()
|   ... repeated ad infinitum ...
`

thanks,
eric

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org release_7.8.09-482-gf47915

Re: [O] [bug] new exporter fails on read only files

[Eric Fraga]

Nicolas Goaziou  writes:

> Hello,
>
> Eric Fraga  writes:
>
>> Actually, I have updated (one minute ago) and the problem has now
>> changed!  I now get this error:
>>
>> ,
>> | and: Wrong type argument: stringp, (latex-fragment (:value 
>> "\\ref{sec:evaporative}" :begin 11957 :end 11978 :post-blank 0))
>> `
>
> This is a bit short to start investigations. Something is happening at
> position 11957 in your buffer. You may want to narrow it to the
> paragraph/table/construct around and try to export it again. It could
> make a minimal example.

Okay, I have investigated.  Attached is a simple example which
illustrates the problem which appears to be use of a latex macro within
a table.  Are latex macros still allowed?  I have used emacs -Q and
loaded in the new export etc.  No customisations.

The error message for this example is:

,
| and: Wrong type argument: stringp, (latex-fragment (:value "\\ref{sec:bug}" 
:begin 322 :end 335 :post-blank 0))
`

> You may also try (org-element-parse-buffer) to see if the error comes
> from the parser or the export engine. You could even try to export to

It's the export engine and it's due to my \ref{...} having the \
escaped, which should not happen.

Thanks,
eric

#+TITLE: examplebug.org
#+AUTHOR:Eric S Fraga
#+EMAIL: e.fr...@ucl.ac.uk
#+DATE:  2012-01-09 Mon

* new exporter
  \label{sec:bug}

  This section illustrates a simple bug in the new exporter, I think.

  | Section   | Description|
  |---+|
  | \ref{sec:bug} | An illustration of the bug |
  |---+|

  The table has a reference using a direct latex command.



-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org release_7.8.09-414-gb3e8a8

Re: [O] Some settings are missing while exporting included org files to the tex file

[Eric Fraga]

Keith  writes:

> Dear Org-mode users:
>
> Recently I am considering using org-mode to write my thesis and would 
> like to separate each chapter into a single file. In order to do so, I 
> created a file gathering all the rest files like this:

[...]

> In addition, I also tried to export a single org file without any 
> preamble to be able to use input/include in latex but with no luck. And 
> it seems org mode does not support this function yet. I would recommend 
> the development team to re-consider this feature. Now the tex output of 
> org mode draws all the separate files into single tex file and the user 
> has to compile the entire tex file every time. By doing so, it also 
> misses the feature of LaTex as mentioned here: 
> http://web.science.mq.edu.au/~rdale/resources/writingnotes/latexstruct.html
>

Keith,

I cannot help you with the bulk of your email, regarding the use of
#+include to bring in different chapters etc into a document and/or the
possibility of working on each individual chapter in turn.

However, because of these limitations, that I also ran into a long time
ago, I simply put everything into one document.  The advice given in the
web page noted above is directed at LaTeX but is less necessary for org
files.  The motivation is the need or desire to work on smaller bits at
a time to have things go quicker, I believe.  The easy way to handle
this in org is to use selective exporting, primarily through the use of
tags.

So, for instance, if I am working on a long document and am currently
working on chapter 2 of this document, my document would look like this:

,
| ... |
| #+EXPORT_SELECT_TAGS: export|
| #+EXPORT_EXCLUDE_TAGS: noexport |
| ... |
| * Introduction ...   :noexport: |
| * Chapter 1 ...  :noexport: |
| * Chapter 2 |
| ... |
| * Chapter 3 ...  :noexport: |
| ... |
`

When asking for an export, only Chapter 2 would be exported.

It is trivial to add/remove the noexport tags.

The only difficulty with this arises when you need latex material at the
*end* of the document, such as bibliography settings.  For this, I
simply create a final "* Postamble" section which is exported.  When my
document is finished, I simply remove the heading line and re-export the
whole document.

A minor irritation appears if you have cross-references between chapters
but that really is nothing more than an irritation so I have learnt to
ignore it.

HTH,
eric

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org release_7.8.09-414-gb3e8a8

Re: [O] orgstuct++ does not lurk silently in the shadow

[Eric Fraga]

Eric Fraga  writes:


[...]

> Bastian,
>
> Filling seems to work much better now but I don't know whether any of
> this is org or gnus.  

Actually, I just noticed from my modeline that OrgTbl is
active.  However, I have searched everything in my configuration and
cannot see where I turn this on!  I am perturbed :(

The point being that orgstruct++-mode does cause problems with
indentation and filling in email messages but without it, but with
OrgTbl maybe, filling is working very nicely now.

Thanks again,
eric


-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org release_7.8.09-414-gb3e8a8

Re: [O] orgstuct++ does not lurk silently in the shadow

[Eric Fraga]

Bastien  writes:

> Hi Eric,
>
> Eric Fraga  writes:
>
>> Thanks for this.  This behaviour has annoyed me for years now.  
>
> Me too...
>
>> I've
>> never gotten around to figuring out why I got this behaviour because I
>> get caught up with writing the email and forget by the time I finish...
>>
>> I hope somebody can indeed fix this as it sounds quite straightforward
>> (for better elisp programmers than I...).
>
> This should be fixed now in master.
>
> Can you confirm?
>
> There is one remaining use-case I didn't fix: the case where you use M-q
> on the first line of the message (things are messed up then.)  I don't
> know how to fix this, but this is a rather border-line case, as simply
> typing and using auto-fill does the right thing.
>
> Thanks for insisting on this!

Bastian,

Filling seems to work much better now but I don't know whether any of
this is org or gnus.  However, I am not sure what is happening
here.  With the following line in my configuration:

(add-hook 'message-setup-hook 'turn-on-orgstruct++)

all my emails end up indented strangely.  Specifically, if this email
had been composed with that hook entry, all my lines would have been
indented 2 spaces.  See my previous message to this list if you can find
such easily...

I commented out that line in my configuration and restarted Emacs to
compose this reply.  No indenting is happening (which is a good thing).

Very strange.  I do not understand why turning on orgstuct++ would cause
a default indentation of all text.

I am happy to explore this further if you give me some hint as to what
to try.

I am using gnus and org up to date as of yesterday (Australia time).  I
haven't updated today yet.

Thanks,
eric

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org release_7.8.09-414-gb3e8a8

Re: [O] mail integration, advice?

[Eric Fraga]

Rasmus  writes:

> Eric Fraga  writes:
>
>> Rasmus  writes:
>
> As this is becoming somewhat of a dovecot thread I've got a question:
>
> Often, after resuming the computer from standby, say, Gnus looses the
> connection to Dovecot.  I have to press `g' three times it updates mail
> group and each time I must wait for it to time out. 
>
> Has anyone found a solution to this bothersome issue?
>
> Thanks,
> Rasmus

  Not sure but you could try going to the server list (^ from the Group
  buffer) and then hit O on the server you want to connect to?

  Alternatively, you might try (from the Group buffer) telling gnus to
  unplug (J j) and then plug back in (J j).

  I cannot verify that either of these will work as the problem might be
  with dovecot.  You could try asking on the gnus mailing list?
  
  HTH,
  eric

  PS - by the way, my lines are all indented because between yesterday
  and today, something has changed in either gnus or org!  Paragraph
  filling is working nicely in one sense but everything is indented more
  than I would like.  Haven't explored the cause yet...
  
-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org release_7.8.09-414-gb3e8a8

Re: [O] Per file customisation of sectioning structure in latex export

[Eric Fraga]

Vikas Rawal  writes:

> I would like to specify the correspondence between heading levels and
> sectioning structure for latex export in a specific file. Could
> somebody point me to the right method. I have checked
>  on
> worg. Isn't there a way by which I could specify this in the header.
>
> I am using latex class "article". Isn't it possible to the sectioning
> structure through #+LATEX_CLASS_OPTIONS?
>
> Vikas


You probably want to look at

,[ C-h v org-export-latex-classes RET ]
| org-export-latex-classes's value is shown below.
| 
| Documentation:
| Not documented as a variable.
| 
| Value: (("article" "\\documentclass{scrartcl}"
|   ("\\section{%s}" . "\\section*{%s}")
|   ("\\subsection{%s}" . "\\subsection*{%s}")
|   ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
|   ("\\paragraph{%s}" . "\\paragraph*{%s}")
|   ("\\subparagraph{%s}" . "\\subparagraph*{%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}"))
|  ("beamer" "\\documentclass{beamer}" org-beamer-sectioning))
| 
| [back]
`

Each entry in the list is a list which has the name of the type of
document, the latex class command and then a list of latex commands to
use for the heading levels.  Each heading level is given two latex
commands, one for numbered headings and one for unnumbered.  The choice
of numbered vs unnumbered is through the num: option.  You can generate
a template in your org file with default options and other settings
using C-c C-e t.
  
-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org release_7.8.09-414-gb3e8a8

Re: [O] mail integration, advice?

[Eric Fraga]

Stephen Eglen  writes:

> A relatively new emacs mailer, mu4e, is worth mentioning:
>
> http://www.djcbsoftware.nl/code/mu/mu4e.html

Somewhat surreal to bring up this page, look at the second screen shot
and see my name on the first line!  Not to mention the usual suspects
from the org mailing list as well ;-).
-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org release_7.8.09-406-g0233eb

Re: [O] mail integration, advice?

[Eric Fraga]

Eric Schulte  writes:

> As a long-time user of gnus with imap my only complaints are the
> inability to work offline and the relatively poor sorting rules of my
> web-mail imap servers.  It sounds like dovecot and offline-imap could
> solve both of these problems.

I used to use offline-imap + dovecot when I used wl and things worked
very well indeed.  When I moved to gnus, I used the gnus agent which
also now works very well (there was a period of instability a year or
two ago).  The gnus agent fully supports offline use (gnus-unplugged).
  
-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.09 (release_7.8.09-406-g0233eb @ 
/home/ucecesf/git/org-mode/lisp/org-install.el)

Re: [O] mail integration, advice?

[Eric Fraga]

Rasmus  writes:

> Matt Price  writes:
>
>> I'd like to take one more shot at returning to text-based email within
>> emacs, mostly because I want to be able to integrate mail easily into
>> my org-mode workflow.  
   
> I used wl but switched to Gnus. 

ditto.

>
>> - wl causes emacs to freeze up when it checks or sends mail, and can
>> take quite a long while to complete these operations
>
> I know of no solution to this.  You could run a dedicated Gnus process
> if it bothers you.

This is what I do. I have two emacs instances running all times, one for
email and one for everything else.  The second one includes all org
related stuff.  As I do capture things in org from email (gnus), I do
have to make sure that I save my org files frequently.  There's no issue
in terms of getting stuff lost as org does lock any modified but not
saved files and the other emacs will prompt if you try to save something
to an org file that has not been saved in other emacs.
 
-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.09 (release_7.8.09-406-g0233eb @ 
/home/ucecesf/git/org-mode/lisp/org-install.el)

Re: [O] [bug] new exporter fails on read only files

[Eric Fraga]

Bastien  writes:

> Hi Eric,
>
> Eric Fraga  writes:
>
>> Specifically, I have added
>>
>>(require 'org-export)
>>(require 'org-e-latex)
>>
>> to my org customisation.  Then, while visiting a read only file, I try
>>
>>M-x org-export-dispatch RET p
>
> Mhh.. I can't reproduce this error with latest Org.

Arghhh.  Strange.

>
>> and I get the error:
>>
>> ,
>> | org-refresh-category-properties: Buffer is read-only: #> proposal.org>
>> `
>
> Maybe you have a hook which call this function?

I do not believe so.  Grepping for "category" in my .el files (including
custom variable setting) finds nothing org related.

Obviously, I can try emacs -Q etc and will do so later this weekend
hopefully.

In the meantime:

> In any case, as the other place where `org-refresh-category-properties'
> is called is `org-prepare-agenda-buffers' and those buffers might be
> read-only (for some obscure reason), I pushed a fix that make sure 
> `org-refresh-category-properties' can modify the buffer correctly.
>
> Please let me know if this fixes your problem.

Actually, I have updated (one minute ago) and the problem has now
changed!  I now get this error:

,
| and: Wrong type argument: stringp, (latex-fragment (:value 
"\\ref{sec:evaporative}" :begin 11957 :end 11978 :post-blank 0))
`

and I have no idea what is happening here.  For this error, I do get a
debug trace but it is rather long and my org file has material I cannot
post. The old exporter still works perfectly fine.

I will try emacs -Q later and will also see if I can come up with a
minimal example that fails in the same way as my longer confidential
document.

Thanks,
eric

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.09 (release_7.8.09-392-ge02226 @ 
/home/ucecesf/git/org-mode/lisp/org-install.el)

Re: [O] [babel] hide inline source code blocks by results

[Eric Fraga]

Eric Schulte  writes:


[...]

> I think both this and Torsten's original idea would both be nice
> options.  Preferably the final solution would subsume either use case.
> Unfortunately either implementation would require a fairly significant
> amount of work on the inline source block system, work which I
> unfortunately do not have time for at the moment (although I'm happy to
> help if anyone else wants to jump into the code).

Understood!!  You don't have to tell me about finite time resources :(
But it *is* nice to ponder new syntax for org :-) I even started
thinking of other link type syntax:

 [[inline:octave("3*x+5")]]
 [[call:f(5)]]
 etc.

It's fun.

Thanks,
eric

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.09 (release_7.8.09-392-ge02226 @ 
/home/ucecesf/git/org-mode/lisp/org-install.el)

[O] [bug] new exporter fails on read only files

[Eric Fraga]

Hello all,

>From one of the recent threads (on producing latex files for ACM
publications), I was finally motivated to try the new export engine.  I
have run into a small problem: org-export-dispatch fails if the file is
read only.  I often have read only files as I use RCS as my version
control system for one-off standalone files (as opposed to git or
mercurial for larger projects).

Specifically, I have added

   (require 'org-export)
   (require 'org-e-latex)

to my org customisation.  Then, while visiting a read only file, I try

   M-x org-export-dispatch RET p

and I get the error:

,
| org-refresh-category-properties: Buffer is read-only: #
`

This doesn't happen if I use the old exporter (C-c C-e p).  Also, the
error does not appear if I try the new export engine on a writable
file.  Toggling debug-on-error doesn't actually put me in the debugger
when the error occurs, by the way.

I *think* am running an up to date org (from an hour or so ago) but the
org-version information (auto-generated for my signature) seems
confused...  but maybe that's a problem for another day?

Thanks,
eric

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.06 (release_7.8.09.392.ge0222)

Re: [O] Org tasks from gnus

[Eric Fraga]

Rémi Vanicat  writes:

> Kyle Sexton  writes:
>
>> Does anyone know a way to automatically create/link org-tasks from Gnus
>> messages?  My current workflow is to just start a new capture and type
>> in or paste some of the relevant info, but if org could link to the
>> message that would be ideal.
>
> I've the following recipe in my org-capture-template:
>
>  ("m" "mailnote" entry (file+headline "~/org/notes.org" "Notes")
>   "** From: %:from Subject: %:subject\n   %a" :kill-buffer t)
>
> So when I do `C-c r m` it create a note with a link to the relevant gnus
> message. Look at http://orgmode.org/manual/Template-expansion.html for
> other %:something.

Thanks for this.  Very useful.  I didn't know about the %:from
etc. keywords.

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.06 (release_7.8.09.392.ge0222)

Re: [O] Ever used org-mode contrib packages?

[Eric Fraga]

 On Wed, Apr 11, 2012 at 21:22, François Allisson  
 wrote:
> I'm curious
> to know what you are using from org-contrib...

The only one I use currently is org-mime and even then only infrequently.

However, this thread has spurred me on to have a look at org-collector
as this could prove quite useful to me!

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.06 (release_7.8.06.181.g67694.dirty)

Re: [O] Disable links in Latex export

[Eric Fraga]

Nick Dokos  writes:


[...]

> If all you care about is the *appearance*, rather than the existence of
> links, however, you can use hyperref package options to influence
> that. For example
>
> \usepackage[pdfborder={0,0,0}]{hyperref}
>
> will get rid of the red boxes around the links in the TOC: they are
> still links, they are just not that obvious any more.  You can do that
> by customizing the org-export-latex-default-packages-alist variable:
> just add the above option (without the square brackets) to the hyperref
> package entry.

adding the line

#+latex_header: \hypersetup{pdfborder={0,0,0}}

in the org document should be sufficient?

In practice, I actually do:

#+latex_header: \hypersetup{colorlinks=true}

which still colours the links but gets rid of the ugly boxes.

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.06 (release_7.8.06.181.g67694.dirty)

Re: [O] [babel] hide inline source code blocks by results

[Eric Fraga]

Eric Schulte  writes:

> Currently inline blocks like don't associate themselves with their
> results, they are only expected to be evaluated on export, so the
> functionality you suggest below would require first changing how results
> are associated with inline code blocks.
>
> Another option would be to hide everything but the body of the block,
> but this may be more confusing than it is worth.

Eric,

I do like what Torsten suggested a lot.  I wonder if a halfway solution
would be possible.  Define a babel: link type which includes the src_xxx
code and let the description part of the link be whatever the author
wants it to be.  I wouldn't mind not knowing the result of the code
execution as I don't know that at the moment anyway.

So, something like this would be nice:

... and the result is [[babel:src_octave{3*x+5}][f(x)]] which
demonstrates ...

which would look like

... and the result is f(x) which demonstrates ...

(with f(x) highlighted as a link).

Could something like this be possible?

And, to take this further, could the highlighting differ depending on
link type?  I've not explored this latter aspect so maybe it's already
possible...

thanks,
eric

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.06 (release_7.8.06.181.g67694.dirty)

Re: [O] Updating BibTex file

[Eric Fraga]

Julian Burgos  writes:

> Dear list,
>
> How can I made org mode / reftex to recognize changes in my BibTex
> file?  Here is the scenario.  I have my default BibTex file defined
> with the reftex-default-bibliography variable.  While working on my
> org mode document I am adding references and everything is working
> fine.  The problem occurs when I edit my BibTex file to add new
> references (using JabRef), but the new references do not show up when
> I call 'reftex-citation.
> Any ideas?
> Thanks,
>
> Julian

Don't know whether you got an answer to this but googling

"update reftex when bibliography file changes"

gives a number of useful links.  The first one is actually org related:

http://tincman.wordpress.com/2011/01/04/research-paper-management-with-emacs-org-mode-and-reftex/

and mentions the need to auto-revert the bibliography file. The second
google result says the same thing:

https://josephhall.org/nqb2/index.php/reftex-1

HTH,
eric

PS - I have auto-revert set globally so I would have noticed a problem
but, in any case, I do all my bibtex editing in Emacs ;-)

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.06 (release_7.8.06.181.g67694.dirty)

Re: [O] [beamer] When are :BEAMER_envargs: used or ignored?

[Eric Fraga]

James Harkins  writes:

> At Wed, 25 Apr 2012 18:09:18 +0800,
> James Harkins wrote:
>> > Whether it should be a feature request or not is debatable.  The syntax
>> > is, at present, fairly straightforward in that the headline text becomes
>
>> > the argument to the environment defined.
>> 
>> I think "the headline text becomes the argument..." is the opposite of 
>> straightforward. :-)
>
> OK, wait, I get it:
>
> \begin{alertblock}{HEADLINE TEXT HERE}
>
> \begin{beamercolorbox}{HEADLINE TEXT HERE}
>
> OK, it's a consistent translation.

Yes.

> But I still have the issue with it
> that the user has to adapt the org-file structure to suit beamer's
> requirements. Org-mode is all about reflecting the content in a way
> that makes sense FIRST to humans, and only secondarily to exporting
> engines.

I agree.  However, the problems arise when exporting because of
fundamentally different structures between org and the export
target.  This is why we have the various kludges (if people can forgive
me for calling them this) like ATTR_HTML and ATTR_LATEX.  There is no
easy or elegant mechanism in org for satisfying all the different export
target requirements that are fundamentally inconsistent with org's
outline heritage.

For this particular case, it could be that the beamercolorbox
environment could be made to expect a specific PROPERTY, much like the
column environment does.  The question would then be: what should the
headline be used for as beamercolorbox has no real text content
argument.

I would guess that if you could suggest a consistent and more elegant
solution, it would be considered favourably and maybe somebody would
take it up and implement it.  No promises, however!
-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.06 (release_7.8.06.181.g67694.dirty)

Re: [O] [OT] Defining System, process, methodology and framework

[Eric Fraga]

Marcelo de Moraes Serpa  writes:

... a very interesting philosophical email!

[...]

> level. I then asked myself "What the heck is a system" and what is the
> relationship it has with "process", "methodology" and "frameworks" ?

[...]

Others have answered to some degree or another but I thought I'd throw
in my view (as somebody that dabbles in systems... ;-):

- system :: the set of units (building blocks) *and* their interconnections
- process :: what the system actually "does"
- framework :: the structure on which to /instantiate/ systems
- methodology :: the /guide/ for using the framework to build a system

but the boundaries between these different concepts or views are indeed
fuzzy as it is difficult to talk about any single aspect without
reference to the others.

relating this to org, org is a system implemented on the framework
provided by emacs (elisp) which allows one to execute a number of
different processes (GTD, LP, publishing, ...).  the methodology is
rather less well defined ;-)

This is a really nice point at which to stop reading my backlog of org
mailing list messages!  Time for bed now. Good night all.

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.06 (release_7.8.06.181.g67694.dirty)

Re: [O] [beamer] When are :BEAMER_envargs: used or ignored?

[Eric Fraga]

James Harkins  writes:

> At Wed, 25 Apr 2012 14:11:51 +0930,
> Eric Fraga wrote:
>> > It kind of strikes me like an epic hack: you have to name the headline
>> > after the Beamer color ID, instead of naming the headline after the
>
>> > content... not very /org/anized.
>> 
>> Well, the problem is that a beamercolorbox is *not* a block and does not
>> expect a title parameter.  It actually expects only a colour (well, a
>> beamer colour structure, to be precise, such as the one you have
>> defined).  What is /org/ expected to do with the entry you specify?
>
> If the subtree is folded, then the headline shows the color descriptor
> but nothing about the content of the subtree! That's some distance
> away from "an outline works like your brain."

Yes.  You could, of course, turn my suggestion inside out: have the
block first and then the coloured box as a subheading...  then the main
heading would at least give you an indication of what follows.

> It's not that I can't get the right output. It *is* a pretty stark
> inconsistency against org-mode's governing principle. Here, formatting
> information that is irrelevant to content is promoted to be the *most
> important thing* (the headline) of that subtree. What I need to see,
> in order to understand the structure of the content at a glance --
> this IMO is org-mode's genius -- is hidden if the subtree is
> folded. Hm?
>
> It strikes me as flawed design.

Well, it's a compromise, I would suggest.  most compromises can indeed
be considered flawed design from an aesthetic point of view.  org is
based on outlines, not on containers.  Latex is based on containers
(mostly).  This basic inconsistency comes up all the time on this list
(e.g. a lower level entry can only be ended by starting a new headline
at the same or higher level).

>> > Worth a bug report or feature request?
>> 
>> It is not a bug, IMO.
>
> Okay, it's not a bug in the strict sense of a feature that doesn't behave as 
> designed. I would say it's a d@mn ugly design.

Fine.  That's one view.  I would suggest that maybe you could suggest a
better design, remembering, of course, that the basis of org is an
outliner...?

> It's also a matter of incomplete documentation. The syntax is

Indeed.  And I am partly to blame for this.  I do have a number of
outstanding TODO items with respect to the documentation of beamer
support in org.  But I also do have a real job which, unfortunately,
seems to take increasingly more hours every day...

> /perhaps/ straightforward, *after* spending some time wondering why it
> didn't work to put the color into an environment argument (as one
> might reasonably guess), and then spending more time constructing some
> tests and looking at the *.tex output to find out which bit of org
> text gets put where in the TeX code.
>
> C-c C-b lists 19 ways to tag headlines for Beamer environments. [1]

Yes, because the documentation was written to illustrate how org could
support beamer; a comprehensive document has never been written.  I
would be happy if you would consider contributing to the documentation?


-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.06 (release_7.8.06.181.g67694.dirty)

Re: [O] problems with LaTex/BibTex

[Eric Fraga]

"Alan E. Davis"  writes:

> I would have a use for this.  I am curious, though...
>
> Suppose I use this as a standard init-file declaration for
> org-latex-to-pdf-process .  Does that mean that bibtex will always be run,
> every time, during the generation of PDFs via LaTex export?

Yes but you can easily customise this variable on a per file basis.  If
you seldom use bibtex, have the default be to run pdflatex just
once.  Then, for any org file that needs bibtex, simply put in the
following line (or a variation thereof):

#+BIND: org-latex-to-pdf-process ("pdflatex %b" "bibtex %b" "pdflatex %b" 
"pdflatex %b")

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.06 (release_7.8.06.181.g67694.dirty)

Re: [O] setting default BibTex file

[Eric Fraga]

Nick Dokos  writes:


[...]

> ... but you can shorten it by setting BIBINPUTS in your 
> .profile/.login/whatever
> and then using
>
> \bibliography{References}
>
> in your .org/.tex files.

On TeX systems based on kpathsea and texmf, there are defaults which are
quite reasonable.  On Debian/Ubuntu, at the very least, you can put your
files under ~/texmf in an appropriate subdirectory.  Specifically, bib
files can go in ~/texmf/bibtex/bib and they will automatically be found
by bibtex.  Similar directories exist for .bst, .sty and .cls files,
etc.

The actual paths searched by latex et al. are defined by the texmf
configuration, usually found in /etc/texmf/texmf.cnf (again, on Debian
systems; YMMV).  This file is worth looking at as it is better
documented than the man pages etc!  In any case, that configuration file
defines the default settings for BIBINPUTS, BSTINPUTS and so on.

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.06 (release_7.8.06.181.g67694.dirty)

Re: [O] Exporting a presentation to both slides and handouts?

[Eric Fraga]

Alan Schmitt  writes:

> Hello,
>
> I'm finishing a presentation with org-mode which is exported as beamer
> slides. I would like to also export it as a handouts, which basically
> means changing a couple lines in the preamble. Is there a way to do it
> from the org-mode file, or do I need to edit the generated LaTeX
> manually?
>
> (If the solution is to have some lines that specify the options and the name 
> of the exported LaTeX file commented out, it would work fine with me.)
>
> Thanks,
>
> Alan

My solution is akin to yours except that I alter the org file
instead.  I have the following lines in my org file:

--8<---cut here---start->8---
##+LaTeX_CLASS_OPTIONS: [bigger]
#+LaTeX_CLASS_OPTIONS: [handout]
#+latex_header: \mode{\usetheme{progressbar}}
#+latex_header: 
\mode{\usecolortheme[rgb={0.5,0.5,0.5}]{structure}\usetheme[secheader]{Boadilla}\usepackage{pgfpages}\pgfpagesuselayout{4
 on 1}[a4paper,landscape,border shrink=5mm]}
--8<---cut here---end--->8---

and all I do is delete the extra # on the first line and add one to the
second line to switch from generating handouts to generating my
slides.  Remembering to hit C-c C-c, of course, before doing the
export.

I use very different themes for handouts (e.g. grey colour theme) and
for slides but those lines need not change.

Of course, by default, the export generates the same file name in both
cases.  For my use case, this isn't an issue.  I generate the handouts,
copy the resulting PDF file to the web server and then generate the
slides which I will actually present.

HTH,
eric


-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.06 (release_7.8.06.181.g67694.dirty)

Re: [O] Beamer specific setupfile?

[Eric Fraga]

Eric Fraga  writes:

> Nick Dokos  writes:
>
> [...]
>
>> org-infile-export-plist parses the current buffer and takes care of
>> #+SETUPFILE: options (even recursive ones). It constructs an options
>
> This thread has been interesting for the effects it has had on my mail
> reading experience.  I use gnus and I have gnus configured to parse
> *some* org syntax for fontifying messages.
>
> Interestingly, for these messages, org has tried to load in setup files!
> With the original email message, I got the following error message:
>
> : Cannot read file "/home/xxx/org/aux/beamer-setup.org"
>
> and with the last line I quoted above from Nick's email, I got:
>
> : Cannot read file "/home/xxx/options (even recursive ones). It constructs an 
> options"
>
> Fun!
>
> The question is: I believe that I have only configured gnus to do
> fontification on source code blocks and a few other constructs.  None of
> the patterns I have specified includes general #+ lines.  I cannot see
> how these #+SETUPFILE lines are being interpreted.  Any ideas of where
> to look?  It must (?) be an org issue, not gnus per se, I believe.
>
> Thanks,
> eric

Umm, it turns out that gnus does indeed catch lines that start with #+:

,
| (org-meta-line
|  "^[ \t]*#\\+[[:alpha:]]+: "
|  "$"
|  mm-uu-org-src-code-block-extract))
`

I need to investigate mm-uu-org-src-code-block-extract why this leads to
setup file directives being followed.  I do worry a little about
security implications, although there probably aren't any.

Side note: that regex doesn't capture all org mode directives!

Apologies for the noise.

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.06 (release_7.8.06.181.g67694.dirty)

Re: [O] Beamer specific setupfile?

[Eric Fraga]

Nick Dokos  writes:

[...]

> org-infile-export-plist parses the current buffer and takes care of
> #+SETUPFILE: options (even recursive ones). It constructs an options

This thread has been interesting for the effects it has had on my mail
reading experience.  I use gnus and I have gnus configured to parse
*some* org syntax for fontifying messages.

Interestingly, for these messages, org has tried to load in setup files!
With the original email message, I got the following error message:

: Cannot read file "/home/xxx/org/aux/beamer-setup.org"

and with the last line I quoted above from Nick's email, I got:

: Cannot read file "/home/xxx/options (even recursive ones). It constructs an 
options"

Fun!

The question is: I believe that I have only configured gnus to do
fontification on source code blocks and a few other constructs.  None of
the patterns I have specified includes general #+ lines.  I cannot see
how these #+SETUPFILE lines are being interpreted.  Any ideas of where
to look?  It must (?) be an org issue, not gnus per se, I believe.

Thanks,
eric

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.06 (release_7.8.06.181.g67694.dirty)

Re: [O] orgstuct++ does not lurk silently in the shadow

[Eric Fraga]

Christopher Schmidt  writes:

> Hi gurus,
>
> I have a problem with Org-mode version 7.8.03
> (release_7.8.03.351.g47eb3) on GNU Emacs 24.0.94.1
> (x86_64-unknown-linux-gnu, GTK+ Version 2.24.9) of 2012-03-08.
>
> (info "(org)Orgstruct mode") says that one is allowed to use orgtbl-mode
> in message-mode.  Unfortunately this does not work as expected.
>
> Recipe:
>
> emacs -q
> C-x m
> M-q # fill-paragraph ignores the message header
> eval: (add-hook 'message-mode-hook 'turn-on-orgstruct++)
> C-x m
> M-q # fill-paragraph does ignore the message header
>
> The bug is caused by fill-paragraph-function not being set back to
> message-fill-paragraph when orgstruct-hijacker-command-22 falls back to
> fill-paragraph.
>
> Christopher

Thanks for this.  This behaviour has annoyed me for years now.  I've
never gotten around to figuring out why I got this behaviour because I
get caught up with writing the email and forget by the time I finish...

I hope somebody can indeed fix this as it sounds quite straightforward
(for better elisp programmers than I...).

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.06 (release_7.8.06.181.g67694.dirty)

Re: [O] Size and placement of images in table in PDF export

[Eric Fraga]

Nick Dokos  writes:

> Michael Hannon  wrote:
>
>> Greetings.  I've got another export question.  If I put two small images into
>> an Org-mode table and export the containing document to HTML, I see the two
>> images displayed side-by-side in an area of the page that is at least roughly
>> the actual size of the concatenated images.
>> 
>> If I export the same document to PDF, the two images are again displayed
>> side-by-side, but image on the left is magnified to take up most of the
>> horizontal space on the page; the image on the right is also magnified and
>> runs off the page to the right.

[...]

>> Is there some way to override the default size/placement of the images in PDF
>> export?
>> 
>
> The trouble is that the default option says "width=.9\\linewidth" so
> if you try to put two of them on the same "line", they end up overflowing
> the page. For an image not inside a table, you could reset that with
>
> #+ATTR_LaTeX: width=.4\\linewidth

By the way, there should be only one \ in this line as org or emacs do
not need the \ escaped in this context.

>
> but this is a rather blunt instrument: for images inside a table, it
> applies not only to the images but also to the table (and it ends up
> producing a syntactically incorrect latex program - that's probably
> a bug in the latex exporter.)

There is indeed a problem with figures inside tables in that the same
construct is used to pass arguments to \includegraphics
and \begin{tabular}.  Not ideal at all.  We really should have different
constructs for each...

For the above problem from the OP, the best solution in latex directly
would have been to specify the widths of the columns using p{2.5cm}
column formats, say.  If that is done, the default width for images,
based on \linewidth, would work just fine as \linewidth is the width of
the text within the actual latex structure (as opposed to \textwidth or
\columnwidth, say).  This works because the "p" tabular format changes
\linewidth within that column.

However, it is not possible to specify table attributes *if* you have
images inside the table as the same latex attributes are passed to both
table and images...

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.06 (release_7.8.06.181.g67694.dirty)

Re: [O] [beamer] When are :BEAMER_envargs: used or ignored?

[Eric Fraga]

James Harkins  writes:

> According to the online documentation [1], it seems
> that :BEAMER_envargs: should apply to all Beamer environments:

And it does generally although I have tried setting it (for your example
below) to {ybg} and it disappears.  If I set it to [ybg], it does appear
in the exported latex.  I haven't delved into the beamer export code in
a long while but it must be checking for constructs of the form [...] or
<...>, I would guess.

In any case, addressing your real question:

[...]

> Or, the simple question -- how do you set the colors of a color box in
> Beamer export?

> Oh, wait, I just figured it out... though you would have to admit,
> this is not remotely obvious.

> ** Frame 2 \\ where we will not use columns
> #+LaTeX: \setbeamercolor{ybg}{bg=yellow}
> *** ybg  :B_beamercolorbox:
> Please test this stuff!
> :PROPERTIES:
> :BEAMER_env: beamercolorbox
> :END:
>
> It kind of strikes me like an epic hack: you have to name the headline
> after the Beamer color ID, instead of naming the headline after the
> content... not very /org/anized.

Well, the problem is that a beamercolorbox is *not* a block and does not
expect a title parameter.  It actually expects only a colour (well, a
beamer colour structure, to be precise, such as the one you have
defined).  What is /org/ expected to do with the entry you specify?

To achieve what you want (maybe, as I am not clear exactly what you want
;-), you should probably define a block *within* the beamercolorbox or
vice versa.  For instance:

--8<---cut here---start->8---
** Frame 2 \\ where we will not use columns
*** ybg:B_beamercolorbox:
:PROPERTIES:
:BEAMER_env: beamercolorbox
:END:
 Title  :B_block:
 :PROPERTIES:
 :BEAMER_env: block
 :END:
 Please test this stuff!
--8<---cut here---end--->8---

> Worth a bug report or feature request?

It is not a bug, IMO.

Whether it should be a feature request or not is debatable.  The syntax
is, at present, fairly straightforward in that the headline text becomes
the argument to the environment defined.  What that environment does
with the argument is obviously up to the environment itself!

HTH,
eric
-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.06 (release_7.8.06.181.g67694.dirty)

Re: [O] Beamer confusion: environments are ignored

[Eric Fraga]

James Harkins  writes:

> (Sorry for breaking the thread -- I'm using the digest. Come to think
> of it, I was wondering -- how do other digest readers participate in
> discussions without messing up the thread IDs? Use a news reader,
> or...? Nabble?)

You don't appear to have broken the thread; at least, in gnus, this
message is properly threaded with your earlier one... maybe it's a
matter of using an intelligent mail reader! ;-)

[...]

> Still, though, if there is nothing wrong with Carsten's example presentation 
> and it renders incorrectly, then I suppose it's a bug.
>
> Shall I file a bug report? There is a reproducer here:
>
> http://article.gmane.org/gmane.emacs.orgmode/52631
>
> Can someone confirm? Bug or not?

Works fine for me.  The first slide is not /blocked/; the second one
/is/.  Have you looked at the latex produced by the exporter?

What version of org are you using?

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.06 (release_7.8.06.181.g67694.dirty)

Re: [O] Beamer export: upgrade problem, and basic questions

[Eric Fraga]

James Harkins  writes:

> At Tue, 21 Feb 2012 09:39:27 -0500,
> Nick Dokos wrote:
>> Both soul.sty and wrapfig.sty are in the package texlive-latex-extra,
>> so you just need to install that:
>> 
>>   sudo apt-get install texlive-latex-extra
>
> Ah, thanks. Some progress, but still:
>
> ! LaTeX Error: File `marvosym.sty' not found.
>
> Type X to quit or  to proceed,
> or enter new name. (Default extension: sty)
>
> Enter file name: 
> ! Emergency stop.
>  
>  
> l.18 \usepackage
> {wasysym}^^M
> !  ==> Fatal error occurred, no output PDF file produced!
>
> Does anyone have a comprehensive list of all ubuntu packages that are 
> required for beamer to work with org 7.8.03?
>
> hjh

James,

I know I'm coming late to this thread [1] but I thought I would mention
that one way to figure out what packages to add to your Debian/Ubuntu
system is to use apt-cache:

,
| $ apt-cache search marvosym
| texlive-fonts-recommended - TeX Live: Recommended fonts
| ttf-marvosym - Symbol font for school and office
| $ apt-cache search wasysym
| texlive-fonts-recommended - TeX Live: Recommended fonts
| $ 
`

HTH,
eric


Footnotes: 
[1]  I moved to Australia in mid-February and am only now catching
up with non-work emails ... 3000+ in my org folder!  You guys *do* talk!
;-)

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.06 (release_7.8.06.181.g67694.dirty)