Re: [O] Bug: External links buggy with 8.3.1 [8.3.1 (8.3.1-dist @ c:/org-mode/org/)]

2015-09-25 Thread AW
No idea, nobody? Or keeping the tidbits for the weekend?!

Am Donnerstag, 24. September 2015, 15:49:08 schrieb AW:
> To: emacs-orgmode@gnu.org
> Subject: Bug: External links buggy with 8.3.1 [8.3.1 (8.3.1-dist @ c:/org-
> mode/org/)]
> From: aw@PC-21-W8.i-did-not-set--mail-host-address--so-tickle-me
> --text follows this line--
> 
> Remember to cover the basics, that is, what you expected to happen and
> what in fact did happen.  You don't know how to make a good report?  See
> 
>  http://orgmode.org/manual/Feedback.html#Feedback
> 
> Your bug report will be posted to the Org-mode mailing list.
> 
> 
> I'm using link abbrevations. The abbrevations are stored in a file and
> this file is loaded in my .emacs. I hit this bug only on Windows 8.1,
> not under Linux.
> 
> Code of abbrevations as example:
> 
> (setq org-link-abbrev-alist
>(if (eq system-type 'windows-nt)
>   '(("NameA" . "//Sbs2011/Bilder/2011/271-2011/%s")
>   ("NameB" .  "//Sbs2011/Bilder/2012/351-2012/%s")
> )
>   '(("NameA" . "/home/AW/Dokumente/2011-271/%s")
>   ("NameB" .  "/home/AW/Dokumente/2012-351/%s")
> )))
> 
> With orgmode 8.2.10 the links work. Example for link: [[NameA:filename.pdf]
> [whatever]]
> 
> With orgmode 8.3.1 I get the message e.g.:
> 
> user-error: No such file: u:/Sbs2011/Bilder/2011/271-2011/filename.pdf
> 
> You see, orgmode 8.3.1 modifies for no apparent reason the link from
> "//sbs2011..." to "u:/sbs2011..."
> 
> The share "u:" exists, HOME is u:/emacs. This is the orgmode version from
> orgmode.org, not elpa.
> 
> Emacs  : GNU Emacs 25.0.50.5 (x86_64-w64-mingw32)
>  of 2015-09-21 on PC-21-W8
> Package: Org-mode version 8.3.1 (8.3.1-dist @ c:/org-mode/org/)
> 
> current state:
> ==
> (setq
>  org-tab-first-hook '(org-hide-block-toggle-maybe
> org-babel-hide-result-toggle-maybe
> org-babel-header-arg-expand)
>  org-speed-command-hook '(org-speed-command-default-hook
> org-babel-speed-command-hook)
>  org-occur-hook '(org-first-headline-recenter)
>  org-metaup-hook '(org-babel-load-in-session-maybe)
>  org-confirm-shell-link-function 'yes-or-no-p
>  org-after-todo-state-change-hook '(org-clock-out-if-current)
>  org-src-mode-hook '(org-src-babel-configure-edit-buffer
>org-src-mode-configure-edit-buffer)
>  org-agenda-before-write-hook '(org-agenda-add-entry-text)
>  org-babel-pre-tangle-hook '(save-buffer)
>  org-mode-hook '(#[nil "\300\301\302\303\304$\207"
>  [org-add-hook change-major-mode-hook org-show-block-all
>   append local]
>  5]
>#[nil "\300\301\302\303\304$\207"
>  [org-add-hook change-major-mode-hook
>   org-babel-show-result-all append local]
>  5]
>org-babel-result-hide-spec org-babel-hide-all-hashes)
>  org-archive-hook '(org-attach-archive-delete-maybe)
>  org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point
> org-babel-execute-safely-maybe)
>  org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
> org-cycle-show-empty-lines
> org-optimize-window-after-visibility-change)
>  org-link-abbrev-alist   '(("NameA" .
> "//Sbs2011/Bilder/2011/271-2011/%s") ("NameB" .
> "//Sbs2011/Bilder/2012/351-2012/%s")
> );;; CAVE: I deleted the real output and wrote my example 
>  org-confirm-elisp-link-function 'yes-or-no-p
>  org-metadown-hook '(org-babel-pop-to-session-maybe)
>  org-agenda-files '("u:/Emacs/Sonstiges.org" "u:/Emacs/this.org"
>   "u:/Emacs/that.org" "u:/Emacs/Privat.org"
> )
>  org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
>  )
> -




[O] emacs-lisp babel won't print

2015-09-25 Thread Lawrence Bottorff
If I do this:

