Re: [O] Multi string search of org entries

2012-01-09 Thread Thomas Holst
Hi Tom,

· On Jan 05 2012, Tom adatgyu...@gmail.com wrote:
 Bastien bzg at altern.org writes:

 
 Please feel free to suggest any better description, I 
 just took the one from the commentary section of the .el
 file.

 They look fine to me which is not suprising, because I wrote these
 descriptions in the first place. :)

I downloaded org-search-goto-ml.el and tried

  (require 'org-search-goto-ml)

which failed. This is because of the (provide ...) statement.

Attached is a patch which corrects this line.

-- 
Mit freundlichen Grüßen / Best regards 

Thomas Holst 
From 42aa4ffcb6e36d3cf4df1c24796a6ae4c995052f Mon Sep 17 00:00:00 2001
From: Thomas Holst thomas.ho...@de.bosch.com
Date: Mon, 9 Jan 2012 10:20:58 +0100
Subject: [PATCH] org-search-goto-ml.el: corrected the proviede statement

---
 org-search-goto-ml.el |4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/org-search-goto-ml.el b/org-search-goto-ml.el
index 52b473a..4668401 100755
--- a/org-search-goto-ml.el
+++ b/org-search-goto-ml.el
@@ -298,5 +298,5 @@
 
 
 
-(provide 'org-search-goto)
-;;; org-search-goto.el ends here
+(provide 'org-search-goto-ml)
+;;; org-search-goto-ml.el ends here
-- 
1.7.5.1



Re: [O] Dangling link [was: Re: Multi string search of org entries]

2012-01-09 Thread Bastien
pin...@iro.umontreal.ca (François Pinard) writes:

 Glancing through it, I notice in section org-R.el that the URL for
 documented in the manual is dangling.

Fixed, thanks!

-- 
 Bastien



Re: [O] Strange non-existent agenda file message

2012-01-09 Thread Bastien
Hi François,

 Command C-c C-e d yields this strange message:

   non-existent agenda file
   ~/fp/notes/Bureautique/Org_mode_Présentation.org.
   [R]emove from list or [A]bort?

I cannot reproduce this.  Can you provide a minimal setup and an 
example file that will help me reproduce this?  

Thanks!

-- 
 Bastien



Re: [O] Manual -- updating the Customization node

2012-01-09 Thread Bastien
Hi François,

pin...@iro.umontreal.ca (François Pinard) writes:

 Section 15.5 Customization in the Org manual says:

  There are more than 180 variables that can be used to customize Org.

 In a recent message to the mailing list, someone said 580 or so
 variables.  Another gave a number over one thousand.

 Maybe that 180 is too low an estimate, at least from now on, and
 should be amended!

There is 733 now defcustom declarations in lisp/ -- but some of 
these options are not available, depending on `org-modules'.  I 
updated the manual to 500.  The number is not important, just the
idea.

-- 
 Bastien



Re: [O] Problem at capture time

2012-01-09 Thread Bastien
Hi François,

please be patient -- your patches are under radar, resending
them does not help.

What helps is to send them using git format-patch, to include a
detailed and clean changelog entry, and to make it clear whether
the patch is okay or for testing purpose first.

When I read your message, I could not be sure you were yourself 
confident it was the right fix.

I will look into this later on.

Thanks,

-- 
 Bastien



Re: [O] New issue with capture

2012-01-09 Thread Bastien
Hi Ido,

Ido Magal i...@idomagal.com writes:

 When I attempt to org-capture-finalize, I get

 Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
   org-capture-bookmark-last-stored-position()
   org-capture-finalize(nil)
   call-interactively(org-capture-finalize nil nil)

I cannot (even try to) reproduce this.

Please provide a complete and minimal example -- a test file 
and the relevant part of your configuration.

Thanks,

-- 
 Bastien



[O] LaTeX export: how to customize date format?

2012-01-09 Thread Carlos Russo
Hello,

Is there a way to customize how a date is exported into LaTeX?
Google couldn't help me on this.

For example, if an org file contains a timestamp 2012-01-09 Mon, I'm
getting an italicized version in the .tex file, i.e. \textit{2012-01-09
Mon}.

I would like to be able to change how dates are displayed in a global
way. In particular, I'm interested in automatically formatting the dates
in my documents using \usepackage[option]{isodate}?

So, in other words, I'd like to tell orgmode that it should output the
following
\printdate{2012-01-09}
or
\date-range{2012-01-01}{2012-01-09}
for date ranges.

I could use then use
#+LATEX_HEADER: \usepackage[option]{isodate}
to quickly change the date format, which could produce results as
diverse as:
Jan 9, 2012
January 9, 2012
Janvier 9, 2012
2012/01/09
2012/09/01
and so on...

Any hints on how to do this?

Cheers,
Carlos








Re: [O] LaTeX export: how to customize date format?

2012-01-09 Thread Bastien
Hi Carlos,

Carlos Russo mestre.adamas...@gmail.com writes:

 Is there a way to customize how a date is exported into LaTeX?

You cannot do this right now.

See these variables:

org-export-latex-timestamp-markup:
  A printf format string to be applied to time stamps.

org-export-latex-timestamp-inactive-markup:
  A printf format string to be applied to inactive time stamps.

org-export-latex-timestamp-keyword-markup:
  A printf format string to be applied to time stamps.

HTH,

-- 
 Bastien



Re: [O] LaTeX export: how to customize date format?

2012-01-09 Thread Bastien
Bastien b...@altern.org writes:

 Is there a way to customize how a date is exported into LaTeX?

 You cannot do this right now.

Er.. forget this sentence -- perhaps my subconscious is trying
to tell me there are too many variables in Org now :) 

-- 
 Bastien



Re: [O] LaTeX export: how to customize date format?

2012-01-09 Thread Carlos Russo
Thanks, it seems that
(setq org-export-latex-timestamp-markup \\printdate{%s})
does half of the job already.

 Er.. forget this sentence -- perhaps my subconscious is trying
 to tell me there are too many variables in Org now :) 


I suppose this means there are no plans of creating a variable containing the 
markup associated with a date range, right :-p?

Cheers,
Carlos




Re: [O] LaTeX export: how to customize date format?

2012-01-09 Thread Bastien
Carlos Russo mestre.adamas...@gmail.com writes:

 I suppose this means there are no plans of creating a variable containing
 the markup associated with a date range, right :-p?

Not that I know -- but beware of the conspiracy, as the LaTeX exporter
is currently being rewritten by Nicolas...  see org-e-latex.el in the 
EXPERIMENTAL/ directory.  I guess configuring the format for dates range 
is not beyond possibility.

-- 
 Bastien



Re: [O] Problem at capture time

2012-01-09 Thread François Pinard
Bastien b...@altern.org writes:

 Hi François, please be patient -- your patches are under radar,
 resending them does not help.

OK, sorry.  I do not know enough, yet, how Org works.  I sent a problem,
got a question, sent a reply which was rejected, then nothing.  A mere
short acknowledgement would have told me the message was not lost.

 What helps is to send them using git format-patch, to include a
 detailed and clean changelog entry, and to make it clear whether the
 patch is okay or for testing purpose first.  When I read your message,
 I could not be sure you were yourself confident it was the right fix.

I'm still not confident.  And I'm not pedant enough -- yet! :-) -- to
write formal patches when I'm not at least rather sure.

Besides the lack of confidence in a solution, however, the problem is
real.  The patch I sent was merely a trail for thinking.  But if nothing
else, it would do I presume.

 I will look into this later on.

Let me the one thanking you for supporting Org mode and its users, even
those like me! :-)

François



Re: [O] Manual -- updating the Customization node

2012-01-09 Thread François Pinard
Bastien b...@altern.org writes:

 There is 733 now defcustom declarations in lisp/ -- but some of 
 these options are not available, depending on `org-modules'.  I 
 updated the manual to 500.  The number is not important, just the
 idea.

:-).  No need, then, to include standard deviation nor kurtosis!

François



Re: [O] Multi string search of org entries

2012-01-09 Thread Tom
Thomas Holst thomas.holst at de.bosch.com writes:
 
 Attached is a patch which corrects this line.
 

Applied, thanks.





Re: [O] Footnotes issue with LaTeX export

2012-01-09 Thread John Hendy
On Mon, Jan 9, 2012 at 1:05 AM, Nicolas Goaziou n.goaz...@gmail.com wrote:

 Hello,

 John Hendy jw.he...@gmail.com writes:

  #+begin_src orgmode
  * Header
 
  Test paragraph where I insert a dollar amount of $100.
 
  Test paragraph where I insert a dollar amount of \$100.
 
  Test paragraph where I insert a dollar amount of 100.[fn:1]
 
  * Footnotes
 
  [fn:1] Successful; the first two give the error 'Cannot insert a footnote
  here'
  #+end_src

 Yes, that's what I thought: `org-inside-LaTeX-fragment-p' is the key.

 ,
 |(org-inside-LaTeX-fragment-p)
 |
 | Test if point is inside a LaTeX fragment.
 | I.e. after a \begin, \(, M-x , $, or $$, without the corresponding
 closing
 | sequence appearing also before point.
 | Even though the matchers for math are configurable, this function assumes
 | that \begin, \(, \[, and $$ are always used.  Only the single dollar
 | delimiters are skipped when they have been removed by customization.
 | The return value is nil, or a cons cell with the delimiter and the
 | position of this delimiter.
 |
 | This function does a reasonably good job, but can locally be fooled by
 | for example currency specifications.  For example it will assume being in
 | inline math after $22.34.  The LaTeX fragment formatter will only
 format
 | fragments that are properly closed, but during editing, we have to live
 | with the uncertainty caused by missing closing delimiters.  This function
 | looks only before point, not after.
 `

 On purpose, Org won't insert a footnote inside a LaTeX fragment.  But,
 in your example, it is fooled by the currency.

 One workaround would be to remove $ as a math delimiter from
 `org-format-latex-options'.


How about another idea... would it be possible to remove \$ as a math
delimiter? I *do* use $math$ a bit, at least in this document, and have
=TeX:t and LaTeX:t= in my options... thus, I'm very careful about prefixing
\ to any instances of $ and %. Removing \$ as a math delimiter or making
\ register as the universal escape character would also do the trick.

If I removed $ as you suggest, could I use \begin{math}/\end{math} inline?
I have quite a bit of inline math.


Thanks!
John




 Regards,

 --
 Nicolas Goaziou



Re: [O] Strange non-existent agenda file message

2012-01-09 Thread François Pinard
Bastien b...@altern.org writes:

 Command C-c C-e d yields this strange message:

   non-existent agenda file
   ~/fp/notes/Bureautique/Org_mode_Présentation.org.
   [R]emove from list or [A]bort?

 I cannot reproduce this.  Can you provide a minimal setup and an 
 example file that will help me reproduce this?

I'll try to do so, yet a bit later.  The holidays ended -- I mean, the
weekend is over! :-).  Other duties will keep me busy for a few days...

François



[O] Minor org mode for achieve code folding effects

2012-01-09 Thread Giovanni Giorgi
  

Hi all,
 I'd like to edit some ruby/python/shell script using
functions folding. 

I'd like to get a way to fold functions or method.


I have found this article using outline mode:

http://stackoverflow.com/questions/1085170/how-to-achieve-code-folding-effects-in-emacs


but frankly I find it difficult to use because navigation is too
difficult. (I have also excluded folding mode). 

Org Mode has a very
nice navigation and key bindings, and I know it better then
outline.
There is a way to get a minor org-mode for replacing the above
outline configuration?
I am ready to experiment, if I need to patch
things...  

---
Gio's Blog http://gioorgi.com
  

Re: [O] Minor org mode for achieve code folding effects

2012-01-09 Thread Carsten Dominik

On Jan 9, 2012, at 4:14 PM, Giovanni Giorgi wrote:

 Hi all,
 I'd like to edit some ruby/python/shell script using functions folding.
 
 I'd like to get a way to fold functions or method.
 
 I have found this article using outline mode: 
 http://stackoverflow.com/questions/1085170/how-to-achieve-code-folding-effects-in-emacs
 
 but frankly I find it difficult to use because navigation is too difficult. 
 (I have also excluded folding mode).
 
 
 Org Mode has a very nice navigation and key bindings, and I know it better 
 then outline.
 There is a way to get a minor org-mode for replacing the above outline 
 configuration?
 I am ready to experiment, if I need to patch things... 

Start by reading the FAQ:

http://orgmode.org/worg/org-faq.html#use-visibility-cycling-in-outline-mode


- Carsten






Re: [O] Generating boxplot (candlestick) diagrams (babel or org-plot)

2012-01-09 Thread Karl Voit
* Eric Schulte eric.schu...@gmx.com wrote:
 Karl Voit devn...@karl-voit.at writes:

 I'm using gnuplot 4.5 patchlevel 0 which is probably where this
 difference comes in.  As I use gnuplot all the time, I find it
 worthwhile to track the development head for nice new features such as
 this and beautiful pdf plots through pgf/tikz.

Glad to know that gnuplot is under active development!

But CSV? ... geesh seriously? ...

 And now I also understand the problem I had: I thought that gnuplot
 is able to derive min/max whisker min/max from the data columns by
 itself.

 Well - this is bad news to me since I do not see any reasonable way
 to use gnuplot for that purpose. I might need to learn R or
 Python/matplotlib :-(

 Judging from the help output for boxplot it looks as though the boxplot
 option *will* perform these calculations for you, if you are willing to
 move to version 4.5 or later.  The only downside of using new features
 in gnuplot is that it is noticeably harder to find help through google.

Thanks for giving me OT gnuplot support!

-- 
Karl Voit




Re: [O] Footnotes issue with LaTeX export

2012-01-09 Thread Nicolas Goaziou
Hello,

John Hendy jw.he...@gmail.com writes:

 One workaround would be to remove $ as a math delimiter from
 `org-format-latex-options'.

 How about another idea... would it be possible to remove \$ as a math
 delimiter? I *do* use $math$ a bit, at least in this document, and have
 =TeX:t and LaTeX:t= in my options... thus, I'm very careful about prefixing
 \ to any instances of $ and %. Removing \$ as a math delimiter or making
 \ register as the universal escape character would also do the trick.

 If I removed $ as you suggest, could I use \begin{math}/\end{math} inline?
 I have quite a bit of inline math.

You can already use \(inline math\). I don't think there is
a need for extra syntax.


Regards,

-- 
Nicolas Goaziou



[O] Numbering source lines not from 1

2012-01-09 Thread François Pinard
Hi, Org people.

If I use:

   #+BEGIN_SRC bash +n

line numbering resumes from the last listed number.  Is there a way to
resume with a user specified number?

My intent would be to have the full numbered listing in an appendix, but
then, excerpt a few group of lines here and there in the running text,
using the same numbering for the quoted lines as in the appendix.  I
could of course write sentences like The following code may be read in
context starting at line NN in the appendix, but it might be just
better to repeat the numbering right with the line, silently, without
such introductory sentences.

François



Re: [O] How to force redisplay?

2012-01-09 Thread Nicolas Goaziou
Hello,

pin...@iro.umontreal.ca (François Pinard) writes:

 Playing a bit to reply to your questions, I think I just found a way to
 reproduce the problem dependably.  If on a header line of a section
 having contents, I do something like:

C-e RET *** Allo RET

 (well, merely choose the number of asterisks so the problem shows!).
 The Allo line will then get intended according to the number of stars
 (which is very convenient), but the following contents lines keep their
 original visual indentation, which might happen to be incorrect.

Thanks to your recipe, I have committed a patch for that problem on
master branch. May you test it and let me know if it fixes your
indentation problems?


Regards,

-- 
Nicolas Goaziou



Re: [O] Footnotes issue with LaTeX export

2012-01-09 Thread John Hendy
On Mon, Jan 9, 2012 at 11:31 AM, Nicolas Goaziou n.goaz...@gmail.comwrote:

 Hello,

 John Hendy jw.he...@gmail.com writes:

  One workaround would be to remove $ as a math delimiter from
  `org-format-latex-options'.

  How about another idea... would it be possible to remove \$ as a math
  delimiter? I *do* use $math$ a bit, at least in this document, and have
  =TeX:t and LaTeX:t= in my options... thus, I'm very careful about
 prefixing
  \ to any instances of $ and %. Removing \$ as a math delimiter or
 making
  \ register as the universal escape character would also do the trick.
 
  If I removed $ as you suggest, could I use \begin{math}/\end{math}
 inline?
  I have quite a bit of inline math.

 You can already use \(inline math\). I don't think there is
 a need for extra syntax.


Ah. Neat. I was unaware of this. That should do it. I'd still kind of
prefer not to have to tweak around with stuff. Given that special
combinations of \ + char are LaTeX specific, it would seem that a
natural combination would be to activate such combinations when LaTeX:t is
used in #+options.

Your solution will work for me for now.

Thanks for the assistance!
John



 Regards,

 --
 Nicolas Goaziou



Re: [O] How to force redisplay?

2012-01-09 Thread François Pinard
Nicolas Goaziou n.goaz...@gmail.com writes:

 If on a header line of a section having contents, I do something
 like:

C-e RET *** Allo RET

 [...] the Allo line will then get intended according to the number
 of stars, but the following contents lines keep their original visual
 indentation, which might happen to be incorrect.

 Thanks to your recipe, I have committed a patch for that problem on
 master branch.  May you test it and let me know if it fixes your
 indentation problems?

Hi, Nicolas.  It does, and wonderfully so!  Thanks a lot! :-)

François



[O] text background when exporting as HTML

2012-01-09 Thread David Rogoff

Hi all.

I'm using orgmode for outlines and documentation.  Since no one else I 
work with does this, I export to HTML which generally works fine. 
However, I've got a problem with embedded code samples using #+BEGIN_SRC 
/ #+END_SRC.   The faces for the source code are set up for a black 
background.  The exported HTML picked up the face colors, but the 
background is white, so they're mostly unreadable.  Is there a 
(hopefully simple) way to tell the HTML export to specify a black 
background for these blocks?


FYI, emacs 23.3.1, REH Linux, orgmode 7.5

Thanks,

 David



Re: [O] [Orgmode] Automatic screenshot insertion

2012-01-09 Thread Eric S Fraga
pin...@iro.umontreal.ca (François Pinard) writes:

 Russell Adams rlad...@adamsinfoserv.com writes:
 On Sun, Nov 28, 2010 at 08:35:23PM +0100, David Maus wrote:
 At Thu, 18 Nov 2010 18:16:22 +0100, Jonathan BISSON wrote:

  Here is a little function that allows a user to insert a screenshot
  easily. Only works on unix-like systems where ImageMagick is installed
  (adapt import to your screenshot program if needed).

 Nice.  Do you mind of I put the function on Org mode'S wiki (Worg) in
 the Org hacks page?[1]

 I made a minor change. File names are now generated by using the
 current org buffer filename, plus the date and time, and a unique
 number. This allows me to sort out the images better.

 For my own usage, I modified it further, like below:


 (defun fp-org-image (name)

[...]

Thanks!  Very nice update.  I'd been using the original code for a while
but prompting for the file name is quite helpful.  However, if I give it
a directory name, the function fails with Cannot create image file in
the mini-buffer.  With debug (note: only function name is different):

,
| Debugger entered--Lisp error: (error Cannot create image file)
|   signal(error (Cannot create image file))
|   error(Cannot create image file)
|   (if (file-writable-p name) nil (error Cannot create image file))
|   (unless (file-writable-p name) (error Cannot create image file))
|   (if (file-exists-p name) nil (unless (file-writable-p name) (error Cannot 
create image file)) (message Taking screenshot...) (call-process import 
nil nil nil name) (message Taking screenshot...done))
|   (unless (file-exists-p name) (unless (file-writable-p name) (error Cannot 
create image file)) (message Taking screenshot...) (call-process import 
nil nil nil name) (message Taking screenshot...done))
|   esf/org-screenshot(~/s/test)
|   call-interactively(esf/org-screenshot nil nil)
`

In summary, if I give it an existing file name, that works; if I give it
a non-existing file name, that also works.  It only fails if I give it a
directory.

thanks,
eric
-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1
: using Org-mode version 7.8.03 (release_7.8.03.66.g1283.dirty)



Re: [O] Footnotes issue with LaTeX export

2012-01-09 Thread Eric S Fraga
John Hendy jw.he...@gmail.com writes:

[...]

 If I removed $ as you suggest, could I use \begin{math}/\end{math} inline?
 I have quite a bit of inline math.

You can use \( ... \) for inline math.  Works well for me.

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1
: using Org-mode version 7.8.03 (release_7.8.03.66.g1283)



[O] LaTeX export problem

2012-01-09 Thread Piotr Kaźmierczak
Hi,   

I have a very strange problem: I can no longer process an org file with all my 
notes to LaTeX. I've been using org-mode this way for some time now, and I was 
always able to get a nice tex file I could later process to PDF. Now all I get 
is a TeX file with absolutely no new-line symbols (a huge one-line file), and 
pdflatex obviously can't process that. I haven't updated org for a while, and 
it doesn't seem to matter which Emacs version I try (GNU 23, GNU 24, Aquamacs 
2.4), I still can't get the correct output. The only difference from the last 
time I managed to get a correct tex output is that I added some more notes to 
the org file.  

I'm using Org 7.8.

Any ideas?

regards,
Piotr Kaźmierczak





Re: [O] [Orgmode] Automatic screenshot insertion

2012-01-09 Thread François Pinard
Eric S Fraga e.fr...@ucl.ac.uk writes:

 pin...@iro.umontreal.ca (François Pinard) writes:

 Thanks!  However, if I give it a directory name, the function fails
 with Cannot create image file in the mini-buffer.  [...]  In
 summary, if I give it an existing file name, that works; if I give it
 a non-existing file name, that also works.  It only fails if I give it
 a directory.

Hi, Eric.  Sorry.  Here is a quick correction for that problem.  This is
only this week that I plan to use that function for actual work; last
week was rather an exploration of the capability of various tools.  Of
course, do not hesitate if you see that I goofed elsewhere! :-).

Thanks, François



(defun fp-org-image (name)
  Insert a link to an already existing image, or else to a screenshot.
The screenshot is either taken to the given non-existing file name,
or added into the given directory, defaulting to the current one.
  ;; FIXME: Should limit to '(pdf jpeg jpg png ps eps)
  ;; which is org-export-latex-inline-image-extensions.
  (interactive GImage name? )
  (when (file-directory-p name)
(setq name (concat
(make-temp-name
 (concat (file-name-as-directory name)
 (subst-char-in-string
  . -
  (file-name-sans-extension
   (file-name-nondirectory
(buffer-file-name))
.png)))
  (unless (file-exists-p name)
(unless (file-writable-p name)
  (debug)
  (error Cannot create image file))
(message Taking screenshot...)
(call-process import nil nil nil name)
(message Taking screenshot...done))
  (insert (concat [[ name ]]))
  (org-display-inline-images))



Re: [O] org-jira.el

2012-01-09 Thread OSiUX
El vie, 06 ene 2012, Bao Haojun decía:

 Hi, OSiUX
 
 OSiUX xu...@osiux.com.ar writes:
 
  El lun, 02 ene 2012, Bao Haojun decía:
 
  Hi, all
  
  I have implemented org-jira.el, bringing org-mode and Jira system
  together.
  
  Wrote a Wiki page for it on emacswiki:
  http://www.emacswiki.org/emacs/OrgJiraMode
  
  Hope somebody find it useful, if he/she is also using Jira and loves
  org-mode.
  
  
  
 
  after running Mx jira2-login, I get the following error:
 
  Symbol's function definition is void: auth-source-search
 
  howto configure login?
 
 I have fixed it. The auth-source-search is a new API from emacs24.
 
 With the new code, you will be prompted for username and password if you
 are using a lower version of EMACS.
 
 BTW, I have also renamed jira2 to jiralib, so after you check out the
 new code, you need change your .emacs accordingly:
 
 #+begin_src emacs-lisp
 (setq jiralib-url http://jira-host;)
 (require 'org-jira) ;jiralib is not explicitly required, since org-jira will 
 load it
 #+end_src
 
 Thanks.
 
 -- 
 All the best
 
  Bao Haojun

Hi Bao Haojun,

I finally discovered the error, I was using an anonymous proxy server
and JIRA apparently did not return the correct xml.

Does not work in emacs, but in emacs 24 enabling the debug managed to
capture the error::

  (let ( (url-request-method GET) (url-package-name)) 
  (let ( (soap-client.el) (url-package-version 1.0)  )) 
  (let ( ((url-mime-charset-string utf-8;q=1, iso-8859-1;q=0.5))) 
  (let ( ((url-request-coding-system (quote utf-8))  )) 
  (let ( ((url-http-attempt-keepalives nil)) (let ( (buffer  )) 
  (let ( ((url-retrieve-synchronously url))) (with-current-buffer)) 
  (let ( (buffer (declare (special url-http-response-status)))) 
  (let ( ((if ( url-http-response-status 299) (error Error )) 
  (let ( (retrieving WSDL: %s url-http-response-status mime-part)) 
  (let ( ((mm-dissect-buffer t t))) (unless mime-part (error Failed )) 
  (let ( (to decode response from server)) (unless (equal (car  )) 
  (let ( ((mm-handle-type mime-part)) text/xml) (error Server )) 
  (let ( (response is not an XML document   )) 

... then disable the proxy, start using emacs and execute
org-jira-get-projects got the list of projects and then some issues.

Excellent work, I hope that the error messages to help correct for
emacs23 org-jira.

Finally I would like to know where to change the path for the projects,
actually: /home/.org-jira

Thank you very much!
I'll stop now copy and paste from jira to  org-mode. ;-)


Enviroment Emacs23:

- Org-mode commit: 258aad0b9a428cec9195b22063e42df77dee19c2
- GNU Emacs 23.3.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.6) of
  2011-10-25 on trouble, modified by Debian
- org-jira commit: 6fd1fd891eb716871dc5d6d680f99585f1f3602e

Enviroment Emacs24
- Org-mode commit: 56c73255c0bdd27ac42af0a02ecea9336c4594d6
- GNU Emacs 24.0.92.1 (x86_64-pc-linux-gnu, GTK+ Version 3.2.3) of
  2012-01-05 on zelenka, modified by Debian
- org-jira commit: 6fd1fd891eb716871dc5d6d680f99585f1f3602e

-- 

::

  Osiris Alejandro Gomez (OSiUX) os...@osiux.com.ar
  AA70 93FD B6EF EB42 6920 7530 A799 B226 74C8 A3FE
  http://osiux.com http://wiki.buenosaireslibre.org


signature.asc
Description: Digital signature


Re: [O] LaTeX export problem

2012-01-09 Thread Nick Dokos

Piotr Kaźmierczak p.h.kazmierc...@gmail.com wrote:


 I have a very strange problem: I can no longer process an org file
 with all my notes to LaTeX. I've been using org-mode this way for some
 time now, and I was always able to get a nice tex file I could later
 process to PDF. Now all I get is a TeX file with absolutely no
 new-line symbols (a huge one-line file), and pdflatex obviously can't
 process that. I haven't updated org for a while, and it doesn't seem
 to matter which Emacs version I try (GNU 23, GNU 24, Aquamacs 2.4), I
 still can't get the correct output. The only difference from the last
 time I managed to get a correct tex output is that I added some more
 notes to the org file.
 

Have you tried exporting a simple file to latex? Perhaps something as simple
as:

---
* Foo
Bar
---


Nick



[O] Bug inserting preamble from function in org-export-as-html

2012-01-09 Thread Bill Jackson
I believe that a bug was introduced into org-export-as-html sometime 
after version 7.7, and is still present in 7.8.03.  In the file 
org-html.el, the section of org-export-as-html that inserts the HTML 
preamble is broken in the case were a function is passed for the 
preamble.  The following change works for me, but I have not tested it 
for other use cases:


diff -u org-html.el.ORIG org-html.el
--- org-html.el.ORIG2012-01-03 00:32:07.0 -0800
+++ org-html.el 2012-01-09 13:46:15.458708317 -0800
@@ -1351,7 +1351,7 @@
;; insert html preamble
(when (plist-get opt-plist :html-preamble)
  (let ((html-pre (plist-get opt-plist :html-preamble))
-   html-pre-real-contents)
+   (html-pre-real-contents ))
(cond ((stringp html-pre)
   (setq html-pre-real-contents
 (format-spec html-pre `((?t . ,title) (?a . 
,author)


Regards,
Bill



Re: [O] org-jira.el

2012-01-09 Thread Bao Haojun
Hi OSiUX,



OSiUX xu...@osiux.com.ar writes:
 Hi Bao Haojun,

 I finally discovered the error, I was using an anonymous proxy server
 and JIRA apparently did not return the correct xml.

 Does not work in emacs, but in emacs 24 enabling the debug managed to
 capture the error::

   (let ( (url-request-method GET) (url-package-name)) 
   (let ( (soap-client.el) (url-package-version 1.0)  )) 
   (let ( ((url-mime-charset-string utf-8;q=1, iso-8859-1;q=0.5))) 
   (let ( ((url-request-coding-system (quote utf-8))  )) 
   (let ( ((url-http-attempt-keepalives nil)) (let ( (buffer  )) 
   (let ( ((url-retrieve-synchronously url))) (with-current-buffer)) 
   (let ( (buffer (declare (special url-http-response-status)))) 
   (let ( ((if ( url-http-response-status 299) (error Error )) 
   (let ( (retrieving WSDL: %s url-http-response-status mime-part)) 
   (let ( ((mm-dissect-buffer t t))) (unless mime-part (error Failed )) 
   (let ( (to decode response from server)) (unless (equal (car  )) 
   (let ( ((mm-handle-type mime-part)) text/xml) (error Server )) 
   (let ( (response is not an XML document   )) 

 ... then disable the proxy, start using emacs and execute
 org-jira-get-projects got the list of projects and then some issues.

 Excellent work, I hope that the error messages to help correct for
 emacs23 org-jira.

 Finally I would like to know where to change the path for the projects,
 actually: /home/.org-jira

 Thank you very much!
 I'll stop now copy and paste from jira to  org-mode. ;-)


 Enviroment Emacs23:

 - Org-mode commit: 258aad0b9a428cec9195b22063e42df77dee19c2
 - GNU Emacs 23.3.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.6) of
   2011-10-25 on trouble, modified by Debian
 - org-jira commit: 6fd1fd891eb716871dc5d6d680f99585f1f3602e

 Enviroment Emacs24
 - Org-mode commit: 56c73255c0bdd27ac42af0a02ecea9336c4594d6
 - GNU Emacs 24.0.92.1 (x86_64-pc-linux-gnu, GTK+ Version 3.2.3) of
   2012-01-05 on zelenka, modified by Debian
 - org-jira commit: 6fd1fd891eb716871dc5d6d680f99585f1f3602e

Great!

I was also using proxy through setting the url-proxy-services variable,
and the org-jira.el does not work. After some googling around, I found
that url-proxy-services supports disabling proxy for some hosts:

(setq url-proxy-services 
  (quote
   ((http . localhost:8580)
(no_proxy . ^[^.]*$\\|sina.com

(just in case you don't know this already:-)

For the org-jira save path, I will make it a defcustom.

Thanks!
-- 
All the best

 Bao Haojun



Re: [O] Is it possible to have a code fragment in a bulleted list?

2012-01-09 Thread Stephen J. Barr
Thank you for the suggestion. I'll take a look at it.

On Mon, Jan 9, 2012 at 2:13 AM, Nicolas Goaziou n.goaz...@gmail.com wrote:
 Hello,

 Stephen J. Barr stephenjb...@gmail.com writes:

 Quick question. Is it possible to have a code fragment in a bulleted
 list? For example, I would like to do

 - This is interesting
   - Level 2 for loop

 #+begin_src R
 for (i in 1:10) {
     ...
 }
 #+end_src

   - This should also be on level 2

 When I render this as HTML, the sentences Level 2 for loop and This
 should also be on level 2 to be at the same depth, with the source
 code block in the middle. How do I do this?

 You have to indent your whole code block so that it belongs to the list.
 In other words, the #+begin_src line has to start at the L of Level
 2.

 You may want to read the section 2.7 of the manual for more information.


 Regards,

 --
 Nicolas Goaziou



[O] Capitalisation and good taste ?

2012-01-09 Thread François Pinard
Hi, Org people.

I really have mixed feelings about capitalisation of #+WORDS, and wonder
if some consensus and good taste has developed over time among Org mode
users.  What is the collective wisdom saying as being nicer among:

#+LATEX_HEADER:
#+Latex_Header:
#+LaTeX_HEADER:
#+latex_header:

etc.

I'm just unable to fix myself on any convention, and my own lack of
decision irritates me.  I hate changing my mind so often, and my files
are already a mess on this particular point.

Despite all capitals have the advantage of standing out clearly, I
usually don't like any kind of shouting in my files.  If I was writing
constants in C code, I would tolerate some exceptions of course, but
now, I'm writing documentation.  #+begin_quote and such are just OK in
small letters, they really look like shouting otherwise.

On the other hand, it seems that #+TITLE, #+AUTHOR and #+EMAIL, and all
those things which are high lighted in gray, use capitals only in all
examples I've seen so far.  Maybe the pale high lighting is a
counter-measure so it gets tolerable.

It seems that capitals are also favoured for #+OPTIONS, #+BIND, and many
other things (high lighted in red), yet I got the impression that parts
of the documentation (which look newer or younger to me on the
average) are getting away from the all capital conventions.  I do not
really know.

The writing LaTeX has the nicety of being the proper way to write
LaTeX, which is mandated by Lamport (after TeX has been mandated by
Knuth).  And I will not even speak of the revolutionary iTex, because I
do not have a bell handy! :-) If any of you are not aware of it, make
sure you do not miss http://www.youtube.com/watch?v=eKaI78K_rgA (you
then need half an hour of free time to listen to the video).

Not helping is that the manual and the Wiki are not using capitalisation
consistently between files, and even sometimes in the same area of a
same file.  They are not giving me clear advice about what is proper
style.

Maybe this has already been debated to death?  I do not know for Org
mode files, yet I know that style issues are usually flame-prone.  I'm
surely not trying to start any kind of war.  Nevertheless, I would like
if the manual and the Wiki select and document a preferred convention,
and were amended to be very consistent on it.  So, I'll have a clear
model to follow. :-)

François





Re: [O] Capitalisation and good taste ?

2012-01-09 Thread Bernt Hansen
pin...@iro.umontreal.ca (François Pinard) writes:

 I really have mixed feelings about capitalisation of #+WORDS, and wonder
 if some consensus and good taste has developed over time among Org mode
 users.  What is the collective wisdom saying as being nicer among:

 #+LATEX_HEADER:
 #+Latex_Header:
 #+LaTeX_HEADER:
 #+latex_header:

 etc.

 I'm just unable to fix myself on any convention, and my own lack of
 decision irritates me.  I hate changing my mind so often, and my files
 are already a mess on this particular point.

 Despite all capitals have the advantage of standing out clearly, I
 usually don't like any kind of shouting in my files.  If I was writing
 constants in C code, I would tolerate some exceptions of course, but
 now, I'm writing documentation.  #+begin_quote and such are just OK in
 small letters, they really look like shouting otherwise.

 On the other hand, it seems that #+TITLE, #+AUTHOR and #+EMAIL, and all
 those things which are high lighted in gray, use capitals only in all
 examples I've seen so far.  Maybe the pale high lighting is a
 counter-measure so it gets tolerable.

 It seems that capitals are also favoured for #+OPTIONS, #+BIND, and many
 other things (high lighted in red), yet I got the impression that parts
 of the documentation (which look newer or younger to me on the
 average) are getting away from the all capital conventions.  I do not
 really know.

 The writing LaTeX has the nicety of being the proper way to write
 LaTeX, which is mandated by Lamport (after TeX has been mandated by
 Knuth).  And I will not even speak of the revolutionary iTex, because I
 do not have a bell handy! :-) If any of you are not aware of it, make
 sure you do not miss http://www.youtube.com/watch?v=eKaI78K_rgA (you
 then need half an hour of free time to listen to the video).

 Not helping is that the manual and the Wiki are not using capitalisation
 consistently between files, and even sometimes in the same area of a
 same file.  They are not giving me clear advice about what is proper
 style.

 Maybe this has already been debated to death?  I do not know for Org
 mode files, yet I know that style issues are usually flame-prone.  I'm
 surely not trying to start any kind of war.  Nevertheless, I would like
 if the manual and the Wiki select and document a preferred convention,
 and were amended to be very consistent on it.  So, I'll have a clear
 model to follow. :-)

Hi François,

A long time ago all capitals was the only way these keywords were
supported.  Since then they have become case insensitive and I use all
lowercase for most of my keywords now (#+begin_src:, #+begin_example:
etc)

With fontification these stand out enough now and the capitalization can
be removed.  I still tend to use allcaps at the top of the file for
things like #+FILETAGS:, #+TITLE:, #+OPTIONS, etc but the blocks
embedded in my text are all lowercase now.

I wouldn't spend too much time agonizing over the 'right' way - do what
works for you :)

HTH,
Bernt



Re: [O] New issue with capture

2012-01-09 Thread Ido Magal
This is GNU Emacs 24.0.92.1 (i386-apple-darwin11.2.0, NS apple-appkit-1138.23)

I've reduced my .emacs to the following:

=
(setq org-capture-templates
  '((t Task entry (file+datetree ~/org/tasks.org)
 ** next %?)))
=

~/org/tasks.org may not exist for this to repro. It repros either way.


Repro steps:

1. M-x org-capture

2. enter anything

3. C-c C-c

Result:
byte-code: To bind the key M-DEL, use \M-\d, not [M-DEL]

4. C-c C-c again.

Result:
save-restriction: Wrong type argument: integer-or-marker-p, nil

5. Kill the 'CAPTURE-tasks.org' buffer. (C-x k)

6. repeat steps 1-3
Result: Success(!?)



Thanks for investigating!


On Mon, Jan 9, 2012 at 02:57, Bastien b...@altern.org wrote:
 Hi Ido,

 Ido Magal i...@idomagal.com writes:

 When I attempt to org-capture-finalize, I get

 Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
   org-capture-bookmark-last-stored-position()
   org-capture-finalize(nil)
   call-interactively(org-capture-finalize nil nil)

 I cannot (even try to) reproduce this.

 Please provide a complete and minimal example -- a test file
 and the relevant part of your configuration.

 Thanks,

 --
  Bastien



Re: [O] Capitalisation and good taste ?

2012-01-09 Thread Nick Dokos
Bernt Hansen be...@norang.ca wrote:

 pin...@iro.umontreal.ca (François Pinard) writes:
 
  I really have mixed feelings about capitalisation of #+WORDS, and wonder
  if some consensus and good taste has developed over time among Org mode
  users.  What is the collective wisdom saying as being nicer among:
 
  #+LATEX_HEADER:
  #+Latex_Header:
  #+LaTeX_HEADER:
  #+latex_header:
 
  etc.
 
  I'm just unable to fix myself on any convention, and my own lack of
  decision irritates me.  I hate changing my mind so often, and my files
  are already a mess on this particular point.
 
  Despite all capitals have the advantage of standing out clearly, I
  usually don't like any kind of shouting in my files.  If I was writing
  constants in C code, I would tolerate some exceptions of course, but
  now, I'm writing documentation.  #+begin_quote and such are just OK in
  small letters, they really look like shouting otherwise.
 
  On the other hand, it seems that #+TITLE, #+AUTHOR and #+EMAIL, and all
  those things which are high lighted in gray, use capitals only in all
  examples I've seen so far.  Maybe the pale high lighting is a
  counter-measure so it gets tolerable.
 
  It seems that capitals are also favoured for #+OPTIONS, #+BIND, and many
  other things (high lighted in red), yet I got the impression that parts
  of the documentation (which look newer or younger to me on the
  average) are getting away from the all capital conventions.  I do not
  really know.
 
  The writing LaTeX has the nicety of being the proper way to write
  LaTeX, which is mandated by Lamport (after TeX has been mandated by
  Knuth).  And I will not even speak of the revolutionary iTex, because I
  do not have a bell handy! :-) If any of you are not aware of it, make
  sure you do not miss http://www.youtube.com/watch?v=eKaI78K_rgA (you
  then need half an hour of free time to listen to the video).
 
  Not helping is that the manual and the Wiki are not using capitalisation
  consistently between files, and even sometimes in the same area of a
  same file.  They are not giving me clear advice about what is proper
  style.
 
  Maybe this has already been debated to death?  I do not know for Org
  mode files, yet I know that style issues are usually flame-prone.  I'm
  surely not trying to start any kind of war.  Nevertheless, I would like
  if the manual and the Wiki select and document a preferred convention,
  and were amended to be very consistent on it.  So, I'll have a clear
  model to follow. :-)
 
 Hi François,
 
 A long time ago all capitals was the only way these keywords were
 supported.  Since then they have become case insensitive and I use all
 lowercase for most of my keywords now (#+begin_src:, #+begin_example:
 etc)
 
 With fontification these stand out enough now and the capitalization can
 be removed.  I still tend to use allcaps at the top of the file for
 things like #+FILETAGS:, #+TITLE:, #+OPTIONS, etc but the blocks
 embedded in my text are all lowercase now.
 
 I wouldn't spend too much time agonizing over the 'right' way - do what
 works for you :)
 

... and check out easy templates to get consistent capitalization
*and* speed up your typing:

(info (org) Easy Templates)

Nick




Re: [O] Capitalisation and good taste ?

2012-01-09 Thread François Pinard
Bernt Hansen be...@norang.ca writes:

 pin...@iro.umontreal.ca (François Pinard) writes:

 I really have mixed feelings about capitalisation of #+WORDS, and
 wonder if some consensus and good taste has developed over time among
 Org mode users.

 A long time ago all capitals was the only way these keywords were
 supported.

Thanks, Bernt, for the historical perspective!

 I wouldn't spend too much time agonizing over the 'right' way

Truth is that I've been so agonizing for the whole of my computer life!
Each one his sickness, I guess... :-)

Keep happy!

François

P.S. Who, by the way, felt glad and relieved recently, seeing many
commits by Bastien correcting lots of spurious trailing white space. :-)

Should I say, I notice a strong correlation between rotten software and
the lack of attention to such details.  I'm not saying that avoiding
trailing white space is a guarantee of good software.  But I'm saying
that people unwilling to pay attention to details are not prone to pay
attention for a lot of other things, which is not good for software.





Re: [O] Capitalisation and good taste ?

2012-01-09 Thread François Pinard
Nick Dokos nicholas.do...@hp.com writes:

 ... and check out easy templates to get consistent capitalization
 *and* speed up your typing: (info (org) Easy Templates)

Good advice!  Thanks!

François

P.S. By the way, the node mentions #+begin_ascii, but the manual does
not tell about what it is.  (Or at least t s begin_ascii RET s RET in
the Info node only finds the Easy Templates reference.)

P.P.S. How about amending the manual for consistent capitalization?



Re: [O] Capitalisation and good taste ?

2012-01-09 Thread Nick Dokos
François Pinard pin...@iro.umontreal.ca wrote:

 P.S. By the way, the node mentions #+begin_ascii, but the manual does
 not tell about what it is.  (Or at least t s begin_ascii RET s RET in
 the Info node only finds the Easy Templates reference.)
 

In general, #+begin_foo ... #+end_foo will include the contents of the
block for foo export but get rid of it for non-foo export. So if you
don't intend to export to ascii, you can use an ascii block to include
comments in your file (and similarly for other formats). Of course, you
can also use #+begin_comment...#+end_comment, but afaict, there is an
inconsistency here: the latter can not be indented, whereas the other blocks
can. I haven't tried this with org-indent-mode though[fn:1].

 P.P.S. How about amending the manual for consistent capitalization?
 
Knock yourself out! ;-)

Nick

Footnotes:

[fn:1] Here is a test file:

--8---cut here---start-8---

* foo export

  #+begin_ascii
  This is not exported in anything other than ascii.
  #+end_ascii

  #+begin_comment
  foo
  #+end_comment


  #+begin_example
  This is exported in anything.  
  #+end_example

  #+begin_html
  This is not exported in anything other than html.
  #+end_html

  #+begin_latex
  This is not exported in anything other than latex.
  #+end_latex
--8---cut here---end---8---