Re: [O] Bug: Literal Examples are malformed in exports (to html/tex) [8.0.3 (release_8.0.3-165-g60ca9e @ /home/quazimodo/.emacs.d/vendor/org-mode/lisp/)]

[Nicolas Goaziou]

Hello,

S S  writes:

> Problem found and solved, how do we close things?

Just let them fade away.

> lua-mode was modifying stuff in the same syntax table that org-mode
> 8.0 + was using. lua-mode has updated since and problem is solved, my
> repo was out of date. Thanks and sorry about cluttering up the mailing
> list. Took a while to figure out what was going on.

It was a strange problem indeed.

> https://github.com/immerrr/lua-mode/
> 1st commit that caused the conflict: c2f8a7f8
> 1st commit that solved the conflict: 9f5107ef

Interesting. Thank you for reporting back that the problem was solved.


Regards,

-- 
Nicolas Goaziou

[O] [Need a feature] complete email with alias in gnus

[Feng Shu]

Hi:

I want to complete email with alias instead of name, when I write a mail
in gnus.

I'm using  a tmp solution now, however it is nearly imposssible to be included 
into master,

so I have to rebase this patch every pull, I want to find a better solution,

Coule someone can help me ?


#+begin_example
,[ 0001-org-contacts.el-stupid-solutions-which-can-complete-.patch ]
| From 27b896a813203bad7c55dece6bc37cd2eeff0f40 Mon Sep 17 00:00:00 2001
| From: Feng Shu 
| Date: Thu, 11 Apr 2013 21:12:38 +0800
| Subject: [PATCH] org-contacts.el, stupid solutions which can  complete email
|  address using alias  in message-mode
| 
| * contrib/lisp/org-contacts.el (org-contacts-complete-name): Add alias varible
| ---
|  contrib/lisp/org-contacts.el |4 +++-
|  1 个文件被修改，插入 3 行(+)，删除 1 行(-)
| 
| diff --git a/contrib/lisp/org-contacts.el b/contrib/lisp/org-contacts.el
| index 7b0b603..999bd5d 100644
| --- a/contrib/lisp/org-contacts.el
| +++ b/contrib/lisp/org-contacts.el
| @@ -488,11 +488,13 @@ A group FOO is composed of contacts with the tag FOO."
|   for email-list = (org-contacts-split-property (or
|   (cdr (assoc-string 
org-contacts-email-property
|  (caddr 
contact))) ""))
| + for alias = (cdr (assoc-string org-contacts-alias-property 
(caddr contact)))
|   ;; If the user has email addresses…
|   if email-list
|   ;; … append a list of USER .
|   nconc (loop for email in email-list
| - collect (org-contacts-format-email contact-name 
(org-contacts-strip-link email)
| + collect (org-contacts-format-email (if alias
| +(concat 
contact-name "(" alias ")") contact-name)  (org-contacts-strip-link email)
|(completion-list (org-contacts-all-completions-prefix
|  string
|  (org-uniquify completion-list
| -- 
| 1.7.10.4
| 
`


#+end_example







-- 

Re: [O] [PATCH] org-contacts.el: add expire feature

[Daimrod]

Feng Shu  writes:

> Daimrod  writes:
>
>>
>> This is not very idiomatic elisp, I would write something more like:
>> #+BEGIN_SRC emacs-lisp
>>   (remove-if (lambda (el)
>>(member el expire-list)) 
>>  list)
>> #+END_SRC
>
> Thanks!
>
> Is this possible?
>
>  test1@g  =  te...@gmail.com

Yes, you could do it like this:
#+BEGIN_SRC emacs-lisp
  (remove-if (lambda (el)
   (find-if (lambda (x)
  (string-match-p x el))
expire-list))
 list)
#+END_SRC

This way you can use regular expressions in the ignore list.

-- 
Daimrod/Greg


signature.asc
Description: PGP signature

Re: [O] Guidance for preparing document with code

[SabreWolfy]

Hi Thorsten,

Thanks for the links.

Re: [O] [PATCH] org-contacts.el: add expire feature

[Feng Shu]

Daimrod  writes:

> Feng Shu  writes:
>
>> Daimrod  writes:
>>
>>>
>>> This is not very idiomatic elisp, I would write something more like:
>>> #+BEGIN_SRC emacs-lisp
>>>   (remove-if (lambda (el)
>>>(member el expire-list)) 
>>>  list)
>>> #+END_SRC
>>
>> Thanks!
>>
>> Is this possible?
>>
>>  test1@g  =  te...@gmail.com
>
> Yes, you could do it like this:
> #+BEGIN_SRC emacs-lisp
>   (remove-if (lambda (el)
>(find-if (lambda (x)
>   (string-match-p x el))
> expire-list))
>  list)
> #+END_SRC
>
> This way you can use regular expressions in the ignore list.

It's very power,I will copy it! 
Thanks!

-- 

[O] How to prevent tabs from turning into spaces in source-code export?

[James Harkins]

I have (where  is a tab character):

#+BEGIN_SRC {}
// SuperCollider code here

(
r = p.chan.play(Pspawner { |sp|
var num, subdiv,
...
});
)
#+END_SRC

The exported .tex file contains:

\begin{lstlisting}
// SuperCollider code here

(
r = p.chan.play(Pspawner { |sp|
var num, subdiv,
...
});
)
\end{lstlisting}

I do not want this conversion to happen. If it doesn't happen, then I
can use listings' tabsize property to control the tab width.

Failing that, how do I tell org to use fewer than 8 spaces? The tabs
are much much too wide in the resulting pdf.

hjh

Re: [O] Guidance for preparing document with code

[SabreWolfy]

Sebastien Vauban  writes:

> Little starter for your R code:
> 
> #+BEGIN_SRC R :results graphics :file testout.png
> plot(1:10, (1:10)^2)
> #+END_SRC



w00t! I exported a quick structured document, with text, code and the "png"
file as an HTML document. This is super-cool :) I should have figured out
how to this ages ago. Thanks for the example. And thanks to Carsten, /et
al./ too ;)

Re: [O] [PATCH] org-contacts.el: add expire feature

[Feng Shu]

Daimrod  writes:

> Feng Shu  writes:
>
>> Daimrod  writes:
>>
>>>
>>> This is not very idiomatic elisp, I would write something more like:
>>> #+BEGIN_SRC emacs-lisp
>>>   (remove-if (lambda (el)
>>>(member el expire-list)) 
>>>  list)
>>> #+END_SRC
>>
>> Thanks!
>>
>> Is this possible?
>>
>>  test1@g  =  te...@gmail.com
>
> Yes, you could do it like this:
> #+BEGIN_SRC emacs-lisp
>   (remove-if (lambda (el)
>(find-if (lambda (x)
>   (string-match-p x el))
> expire-list))
>  list)
> #+END_SRC
>
> This way you can use regular expressions in the ignore list.

Hi Daimrod!
This is the 3 updated patch, if possible, please include it to master.

Thanks for your help!

>From 362bf0657a0a270416d5e9b51aaba868ad963439 Mon Sep 17 00:00:00 2001
From: Feng Shu 
Date: Wed, 29 May 2013 20:30:43 +0800
Subject: [PATCH] Add a feature, which can ignore emails or phones with
 property

* contrib/lisp/org-contacts.el (org-contacts-ignore-property): New variable.
(org-contacts-remove-ignored-property-values): New function, which
remove all ignore-list's elements from list.
(org-contacts-complete-name): When completing, ignore the
values which has been included into the ignore property.
(org-contacts-vcard-format): Don't export the values which has
been included into the ignore property.

If emails or phones is included into the ignore property, they will
not show in complete buffer. When the contact is exported to vcard,
they will be ignored too.
---
 contrib/lisp/org-contacts.el |   34 +-
 1 个文件被修改，插入 29 行(+)，删除 5 行(-)

diff --git a/contrib/lisp/org-contacts.el b/contrib/lisp/org-contacts.el
index 7b0b603..2aee0f6 100644
--- a/contrib/lisp/org-contacts.el
+++ b/contrib/lisp/org-contacts.el
@@ -86,6 +86,11 @@ When set to nil, all your Org files will be used."
   :type 'string
   :group 'org-contacts)
 
+(defcustom org-contacts-ignore-property "IGNORE"
+  "Name of the property,  which values will be ignored when complete or export to vcard."
+  :type 'string
+  :group 'org-contacts)
+
 
 (defcustom org-contacts-birthday-format "Birthday: %l (%Y)"
   "Format of the anniversary agenda entry.
@@ -476,6 +481,16 @@ A group FOO is composed of contacts with the tag FOO."
 		(completion-table-case-fold completion-list
 	(not org-contacts-completion-ignore-case
 
+
+(defun org-contacts-remove-ignored-property-values (ignore-list list)
+  "Remove all ignore-list's elements from list and you can use
+   regular expressions in the ignore list."
+(remove-if (lambda (el)
+   (find-if (lambda (x)
+  (string-match-p x el))
+ignore-list))
+ list))
+
 (defun org-contacts-complete-name (start end string)
   "Complete text at START with a user name and email."
   (let* ((completion-ignore-case org-contacts-completion-ignore-case)
@@ -484,10 +499,17 @@ A group FOO is composed of contacts with the tag FOO."
 		;; The contact name is always the car of the assoc-list
 		;; returned by `org-contacts-filter'.
 		for contact-name = (car contact)
+
+		;; Build the list of the email addresses which has
+		;; been expired
+		for ignore-list = (org-contacts-split-property (or
+(cdr (assoc-string org-contacts-ignore-property
+		   (caddr contact))) ""))
 		;; Build the list of the user email addresses.
-		for email-list = (org-contacts-split-property (or
-		(cdr (assoc-string org-contacts-email-property
-   (caddr contact))) ""))
+		for email-list = (org-contacts-remove-ignored-property-values ignore-list
+	  (org-contacts-split-property (or
+	(cdr (assoc-string org-contacts-email-property
+			   (caddr contact))) "")))
 		;; If the user has email addresses…
 		if email-list
 		;; … append a list of USER .
@@ -869,15 +891,17 @@ to do our best."
 	 (n (org-contacts-vcard-encode-name name))
 	 (email (cdr (assoc-string org-contacts-email-property properties)))
 	 (tel  (cdr (assoc-string org-contacts-tel-property properties)))
+	 (ignore  (cdr (assoc-string org-contacts-ignore-property properties)))
 	 (note (cdr (assoc-string org-contacts-note-property properties)))
 	 (bday (org-contacts-vcard-escape (cdr (assoc-string org-contacts-birthday-property properties
 	 (addr (cdr (assoc-string org-contacts-address-property properties)))
 	 (nick (org-contacts-vcard-escape (cdr (assoc-string org-contacts-nickname-property properties
 	 (head (format "BEGIN:VCARD\nVERSION:3.0\nN:%s\nFN:%s\n" n name))
+	 (ignore-list (when ignore (setq ignore-list (org-contacts-split-property ignore
 	 emails-list result phones-list)
 (concat head
 	(when email (progn
-			  (setq emails-list (org-contacts-split-property email))
+			  (setq emails-list (org-contacts-remove-ignored-property-values ignore-list (org-contacts-split-property email)))
 			  (setq result "")
 		

[O] Exporting output and graphics from R

[SabreWolfy]

When the following code is evaluated or exported, only the link to
"testout.png" appears in the RESULTS section.

--8<---cut here---start->8---
#+BEGIN_SRC R :results output graphics :file testout.png :exports both
plot(1:10, 1:10)
x <- 1:10
library(ascii)
options(asciiType = "org")
ascii(x)
#+END_SRC
--8<---cut here---end--->8---

When this code is evaluated, the value of "x" appears in the RESULTS:

--8<---cut here---start->8---
#+BEGIN_SRC R :results output :exports both
x <- 1:10
library(ascii)
options(asciiType = "org")
ascii(x)  
#+END_SRC
--8<---cut here---end--->8---

How can I get the first example to output both graphics and ascii output?
I'm using Org 7.9.2.

Re: [O] Exporting output and graphics from R

[Sebastien Vauban]

Hi SabreWolfy,

SabreWolfy wrote:
> When the following code is evaluated or exported, only the link to
> "testout.png" appears in the RESULTS section.
>
> #+BEGIN_SRC R :results output graphics :file testout.png :exports both
> plot(1:10, 1:10)
> x <- 1:10
> library(ascii)
> options(asciiType = "org")
> ascii(x)
> #+END_SRC

Removing `output' here should solve the above point.

> When this code is evaluated, the value of "x" appears in the RESULTS:
>
> #+BEGIN_SRC R :results output :exports both
> x <- 1:10
> library(ascii)
> options(asciiType = "org")
> ascii(x)
> #+END_SRC
>
> How can I get the first example to output both graphics and ascii output?

AFAICT, you can't have both at the same time. Do you have a real use case for
this?

If really needed, you can define your code once, wrap it with some value for
the ":results" header, and "copy" it somewhere else via Noweb's facility,
where it can be evaluated under other values for the ":results" header.

> I'm using Org 7.9.2.

Try upgrading now to Org 8 so that you fiddle only once with the export
variables -- which changed, even if similar, between Org 7.9 and Org 8.

Best regards,
  Seb

-- 
Sebastien Vauban

[O] how i can unsubscribe this mail list

[Tongzhu Zhang]

i want read this mail list from gnus in emacs, but i cant remember my
password, i have been already tried :
https://lists.gnu.org/mailman/options/emacs-orgmode

but no mail received .
how i can do now ?

Re: [O] Problem when EXPORT_FILE_NAME contains a subdirectory

[Nicolas Goaziou]

Hello,

Martin Marier  writes:

> When trying to export a subtree as PDF in a subdirectory, I get this
> error:
> ! I can't write on file `test.log'.
>
> This is using this source:
>
> * head 1
>   :PROPERTIES:
>   :EXPORT_FILE_NAME: pdf/test.pdf
>   :END:
>   Moo Moo Moo.
> * head 2
>
> This used to work fine with the old exporter.  It I remove the
> subdirectory :
>   :EXPORT_FILE_NAME: test.pdf
>
> Everything works as expected.  Is this intended behavior?  Is there a
> work around that would let me export to a subdirectory?

I just fixed a bug around the same area: when providing a relative path,
pdf file was produced but not found and process returned an error.
Though, the error message wasn't the same.

Could you test it again with an updated Org anyway?


Regards,

-- 
Nicolas Goaziou

Re: [O] Exporting output and graphics from R

[Rainer M. Krug]

"Sebastien Vauban" 
writes:

> Hi SabreWolfy,
>
> SabreWolfy wrote:
>> When the following code is evaluated or exported, only the link to
>> "testout.png" appears in the RESULTS section.
>>
>> #+BEGIN_SRC R :results output graphics :file testout.png :exports both
>> plot(1:10, 1:10)
>> x <- 1:10
>> library(ascii)
>> options(asciiType = "org")
>> ascii(x)
>> #+END_SRC
>
> Removing `output' here should solve the above point.
>
>> When this code is evaluated, the value of "x" appears in the RESULTS:
>>
>> #+BEGIN_SRC R :results output :exports both
>> x <- 1:10
>> library(ascii)
>> options(asciiType = "org")
>> ascii(x)
>> #+END_SRC
>>
>> How can I get the first example to output both graphics and ascii output?
>
> AFAICT, you can't have both at the same time. Do you have a real use case for
> this?

Not directly, But I used the following approach to include pdf as well
as jpeg ion a document.

You simply have to create your graph in R and then include a link in org
manually:

,
| #+BEGIN_SRC R :results output :exports both
| png("testout.png")
| plot(1:10, 1:10)
| dev.off()
| x <- 1:10
| library(ascii)
| options(asciiType = "org")
| ascii(x)  
| #+END_SRC
| 
| 
| [[./testout.png]]
`

you will get the code, result (output) and the graph (tested on export
to pdf).

Cheers,

Rainer

>
> If really needed, you can define your code once, wrap it with some value for
> the ":results" header, and "copy" it somewhere else via Noweb's facility,
> where it can be evaluated under other values for the ":results" header.
>
>> I'm using Org 7.9.2.
>
> Try upgrading now to Org 8 so that you fiddle only once with the export
> variables -- which changed, even if similar, between Org 7.9 and Org 8.
>
> Best regards,
>   Seb
<#secure method=pgpmime mode=sign>

-- 
Rainer M. Krug

[O] how i can unsubscribe this mail list ?

[Tongzhu Zhang]

i want read this mail list from gnus in emacs, but i cant remember my
password, i have been already tried :
https://lists.gnu.org/mailman/options/emacs-orgmode

but no mail received .
how i can do now ?

Re: [O] Exporting output and graphics from R

[Feng Shu]

rai...@krugs.de (Rainer M. Krug) writes:

> "Sebastien Vauban" 
> writes:
>
>> Hi SabreWolfy,
>>
>> SabreWolfy wrote:
>>> When the following code is evaluated or exported, only the link to
>>> "testout.png" appears in the RESULTS section.
>>>
>>> #+BEGIN_SRC R :results output graphics :file testout.png :exports both
>>> plot(1:10, 1:10)
>>> x <- 1:10
>>> library(ascii)
>>> options(asciiType = "org")
>>> ascii(x)
>>> #+END_SRC
>>
>> Removing `output' here should solve the above point.
>>
>>> When this code is evaluated, the value of "x" appears in the RESULTS:
>>>
>>> #+BEGIN_SRC R :results output :exports both
>>> x <- 1:10
>>> library(ascii)
>>> options(asciiType = "org")
>>> ascii(x)
>>> #+END_SRC
>>>
>>> How can I get the first example to output both graphics and ascii output?
>>
>> AFAICT, you can't have both at the same time. Do you have a real use case for
>> this?
>
> Not directly, But I used the following approach to include pdf as well
> as jpeg ion a document.
>
> You simply have to create your graph in R and then include a link in org
> manually:
>
> ,
> | #+BEGIN_SRC R :results output :exports both
> | png("testout.png")
> | plot(1:10, 1:10)
> | dev.off()
> | x <- 1:10
> | library(ascii)
> | options(asciiType = "org")
> | ascii(x)  
> | #+END_SRC
> | 
> | 
> | [[./testout.png]]
> `
>


 #+BEGIN_SRC R :results output :exports both
 pngname <- "testout.png"
 png(pngname)
 plot(1:10, 1:10)
 dev.off()
 x <- 1:10
 paste("[[./", pngname, "]]",sep="")
 #+END_SRC



> you will get the code, result (output) and the graph (tested on export
> to pdf).
>
> Cheers,
>
> Rainer
>
>>
>> If really needed, you can define your code once, wrap it with some value for
>> the ":results" header, and "copy" it somewhere else via Noweb's facility,
>> where it can be evaluated under other values for the ":results" header.
>>
>>> I'm using Org 7.9.2.
>>
>> Try upgrading now to Org 8 so that you fiddle only once with the export
>> variables -- which changed, even if similar, between Org 7.9 and Org 8.
>>
>> Best regards,
>>   Seb
> <#secure method=pgpmime mode=sign>
>

-- 

Re: [O] How to prevent tabs from turning into spaces in source-code export?

[Nicolas Goaziou]

Hello,

James Harkins  writes:

> I have (where  is a tab character):
>
> #+BEGIN_SRC {}
> // SuperCollider code here
>
> (
> r = p.chan.play(Pspawner { |sp|
> var num, subdiv,
> ...
> });
> )
> #+END_SRC
>
> The exported .tex file contains:
>
> \begin{lstlisting}
> // SuperCollider code here
>
> (
> r = p.chan.play(Pspawner { |sp|
> var num, subdiv,
> ...
> });
> )
> \end{lstlisting}
>
> I do not want this conversion to happen. If it doesn't happen, then I
> can use listings' tabsize property to control the tab width.

Try to preserve indentation:

  #+begin_src {} -i
  ...
  #+end_src


Regards,

-- 
Nicolas Goaziou

Re: [O] Fix `listings' language for `latex' code blocks

[Nicolas Goaziou]

Hello,

"Sebastien Vauban" 
writes:

> Listings should use the LaTeX flavor of the TeX language for `latex' code
> blocks.
>
> Here is the patch therefore.

Applied. Thank you.


Regards,

-- 
Nicolas Goaziou

Re: [O] Exporting output and graphics from R

[Rainer M. Krug]

Feng Shu  writes:

> rai...@krugs.de (Rainer M. Krug) writes:
>
>> "Sebastien Vauban" 
>> writes:
>>
>>> Hi SabreWolfy,
>>>
>>> SabreWolfy wrote:
 When the following code is evaluated or exported, only the link to
 "testout.png" appears in the RESULTS section.

 #+BEGIN_SRC R :results output graphics :file testout.png :exports both
 plot(1:10, 1:10)
 x <- 1:10
 library(ascii)
 options(asciiType = "org")
 ascii(x)
 #+END_SRC
>>>
>>> Removing `output' here should solve the above point.
>>>
 When this code is evaluated, the value of "x" appears in the RESULTS:

 #+BEGIN_SRC R :results output :exports both
 x <- 1:10
 library(ascii)
 options(asciiType = "org")
 ascii(x)
 #+END_SRC

 How can I get the first example to output both graphics and ascii output?
>>>
>>> AFAICT, you can't have both at the same time. Do you have a real use case 
>>> for
>>> this?
>>
>> Not directly, But I used the following approach to include pdf as well
>> as jpeg ion a document.
>>
>> You simply have to create your graph in R and then include a link in org
>> manually:
>>
>> ,
>> | #+BEGIN_SRC R :results output :exports both
>> | png("testout.png")
>> | plot(1:10, 1:10)
>> | dev.off()
>> | x <- 1:10
>> | library(ascii)
>> | options(asciiType = "org")
>> | ascii(x)  
>> | #+END_SRC
>> | 
>> | 
>> | [[./testout.png]]
>> `
>>
>
>
>  #+BEGIN_SRC R :results output :exports both
>  pngname <- "testout.png"
>  png(pngname)
>  plot(1:10, 1:10)
>  dev.off()
>  x <- 1:10
>  paste("[[./", pngname, "]]",sep="")
>  #+END_SRC
>

There are many ways to kill a bird - but you are right - this one is
nicer. You could even use an org variable to specify the file name.

Cheers,

Rainer


>
>
>> you will get the code, result (output) and the graph (tested on export
>> to pdf).
>>
>> Cheers,
>>
>> Rainer
>>
>>>
>>> If really needed, you can define your code once, wrap it with some value for
>>> the ":results" header, and "copy" it somewhere else via Noweb's facility,
>>> where it can be evaluated under other values for the ":results" header.
>>>
 I'm using Org 7.9.2.
>>>
>>> Try upgrading now to Org 8 so that you fiddle only once with the export
>>> variables -- which changed, even if similar, between Org 7.9 and Org 8.
>>>
>>> Best regards,
>>>   Seb
>> <#secure method=pgpmime mode=sign>
>>
>
<#secure method=pgpmime mode=sign>

-- 
Rainer M. Krug

Re: [O] How to prevent tabs from turning into spaces in source-code export?

[Andreas Röhler]

Am 30.05.2013 15:22, schrieb Nicolas Goaziou:

Hello,

James Harkins  writes:


I have (where  is a tab character):

#+BEGIN_SRC {}
// SuperCollider code here

(
r = p.chan.play(Pspawner { |sp|
var num, subdiv,
...
});
)
#+END_SRC

The exported .tex file contains:

\begin{lstlisting}
// SuperCollider code here

(
r = p.chan.play(Pspawner { |sp|
var num, subdiv,
...
});
)
\end{lstlisting}

I do not want this conversion to happen. If it doesn't happen, then I
can use listings' tabsize property to control the tab width.


Try to preserve indentation:

   #+begin_src {} -i
   ...
   #+end_src


Regards,



Hi Nicolas,

as indentation might be provided by TAB and whitespace chars likewise, what 
about following setting of `indent-tabs-mode'?

Best,

Andreas

[O] de-tangle function?

[Rainer M. Krug]

Hi

I remember something about a de-tangle function, which re-imports the
source code blocks into the org file is previously tangled with comments
et al, but I can't find that function any more.

Is it still there? Does it work reliably?

Thanks,

Rainer

-- 
Rainer M. Krug


pgpgePIeqq7XT.pgp
Description: PGP signature

Re: [O] Problem when EXPORT_FILE_NAME contains a subdirectory

[Martin Marier]

2013-05-30 08:39   Nicolas Goaziou :
>
> I just fixed a bug around the same area: when providing a relative path,
> pdf file was produced but not found and process returned an error.
> Though, the error message wasn't the same.
>
> Could you test it again with an updated Org anyway?

Yes.  I just updated and I still get the same problem.  The full output
is here:

> Wrote /home/myHome/aFolderWithAnOrgFile/pdf/test.tex
> Processing LaTeX file ./pdf/test.tex...
> This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian)
> entering extended mode
> ! I can't write on file `test.log'.
> (Press Enter to retry, or Control-D to exit; default file extension is `.log')
> Please type another transcript file name
> ! Emergency stop
> !  ==> Fatal error occurred, no output PDF file produced!

Since I use the "run latex three times" option, this output appears
three times.  Thank you for looking into that!

Martin
-- 
Martin Marier
http://www.martinmarier.com


smime.p7s
Description: S/MIME cryptographic signature

[O] refine org-babel-tangle-jump-to-org?

[Rainer M. Krug]

Hi

I am using  org-babel-tangle-jump-to-org when debugging code written in
org and tangled. I have some longisch code blocks and it is always
irritating, as it only jumps to the codde block. Would it be possible to
extend the function, that it jumps to the line of the code?
That would make this funktion much more user friendly.

Thanks,

Rainer

-- 
Rainer M. Krug


pgpSW5XKkPSlx.pgp
Description: PGP signature

Re: [O] how i can unsubscribe this mail list

[Memnon Anon]

Looking at the header of your mail (`t' in gnus :), you'll see this
line:

List-Unsubscribe: , 


So, did you try to send an email to emacs-orgmode-requ...@gnu.org
with the a subject "unsubscribe" ?

hth
Memnon

Re: [O] Problem when EXPORT_FILE_NAME contains a subdirectory

[Nicolas Goaziou]

Martin Marier  writes:

> Yes.  I just updated and I still get the same problem.  The full output
> is here:
>
>> Wrote /home/myHome/aFolderWithAnOrgFile/pdf/test.tex
>> Processing LaTeX file ./pdf/test.tex...
>> This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian)
>> entering extended mode
>> ! I can't write on file `test.log'.
>> (Press Enter to retry, or Control-D to exit; default file extension is 
>> `.log')
>> Please type another transcript file name
>> ! Emergency stop
>> !  ==> Fatal error occurred, no output PDF file produced!
>
> Since I use the "run latex three times" option, this output appears
> three times.  Thank you for looking into that!

I don't think it is related to Org.

Do you have write access on "test.log" file in that directory? Also,
what happens if you remove it first and export the document twice?


Regards,

-- 
Nicolas Goaziou

Re: [O] Minor problems with dvipng latex image preview

[Nicolas Goaziou]

Hello,

Nick Dokos  writes:

> I wouldn't say inferior, although the dvipng implementation is slightly
> more brittle than the imagemagick one (imo, of course). But it is two
> implementations where one would suffice (Windows might present problems
> however: I don't know the availability of dvipng/imagemagick on that
> platform - I believe they are both available on MacOS, but I could be
> wrong).

What about asking, in a fresh thread, the users about it, then? FWIW,
I'm all for anything related to spring cleaning.

>> Also, imagemagick is not optimal either. Since it uses
>> `org-latex-pdf-process', "pdflatex" is called three times by default,
>> which is unnecessary for a short snippet.

> Agreed again (about the self-documenting part: not sure about the URL
> not being very handy), but some things are just too fiddly to fit into a
> few sentences. I have now written a document of 335 lines (still not
> done and only covering the options available today, but I am trying to
> provide enough context to make it stand on its own): I may be suffering
> from Pascal's syndrome ("Forgive the length of this letter; I did not
> have the time to make it shorter") and I do tend to be verbose in
> explanations (as some people on this list can probably testify), but I'm
> not sure I can shorten it by much, even if I suddenly turn into
> Hemingway - yeah, I wish :-)
>
> In any case, a note like "If you get into trouble or you want to know
> more, see FOO for the gory details" does not seem too bad to me.

So be it. Tell me when the worg page is ready, I'll update the docstring
accordingly.

> Optimal in what sense? Also, I'm not sure what you mean by a "meta
> debug" variable. I was thinking of a more global debug variable (it
> would e.g. subsume the role of org-export-async-debug), but you
> are right that it's more complicated than that: e.g. there is the
> question of what all the intermediate files are and where they are
> located.

"debug" can cover many different cases, and a "meta", i.e. global,
variable would have to explain all of them in its docstring. In the end,
the net gain for adding such a variable is not clear (besides
discoverability, but is it important for this kind of variable?).

> That's why I wanted a log message in *Messages*: I could then say "keep
> all intermediate files" by turning on the variable, carry out the
> operation and then look in *Messages* to find out where those files are
> - no mucking around through the sources. What I do now is find the
> function that produces the file(s), and either edebug it, break at (or
> just after) the call-process call site and evaluate the variables to
> figure out where everything is, then go look at them; or add a (debug)
> call just after and otherwise proceed the same way.
>
> It's not too bad, but I like systems that can tell me what they are
> doing, so if the need arises, I can easily figure out what went wrong.

Improvements to the debug system need to be discussed thoroughly in
order to set up complete specifications (I don't think it's just about
latex snippets).

This cannot happen as a side note in a thread between you and me. If you
think it is important enough, please initiate the process in a new
thread.


Regards,

-- 
Nicolas Goaziou

Re: [O] How to prevent tabs from turning into spaces in source-code export?

[Nicolas Goaziou]

Hello,

Andreas Röhler  writes:

> as indentation might be provided by TAB and whitespace chars likewise,
> what about following setting of `indent-tabs-mode'?

It is indeed possible to propagate `indent-tabs-mode' value to the
original buffer's copy where export happens, but it will not be enough
to guaranty that indentation related TAB characters are preserved (e.g.,
if relative indentation falls below `tab-width' value although global
one was above).

The only way to make sure TAB will be preserved is to set
`org-src-preserve-indentation' to a non-nil value (or, locally, to use
"-i" switch).


Regards,

-- 
Nicolas Goaziou

Re: [O] Minor problems with dvipng latex image preview

[Nick Dokos]

Nicolas Goaziou  writes:


>> But it is two implementations where one would suffice (Windows might
>> present problems however: I don't know the availability of
>> dvipng/imagemagick on that platform - I believe they are both
>> available on MacOS, but I could be wrong).
>
> What about asking, in a fresh thread, the users about it, then? FWIW,
> I'm all for anything related to spring cleaning.
>

OK, will do.

> So be it. Tell me when the worg page is ready, I'll update the docstring
> accordingly.
>

OK, will do.

> Improvements to the debug system need to be discussed thoroughly in
> order to set up complete specifications (I don't think it's just about
> latex snippets).
>
> This cannot happen as a side note in a thread between you and me. If you
> think it is important enough, please initiate the process in a new
> thread.

OK, will do.

Thanks!
-- 
Nick (AKA "broken record")

Re: [O] Problem when EXPORT_FILE_NAME contains a subdirectory

[Martin Marier]

2013-05-30 11:01   Nicolas Goaziou :
> I don't think it is related to Org.
>
> Do you have write access on "test.log" file in that directory? 

Yes I do.  And by the way, the .tex file is rendered correctly in the
pdf/ folder.

> Also, what happens if you remove it first and export the document
> twice?

I get the same error twice.

And just to make sure I was expressing myself clearly: this happens when
exporting a subtree only; there is no issue when exporting the full
document.  You (or anyone else) can't reproduce the problem?

Thanks!
Martin
-- 
Martin Marier
http://www.martinmarier.com

Re: [O] de-tangle function?

[Sebastien Vauban]

Hi Rainer,

Rainer M. Krug wrote:
> I remember something about a de-tangle function, which re-imports the
> source code blocks into the org file is previously tangled with comments
> et al, but I can't find that function any more.
>
> Is it still there?

M-x org-babel-detangle

> Does it work reliably?

You need the code blocks to be wrapped into comments for it to work.

Regarding reliability, it does work well on small examples. I remember having
had really bad results with my huge .emacs file, but hadn't any time to debug
the problem -- try to reproduce -- at that time.

So, when you do it, please keep a backup of your original Org file. It's
safer.

But, if there are bugs, they should be clearly identified, and fixed...

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] [PATCH] org.el: Don't flyspell check within source code blocks

[Matt Lundin]

Bastien  writes:

> Hi Trevor,
>
> Trevor Murphy  writes:
>
>> + (not (eq (org-element-type (org-element-at-point)) 'src-block)
>
> I think `org-in-src-block-p', while a bit less reliable, will be
> faster, and reliable/fast enough for this use-case.
>
> Let's see what others think/test.

For the record, here are the results of a very unscientific profiling of
the patch above. On my woefully under-powered and aging Atom processor,
For each scenario I typed without errors "The quick brown fox jumps over
the lazy dog."

With the old behavior (i.e., no test for source blocks):

org-mode-flyspell-verify  27  0.005580378   0.0002066806

With the patch above:

org-mode-flyspell-verify  27  0.353597550.0130962055

Using (not (org-in-src-block-p)), as Bastien suggests:

org-mode-flyspell-verify  27  0.0112581490  0.0004169684

With org-in-src-block-p, a half of a hundredth of a second spread over
27 characters causes no noticeable slowdowns.

But using org-element-at-point causes the cursor to lag a bit.

So +1 is for (not (org-in-src-block-p)).

Best,
Matt

Re: [O] [PATCH] org-contacts.el: add expire feature

[Karl Voit]

* Daimrod  wrote:
>
> Feng Shu  writes:
>
>> * test
>>   :PROPERTIES:
>>   :EMAIL: te...@gmail.com  te...@gmail.com  te...@gmail.com
>>   :PHONE:  123456  123457 123458
>>   :EXPIRE:  te...@gmail.com 123457
>>   :END:
>>
>> when completing or exporting to vcard,  the emails and  phones in the
>> expire property (te...@gmail.com and 123457) will be ignore

This is a very good patch, fixing an issue I also do have currently.

> Since the purpose of this property is to ignore some values when
> exporting to vcard, don't you think it would be better to name it IGNORE
> or VCARD_IGNORE? (and of course to rename all functions accordingly)

I totally agree.

At first, I could not follow Feng Shu's explanation because I
thought that some (meta-) data gets expired after a certain period
of time. But then I realized that he meant that these things expired
in the past.

>From the user point of view, I also do think that renaming the
property from :EXPIRE: to :IGNORE: would be better in terms of
understanding its purpose and how it works.

(If you do tend to keep the wording, I would at least rename it to
:EXPIRED: which emphasizes the fact that these things expired in the
past.)

-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
   > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github

Re: [O] Problem when EXPORT_FILE_NAME contains a subdirectory

[Nicolas Goaziou]

Martin Marier  writes:

> And just to make sure I was expressing myself clearly: this happens when
> exporting a subtree only; there is no issue when exporting the full
> document.  You (or anyone else) can't reproduce the problem?

I could reproduce the problem: I wasn't using default value for
`org-latex-pdf-process'.

The problem should be fixed in maint. Thank you for reporting it.


Regards,

-- 
Nicolas Goaziou

[O] How to join cells in tables and center content

[Ivanov Dmitry]

Suppose, I am writing a database table structure.
Is it possible to join the 1-st two cells? And make 'table1' centered?
Current view and desired:


| table1 |   |  | table1 |
|+---+  |+---+
| id | value |->| id | value |
||   |  ||   |


I understand, that it will require programming. Just give me a hint, where is 
the function, expanding table cells, and I'll try to implement it.

[O] Ordered List (Alphabetical) and HTML Export

[Josiah Schwab]

Hi All,

I am using orgmode 8.0.3 with emacs 24.3.  I frequently use
ordered lists with alphabetical bullets.  I have
  (setq org-list-allow-alphabetical t)
in my .emacs.

I just noticed that when I export an alphabetical list using the HTML
exporter, it appears as a numerical list in the rendered HTML.  My
expectation was that the ol tags for this list would look like , but instead they are just plain . (At the end of the
message is a snippet that lets you reproduce this.)

From poking around in ox-html.el (specfically, looking at
org-html-begin-plain-list), I see that there is no code that handles
the list "type".

I spent a few minutes looking at org-list.el, but I'm new enough to
both org-mode and elisp, that I couldn't immediately see how to extend
org-html-begin-plain-list so that it could figure out the kind of list
bullet and properly set the type.

Could anyone help walk me through what one would need to do to get the
desired behavior of HTML export preserving alphabetically bulleted
lists?

Best,
Josiah Schwab

P.S.  Here's an example org snippet.

* Letters
a. foo
b. bar
c. baz
* Numbers
1. foo
2. bar
3. baz

[O] org-publish bug

[Marvin Doyley]

Hi Orgers,

For some reason that I cannot fathom ox-publish is unable to generate index
file for a web site that I am creating. It only creates an empty
 theindex.inc.

Thanks in advance for your help

cheers,

M

Re: [O] conflict load of epresent - org mode 8.0.3

[d . tchin]

Hi, 

> I just updated the require statements in epresent.el.
> 
>   https://github.com/eschulte/epresent/blob/master/epresent.el


> 
> I'm not sure what epresent-org.el is.


For your information, Sacha Chua on her blog has given a short description 
of EPresent accessible on the following link

http://sachachua.com/blog/2013/04/how-to-present-using-org-mode-in-emacs/

Above it is mentioned about a tool called org-present developed by Ric 
Lister. I certainly made a confusion in my mail with this tool when I 
mentioned epresent-org.el. Sorry for this.

Anyway your changes work well. 

Thanks

[O] [PATCH] ox-html: Fix handling of time-stamp-file

[Kodi Arfer]

 >From 10814da65829d6918d736188027723dde30b4a3c Mon Sep 17 00:00:00 2001
From: Kodi Arfer 
Date: Thu, 30 May 2013 15:19:57 -0400
Subject: [PATCH] ox-html: Fix handling of time-stamp-file

* lisp/ox-html.el (org-html--build-meta-info): Insert no timestamp
  when :time-stamp-file is nil.

TINYCHANGE
---
 lisp/ox-html.el | 7 +++
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/lisp/ox-html.el b/lisp/ox-html.el
index 297cb55..949c3ba 100644
--- a/lisp/ox-html.el
+++ b/lisp/ox-html.el
@@ -1506,10 +1506,9 @@ INFO is a plist used as a communication channel."
 		 "iso-8859-1")))
 (concat
  (format "%s\n" title)
- (format
-  (when :time-stamp-file
-	(format-time-string
-	 (concat "\n"
+ (when (plist-get info :time-stamp-file)
+   (format-time-string
+	 (concat "\n")))
  (format
   (if (org-html-html5-p info)
 	  (org-html-close-tag "meta" " charset=\"%s\"" info)
-- 
1.8.1.2

Re: [O] de-tangle function?

[Rasmus]

"Sebastien Vauban" 
writes:

>> Does it work reliably?
>
> You need the code blocks to be wrapped into comments for it to work.
>
> Regarding reliability, it does work well on small examples. I remember having
> had really bad results with my huge .emacs file, but hadn't any time to debug
> the problem -- try to reproduce -- at that time.
>
> So, when you do it, please keep a backup of your original Org file. It's
> safer.
>
> But, if there are bugs, they should be clearly identified, and fixed...

It not always good at finding its way back into the Org file, and I
found that some of the header arguments didn't 'work properlyø for
'complicated' blocks.  I'll see if I can make reproducible examples
later.

It's definitely a potentially cool feature though.  Notice you have to
run it from the tangled file.

–Rasmus

-- 
Don't panic!!!

Re: [O] [PATCH] ox-html: Fix handling of time-stamp-file

[Nicolas Goaziou]

Hello,

Kodi Arfer  writes:

> From: Kodi Arfer 
> Date: Thu, 30 May 2013 15:19:57 -0400
> Subject: [PATCH] ox-html: Fix handling of time-stamp-file
>
> * lisp/ox-html.el (org-html--build-meta-info): Insert no timestamp
>   when :time-stamp-file is nil.
>
> TINYCHANGE

Applied. Thank you.


Regards,

-- 
Nicolas Goaziou

Re: [O] Xemacs 21.5.32 and org-8.03, compilation problems

[Uwe Brauer]

>> "Achim" ==Achim Gratz  writes:

   > Uwe Brauer writes:
   >> I know that compiling  org under Xemacs is delicate. I succeeded with
   >> 7.8.3 but it seems that the installation process has changed quite a
   >> bit.

   > No, not really.
Ok, good
   >> I edit the relevant 
   >> 
   >> default.mk
   >> file (OK I should not do that but create local.mk)
   >> 
   >> EMACS=/usr/local/bin/xemacs
   >> BATCH = $(EMACS) -batch -vanilla # Xemacs

   > Yes, you should not do this.  A configuration file for XEmacs is here:
   > http://orgmode.org/worg/dev/org-build-system.html#sec-4-1-4


Thanks!


   >> Now when running make  the following problems showed up:

   > You're not using the sources you think you are using.

That was a little my feeling.

   >> Did anybody sucessfully compile the latest org version under
   >> Xemacs 21.5.X?

   > No, despite repeated calls for help no feedback from actual XEmacs users
   > was registered and at some point I've stopped bugging Bastien about the
   > incompatibilities introduced.  There are at least a handful of functions
   > that'd need compatibility macros /defuns on XEmacs and I don't know what
   > turns up when these are out of the way, but the results were sketchy
   > already on 7.x whenever I tried.  Your best bet is running uncompiled
   > (which probably still needs compatibility definitions).

You are right, this is a sad fact but true. The only person who cared,
and knows enough Lisp is Michael Sperber, who right now is very busy.

Actually I am right now very busy my self, but maybe in the next days I
give it another try, now that you sent me this information!

Thanks and regards

Uwe 


smime.p7s
Description: S/MIME cryptographic signature

Re: [O] refine org-babel-tangle-jump-to-org?

[Eric Schulte]

rai...@krugs.de (Rainer M. Krug) writes:

> Hi
>
> I am using  org-babel-tangle-jump-to-org when debugging code written in
> org and tangled. I have some longisch code blocks and it is always
> irritating, as it only jumps to the codde block. Would it be possible to
> extend the function, that it jumps to the line of the code?
> That would make this funktion much more user friendly.
>

I've just pushed up a change which should make this change.  I tested
this against the example.C file tangled from the attached Org-mode file.

* example
  :PROPERTIES:
  :tangle:   yes
  :comments: link
  :END:

The required headers.
#+name: header
#+begin_src C
  #include 
#+end_src

Here is the auxiliary function.
#+name: auxiliary
#+begin_src C
  void aux(char* arg){
printf("first argument: %s\n", arg);
  }
#+end_src

Here is the main function.
#+name: main
#+begin_src C
  int main(int argc, char *argv[])
  {
aux(argv[1]);
return 0;
  }
#+end_src


While implementing this change I did notice that this jumping
functionality only appears to work with linked code blocks, which should
I believe is a bug.

Best,

>
> Thanks,
>
> Rainer

-- 
Eric Schulte
http://cs.unm.edu/~eschulte

Re: [O] [PATCH] org-contacts.el: add expire feature

[Feng Shu]

Karl Voit  writes:

> * Daimrod  wrote:
>>
>> Feng Shu  writes:
>>
>>> * test
>>>   :PROPERTIES:
>>>   :EMAIL: te...@gmail.com  te...@gmail.com  te...@gmail.com
>>>   :PHONE:  123456  123457 123458
>>>   :EXPIRE:  te...@gmail.com 123457
>>>   :END:
>>>
>>> when completing or exporting to vcard,  the emails and  phones in the
>>> expire property (te...@gmail.com and 123457) will be ignore
>
> This is a very good patch, fixing an issue I also do have currently.
>
>> Since the purpose of this property is to ignore some values when
>> exporting to vcard, don't you think it would be better to name it IGNORE
>> or VCARD_IGNORE? (and of course to rename all functions accordingly)
>
> I totally agree.
>

I have changed it to "IGNORE"
> At first, I could not follow Feng Shu's explanation because I
> thought that some (meta-) data gets expired after a certain period
> of time. But then I realized that he meant that these things expired
> in the past.
>
> From the user point of view, I also do think that renaming the
> property from :EXPIRE: to :IGNORE: would be better in terms of
> understanding its purpose and how it works.
>
> (If you do tend to keep the wording, I would at least rename it to
> :EXPIRED: which emphasizes the fact that these things expired in the
> past.)

-- 

Re: [O] [PATCH] org-contacts.el: add expire feature

[Daimrod]

Feng Shu  writes:

> Hi Daimrod!
> This is the 3 updated patch, if possible, please include it to master.

It's merged and pushed. I've also pushed another commit to fix the
formatting in some parts of the code and I've found a bug in
`org-contacts-split-property', but it should be fixed now.

> Thanks for your help!

-- 
Daimrod/Greg


signature.asc
Description: PGP signature

Re: [O] [Patch] phone links...

[Daimrod]

Michael Strey  writes:

Hello Michael,

While merging a patch (from Feng Shu) I have found a bug in
`org-contacts-split-property'. Though the docstring says that OMIT-NULLS
is forced to t when SEPARATORS is nil (just like `split-string'), it
wasn't the case. I've pushed a fix; could you check on your side that it
doesn't break anything in your workflow?

Thanks,

-- 
Daimrod/Greg


signature.asc
Description: PGP signature

Re: [O] [PATCH] org-contacts.el: add expire feature

[Daimrod]

Karl Voit  writes:

Hi Karl,

> This is a very good patch, fixing an issue I also do have currently.

I am curious, what was the issue?

Regards,

-- 
Daimrod/Greg


signature.asc
Description: PGP signature

[O] org-publish bug

[Marvin Doyley]

Hi there,

I solved the problem. It turns out that I needed to include

#+index:

cheers,
M

Re: [O] [PATCH] org-contacts.el: add expire feature

[Feng Shu]

Daimrod  writes:

> Feng Shu  writes:
>
>> Hi Daimrod!
>> This is the 3 updated patch, if possible, please include it to master.
>
> It's merged and pushed. I've also pushed another commit to fix the
> formatting in some parts of the code and I've found a bug in
> `org-contacts-split-property', but it should be fixed now.

Thanks! 

Now I want to code a function:
(defun org-contacts-add-value-to-ignore-property (value)
  "Create agenda view for contacts matching NAME."
  (interactive (list (read-string "Ignored email or phone: ")))

...

)


1. find a contact which email or phone property include the value ,If the
   result is two or more different contacts, message: "Two or more
   contacts, abort!".
  
2. add the value to the ignore property of  the result contact


Any suggestion?

Thanks!
>
>> Thanks for your help!

-- 

[O] installation

[jacob lindberg]

I'm a true beginner. I've never used emacs. But I'm eager to learn, and
I've have watched videos and read what orgmode can do.

I'v read 1.2 Installation but don't understand the language, since I'm new.
How to install it–do I need emacs?

Running OS X 10.7.5

Re: [O] installation

[Bastien]

Hi Jacob,

I think your best starting point is here:

  http://emacsformacosx.com

Org-mode is part of Emacs, so Emacs is all what you need.

Then learn to use Emacs by reading the tutorial.

Then start editing an .org file -- and you're done!

(Well, nearly done.)

-- 
 Bastien

Re: [O] How to join cells in tables and center content

[Bastien]

Hi Ivanov,

Ivanov Dmitry  writes:

> Suppose, I am writing a database table structure.
> Is it possible to join the 1-st two cells? And make 'table1'
> centered?

No.

> Current view and desired:
>
>
> | table1 |   |  | table1 |
> |+---+  |+---+
> | id | value |->| id | value |
> ||   |  ||   |
>
>
> I understand, that it will require programming. Just give me a hint,
> where is the function, expanding table cells, and I'll try to
> implement it.

Most code is in org-table.el -- but beware that even with some
programming skills this is a hard-perhaps-impossible task...

Good luck,

-- 
 Bastien