#+BEGIN_SRC emacs-lisp
(setq animals '(gazelle giraffe lion tiger))
#+END_SRC

#+RESULTS:
| gazelle | giraffe | lion | tiger |

and then this

#+begin_src emacs-lisp
(defun print-elements-of-list (list)
  "Print each element of LIST on a line of its own."
  (while list
(print (car list))
(setq list (cdr list
#+end_src

#+RESULTS:
: print-elements-of-list

and finally

#+BEGIN_SRC emacs-lisp
(print-elements-of-list animals)
#+END_SRC

I get nothing for results and "Code block produced no output." in Messages.
Why can't it print out? Same code works fine in the IELM buffer.

LB


Re: [O] help debugging org-element crashes?

2015-09-25 Thread Suvayu Ali
On Fri, Sep 25, 2015 at 01:34:50PM +0200, Nicolas Goaziou wrote:
> Hello,
> 
> Suvayu Ali  writes:
> 
> > @Nicolas, others, do you think this should be on an FAQ on worg?
> 
> Not yet, please. I plan to change the internals of the cache at some
> point, when I get sufficient spare time.

Sure!

-- 
Suvayu

Open source is the future. It sets us free.



Re: [O] The Org Manual

2015-09-25 Thread Jonathan Leech-Pepin
Hello,

On 24 September 2015 at 18:01, Rasmus  wrote:

> nascii boy  writes:
>
> > Org advancement manual in org
> >
> > https://github.com/nasciiboy/TheOrgManual
>
> Interesting.  Is this a port of the current org manual?  Does it produce
> good texi code with ox-texi?
>

Looking at it it looks as though it is an exact recreation of the
existing manual (did not verify version).

It includes all the texi-like section menus as manually created
targets.  This will not end up producing the expected out put in
ox-texinfo because those menu entries are dynamically generated in a
TOC-esque manner.  I did not look through to see if the various
indices and other texi-specific features were accounted for or just
hard coded in.

Regards,
Jon


> Thanks,
> Rasmus
>
> --
> Er du tosset for noge' lårt!
>
>
>


Re: [O] help debugging org-element crashes?

2015-09-25 Thread Nicolas Goaziou
Hello,

Suvayu Ali  writes:

> @Nicolas, others, do you think this should be on an FAQ on worg?

Not yet, please. I plan to change the internals of the cache at some
point, when I get sufficient spare time.

Regards,

-- 
Nicolas Goaziou



Re: [O] emacs-lisp babel won't print

2015-09-25 Thread John Kitchin
try:

#+BEGIN_SRC emacs-lisp :results output
(print-elements-of-list animals)
#+END_SRC

the default results are value, and your function does not return
anything I think. It prints them to output.

Lawrence Bottorff writes:

> If I do this:
>
> #+BEGIN_SRC emacs-lisp
> (setq animals '(gazelle giraffe lion tiger))
> #+END_SRC
>
> #+RESULTS:
> | gazelle | giraffe | lion | tiger |
>
> and then this
>
> #+begin_src emacs-lisp
> (defun print-elements-of-list (list)
>   "Print each element of LIST on a line of its own."
>   (while list
> (print (car list))
> (setq list (cdr list
> #+end_src
>
> #+RESULTS:
> : print-elements-of-list
>
> and finally
>
> #+BEGIN_SRC emacs-lisp
> (print-elements-of-list animals)
> #+END_SRC
>
> I get nothing for results and "Code block produced no output." in Messages.
> Why can't it print out? Same code works fine in the IELM buffer.
>
> LB

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



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

2015-09-25 Thread Charles C. Berry

On Thu, 24 Sep 2015, Nicolas Goaziou wrote:


Hello,

"Charles C. Berry"  writes:


On Tue, 22 Sep 2015, Charles C. Berry wrote:

Just to tie this up, this is an issue with `org-src-preserve-indentation',
see

(info "(org) Editing source code")

for the best documentation. I found the "replace sequences of spaces with
tab characters" for nil values confusing. The opposite is happening in
this example.


Would you want to write a documentation patch about it?



Attached is a patch.

I think it is an improvement, but `org-src-preserve-indentation' behaves 
differently according to context, which makes it hard to document 
succinctly.


In brief:

Setting to `t' or `nil' will keep or allow removal of tabs in these 
functions:


org-babel-parse-src-block-match
org-babel-haskell-export-to-lhs
org-babel-spec-to-string
org-src--edit-element
org-edit-src-code

but have no effect on embedded tabs in

org-babel-exp-process-buffer
org-export-unravel-code
org-element-src-block-interpreter
org-element-example-block-interpreter
org-fixup-indentation

Also, as briefly noted in the doc/org.texi part of the patch global 
indent/outdent operations (e.g. org-metaright on a heading) are affected.

This might make sense but sometimes the results surprise me.

HTH,

Chuck
From 12a912e9cbc1b2b475632dd724ca55af54b56236 Mon Sep 17 00:00:00 2001
From: Charles Berry 
Date: Fri, 25 Sep 2015 12:02:32 -0700
Subject: [PATCH] org-src-preserve-indentation: docstring and info fixes

doc/org.texi: The `Literal examples' node mentions the effect of the
  `-i' switch on embedded tabs.

  The `Editing source code' node correctly states that
  setting `org-src-preserve-indentation' to `t' prevents
  converting tabs to spaces.  Also, its effect on
  indentation operations is noted. A mention of the `-i'
  switch is given.

lisp/org-src.el: The `org-src-preserve-indentation' docstring mentions
 the effect of setting its value to `t' is to protect
 conversion of tabs to spaces.
---
 doc/org.texi| 17 ++---
 lisp/org-src.el |  7 ---
 2 files changed, 14 insertions(+), 10 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index 8de8efc..62c39e3 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -10053,8 +10053,8 @@ jumps to point-min.
 @end example
 
 @cindex indentation, in source blocks
-Finally, you can use @code{-i} to preserve the indentation of a specific code
-block (@pxref{Editing source code}).
+Finally, you can use @code{-i} to preserve the indentation and tab
+characters of a specific code block (@pxref{Editing source code}).
 
 @vindex org-coderef-label-format
 If the syntax for the label format conflicts with the language syntax, use a
@@ -14826,11 +14826,14 @@ Controls the way Emacs windows are rearranged when 
the edit buffer is created.
 @cindex indentation, in source blocks
 By default, the value is @code{nil}, which means that when code blocks are
 evaluated during export or tangled, they are re-inserted into the code block,
-which may replace sequences of spaces with tab characters.  When 
non-@code{nil},
-whitespace in code blocks will be preserved during export or tangling,
-exactly as it appears.  This variable is especially useful for tangling
-languages such as Python, in which whitespace indentation in the output is
-critical.
+which may replace tab characters with sequences of spaces.  When
+non-@code{nil}, whitespace in code blocks will be preserved during export or
+tangling, exactly as it appears.  This variable is especially useful for
+tangling languages such as Python, in which whitespace indentation in the
+output is critical.  A value of @code{t} prevents global indent/outdent
+operations from moving source or example block contents. The @code{-i} switch
+has a similar effect on a single source or example block (@pxref{Literal
+examples}).
 @item org-src-ask-before-returning-to-edit-buffer
 By default, Org will ask before returning to an open edit buffer.  Set this
 variable to @code{nil} to switch without asking.
diff --git a/lisp/org-src.el b/lisp/org-src.el
index 9c205e1..394633d 100644
--- a/lisp/org-src.el
+++ b/lisp/org-src.el
@@ -108,9 +108,10 @@ These are the regions where each line starts with a colon."
 
 (defcustom org-src-preserve-indentation nil
   "If non-nil preserve leading whitespace characters on export.
-If non-nil leading whitespace characters in source code blocks
-are preserved on export, and when switching between the org
-buffer and the language mode edit buffer.
+If non-nil leading whitespace characters and embedded tab
+characters in source code blocks are preserved on export, and
+when switching between the org buffer and the language mode edit
+buffer.
 
 When this variable is nil, after editing with \\[org-edit-src-code],
 the minimum (across-lines) number of leading whitespace characters
-- 
2.3.8 (Apple Git-58)



[O] Italicized code/verbatim blocks

2015-09-25 Thread Kaushal Modi
Hi all,

I got intrigued by this question on emacs.SE:
http://emacs.stackexchange.com/q/16915/115

The example that the OP uses reveals a bug (I believe).

If you type the below in an org-mode buffer:

call the /static/ method =something(/$with/, /$param/)=


​you see that the $with and $param are italicized even when they are
surrounded by verbatim markers (doesn't matter what the value of
org-emphasis-hide-markers is).

The export of that to HTML and LaTeX works fine.
​

​That led me to try to find a solution to get italicized code/verbatim
blocks in HTML/LaTeX exports but I couldn't find a way to do it.
​


--
Kaushal Modi


Re: [O] emacs-lisp babel won't print

2015-09-25 Thread Charles Millar

maybe add :results output to the last block

On 09/25/2015 12:04 PM, Lawrence Bottorff wrote:

#+BEGIN_SRC emacs-lisp
(setq animals '(gazelle giraffe lion tiger))
#+END_SRC

#+RESULTS:
| gazelle | giraffe | lion | tiger |

and then this

#+begin_src emacs-lisp
(defun print-elements-of-list (list)
  "Print each element of LIST on a line of its own."
  (while list
(print (car list))
(setq list (cdr list
#+end_src

#+RESULTS:
: print-elements-of-list

and finally

#+BEGIN_SRC emacs-lisp
(print-elements-of-list animals)
#+END_SRC





Re: [O] The Org Manual

2015-09-25 Thread nascii boy
org Hello dear community, the manual is a port of texi manually exported to
html, passed org Pandoc and formated by hand. texi okay to make books. but
PDFs and web pages are a nuisance as quick method of consultation (compared
to org).

is my ideal to have only with org books that can be read without further
Emacs and have a nice appearance, efficiency and puts org

the vension manual is an advance, do not understand much English but
have already
begun to introduce the Spanish. at the end I would like to take care of the
version of the manual in org-mode, but I leave the job for someone shares
this vision, to start from scratch ne

-- nasciiboy

# hola querida comunidad org, el manual es un port del manual texi
# exportado a html, pasado a org mediante pandoc y maquetado a
# mano. texi esta bien para hacer libros. pero los pdf's y las paginas
# web son un fastidio como metodo rapido de consulta ( comparados con
# org).
#
# es mi ideal contar con libros solo con org que se puedan leer en Emacs
# sin mas y que tengan una apariencia linda, la eficacia ya la pone org
#
# la vension del manual, es un adelanto, no entiendo mucho ingles pero
# ya he empezado a troducir al español. al terminar me gustaria
# encargarme de la version del manual en org-mode, sin enmbargo dejo el
# trabajo por si alguien comparte esta vision, para que ne empiese de
# cero La función sprintf realiza las mismas conversiones que printf,
# pero almacena la salida en de una cadena:


Re: [O] Bug: External links buggy with 8.3.1 [8.3.1 (8.3.1-dist @ c:/org-mode/org/)]

2015-09-25 Thread Nicolas Goaziou
Hello,

AW  writes:

> No idea, nobody? Or keeping the tidbits for the weekend?!

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou



Re: [O] Bug: org-capture-refile doc inconsistency, refile bug [8.3.1 (8.3.1-129-ga7c8d2-elpaplus @ /home/jeeger/.emacs.d/elpa/org-plus-contrib-20150921/)]

2015-09-25 Thread Nicolas Goaziou
Hello,

Jan Seeger  writes:

> I've reworked the patch to restore the original order of
> org-capture-finalize and org-capture-refile, but working around the
> interaction with :kill-buffer that required reversing the order in the
> first place.
>
> org-capture-finalize requires the capture buffer to be set up
> correctly, and restoring this correctly after refiling appears to
> require a lot of work.

Thank you. 

Could you provide an appropriate commit message and send it with git
format-patch? You may need to add TINYCHANGE at the end of the message.

> +(if kill-buffer
> + (kill-buffer base

(when kill-buffer (kill-buffer base))


Regards,

-- 
Nicolas Goaziou



Re: [O] Capture questions

2015-09-25 Thread Xebar Saram
anyone?

thx so much in advance

Z

On Sun, Sep 20, 2015 at 2:38 PM, Xebar Saram  wrote:

> Hi all!
>
> I finally had time to properly setup capture for orgmode and i have a few
> questions
>
> 1) can one define default and/or completion values for capture properties
> in the property drawers, in example:
>
> %^{Rating}p
>
> so that when I launch the capture and it goes through entering a specific
> property value I will get some defaults to choose from or a completion
> option?
>
> 2) can one customize the help line (the one with hints like C-c C-k to
> kill etc..) to include more hints?
>
> 3) im looking for a way to better insert a sub header
> currently my template looks like this
>
>  food simple template
> ("f" "food" entry (file+headline "/home/zeltak/org/files/agenda/food.org"
> "Inbox")
> "* COOK %^{Description}   %^g
> %t
> %^{Time}p
> %^{Rating}p
> %^{Source}p
> %^{Ammount}p
> %^{Fav}p
> %^{prompt|** Ingridients}
> %?
> %^{prompt|** Preperation}
> "
>  )
>
> Note that I use %^{prompt|** Ingridients} to force a subheader, which
> seems to be odd. I couldn't find a better way to do that without getting
> lisp errors
>
>
> 4) can one use multikeys as capture keys such as
> ("xd" "nix_TD" entry (file+headline "~/org/files/agenda/TODO.org" "TODO")
>  "*  %^{Description}" )
> the use of 2 keys like 'xd' doesn't seem to work here
>
> 5)can I capture and automatically refile to a specific file. In example
> only ask to refile to headers in a pre
> defined files?
>
> 6)has anyone tried using hydra for org capture (instead of dispatch), this
> will have nicer looks and color support etc :) is this possible?
>
>


[O] cant get todos with #A priorities to show up first with dispatcher

2015-09-25 Thread Xebar Saram
Hi all

i use the orgmode's dispatcher to show my todos per file. for some reason i
cant get the #A priorities to show up first. here is what i have in my
config:



("f" "food" todo "COOK"
 (
 (org-agenda-files '("~/org/files/agenda/food.org"))
  (org-agenda-sorting-strategy  '(priority-down))
)
)


any clue?

thx

Z


Re: [O] Exporter aborts upon encountering even one unresolvable link

2015-09-25 Thread Rainer M Krug
"D. C. Toedt"  writes:

> I just updated to 8.3.1 from 8.3beta (from git).  That appears to have been
> a terrible mistake on my part.>
> From this thread
>  I
> see that the exporter now throws an error and aborts when it encounters an
> unresolvable link.  That makes things really, REALLY difficult.  It means I
> can't get a complete, working export to HTML (in my case) until all link
> problems are fixed in my 22KLOC .org file (which I use to generate
> http://www.CommonDraft.org/index.html
> ).  That seems EXTREMELY suboptimal.
> (I'm trying to be tactful here.)

See the thread 
,
|  Bug: Export to html fails when link to header in non existing file in
|  document present WAS: Error export to html - "Org-publish-cache-get:
|  `org-publish-cache-get' called, but no cache present" [8.3beta
|  (release_8.3beta-1115-g8f3946 @
|  /Users/rainerkrug/.emacs.d/org-mode/lisp/)]
`

For further details.

>
> Worse, the exporter doesn't even generate a list of unresolvable links
> before aborting.  That means the only way that I can find and fix busted
> links (so far as I know) is to do an export --- which takes several minutes
> given the large file  --- and have the export abort on a single link. Then
> I fix that one link, export again, and have it abort again. Repeat.
> Aaaargg.

You can use org-lint for this.

>
> I started looking at the hooks, as suggested in a message in the previous
> thread, but I'm not nearly skilled enough in elisp to be able to do
> anything useful.

Look at publishing instead of exporting to html which works with
missing links.

I have the following in my emacs.org which makes it possible to publish
all org files to html in the folder ./pubHTML/ which is equivalent to
exporting.

#+begin_src emacs-lisp 
(setq org-publish-project-alist
  '(
("local"
 :base-directory "./"
 :base-extension "org"
 :publishing-directory "./pubHTML/"
 :recursive t
 :publishing-function org-html-publish-to-html
 :headline-levels 6
 :auto-preamble t)
))
#+end_src

Cheers,

Rainer

>
> Any suggestions?
>
>
> *D. C. Toedt III  **(My last name is pronounced "Tate"; I go by "D. C.,"
> which stands for Dell Charles**) *
> Attorney & neutral arbitrator -- tech contracts & IP  |  Adjunct professor,
> University of Houston Law Center
> ​Author, ​​​Common Draft  desk book of
> contract clauses & research notes   |  LinkedIn: dctoedt
>    |   Calendar
> 
> (redacted)
> E: d...@toedt.comO: +1 (713) 364-6545C: +1 (713) 516-8968
> ​​
>
> ​
> Houston, Texas (Central time zone)
>
> Unless expressly stated otherwise, this message is not intended
> to serve as assent to an agreement or other document, whether or not
> attached to this message.

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

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

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

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

email:  rai...@krugs.de

Skype:  RMkrug

PGP: 0x0F52F982


signature.asc
Description: PGP signature


Re: [O] Exporter aborts upon encountering even one unresolvable link

2015-09-25 Thread Rainer M Krug
"D. C. Toedt"  writes:

> P.S.:   Thank heavens for Time Machine.

True - but mainly for other things.


>
>
>
>
> On Thu, Sep 24, 2015 at 9:50 PM, D. C. Toedt  wrote:
>
>> I just updated to 8.3.1 from 8.3beta (from git).  That appears to have
>> been a terrible mistake on my part.
>>
>> From this thread
>> 
>> I see that the exporter now throws an error and aborts when it encounters
>> an unresolvable link.  That makes things really, REALLY difficult.  It
>> means I can't get a complete, working export to HTML (in my case) until all
>> link problems are fixed in my 22KLOC .org file (which I use to generate
>> http://www.CommonDraft.org/index.html
>> ).  That seems EXTREMELY
>> suboptimal. (I'm trying to be tactful here.)
>>
>> Worse, the exporter doesn't even generate a list of unresolvable links
>> before aborting.  That means the only way that I can find and fix busted
>> links (so far as I know) is to do an export --- which takes several minutes
>> given the large file  --- and have the export abort on a single link.
>> Then I fix that one link, export again, and have it abort again. Repeat.
>> Aaaargg.
>>
>> I started looking at the hooks, as suggested in a message in the previous
>> thread, but I'm not nearly skilled enough in elisp to be able to do
>> anything useful.
>>
>> Any suggestions?
>>
>>
>> *D. C. Toedt III  **(My last name is pronounced "Tate"; I go by "D. C.,"
>> which stands for Dell Charles**) *
>> Attorney & neutral arbitrator -- tech contracts & IP  |  Adjunct
>> professor, University of Houston Law Center
>> ​Author, ​​​Common Draft  desk book of
>> contract clauses & research notes   |  LinkedIn: dctoedt
>>    |   Calendar
>> 
>> (redacted)
>> E: d...@toedt.comO: +1 (713) 364-6545C: +1 (713) 516-8968
>> ​​
>>
>> ​
>> Houston, Texas (Central time zone)
>>
>> Unless expressly stated otherwise, this message is not intended
>> to serve as assent to an agreement or other document, whether or not
>> attached to this message.
>>
>>
>>

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

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

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

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

email:  rai...@krugs.de

Skype:  RMkrug

PGP: 0x0F52F982


signature.asc
Description: PGP signature


Re: [O] help debugging org-element crashes?

2015-09-25 Thread Rainer M Krug
Peter Salazar  writes:

> Hey everyone,
>
> I'm finding my Emacs crashing a lot; other times I get errors like these
> which I assume are related to the crashes:
> http://pastebin.com/Tncs79r0
> http://pastebin.com/jfdEYwVk
>
> I mean total Emacs crashes, where I have to force quit Emacs itself. It's
> happened in various org-mode situations including:
> - pasting text from OSX clipboard
> - promoting/demoting org-headings
> - moving subtree up or down (i.e. using org-metadown org org-metaup)

I also experience frequent crashes at the moment and they happen in
similar situations.

I am in contact with an emacs dev to give him all the info needed to
sort out what is happening.

I would suggest that you file a bug report including backtrace of emacs
after the crash so that this can be followed up as a new bug or added as
additional data points to my bug report.

You could try to use HEAD - but I had the same crashes there.

You can see my bug report and tips on how to figure out what is
happening at https://debbugs.gnu.org/cgi/bugreport.cgi?bug=21428

Cheers,

Rainer

>
> My details:
>
> Mac OSX Yosemite 10.10.5
> GNU Emacs 24.5.1 (x86_64-apple-darwin14.5.0, Carbon Version 157 AppKit
> 1348.17)
> Org-mode version 8.3.1 (8.3.1-129-ga7c8d2-elpaplus @
> org-plus-contrib-20150921/)
>
> I've tried reinstalling org-plus-contrib... I have also enabled
> org-element-debug.
>
> Any suggestions on how I can track this down and fix it?
>
> Thanks!

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

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

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

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

email:  rai...@krugs.de

Skype:  RMkrug

PGP: 0x0F52F982


signature.asc
Description: PGP signature


[O] [Babel R] Error evaluating table

2015-09-25 Thread Loris Bennett
Hi,

With the following


#+NAME: numbers
| 1 |
| 2 |
| 3 |

#+NAME: mean
#+HEADER: :var data=numbers
#+BEGIN_SRC R
mean(data)
#+END_SRC


I get the error:


Error: unexpected input in:
"   #("\"1\"
\"
Execution halted


when I execute the source block.  I'm fairly sure something like this
used to work.  I'm using

8.3.1-129-ga7c8d2-elpaplus @ 
/home/loris/.emacs.d/elpa/org-plus-contrib-20150921/)

but, of course, I may have overtweaked my .emacs at some point.

Any ideas?

Cheers,

Loris

-- 
This signature is currently under construction.




Re: [O] help debugging org-element crashes?

2015-09-25 Thread Suvayu Ali
On Thu, Sep 24, 2015 at 04:30:13PM -0400, Peter Salazar wrote:
> Hey everyone,
> 
> I'm finding my Emacs crashing a lot; other times I get errors like these
> which I assume are related to the crashes:
> http://pastebin.com/Tncs79r0
> http://pastebin.com/jfdEYwVk
> 
> I mean total Emacs crashes, where I have to force quit Emacs itself. It's
> happened in various org-mode situations including:
> - pasting text from OSX clipboard
> - promoting/demoting org-headings
> - moving subtree up or down (i.e. using org-metadown org org-metaup)

 [...chomp...chomp...chomp...]

> Any suggestions on how I can track this down and fix it?

You could use this minor mode to track down the cache issue:

https://github.com/suvayu/.emacs.d/blob/master/lisp/org-element-debug.el

Once you know what triggers the crash, you can probably come-up with a
minimal example and post it here.

@Nicolas, others, do you think this should be on an FAQ on worg?

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.



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

2015-09-25 Thread Nicolas Goaziou
Hello,

Richard Hansen  writes:

> The intended meanings of #+INCLUDE and #+SETUPFILE have never been clear
> to me, so I have a couple of questions:

INCLUDE is only expanded during export. SETUPFILE are parsed when
refreshing document properties (e.g., when using C-c C-c on a keyword).

>   * What is supposed to happen if you have a #+SETUPFILE that has
> an #+INCLUDE?

Org will SETUPFILE when refreshing document properties, but will parse
it when exporting the document.

>   * What is supposed to happen if you have an #+INCLUDE file that
> has a #+SETUPFILE line?

Nothing. Contents of a SETUPFILE are not inserted in the current
document. INCLUDE keywords are not read when refreshing properties.


Regards,



Re: [O] Quoting "_" for html and LaTeX output

2015-09-25 Thread Peter Davis

Thanks, Nicolas and Nick. The option solves it perfectly.

Cheers,
-pd

On 9/24/15 3:29 PM, Peter Davis wrote:
A lot of the information I track in org-mode includes filepaths and 
names and other strings containing underscore ("_") characters. I'd 
like to be able to quote these for HTML and LaTeX output, so I don't 
wind up with unwanted subscripts.


On the other hand, I want the data to be pretty readable within the 
org buffer, so using \under{} pretty much fails that.


Is there another, more concise way to do this, possible for large 
stretches of text at a time? I don't want to use an example block, as 
I still want to format the text and avoid the mono-spaced font.


I understand that "\_" used to work, but doesn't on more recent 
versions. Any chance of getting that back?


Thanks!
-pd






Re: [O] [PATCH 2/2] fix SETUPFILE pathname expansion from within an INCLUDE

2015-09-25 Thread Nicolas Goaziou
Hello,

Richard Hansen  writes:

> * lisp/ox.el (defun org-export-expand-include-keyword):  cd instead of
> passing DIR to expand-file-name so that if the INCLUDE file has a
> SETUPFILE line with a relative pathname the full pathname to the
> SETUPFILE will be expanded properly.

SETUPFILE within INCLUDE doesn't do what you think.

Org first includes contents from all INCLUDE keyword, then reads read
SETUPFILE keywords.

>
> Assume the following files:
>
>   /home/foo/a.org:
> #+INCLUDE: subdir/b.org
>
>   /home/foo/subdir/b.org:
> #+SETUPFILE: c.org
>
>   /home/foo/subdir/c.org:
> stuff

In your example, a.org becomes

  #+SETUPFILE: c.org

So, it is meant to look after /home/foo/c.org.
 

Regards,

-- 
Nicolas Goaziou



Re: [O] Bug: org-capture-refile doc inconsistency, refile bug [8.3.1 (8.3.1-129-ga7c8d2-elpaplus @ /home/jeeger/.emacs.d/elpa/org-plus-contrib-20150921/)]

2015-09-25 Thread Jan Seeger
Hello! 
Thanks for your reply. However, the current behavior definitely results in bugs 
when refiling from the capture buffer (newlines don't get deleted properly, for 
example). 

I'll look into how to correctly set the position for org-capture-finalize after 
the refile then, and try to make a patch for that.
Regards,
Jan

Am 24. September 2015 22:54:38 MESZ, schrieb Nicolas Goaziou 
:
>Hello,
>
>Jan Seeger  writes:
>
>> I've fixed this bug for me by reversing the order of finalization and
>> refiling, as stated in the documentation. I've attached a patch to do
>> this, but I'm not entirely sure about the side effects caused by the
>> patch. The test suite does pass though. If someone could weigh in on
>> this, I'd be grateful!
>
>Thank you for the patch. However, it contradicts
>47b0eec8dc39990731f400640d64ab70a8356ccd.
>
>See thread starting
> for an
>explanation.
>
>
>Regards,
>
>-- 
>Nicolas Goaziou

-- 
Diese Nachricht wurde von meinem Mobiltelefon gesendet.

Re: [O] [Babel R] Error evaluating table

2015-09-25 Thread Nicolas Goaziou
Hello,

"Loris Bennett"  writes:

> With the following
>
> 
> #+NAME: numbers
> | 1 |
> | 2 | 3 |
>
> #+NAME: mean
> #+HEADER: :var data=numbers
> #+BEGIN_SRC R
> mean(data)
> #+END_SRC
> 
>
> I get the error:
>
> 
> Error: unexpected input in:
> "   #("\"1\"
> \"
> Execution halted
> 
>
> when I execute the source block.  I'm fairly sure something like this
> used to work.  I'm using
>
> 8.3.1-129-ga7c8d2-elpaplus @ 
> /home/loris/.emacs.d/elpa/org-plus-contrib-20150921/)
>
> but, of course, I may have overtweaked my .emacs at some point.
>
> Any ideas?

This bug was fixed a short time ago. It hasn't reached ELPA yet, but
should be available by Monday.

Regards,

-- 
Nicolas Goaziou



Re: [O] Bug: org-capture-refile doc inconsistency, refile bug [8.3.1 (8.3.1-129-ga7c8d2-elpaplus @ /home/jeeger/.emacs.d/elpa/org-plus-contrib-20150921/)]

2015-09-25 Thread Nicolas Goaziou
Hello,

Jan Seeger  writes:

> Thanks for your reply. However, the current behavior definitely
> results in bugs when refiling from the capture buffer (newlines don't
> get deleted properly, for example).

I agree. I'm just pointing out we shouldn't step back and re-introduce
a fixed issue.

> I'll look into how to correctly set the position for
> org-capture-finalize after the refile then, and try to make a patch
> for that.

Thank you.


Regards,

-- 
Nicolas Goaziou0x80A93738



Re: [O] Bug: org-capture-refile doc inconsistency, refile bug [8.3.1 (8.3.1-129-ga7c8d2-elpaplus @ /home/jeeger/.emacs.d/elpa/org-plus-contrib-20150921/)]

2015-09-25 Thread Jan Seeger
Hello!

I've reworked the patch to restore the original order of
org-capture-finalize and org-capture-refile, but working around the
interaction with :kill-buffer that required reversing the order in the
first place.

org-capture-finalize requires the capture buffer to be set up
correctly, and restoring this correctly after refiling appears to
require a lot of work.

Regards,
Jan

diff --git a/lisp/org-capture.el b/lisp/org-capture.el
index 67dc319..3d5df83 100644
--- a/lisp/org-capture.el
+++ b/lisp/org-capture.el
@@ -792,7 +792,10 @@ already gone.  Any prefix argument will be passed to the 
refile command."
  "Refiling from a capture buffer makes only sense for `entry'-type 
templates"))
   (let ((pos (point))
(base (buffer-base-buffer (current-buffer)))
-   (org-refile-for-capture t))
+   (org-refile-for-capture t)
+   (kill-buffer (org-capture-get :kill-buffer 'local)))
+(org-capture-put :kill-buffer nil)
+(org-capture-finalize)
 (save-window-excursion
   (with-current-buffer (or base (current-buffer))
(save-excursion
@@ -800,7 +803,8 @@ already gone.  Any prefix argument will be passed to the 
refile command."
(widen)
(goto-char pos)
(call-interactively 'org-refile)
-(org-capture-finalize)))
+(if kill-buffer
+   (kill-buffer base
 
 (defun org-capture-kill ()
   "Abort the current capture process."


Re: [O] Outut file name by backend

2015-09-25 Thread Rasmus
Fabrice Popineau  writes:

> Hi,
>
> Could it be made possible that the output file name when exporting be
> chosen by backend ?
> Something like :
>
> :EXPORT_FILE_NAME: (by-backend (latex "PDFL2A/pdf/pdl2a.tex) (html
> "PDFL2A/projets.html"))
>
> Am I missing another option here ?

Could you use ox-publish?

-- 
Together we'll stand, divided we'll fall