Re: [O] inserting a path string fires the italic formatting

[Luca Ferrari]

Thanks,
using the = symbol makes it looking less strange that a ~ (for the
backup, home directory, and so on).

Luca

On Wed, Feb 6, 2013 at 2:22 PM, Sebastien Vauban
 wrote:
> Hi Luca,
>
> Luca Ferrari wrote:
>> this could be trivial, but if I have to place a unix path name into my
>> org text, without having a link, how can I prevent the mode to assume
>> I'm doing italic formatiing?
>> For instance in the text:
>>- check /usr/bin/chmod
>>- check /usr/lib/bla
>>
>> Suggestions?
>
> For example, by "protecting" those paths, declaring them as `org-code' or
> `org-verbatim', that is using the markers `=' or `~'; for example:
>
> - check ~/usr/bin/chmod~
> - check ~/usr/bin/bla~
>
> Best regards,
>   Seb
>
> --
> Sebastien Vauban
>
>

Re: [O] Dropbox integration suddenly stopped working with Mobile-Org

[Matthew Jones]

I'm the developer of the Android version of MobileOrg... and you, and the
developers of the IOS app, should be aware that they retired the old
version of their api and shut it off sometime in December or January...
that could be what's keeping it from working.  It's just a guess... I had
to release a new version of MobileOrg for Android in December to update it
to use the new api.


On Fri, Feb 1, 2013 at 5:19 AM, Adrian Tritschler  wrote:

> > "Benjamin" == Benjamin Alexander  writes:
>
> Benjamin> Hello all!  I've been a happy (!) user of Mobile-Org for some
> Benjamin> time now, on the iPhone, and a few months ago I switched to
> Benjamin> Dropbox integration.  Things have gone fine until today when I
> Benjamin> synced for the first time in a week or so.  The Dropbox
> Benjamin> password that was saved, and had worked fine (and still works
> Benjamin> from the web interface) simply gives an error message from
> Benjamin> within the "Settings" page of Mobile-Org.
>
> Benjamin> Dropbox Error Bad username and password or network error.
>
> The same thing has just happened to me.  I've been using org-mode for
> years, org-mobile on my iPhone for a couple of years (I suspect) and on
> an Android tablet for about a year.  I went away on holiday a week ago
> and had no net access, when I came back I tried to synch. the iPhone app
> and I get the same error.
>
> Dropbox integration from other iPhone apps still works fine, as does
> browsing via safari.
>
> Benjamin> The strange thing is, the Dropbox app works fine.  So it isn't
> Benjamin> a network problem (at least, not a simple case of being
> Benjamin> offline). And I've tried retyping the password, with and
> Benjamin> without a terminating  as the known issue from the
> Benjamin> Mobile-Org web page suggests.  The files are still on Dropbox
> Benjamin> and I can still push and pull (though there is nothing new to
> Benjamin> pull) from within emacs.
>
> Benjamin> I'm really stumped.  I don't even know where to look on the
> Benjamin> iPhone for log messages.  I've even tried using my old phone
> Benjamin> (which was configured to use my now discontinued webdav
> Benjamin> server) using dropbox and I get the same error.
>
> Benjamin> My current phone is running iOS 6.0.1 (10A523). I have not
> Benjamin> installed the new iOS update yet.  I am considering doing that
> Benjamin> to see if it helps, but I know I can't roll it back.
>
> Happens on my phone running iOS 6.0.1 and 6.1 (updated some time this
> afternoon)
>
> Benjamin> I've also considered deleting mobile-org and reinstalling, but
> Benjamin> I'm worried that mobile-org isn't in the App store anymore so
> Benjamin> I may lose all functionality!
>
> Benjamin> Does anyone have any suggestions?  I would really appreciate
> Benjamin> it.
>
> Benjamin> Best Wishes, Ben
>
>   Adrian
> --
> Adrian Tritschler  mailto:a...@ajft.org
> Latitude 38°S, Longitude 145°E, Altitude 50m,  Shoe size 44
>
>
>

[O] org-html-link problem

[cberry]

M-x org-export-dispatch RET h H terminates with an error

,
| 
| * https link
| 
| 
| Here is the
| [[https://github.com/downloads/yihui/knitr/knitr-minimal.html][link]]
| 
`

The problem seems to be here:

lisp/ox-html.el around line 2172:

 (unless (and desc (string-match (regexp-quote (car att)) desc)) 

att is nil


maybe 

(unless (and att desc (string-match (regexp-quote (car att)) desc))??

Chuck

[O] subscribing to this mailing list with gnus

[42 147]

I don't know the correct port / address within the context of this code:

(setq gnus-select-method
'(nntp "gmane.emacs.orgmode"
  (nntp-port-number 119)))

[O] bug in ascii export

[Samuel Wales]

exporting this subtree results in this bt.

===

*** test
test

===

Debugger entered--Lisp error: (wrong-number-of-arguments (lambda
(&optional sort-only) "Collect the footnotes in various formats and
normalize them.

This finds the different sorts of footnotes allowed in Org, and
normalizes them to the usual [N] format.

When SORT-ONLY is set, only sort the footnote definitions into the
referenced sequence." (let* ((limit-level (and (boundp (quote
org-inlinetask-min-level)) org-inlinetask-min-level (1-
org-inlinetask-min-level))) (nstars (and limit-level (if
org-odd-levels-only (1- (* limit-level 2)) limit-level)))
(org-outline-regexp (concat "\\*" (if nstars (format "\\{1,%d\\} "
nstars) "+ "))) (count 0) ins-point ref ref-table) (save-excursion
(goto-char (point-min)) (while (setq ref
(org-footnote-get-next-reference)) (let* ((lbl (car ref)) (pos (nth 1
ref)) (a (and lbl (assoc lbl ref-table))) (marker (or (nth 1 a) (incf
count))) (inlinep (or (stringp (nth 3 ref)) (nth 3 a (if sort-only
(goto-char (nth 2 ref)) (delete-region (nth 1 ref) (nth 2 ref))
(goto-char (nth 1 ref)) (insert (format "[%d]" marker)) (and inlinep
org-footnote-fill-after-inline-note-extraction (org-fill-paragraph)))
(unless a (let ((def (or (nth 3 ref) (nth 3
(org-footnote-get-definition lbl) (push (list lbl marker def
inlinep (copy-marker pos)) ref-table) (cond ((and
org-footnote-section (derived-mode-p (quote org-mode))) (goto-char
(point-min)) (if (re-search-forward (concat "^\\*[  ]+" (regexp-quote
org-footnote-section) "[]*$") nil t) (delete-region (match-beginning
0) (org-end-of-subtree t t))) (goto-char (point-max))
(skip-chars-backward "

") (forward-line) (unless (bolp) (newline))) ((derived-mode-p (quote
org-mode))) (t (when org-footnote-tag-for-non-org-mode-files (let
((tag (concat "^" (regexp-quote
org-footnote-tag-for-non-org-mode-files) "[ ]*$"))) (goto-char
(point-min)) (while (re-search-forward tag nil t) (replace-match "")
(delete-region (point) (progn (forward-line) (point)) (if (and
(derived-mode-p (quote message-mode)) (goto-char (point-max))
(re-search-backward message-signature-separator nil t))
(beginning-of-line) (goto-char (point-max) (setq ins-point
(point-marker)) (setq ref-table (delq nil (mapcar (lambda (x) (cond
((and sort-only (nth 3 x)) (set-marker (nth 4 x) nil) nil) ((not (nth
2 x)) (append (list (car x) (nth 1 x) (format "DEFINITION NOT FOUND:
%s" (car x))) (nthcdr 3 x))) (t x))) ref-table))) (setq ref-table
(nreverse ref-table)) (mapc (lambda (x) (unless (nth 3 x)
(org-footnote-delete-definitions (car x ref-table) (goto-char
ins-point) (cond ((not ref-table)) ((or (not (derived-mode-p (quote
org-mode))) org-footnote-section) (if (not (derived-mode-p (quote
org-mode))) (progn (skip-chars-backward "

") (delete-region (point) ins-point) (unless (bolp) (newline)) (when
org-footnote-tag-for-non-org-mode-files (insert "
" org-footnote-tag-for-non-org-mode-files "
"))) (when (and (cdr (assq (quote heading)
org-blank-before-new-entry)) (zerop (save-excursion
(org-back-over-empty-lines (insert "
")) (insert "* " org-footnote-section "
")) (set-marker ins-point nil) (insert (mapconcat (lambda (x)
(set-marker (nth 4 x) nil) (format "
[%s] %s" (nth (if sort-only 0 1) x) (nth 2 x))) ref-table "
")) (unless (eobp) (insert "

"))) (t (mapc (lambda (x) (let ((pos (nth 4 x))) (goto-char pos)
(set-marker pos nil)) (org-footnote-goto-local-insertion-point)
(insert (format "
[%s] %s
" (if sort-only (car x) (nth 1 x)) (nth 2 x ref-table)) 2)
  org-footnote-normalize(nil (:for-backend ascii
:skip-before-1st-heading nil :drawers nil :tags nil :priority nil
:footnotes t :timestamps t :todo-keywords t :tasks nil
:verbatim-multiline t :select-tags ("export") :exclude-tags ("himitsu"
"noexport") :archived-trees headline :add-text nil))
  (progn (org-footnote-normalize nil parameters))
  (if (plist-get parameters :footnotes) (progn (org-footnote-normalize
nil parameters)))
  (when (plist-get parameters :footnotes) (org-footnote-normalize nil
parameters))
  (progn (erase-buffer) (insert string) (setq case-fold-search t) (let
((inhibit-read-only t)) (remove-text-properties (point-min)
(point-max) (quote (read-only t (org-export-kill-licensed-text)
(let ((org-inhibit-startup t)) (org-mode)) (setq case-fold-search t)
(org-clone-local-variables source-buffer "^\\(org-\\|orgtbl-\\)")
(org-install-letbind) (run-hooks (quote org-export-preprocess-hook))
(untabify (point-min) (point-max))
(org-export-handle-include-files-recurse) (run-hooks (quote
org-export-preprocess-after-include-files-hook))
(org-export-remove-archived-trees archived-trees)
(org-export-remove-comment-blocks-and-subtrees)
(org-export-handle-export-tags (plist-get parameters :select-tags)
(plist-get parameters :exclude-tags)) (run-hooks (quote
org-export-preprocess-after-tree-selection-hook))
(org-export-remove-tasks (plist-get parameters :tasks)) (when
(plist-get parameters :footnotes) (org-footnote

[O] sexp timestamp causing agenda compilation issues as of 8517be79b5c1

[Kyle Machulis]

As of commit 8517be79b5c1fe165d23ea65ad70a282e9c595bb (bisected to
find this), agenda compilation died with the following backtrace for
me:

Debugger entered--Lisp error: (error "Bad timestamp `'
Error was: (Not a standard Org-mode time string: )")
  signal(error ("Bad timestamp `'\nError was: (Not a standard Org-mode
time string: )"))
  error("Bad timestamp `%s'%s\nError was: %s" "" "" ("Not a standard
Org-mode time string: "))
  byte-code(...)
  org-time-string-to-absolute("")
  byte-code(...)
  org-agenda-get-timestamps(nil)
  org-agenda-get-day-entries("~/emacs_org/mozilla/mozilla.org" (2 6
2013) :deadline :scheduled :timestamp :sexp)
  apply(org-agenda-get-day-entries "~/emacs_org/mozilla/mozilla.org"
(2 6 2013) (:deadline :scheduled :timestamp :sexp))
  byte-code(...)
  byte-code(...)
  org-agenda-list(nil)
  call-interactively(org-agenda-list)
  byte-code(...)
  org-agenda(nil)
  call-interactively(org-agenda nil nil)

It's dying when it hits a headline as follows:

* Meeting 13:30
, <%%(memq (calendar-day-of-week date) '(3))>

I'm guessing this has something to do with the agenda sorting updates
in the commit not liking the fact that the sexp evaluates to true. If
the sexp evaluates nil for the day the agenda is trying to parse,
nothing happens. If it evaluates to something other than nil (t if I
use (= 3 (calendar-day-of-week date)), 3 if I use memq on a wednesday,
etc...), I get the above error.

Re: [O] New exporter, beamer confusion

[James Harkins]

On Feb 7, 2013 3:57 AM, "Nicolas Goaziou"  wrote:
> > Btw, *who* preferred \alert? (Orwell, Politics and the English Language:
> > "Never use the passive [voice] where you can use the active.")
>
> Obviously, me, as the author of the back-end. Org offers only one slot
> for "strong emphasis". I had to choose between bold and alert, and so
> I did.

Ok, and as long as I can configure it, no problem.

Aside Re: Orwell, and now veering well off-topic, his point about passive
voice is that it hides human agency and, in the worst cases, suggests that
something simply "is objectively so" rather than "one or more people made
it so, for reasons that may be subjective," or deflects responsibility à la
"mistakes were made." Although the relationship to the present topic is
only tangential, Orwell's caution is at least as relevant today as it was
when he wrote it in 1946. I find for myself that following his advice [6 or
7 rules of thumb at the end of his essay] sounds a little alarm bell when
my thinking is getting sloppy -- so I think it bears repeating. (Apologies
to the scientific authors here, who "are trained" [oops!] to erase
themselves from reports on their experimental procedures by using passive
voice consistently...)

In fact, it wasn't obvious to me whether it was simply your preference, or
if an expert or authority on slideshow style recommends \alert over
\textbf. In the latter case, I would want to know who and why, so I could
read and then make up my own mind.

> > "Reasonably" for me would mean tweaking some configuration options and
> > perhaps changing a few minor details of the markup. If you have to
change
> > the org document's structure (e.g., converting headlines to lists), it
> > isn't backward compatible.
>
> Then, by this definition, it isn't, indeed.

Sure, and that's ok. My frustration stemmed from expecting more
compatibility than there actually is. After adjusting my expectations, I
can figure out how to make it work for me.

hjh

[O] [PATCH] Tiny change in ob-lilypond.el

[Thorsten Jolitz]

Hi, 

A tiny change to make ob-lilypond export the results in the format
specified for the ':file' in the source-block header. 

>From 4d5c79ed1607c3d0263bcde33fc1d795a96aad5f Mon Sep 17 00:00:00 2001
From: tj 
Date: Thu, 7 Feb 2013 01:51:14 +0100
Subject: [PATCH] "test.pdf" replaced with 'out-file' in ly-process-basic
 (otherwise all output-files are in pdf format).

---
 lisp/ob-lilypond.el | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lisp/ob-lilypond.el b/lisp/ob-lilypond.el
index 07ea184..6080a5a 100644
--- a/lisp/ob-lilypond.el
+++ b/lisp/ob-lilypond.el
@@ -152,7 +152,7 @@ specific arguments to =org-babel-tangle="
   " -dbackend=eps "
   "-dno-gs-load-fonts "
   "-dinclude-eps-fonts "
-  (or (cdr (assoc (file-name-extension "test.pdf")
+  (or (cdr (assoc (file-name-extension out-file)
 		  '(("pdf" . "--pdf ")
 			("ps" . "--ps ")
 			("png" . "--png "
-- 
1.8.1.2



-- 
cheers,
Thorsten

Re: [O] [ANN] Merge of new export framework on Wednesday

[Jay Kerns]

Greetings,

The new exporter just arrived in my git repository and I wanted to say
"Congratulations!" but even more importantly, THANK YOU.  Kudos on a
job very well done, if not 100% complete yet.  I have been looking
forward to this for quite some time, now.

I would like to extend my Congratulations and THANK YOU to the rest of
the Org-mode community/team as well, not limited to Nicolas, though
this happens to be the occasion of the new exporter's release.

Org-mode (and GNU-Emacs more generally, and Free software more
generally than that) has changed my life, and by extension those who
live and work near me, in my view, for the better.  Cheers, and may we
share many good days ahead.

-- 
Jay Kerns



On Sun, Feb 3, 2013 at 2:00 PM, Nicolas Goaziou  wrote:
>  ━
>   ANNOUNCING THE NEW EXPORT FRAMEWORK
>  ━
>

Re: [O] inserting a path string fires the italic formatting

[Olaf Meeuwissen]

Sebastien Vauban writes:

> Hi Luca,
>
> Luca Ferrari wrote:
>> this could be trivial, but if I have to place a unix path name into my
>> org text, without having a link, how can I prevent the mode to assume
>> I'm doing italic formatiing?
>> For instance in the text:
>>- check /usr/bin/chmod
>>- check /usr/lib/bla
>>
>> Suggestions?
>
> For example, by "protecting" those paths, declaring them as `org-code' or
> `org-verbatim', that is using the markers `=' or `~'; for example:
>
> - check ~/usr/bin/chmod~
> - check ~/usr/bin/bla~

Looks like Emacs backup files somewhere in a user's home directory ;-)
-- 
Olaf Meeuwissen, LPIC-2   FLOSS Engineer -- AVASYS CORPORATION
FSF Associate Member #1962   Help support software freedom
 http://www.fsf.org/jf?referrer=1962

Re: [O] New exporter, beamer confusion

[Eric S Fraga]

Nicolas Goaziou  writes:

> Hello,
>
> Eric S Fraga  writes:
>
>> Taking your updated version of the example document, I cannot get the
>> exporter to generate a latex file that will compile because it is
>> missing a documentclass directive.  Is there something else that needs
>> to be configured to support beamer, as in maybe org-e-latex-classes?
>
> Indeed. I added it to ox-beamer.el in-file documentation. You need to

Thanks.  This will indeed help.

Should there be a check in the exporter, for latex based backends, if
the document class expected is not defined?  This would have made things
a lot quicker to resolve in this case!

Thanks again,
eric
-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org 7.9.3e-904-g338046

Re: [O] Confused about inline html images

[John Hendy]

On Thu, Jan 31, 2013 at 3:45 AM, Bastien  wrote:
> Hi John,
>
> John Hendy  writes:
>
>> Still one issue: it's applying the attr_html to the wrong bit. Here's
>> the resultant export output:
>>
>> #+attr_html: width="400px"
>> [[http://path/to/file.jpg][http://path/to/file.jpg]]
>>
>> becomes:
>>
>> http://path/to/file.jpg"; width="400px">> src="http://path/to/file.jpg"; alt="file.jpg"/>
>
> Yes, that's wrong.  I fixed this.  Thanks for reporting it!
>

Sorry for the late response. I pulled when you made the change but
hadn't gotten around to testing. Still having odd behavior. The
minimal example:

M-x org-version
Org-mode version 7.9.3e (7.9.3e-910-g33c4f6 @
/home/jwhendy/.elisp/org.git/lisp/)

Emacs installed from Arch Linux main repository (not testing or from source):
$ emacs --version
GNU Emacs 24.2.1


#+begin_src minimal-config
;; set load paths
;; set load dirs and global config options
(add-to-list 'load-path "~/.elisp/org.git/contrib/lisp/")
(add-to-list 'load-path "~/.elisp/org.git/lisp/")
#+end_src

#+begin_src test.org
* A headline

And a random image from imgur:

- full size

[[http://i.imgur.com/tladtBz.jpg][http://i.imgur.com/tladtBz.jpg]]

- with an =attr_html= width passed:

#+attr_html: width="200px"
[[http://i.imgur.com/tladtBz.jpg][http://i.imgur.com/tladtBz.jpg]]
#+end_src

The process:
- emacs -q
- M-x load-file ~/path/to/minimal-config
- C-x C-f ~/path/to/test.org
- C-e h

When I open the file in a browser and view source, this is what I get
for the images portion:

#+begin_src html

http://i.imgur.com/tladtBz.jpg";
alt="http://i.imgur.com/tladtBz.jpg"; />


with an attr_html width passed:





http://i.imgur.com/tladtBz.jpg"; width="200px"
alt="http://i.imgur.com/tladtBz.jpg"; />

#+end_src

It looks like it's using my second option for the alt text instead of
using it for a link? Not sure. This was happening to me when I
originally posted to the list about this (as in, I couldn't even get
the images to be clickable, but then magically it worked right after I
posted). Now it seems to be doing the original behavior.

Any suggestions?


John



> --
>  Bastien

Re: [O] viewing number of nested headlines

[Achim Gratz]

42 147 writes:
> As for the rest, I didn't see some of the other replies, because the
> org-mode mailing list moves a little two fast for my mailbox, and I
> prefer to read selectively from the gmane archive.
>
> That said, it is my responsibility to check that website before
> responding to (some) of the messages that get forwarded to my e-mail
> address in a thread I started.

If you haven't done so already: On Gmane, switch to the "traditional"
interface, then call up any message in the thread and click on the
thread title: that will open just this thread and can be bookmarked
easily.

Better yet, use a real news reader (ahem, Gnus?) and connect to NNTP.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

Re: [O] New exporter, beamer confusion

[Nicolas Goaziou]

James Harkins  writes:

> Btw, *who* preferred \alert? (Orwell, Politics and the English Language:
> "Never use the passive [voice] where you can use the active.")

Obviously, me, as the author of the back-end. Org offers only one slot
for "strong emphasis". I had to choose between bold and alert, and so
I did.

> Although I'm not happy about manual intervention to convert my prior work,
> this is a good step toward consistency. It was odd, in the old framework,
> to use headlines for bullet lists and org's numbered lists for numbered
> lists. "An org list becomes an output list" is an easier rule to
> explain.

As explained in this thread, the H:num options item defines a limit
between regular headlines and "low-level" headlines. Low level headlines
are usually turned into lists during export. But, in the Beamer
exporter, it is a better idea to turn them into blocks. Better as in
"closer, by its properties, to an headline".

> Still, I wonder if there is a way to make the new backend less unfriendly
> toward lists. It's an interesting philosophical question: In what cases is
> it better for the tool to adapt to the users' wishes, versus cases where
> the tool should encourage (Are blocks in the result actually better than
> lists? Who says so, and why should I take his or her word for it?)

Nobody is saying that blocks are better than lists in the output. It's
a matter of taste, isn't it? There are also ways to adapt the tool to
your wishes (through hooks, filters, script, macros).
> "Reasonably" for me would mean tweaking some configuration options and
> perhaps changing a few minor details of the markup. If you have to change
> the org document's structure (e.g., converting headlines to lists), it
> isn't backward compatible.

Then, by this definition, it isn't, indeed.

> For comparison: Lilypond updates frequently break some details of backward
> compatibility. So, they ship a "convert-ly" script to handle many of those
> changes automatically.

Even though the required change in our case are rather minimal, they
mostly depend on the user configuration. Hence, I will not attempt to
provide such a script.

But I will provide instructions on how to make the transition, if they
are needed.


Regards,

-- 
Nicolas Goaziou

Re: [O] Taskjuggler 3

[Bastien]

Hi Frank,

Frank  writes:

> Any information on an exporter for taskjuggler version 3?

See Nicolas' answer in a recent thread:

http://article.gmane.org/gmane.emacs.orgmode/65646

-- 
 Bastien

Re: [O] New exporter, beamer confusion

[Nicolas Goaziou]

Hello,

Eric S Fraga  writes:

> Taking your updated version of the example document, I cannot get the
> exporter to generate a latex file that will compile because it is
> missing a documentclass directive.  Is there something else that needs
> to be configured to support beamer, as in maybe org-e-latex-classes?

Indeed. I added it to ox-beamer.el in-file documentation. You need to
add an entry appropriate for Beamer export. This entry doesn't need to
be named "beamer". For example, after the merge you add the following to
your init file:

#+begin_src emacs-lisp
'(add-to-list 'org-latex-classes
'("pres"
  "\\documentclass[presentation]{beamer}
\[DEFAULT-PACKAGES]
\[PACKAGES]
\[EXTRA]"
  ("\\section{%s}" . "\\section*{%s}")
  ("\\subsection{%s}" . "\\subsection*{%s}")
  ("\\subsubsection{%s}" . "\\subsubsection*{%s}")))
#+end_src

Then, the following in your buffer will suffice.

  #+latex_class: pres



Regards,

-- 
Nicolas Goaziou

Re: [O] org-export-as-html-and-open problem

[Bastien]

Hi Zhenjiang,

zhenjiang xu  writes:

> Sorry I forgot to mention that I don't have mailcap files in my
> Archlinux.

Then you'll need to configure `org-file-apps' to suit your needs.

Best,

-- 
 Bastien

[O] Taskjuggler 3

[Frank]

Any information on an exporter for taskjuggler version 3?

-- 
Frank Breen, PG
Hydrogeologist
Breen GeoScience Management, Inc.
PMB 354, 4234 I-75 Business Spur
Sault Ste. Marie, MI. 49783

ph:   (906) 248-5682
cell: (906) 322-2605
fax:  (800) 471-4855

f...@breengeosci.com

--
This message and any attachments may contain confidential information protected 
by the attorney-client or other privilege.
If you believe that it has been sent to you in error, please reply to the 
sender that you received the message in
error.  Then delete it.  Thank you.
--

Re: [O] org-export-as-html-and-open problem

[zhenjiang xu]

Sorry I forgot to mention that I don't have mailcap files in my Archlinux.


On Wed, Feb 6, 2013 at 8:32 AM, Nick Dokos  wrote:

> zhenjiang xu  wrote:
>
> > It's odd. The value of org-file-apps-defaults-gnu is:
> >
> > ((remote . emacs) (system . mailcap) (t . mailcap))
> >
> > And I checked my local mime file, which shows google-chrome is the
> default app to open html files:
> >
> > $ cat ~/.local/share/applications/mimeapps.list
> > [Added Associations]
> > application/epub+zip=FBReader.desktop;
> > application/pdf=pdf.desktop;
> > application/vnd.rn-realmedia=smplayer.desktop;
> > application/x-matroska=smplayer.desktop;
> > application/x-mimearchive=firefox.desktop;
> > application/x-ole-storage=libreoffice-impress.desktop;
> > audio/mpeg=audacious.desktop;
> > text/html=google-chrome.desktop;
> > video/mpeg=gnome-mplayer.desktop;
> > x-scheme-handler/mailto=google-chrome.desktop;KMail2.desktop;
> >
> > [Default Applications]
> > text/html=google-chrome.desktop
> > x-scheme-handler/mailto=google-chrome.desktop
> >
> > Any idea?
>
> Bastien pointed you to the mailcap files. The mailcap man page says
>
>
>  $HOME/.mailcap:/etc/mailcap:/usr/share/etc/mailcap:/usr/local/etc/mailcap
>  --  default  path
>for mailcap files.
>
> so those are the files to check.
>
> Nick
>
> >
> > On Mon, Feb 4, 2013 at 4:29 PM, Bastien  wrote:
> >
> > zhenjiang xu  writes:
> >
> > > Thanks, Bastien. It's the default value - I've not changed it:
> > >
> > > org-file-apps is a variable defined in `org.el'.
> > > Its value is ((auto-mode . emacs)
> > >  ("\\.mm\\'" . default)
> > >  ("\\.x?html?\\'" . default)
> > >  ("\\.pdf\\'" . default))
> >
> > So you need to check the relevant variable:
> >
> > org-file-apps-defaults-gnu
> > org-file-apps-defaults-macosx
> > org-file-apps-defaults-windowsnt
> >
> > If the relevant variable uses the defaults (as I guess),
> > you need to configure the mailcap file for your system
> >
> > See http://en.wikipedia.org/wiki/Mailcap
> >
> > HTH,
> >
> > --
> >  Bastien
> >
> >
> > 
> > Alternatives:
> >
> > 
>

Re: [O] Has anybody noticed ellipses instead of the top line of the window?

[William]

On Wed, 30 Jan 2013 18:36:16 +0100, Bastien spake thus:
> > Org's visibility code then inserts the ... at the top line of the
> > window for unknown reasons.

> Can you help me reproduce it?

I also have visibility problems when performing undo-es.

I can reproduce such an ellipsis by :

- Cutting part of the buffer containing an ellipsis
- Undoing the cut

On the attached example, all being visible, fold the first second level
headline, kill its line (C-k with cursor at the beginning of line), and undo
the kill. The buffer then looks like

[ellipsis]
** next headlines

Instead of the initial view (seeing the main headline, etc.)

(That doesn't happen if, all folded, you unfold the main headline, then cut the
still-folded second-level headline and undo, apparently.)

> Also, what is the value of these variables?

>   `org-show-hierarchy-above'
t
>   `org-show-following-heading'
t
>   `org-show-entry-below'
((default))
>   `org-show-siblings'
t

--
William

Re: [O] org-export-as-html-and-open problem

[Nick Dokos]

zhenjiang xu  wrote:

> It's odd. The value of org-file-apps-defaults-gnu is:
> 
> ((remote . emacs) (system . mailcap) (t . mailcap))
> 
> And I checked my local mime file, which shows google-chrome is the default 
> app to open html files:
> 
> $ cat ~/.local/share/applications/mimeapps.list 
> [Added Associations]
> application/epub+zip=FBReader.desktop;
> application/pdf=pdf.desktop;
> application/vnd.rn-realmedia=smplayer.desktop;
> application/x-matroska=smplayer.desktop;
> application/x-mimearchive=firefox.desktop;
> application/x-ole-storage=libreoffice-impress.desktop;
> audio/mpeg=audacious.desktop;
> text/html=google-chrome.desktop;
> video/mpeg=gnome-mplayer.desktop;
> x-scheme-handler/mailto=google-chrome.desktop;KMail2.desktop;
> 
> [Default Applications]
> text/html=google-chrome.desktop
> x-scheme-handler/mailto=google-chrome.desktop
> 
> Any idea?

Bastien pointed you to the mailcap files. The mailcap man page says

   
$HOME/.mailcap:/etc/mailcap:/usr/share/etc/mailcap:/usr/local/etc/mailcap  --  
default  path
   for mailcap files.

so those are the files to check.

Nick

> 
> On Mon, Feb 4, 2013 at 4:29 PM, Bastien  wrote:
> 
> zhenjiang xu  writes:
>
> > Thanks, Bastien. It's the default value - I've not changed it:
> >
> > org-file-apps is a variable defined in `org.el'.
> > Its value is ((auto-mode . emacs)
> >  ("\\.mm\\'" . default)
> >  ("\\.x?html?\\'" . default)
> >  ("\\.pdf\\'" . default))
>
> So you need to check the relevant variable:
>
> org-file-apps-defaults-gnu
> org-file-apps-defaults-macosx
> org-file-apps-defaults-windowsnt
>
> If the relevant variable uses the defaults (as I guess),
> you need to configure the mailcap file for your system
>
> See http://en.wikipedia.org/wiki/Mailcap
>
> HTH,
>
> --
>  Bastien
> 
> 
> 
> Alternatives:
> 
> 

Re: [O] Worg publishing issue

[Nick Dokos]

Suvayu Ali  wrote:

> Hello Worgers,
> 
> Amidsts all the commotion about documentation for the new exporter, I
> committed a very early incomplete draft article documenting the new
> beamer exporter.
> 
> 
> 
> But I see that it is not being published.  I got the following
> publishing error after pushing my commit.
> 
> remote: Publishing file
> /home/emacs/git/worg/org-tutorials/org-beamer/org-e-beamer.org using
> `org-publish-org-to-html'
> remote: Exporting...
> remote: Wrong type argument: stringp, nil
> remote: worg publish process 16964 exited at 02/05/13@07:01:27
> 
> Any ideas?
> 

Just to add another data point (or perhaps more confusion): I checked
out worg after your submission and tried my local batch build. I get the
same error but from org-hacks.org. I cleaned out the timestamps and
remade: org-hacks.org was again the first culprit. When I try publishing
it interactively, it succeeds. I added a (setq debug-on-error t) to my
batch init file and I get the attached backtrace - no idea what's causing
it.

NB: it didn't republish org-hacks since it is done already, so the backtrace
happened on org-annotation-helper.org. I expect that if I try publishing
it interactively, it will succeed and I'll get a backtrace on some other
file, further down in the publishing sequence. AFAICT, the backtrace on
org-hacks.org and the backtrace on org-annotation-helper.org are the same.

Nick


Publishing file /home/nick/src/emacs/org/Worg/org-contrib/org-annotation-helper.org using `org-publish-org-to-html'
Exporting...
Loading cc-langs...
...
  org-export-replace-src-segments-and-examples()
  (progn (erase-buffer) (insert string) (setq case-fold-search t) (let ((inhibit-read-only t)) (remove-text-properties (point-min) (point-max) (quote (read-only t (org-export-kill-licensed-text) (let ((org-inhibit-startup t)) (org-mode)) (setq case-fold-search t) (org-clone-local-variables source-buffer "^\\(org-\\|orgtbl-\\)") (org-install-letbind) (run-hooks (quote org-export-preprocess-hook)) (untabify (point-min) (point-max)) (org-export-handle-include-files-recurse) (run-hooks (quote org-export-preprocess-after-include-files-hook)) (org-export-remove-archived-trees archived-trees) (org-export-remove-comment-blocks-and-subtrees) (org-export-handle-export-tags (plist-get parameters :select-tags) (plist-get parameters :exclude-tags)) (run-hooks (quote org-export-preprocess-after-tree-selection-hook)) (org-export-remove-tasks (plist-get parameters :tasks)) (if (plist-get parameters :footnotes) (progn (org-footnote-normalize nil parameters))) (org-export-mark-list-end) (org-export-preprocess-apply-macros) (run-hooks (quote org-export-preprocess-after-macros-hook)) (org-export-blocks-preprocess) (org-export-mark-list-properties) (org-export-replace-src-segments-and-examples) (org-export-protect-colon-examples) (org-export-convert-protected-spaces) (setq target-alist (org-export-define-heading-targets target-alist)) (run-hooks (quote org-export-preprocess-after-headline-targets-hook)) (org-export-remember-html-container-classes) (org-export-remove-or-extract-drawers drawers (plist-get parameters :drawers)) (if (plist-get parameters :skip-before-1st-heading) (progn (goto-char (point-min)) (if (re-search-forward "^\\(#.*\n\\)?\\*+[ 	]" nil t) (progn (delete-region (point-min) (match-beginning 0)) (goto-char (point-min)) (insert "\n") (if (plist-get parameters :add-text) (progn (goto-char (point-min)) (insert (plist-get parameters :add-text) "\n"))) (org-export-remove-headline-metadata parameters) (setq target-alist (org-export-handle-invisible-targets target-alist)) (run-hooks (quote org-export-preprocess-before-selecting-backend-code-hook)) (org-export-select-backend-specific-text) (org-export-protect-quoted-subtrees) (org-export-remove-clock-lines) (org-export-protect-verbatim) (org-export-mark-blockquote-verse-center) (run-hooks (quote org-export-preprocess-after-blockquote-hook)) (if (plist-get parameters :timestamps) nil (org-export-remove-timestamps)) (setq target-alist (org-export-attach-captions-and-attributes target-alist)) (org-export-mark-radio-links) (run-hooks (quote org-export-preprocess-after-radio-targets-hook)) (org-export-concatenate-multiline-links) (run-hooks (quote org-export-preprocess-before-normalizing-links-hook)) (org-export-normalize-links) ...)
  (unwind-protect (progn (erase-buffer) (insert string) (setq case-fold-search t) (let ((inhibit-read-only t)) (remove-text-properties (point-min) (point-max) (quote (read-only t (org-export-kill-licensed-text) (let ((org-inhibit-startup t)) (org-mode)) (setq case-fold-search t) (org-clone-local-variables source-buffer "^\\(org-\\|orgtbl-\\)") (org-install-letbind) (run-hooks (quote org-export-preprocess-hook)) (untabify (point-min) (point-max)) (org-export-handle-include-files-recurse) (run-hooks (quote org-export-preprocess-after-include-files-hook)) (org-exp

Re: [O] python :session issues

[John Kitchin]

Thanks for the -Q reminder. I get the same output if I run with emacs -Q
(although I do have to add :results output to each block. I had that set as
a default in my init files).

I had the problem described in the footnote you listed, and that is why I
am using python-mode 5.2, which doesn't have that issue.

John

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



On Wed, Feb 6, 2013 at 10:10 AM, Myles English wrote:

>
> Hi John,
>
> John Kitchin writes:
>
> > I have been trying to use the :session feature of babel for python code
> > blocks. I have noticed a few things that might be areas for
> > improvement. Some issues are related to what I think might be a need for
> > sanitizing the code blocks and the output.
> >
> > I am using (insert (org-version)) 7.9.3a
> > I am using python-mode 5.2 (more modern versions do not work with
> > :session for me)
> >
> > The first small detail is illustrated here:
> >
> > #+BEGIN_SRC python :session
> > a = 5
> >
> > b = 6
> >
> > print a + b
> > #+END_SRC
> >
> > #+RESULTS:
> > :
> > : >>> >>> >>> 11
> >
> > In the output, there are three sets of >>>, due to the two empty
> > lines. Compare this to
> >
> > #+BEGIN_SRC python :session
> > a = 5
> > b = 6
> > print a + b
> > #+END_SRC
> >
> > #+RESULTS:
> > :
> > : >>> 11
> >
> > I think it would be nice to sanitize the python code block sent to the
> > interpreter to eliminate the empty lines, and avoid the multiple >>> in
> > output. It would also be nice to have an option to not print those at
> > all.
> >
> > The second issue is related. The following code does not work for me in
> > :session, but it works fine as a standalone block. The issue is related
> > to the presence of an empty line in the function definition. I like
> > whitespace like this in functions sometimes for readability.
> >
> > #+BEGIN_SRC python :session
> > def func(x):
> > 'doc string'
> >
> > return x**2
> >
> > print func(2)
> > #+END_SRC
> >
> > #+RESULTS:
> > :
> > : ... >>>   File "", line 1
> > : return x**2
> > : ^
> > : IndentationError: unexpected indent
> > : >>> None
> >
> > Removing the blank line works fine, but still has some non-pretty
> > output.
> >
> > #+BEGIN_SRC python :session
> > def func(x):
> > 'doc string'
> > return x**2
> >
> > print func(2)
> > #+END_SRC
> >
> > #+RESULTS:
> > :
> > : ... ... >>> 4
> >
> > One of the ellipsis is due to the doc string.
> > #+BEGIN_SRC python :session
> > def func(x):
> > return x**2
> >
> > print func(2)
> > #+END_SRC
> >
> > #+RESULTS:
> > :
> > : ... >>> 4
> >
> > Interestingly, this did not work, because there is no empty line after
> > the function definition. So, sanitizing could be tricky.
> >
> > #+BEGIN_SRC python :session
> > def func(x):
> > 'doc string'
> > return x**2
> > print func(2)
> > #+END_SRC
> >
> > #+RESULTS:
> > :
> > : ... ...   File "", line 4
> > : print func(2)
> > : ^
> > : SyntaxError: invalid syntax
> >
> > I think if there was a way to strip all the empty lines from the input,
> > it would go a long way to making the output look like what I think most
> > people would expect and want.
> >
> > Anyway, those are the examples I wanted to highlight in this
> > post.
> >
> >
> > 1. Do you see similar behavior, or is this a feature of my setup?
>
> I haven't tried your examples (no time) but you would be able to tell if
> it was a feature of your setup by making a minimum working example and
> starting emacs with 'emacs -Q'.  If you see the thread in the footnote
> it contains such an example.
>
> > 2. Is there any interest in sanitizing the input and output of a
> > python :session to get prettier output? if so, Any hints on where to
> > start with that?
>
> I had some problems recently with :session, there was a short
> discussion[1],
> and last I heard the maintainer of python-mode.el is looking into it.
>
> Myles
>
> Footnotes:
> [1]
> https://lists.gnu.org/archive/html/emacs-orgmode/2013-01/msg00888.html
>
>
>

Re: [O] python :session issues

[Myles English]

Hi John,

John Kitchin writes:

> I have been trying to use the :session feature of babel for python code
> blocks. I have noticed a few things that might be areas for
> improvement. Some issues are related to what I think might be a need for
> sanitizing the code blocks and the output.
>
> I am using (insert (org-version)) 7.9.3a
> I am using python-mode 5.2 (more modern versions do not work with
> :session for me)
>
> The first small detail is illustrated here:
>
> #+BEGIN_SRC python :session
> a = 5
>
> b = 6
>
> print a + b
> #+END_SRC
>
> #+RESULTS:
> :
> : >>> >>> >>> 11
>
> In the output, there are three sets of >>>, due to the two empty
> lines. Compare this to
>
> #+BEGIN_SRC python :session
> a = 5
> b = 6
> print a + b
> #+END_SRC
>
> #+RESULTS:
> :
> : >>> 11
>
> I think it would be nice to sanitize the python code block sent to the
> interpreter to eliminate the empty lines, and avoid the multiple >>> in
> output. It would also be nice to have an option to not print those at
> all.
>
> The second issue is related. The following code does not work for me in
> :session, but it works fine as a standalone block. The issue is related
> to the presence of an empty line in the function definition. I like
> whitespace like this in functions sometimes for readability.
>
> #+BEGIN_SRC python :session
> def func(x):
> 'doc string'
>
> return x**2
>
> print func(2)
> #+END_SRC
>
> #+RESULTS:
> :
> : ... >>>   File "", line 1
> : return x**2
> : ^
> : IndentationError: unexpected indent
> : >>> None
>
> Removing the blank line works fine, but still has some non-pretty
> output.
>
> #+BEGIN_SRC python :session
> def func(x):
> 'doc string'
> return x**2
>
> print func(2)
> #+END_SRC
>
> #+RESULTS:
> :
> : ... ... >>> 4
>
> One of the ellipsis is due to the doc string.
> #+BEGIN_SRC python :session
> def func(x):
> return x**2
>
> print func(2)
> #+END_SRC
>
> #+RESULTS:
> :
> : ... >>> 4
>
> Interestingly, this did not work, because there is no empty line after
> the function definition. So, sanitizing could be tricky.
>
> #+BEGIN_SRC python :session
> def func(x):
> 'doc string'
> return x**2
> print func(2)
> #+END_SRC
>
> #+RESULTS:
> :
> : ... ...   File "", line 4
> : print func(2)
> : ^
> : SyntaxError: invalid syntax
>
> I think if there was a way to strip all the empty lines from the input,
> it would go a long way to making the output look like what I think most
> people would expect and want.
>
> Anyway, those are the examples I wanted to highlight in this
> post.
>
>
> 1. Do you see similar behavior, or is this a feature of my setup?

I haven't tried your examples (no time) but you would be able to tell if
it was a feature of your setup by making a minimum working example and
starting emacs with 'emacs -Q'.  If you see the thread in the footnote
it contains such an example.

> 2. Is there any interest in sanitizing the input and output of a
> python :session to get prettier output? if so, Any hints on where to
> start with that?

I had some problems recently with :session, there was a short discussion[1],
and last I heard the maintainer of python-mode.el is looking into it.

Myles

Footnotes: 
[1]  https://lists.gnu.org/archive/html/emacs-orgmode/2013-01/msg00888.html

Re: [O] New exporter, beamer confusion

[Sebastien Vauban]

Hi Rasmus,

Rasmus wrote:
> James Harkins  writes:
>
>> Btw, *who* preferred \alert? (Orwell, Politics and the English Language:
>> "Never use the passive [voice] where you can use the active.")
>
> I prefer alert.  See the Beamer manual (texdoc beamer in texlive) on
> change of style and how to use alert (e.g. alert on one particular
> (sub)slide of a "multipage slide").  It's the Beamer way.  Surely it
> cannot be a bad thing?
>
>> Still, I wonder if there is a way to make the new backend less unfriendly
>> toward lists. It's an interesting philosophical question: In what cases is
>> it better for the tool to adapt to the users' wishes, versus cases where
>> the tool should encourage (Are blocks in the result actually better than
>> lists? Who says so, and why should I take his or her word for it?)
>
> Org has many dedicated list symbols namely white space and one of
> {[-+*], [0-9][.)]}.  Why should a headline be converted to a list?  It
> was always awkward to me.

As a reminder, the conversion of headlines to lists is what "daily" happens
within common Org files converted to LaTeX documents: just play with the H
option, and you'll see your deeper levels converted to LaTeX lists.

So, this ain't specific to Beamer.

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] Archiving workflow suggestion?

[Sebastien Vauban]

Hi Vincent,

Vincent Beffara wrote:
> I am using org-mode to track various tasks, organized chronologically, like 
> this:
>
> * 2013
> ** January
> *** Task 1
> *** Task 2
> ** February
> *** Task 3
>
> Once a task is completed I want to archive it, but I find it convenient to
> keep it within the same file for further reference. Optimally, using the
> archive sibling feature to save display space. So far so good, everything if
> fine. Once all tasks in a month are completed, I want to archive the month
> itself (so that the CONTENTS view is as clean as possible).
>
> But using the default methods builds an archive-within-an-archive situation.
> I realize it's not exactly a big deal (and the correct default behavior),
> but I would like to "unarchive" the children of a newly archived month
> automatically to make later traversal easier.
>
> Any suggestion how to do that? Or hints at a better workflow to achieve the
> same thing?

For me, the best way to archive things is to add the tag `:ARCHIVE:' to the
entries, without moving them.

That way, you have a better view of your entries, without your display being
cluttered with all those archived entries (as they won't be opened, even in
the "show all contents" view). The only way to open them, for inspection, is
to C-TAB them (IIRC).

Best regards,
  Seb

-- 
Sebastien Vauban

[O] Archiving workflow suggestion?

[Vincent Beffara]

Dear list, 

I am using org-mode to track various tasks, organized chronologically, like 
this:

* 2013
** January
*** Task 1
*** Task 2
** February
*** Task 3

Once a task is completed I want to archive it, but I find it convenient to keep 
it within the same file for further reference. Optimally, using the archive 
sibling feature to save display space. So far so good, everything if fine. Once 
all tasks in a month are completed, I want to archive the month itself (so that 
the CONTENTS view is as clean as possible).

But using the default methods builds an archive-within-an-archive situation. I 
realize it's not exactly a big deal (and the correct default behavior), but I 
would like to "unarchive" the children of a newly archived month automatically 
to make later traversal easier.

Any suggestion how to do that? Or hints at a better workflow to achieve the 
same thing?

Thanks,

/v

-- 
Vincent Beffara

Re: [O] inserting a path string fires the italic formatting

[Sebastien Vauban]

Hi Luca,

Luca Ferrari wrote:
> this could be trivial, but if I have to place a unix path name into my
> org text, without having a link, how can I prevent the mode to assume
> I'm doing italic formatiing?
> For instance in the text:
>- check /usr/bin/chmod
>- check /usr/lib/bla
>
> Suggestions?

For example, by "protecting" those paths, declaring them as `org-code' or
`org-verbatim', that is using the markers `=' or `~'; for example:

- check ~/usr/bin/chmod~
- check ~/usr/bin/bla~

Best regards,
  Seb

-- 
Sebastien Vauban

[O] Worg publishing issue

[Suvayu Ali]

Hello Worgers,

Amidsts all the commotion about documentation for the new exporter, I
committed a very early incomplete draft article documenting the new
beamer exporter.



But I see that it is not being published.  I got the following
publishing error after pushing my commit.

remote: Publishing file
/home/emacs/git/worg/org-tutorials/org-beamer/org-e-beamer.org using
`org-publish-org-to-html'
remote: Exporting...
remote: Wrong type argument: stringp, nil
remote: worg publish process 16964 exited at 02/05/13@07:01:27

Any ideas?

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] New exporter, beamer confusion

[Suvayu Ali]

On Wed, Feb 06, 2013 at 01:32:22PM +0100, Rasmus wrote:
> 
> I don't know how hard it would be to make the "default" block (of
> level 3, say) a list block, but I guess that's ultimately what you
> want?  Such a behavior shouldn't be the default, IMO, since a headline
> is not a list.
> 

Nested headlines being translated to lists was always a misfeature in
the old exporter.  This was extensibly discussed on the list before
Nicolas implemented the current beamer exporter.  I do not see any
reason to not "fix" old inconsistent behaviour for the sake of backwards
compatibility.

That said, I think the best way to deal with this is to follow what
Nicolas suggested, mark the subtree and then do `C-c -' to convert these
headlines into lists.  This can be automated to a significant degree by
using keyboard macros or custom lisp.  A well tested keyboard macro can
be easily saved and used as a command.  Since the OP says his old beamer
presentations number in the hundreds, the way I would approach this is
to keep the macro/function handy and convert it if and when these
presentations are required.

Hope this helps,

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] New exporter, beamer confusion

[Rasmus]

James Harkins  writes:

> Btw, *who* preferred \alert? (Orwell, Politics and the English Language:
> "Never use the passive [voice] where you can use the active.")

I prefer alert.  See the Beamer manual (texdoc beamer in texlive) on
change of style and how to use alert (e.g. alert on one particular
(sub)slide of a "multipage slide").  It's the Beamer way.  Surely it
cannot be a bad thing?

> Still, I wonder if there is a way to make the new backend less unfriendly
> toward lists. It's an interesting philosophical question: In what cases is
> it better for the tool to adapt to the users' wishes, versus cases where
> the tool should encourage (Are blocks in the result actually better than
> lists? Who says so, and why should I take his or her word for it?)

Org has many dedicated list symbols namely white space and one of
{[-+*], [0-9][.)]}.  Why should a headline be converted to a list?  It
was always awkward to me.

I don't know how hard it would be to make the "default" block (of
level 3, say) a list block, but I guess that's ultimately what you
want?  Such a behavior shouldn't be the default, IMO, since a headline
is not a list.


> "Reasonably" for me would mean tweaking some configuration options and
> perhaps changing a few minor details of the markup. If you have to change
> the org document's structure (e.g., converting headlines to lists), it
> isn't backward compatible.

I'm sure it would be relatively quick to hack together a couple of
regexps and some lisp to do the conversion if you prefer to use the
new exporter.  E.g. find every occurrence of * in the beginning of the
line of length X and convert each occurrence to "-" with appropriate
white space (e.g. X + N).

What might be useful would be a tag telling Org to use the legacy
exporter on a file basis, although it would also be a short run
solution.

–Rasmus

--
Summon the Mothership!

[O] inserting a path string fires the italic formatting

[Luca Ferrari]

Hi all,
this could be trivial, but if I have to place a unix path name into my
org text, without having a link, how can I prevent the mode to assume
I'm doing italic formatiing?
For instance in the text:
   - check /usr/bin/chmod
   - check /usr/lib/bla

I got italic from the first slash to the last slash in the second line.
Suggestions?

Thanks,
Luca

Re: [O] [PATCH] Stop with an error if the LaTeX class is not known to the new exporter

[Sebastien Vauban]

Hi Eric,

Eric S Fraga wrote:
> Sebastien Vauban  writes:
>> I've lost (a bit of) time looking at why my documents were wrong with the new
>> exporter. The fact is I've customized:
>
> Ah ha!  We've found the same problem through different routes.  See my
> recent email re: beamer export also resulting in a latex file with no
> documentclass.

Absolutely... I was reading you in the other thread first, and was thinking:
that wouldn't have happen anymore with my patch! ;-)

Best regards,
  Seb

-- 
Sebastien Vauban

[O] [New exporter] Error: (wrong-type-argument stringp nil)

[Sebastien Vauban]

Hello,

Trying to convert some more files (to HTML) with the new exporter, I did a
test with the following one:

--8<---cut here---start->8---
#+TITLE: ECM for HTML export error
#+LANGUAGE:  en_US

* Tasks

*** TODO Read article

- [[https://lists.gnu.org/archive/html/emacs-orgmode/2012-09/msg01099.html][new 
exporter: exporting subtree as beamer]]
--8<---cut here---end--->8---

When exporting it to HTML (`C-c C-e h o'), I get the following error:

--8<---cut here---start->8---
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  regexp-quote(nil)
  (string-match (regexp-quote (car att)) desc)
  (and desc (string-match (regexp-quote (car att)) desc))
  (if (and desc (string-match (regexp-quote (car att)) desc)) nil att)
  (let ((att (org-element-property :attr_html (org-export-get-parent-element 
link (if (and desc (string-match (regexp-quote (car att)) desc)) nil att))
  (mapconcat (quote identity) (let ((att (org-element-property :attr_html 
(org-export-get-parent-element link (if (and desc (string-match 
(regexp-quote (car att)) desc)) nil att)) " ")
  (setq attributes (mapconcat (quote identity) (let ((att (org-element-property 
:attr_html (org-export-get-parent-element link (if (and desc (string-match 
(regexp-quote (car att)) desc)) nil att)) " "))
  (and (setq attributes (mapconcat (quote identity) (let ((att 
(org-element-property :attr_html (org-export-get-parent-element link (if 
(and desc (string-match (regexp-quote ...) desc)) nil att)) " ")) (setq 
attributes (concat " " attributes)))
  (let* ((--link-org-files-as-html-maybe (function (lambda (raw-path info) 
"Treat links to `file.org' as links to `file.html', if needed.\n   See 
`org-e-html-link-org-files-as-html'." (cond ((and 
org-e-html-link-org-files-as-html ...) (concat ... "." ...)) (t raw-path) 
(type (org-element-property :type link)) (raw-path (org-element-property :path 
link)) (desc (and (not (string= desc "")) desc)) (path (cond ((member type 
(quote ("http" "https" "ftp" "mailto"))) (concat type ":" raw-path)) ((string= 
type "file") (setq raw-path (funcall --link-org-files-as-html-maybe raw-path 
info)) (if (not (file-name-absolute-p raw-path)) raw-path (concat "file://" 
(expand-file-name raw-path (t raw-path))) attributes protocol) (and (setq 
attributes (mapconcat (quote identity) (let ((att (org-element-property 
:attr_html ...))) (if (and desc (string-match ... desc)) nil att)) " ")) (setq 
attributes (concat " " attributes))) (cond ((and (or (eq t 
org-e-html-inline-images) (and org-e-html-inline-images (not desc))) 
(org-export-inline-image-p link org-e-html-inline-image-rules)) 
(org-e-html-link--inline-image link desc info)) ((string= type "radio") (let 
((destination (org-export-resolve-radio-link link info))) (if destination 
(progn (format "%s" (org-export-solidify-link-text path) 
attributes (org-export-data ... info)) ((member type (quote ("custom-id" 
"fuzzy" "id"))) (let ((destination (if (string= type "fuzzy") 
(org-export-resolve-fuzzy-link link info) (org-export-resolve-id-link link 
info (let ((--cl-var-- (org-element-type destination))) (cond ((eql 
--cl-var-- ...) (progn ... nil) (let ... ...)) ((memql --cl-var-- ...) (format 
"%s" ...)) ((eql --cl-var-- ...) nil) ((eql --cl-var-- ...) (let ... 
...)) (t (let ... ... ...)) ((string= type "coderef") (let ((fragment 
(concat "coderef-" path))) (format "%s" fragment 
(format (concat "class=\"coderef\"" " onmouseover=\"CodeHighlightOn(this, 
'%s');\"" " onmouseout=\"CodeHighlightOff(this, '%s');\"") fragment fragment) 
attributes (format (org-export-get-coderef-format path desc) 
(org-export-resolve-coderef path info) ((functionp (setq protocol (nth 2 
(assoc type org-link-protocols (funcall protocol (org-link-unescape path) 
desc (quote html))) ((and path desc) (format "%s" path 
attributes desc)) (path (format "%s" path attributes 
path)) (t (format "%s" desc
  org-e-html-link((link (:type "https" :path 
"//lists.gnu.org/archive/html/emacs-orgmode/2012-09/msg01099.html" :raw-link 
"https://lists.gnu.org/archive/html/emacs-orgmode/2012-09/msg01099.html"; 
:application nil :search-option nil :begin 118 :end 235 :contents-begin 192 
:contents-end 233 :post-blank 0 :parent (paragraph (:begin 118 :end 236 
:contents-begin 118 :contents-end 236 :post-blank 0 :post-affiliated 118 
:parent (item (:bullet "- " :begin 116 :end 236 :contents-begin 118 
:contents-end 236 :checkbox nil :counter nil :hiddenp nil :structure ((116 0 "- 
" nil nil nil 236)) :post-blank 0 :tag nil :parent (plain-list (:type unordered 
:begin 116 :end 236 :contents-begin 116 :contents-end 236 :structure ... 
:post-blank 0 :post-affiliated 116 :parent ...) #4)) #2)) #0 #("\n" 0 1 
(:parent #2 #("new exporter: exporting subtree as beamer" 0 41 (:parent 
#0))) #("new exporter: exporting subtree as beamer" 0 41 (:par