Re: [O] Define org-capture-templates with variables via customize

[Nicolas Girard]

2015-04-04 23:54 GMT+02:00 Xavier Maillard :
>
>
> Ok, sounds like there is something I can /hack/ to permit such thing
> then.
>
> Update: I finally got it running as I wanted to through an ugly hack.
>

Hi Xavier,

could you please elaborate a bit on your hack ?

Thanks in advance,

Nicolas

Re: [O] a link to launch a todo view?

[Nicolas Girard]

2015-09-26 20:42 GMT+02:00 Xebar Saram :
>
> so something like this:
>
> [[elisp:(org-agenda)][TO-COOK]]
>
> this will bring up the dispatcher, how does one make it auto issue lets say
> 'w' in the dispatcher
>

Just try
(org-agenda nil "w")
instead.

Cheers,

Nicolas

Re: [O] [Babel] [possible bug] Empty src block prevents other block to expand

[Nicolas Girard]

2014-06-23 17:56 GMT+02:00 Charles Berry ccbe...@ucsd.edu:
 Nicolas Girard girard.nicolas at gmail.com writes:


 I think the diagnosis is incorrect.

 The empty source block has no effect.

 Adding ':noweb yes' to `capture's header args fixes things.


Charles,

thanks for your feedback.

I've always been under the assumption that, when block A references B
and B references C, then :noweb yes was only needed for block A. At
least, but perhaps I should double check, I'm pretty sure it's the way
I've been writing all my literal programming code until now.

So, in this specific example, :noweb yes shouldn't be necessary but
for the latest code block in the file.

Am I wrong ?

Cheers,
Nicolas

[O] [Babel] [possible bug] Empty src block prevents other block to expand

[Nicolas Girard]

The empty src block at the beginning of the following file prevents
capture-tmpl to expand when tangling.

Admittedly, this empty src block shouldn't exist in the first place,
it's just a residue of some former confg of mine that didn't cause any
problem until I upgraded Org to the latest ELPA package
(8.2.7a-elpaplus -- 20140619).

The test file is
---8---
* Empty org block
#+begin_src org :noweb yes
#+end_src
* Other blocks
#+name: capture-tmpl
#+begin_src org :results value
  ,* A
  :PROPERTIES:
  :ID: %(org-id-new)
  :END:
#+end_src

#+name: capture
#+begin_src emacs-lisp :tangle no
  (C Capture entry 
  capture-tmpl)
#+end_src

#+begin_src emacs-lisp :noweb yes
  (add-to-list 'org-capture-templates '
  capture 'append)
#+end_src
---8---

And the Makefile I used is simply
---8---
all: conf.el

%.el: %.org
emacs --batch -Q -l ob-tangle -l ob-org \
--eval '(setq org-babel-use-quick-and-dirty-noweb-expansion t)' \
--eval '(setq org-confirm-babel-evaluate nil)' \
--eval '(org-babel-tangle-file $ $@ emacs-lisp)'
---8---


Cheers,

Nicolas

Re: [O] proposal to have ignoreheading tags/properties

[Nicolas Girard]

2014-06-12 20:54 GMT+02:00 Aaron Ecay aarone...@gmail.com:
 Hi Eric, hi all,

 2014ko ekainak 12an, Eric Schulte-ek idatzi zuen:

 I just ran across this need myself, and updated an old solution to work
 with the new exporter.  See the thread and my solution at the following.

 http://lists.gnu.org/archive/html/emacs-orgmode/2014-06/msg00238.html

 It’s really wonderful that you and the other members of the org
 community have devoted lots of careful effort to this problem.  See
 also:
 - http://orgmode.org/worg/org-hacks.html#ignoreheadline
 - http://mid.gmane.org/87lhvvjoo0@gmx.us
 - http://mid.gmane.org/87zjii42k9@ucl.ac.uk

 Many of the solutions work approximately, but not in all circumstances
 – see the discussion on worg.  Searching my email archives for the
 string “ignoreheading” in 2014, I see threads from May 14, May 9, May
 6, March 27, March 17, and Jan 7 on this topic. It seems reasonable to
 ask whether this constitutes enough user interest to make this a core
 feature.  The benefits would include:
 - the code can be made robust by the combined effort of those
   interested
 - the feature can be incorporated into the test suite, so it won’t
   accidentally break in the future
 - it will be more “discoverable” in the org info manual (which almost
   certainly gets a larger audience than worg)



I also ran across this need. What I had in mind was that certain todo
types would be treated as inline.
For instance, if P was a member of this hypothetical
org-inline-todo-keywords, then

* P a paragraph
  some contents

would be rendered as

some contents

by the exporter, no matter the backend.

Such a feature is more generic and would be useful in other contexts ;
and the LaTeX-related issues discussed in this thread would be solved
using something like

* INLINE appendix
  \appendix
* Appendix 1


Cheers,

Nicolas

Re: [O] proposal to have ignoreheading tags/properties

[Nicolas Girard]

2014-06-12 21:21 GMT+02:00 Nicolas Girard girard.nico...@gmail.com:
 2014-06-12 20:54 GMT+02:00 Aaron Ecay aarone...@gmail.com:
 Hi Eric, hi all,


 I also ran across this need. What I had in mind was that certain todo
 types would be treated as inline.
 For instance, if P was a member of this hypothetical
 org-inline-todo-keywords, then

 * P a paragraph
   some contents

 would be rendered as

 some contents

 by the exporter, no matter the backend.

 Such a feature is more generic and would be useful in other contexts ;
 and the LaTeX-related issues discussed in this thread would be solved
 using something like

 * INLINE appendix
   \appendix
 * Appendix 1




Or, even better: rendering *both* the headline *and* the body of
lnline nodes as inline contents too:

* INLINE My inline
contents

-- My inline contents

* INLINE \appendix

-- \appendix

Re: [O] proposal to have ignoreheading tags/properties

[Nicolas Girard]

2014-06-12 21:26 GMT+02:00 Ken Mankoff mank...@gmail.com:

 On 2014-06-12 at 15:21, Nicolas Girard wrote:


 I vote for the following tags:

 + :noexport: Does not export item, content, and children.
 + :ignoreheading: Does not export heading. Exports content and children.
 + :ignorecontent: Does not export heading or content. Does export children.
 + :ignorebranch: Does not export heading, content, or children.
 + :promotesubheadings: Promotes children headings, regardless of
   exporting this heading or not



Agreed. That would rock !

Re: [O] proposal to have ignoreheading tags/properties

[Nicolas Girard]

2014-06-12 22:13 GMT+02:00 Eric Schulte schulte.e...@gmail.com:


 Why TODO types rather than a tag?  IMO using a TODO type would conflate
 task management and document structuring.

Agreed.

 What do you think about the
 attached patch which should add this functionality to the core.


Seems fine to me !

I created a public repository containing a Makefile and a bunch of
unit tests here: https://github.com/ngirard/org-inline-headings-tests.


Cheers,

Nicolas

Re: [O] [RFC] org-noweb: org-tangle + org-weave for literate programming using Org

[Nicolas Girard]

2014-06-10 19:54 GMT+02:00 Grant Rettke g...@wisdomandwonder.com:
 On Tue, Jun 10, 2014 at 9:46 AM, Nicolas Girard
 girard.nico...@gmail.com wrote:

 - About =org-babel-use-quick-and-dirty-noweb-expansion=:
   should it be set to 't' by default ? I'd be tempted to say yes,
   given the dramatic performance gain
 Use Emacs to run Emacs Lisp and set
 org-babel-use-quick-and-dirty-noweb-expansion to nil.

Hi Grant,

thanks for your reply. There might be a slight misunderstanding though.
My question was: should org-tangle and org-weave enable
org-babel-use-quick-and-dirty-noweb-expansion before doing their
jobs ? For now I let the default value to be =nil=, and I was
wondering if it wouldn't be bette to do the opposite instead, that is,
enable quick-and-dirty-noweb-expansion by default and provide a
-noquick option.
What do you think ?

Cheers,
Nicolas

[O] [RFC] org-noweb: org-tangle + org-weave for literate programming using Org

[Nicolas Girard]

Hi folks,

I've released today a couple of tools named org-tangle and
org-weave in a public GitHub repository:
https://github.com/ngirard/org-noweb

I thought that Org's literate programming abilities deserved to be
made accessible non-interactively from the command-line via official
commands, and I hope this repository will help establish them.

The benefits of such an approach I can think of are:
- to provide people with reference tools they can refer to;
- to isolate common behavior from people's customization that can be
repeated consistently and reliably;
- to lower the entry barrier for newcomers;
- to attract the people who might just be interested in Org as a
literate programming tool first, before grasping other areas of the
Org platform.

Now, I'd be very glad if we could use this code as a starting point
and discuss about it.

For instance:

- What should these tools do, and how ? It seemed to me that they
should only glue functionality from external tools and libraries,
rather than embedding functionality in their cores.

  For instance, if org-weave ever had to gain cross-indexing and
referencing features similar to its oldest siblings (weave, noweave),
it should be achieved by leveraging some dedicated elisp package,
LaTeX style file, or whatever, rather than implementing them itself.

  What do you think ?

- Into which language should these tools be written ? I've chosen the
Bash shell because it's available almost everywhere. Does it seem ok
for you ? Would it be useful to write them in POSIX-compliant code ?

- About =org-tangle=: should it take only one org file, or several
files, as an argument ?

  I gave =org-tangle= the same behaviour than the code snippet that
can be found in Org manual
([[info:org#Batch%20execution][info:org#Batch execution]]), so for now
you can type

  #+begin_src sh
org-tangle file1.org file2.org
  #+end_src

  But it makes more sense to me, that org-tangle takes only one file,
and optionally the name of a source code block to be extracted, like

  #+begin_src sh
org-tangle file.org [chunkname]
  #+end_src

  What do you think ?

- About =org-babel-use-quick-and-dirty-noweb-expansion=: should it be
set to 't' by default ? I'd be tempted to say yes, given the dramatic
performance gain

- etc, etc...

Also, while not necessary, I thought it would be nice if org-noweb
tools ate their own dogfoot and extracted themselves ; so I've written
them in literate programming style and I have to say I really enjoyed
the process.

The tools are a mix of elisp and shell code, and it seems to me like
Org + literate style really shine here at making the code readable and
understandable.

That said, there are a few quirks into the code I'd be glad to see disappear:

1. It made sense for me to write the command line options as an Org
table (look at =#tblname: options= in
https://raw.githubusercontent.com/ngirard/org-noweb/master/org-tangle.org)
; but if you see the docstring for the =-E= option, I wanted to write
Default value is emacs but couldn't find a way to get this
reference to expand ; so I had to manually write Default value is
x. Any hints ?
2. The boilerplate fonctions =escape-quotes= and =format-options= :
could it be done in a better way ?

Cheers,

Nicolas

Re: [O] Add-on: Github Flavored Markdown exporter

[Nicolas Girard]

2014-04-11 12:29 GMT+02:00 Bastien b...@gnu.org:
 Hi Lars,


 I added your file to /contrib/lisp in the master branch,
 thanks a lot!

 I updated the copyright section of the file to put you
 as the author, instead of the FSF.


Hi, and thanks to Lars for this nice contribution !

=ox-gfm.el= didn't seem to make its way to the org+contrib package
from Org ELPA repo. Could anyone add it ?

Thanks in advance,
cheers,

Nicolas

Re: [O] Add-on: Github Flavored Markdown exporter

[Nicolas Girard]

2014-06-09 18:45 GMT+02:00 Bastien b...@altern.org:

 That's because ELPA packages are made from the maint branch of Org's
 repository.



Hi Bastien,

ooh, I see... nevermind, thanks for your reply !

Nicolas

[O] Outdated reference to http://orgmode.org/pkg/daily/ on the website

[Nicolas Girard]

Hi folks,

unless i'm misunderstood, the preferred Url to the Org Mode ELPA
server is http://orgmode.org/elpa/;, which replaced
http://orgmode.org/pkg/daily/;.

Apparently there is still a reference to the outdated url on the very
page http://orgmode.org/pkg/daily/;, which is confusing (at least to
my eyes).

Also the pages http://orgmode.org/elpa.html; and
http://orgmode.org/pkg/daily/; seem to be redundant.

Any thoughts ?

-- 
Nicolas

Re: [O] [export] Should sidewaystable option automatically add rotating package?

[Nicolas Girard]

2013/9/25 Carsten Dominik carsten.domi...@gmail.com:

 On 19.9.2013, at 11:38, Nicolas Girard girard.nico...@gmail.com wrote:

 I actually have some working code that does this. It lies in a file I
 named 'minimal.tex', which I include into all my latex code using
  \input{minimal}\makeatletter

 Hi Nicolas,

 of I were to include this code not via \input, but directly, somewhere in the 
 header,
 is there something special with makeatletter/makeatother that I have to do?


Good morning Carsten,

Despite being silent, I didn't forget about this thread ;-)

I came to think that, having a piece of code that brings
cross-compatibility between the 3 engines would be of interest to
people outside of the Org community. But this is not trivial,
especially if the code has to work with older TeX distributions (a
reasonable expectation would be that it works with, say, TeXlive 2011
and TeXlive 2012).

For instance, one difficulty is language specifics. pdflatex has Babel
; xelatex has polyglossia ; and lualatex didn't have any equivalent
package until a recent version of polyglossia that comes with the most
recent TeX distributions.

For these reasons, I would like to submit this question, with my code
as a starting point, to the tex.stackexchange.com community, so that
it is peer reviewed and we hopefully get something solid. I'm
currently working on it and intend to post either today or tomorrow.
Stay tuned !

Cheers,
Nicolas

Re: [O] [export] Should sidewaystable option automatically add rotating package?

[Nicolas Girard]

2013/9/19 Carsten Dominik carsten.domi...@gmail.com:

 On 19.9.2013, at 00:21, Rasmus ras...@gmx.us wrote:

 So what would the goal be?  To make it compatible with XeLaTeX and
 LuaLaTeX out of the box?

 Yes, this is what I mean.  I would be happy to have some clever line in there 
 that would do the right thing for variants of LaTeX.  THis is also what I 
 mean by all cases.


Hi all,
I actually have some working code that does this. It lies in a file I
named 'minimal.tex', which I include into all my latex code using
  \input{minimal}\makeatletter
The code allows me to compile my documents using pdflatex, lualatex or xelatex.
Please find attached the relevant part of my 'minimal.tex' file.
Cheers


m.tex
Description: TeX document

Re: [O] [export] Should sidewaystable option automatically add rotating package?

[Nicolas Girard]

2013/9/15 Carsten Dominik carsten.domi...@gmail.com:

 Does anyone know about conflicts arising from loading wrapfig and rotating?



Not that I know of.

Re: [O] How to trigger the clockcheck in an agenda view.

[Nicolas Girard]

2013/8/5 Sebastien Vauban sva-n...@mygooglest.com:

 Except the above, I definitely don't understand why it wouldn't work for you.
 Can you reproduce the problem with a minimal Emacs config file (adding the
 require of `org' and `org-agenda' before)?


I think I understand why Rainer has a problem.

According to the docstring from `org-agenda-custom-commands', there
are two acceptable syntaxes for defining a command:
- the simple one : (key desc type match settings files)
- and the complex or composite one : (key desc (cmd1 cmd2 ...)
general-settings-for-whole-set files).

Now, the following code defines two commands, who are functionally
identical, but syntactically different. The first one uses the simple
syntax, and the second one, the complex syntax.

If you evaluate the code and trigger the agenda, you'll see that the
first command *doesn't* work as expected, while the second works.

(I just borrowed your scissors to delimit my code, hope you don't mind ;-) )

--8---cut here---start-8---
  (setq org-agenda-custom-commands nil)
  (setq org-agenda-custom-commands
(append
 org-agenda-custom-commands '(
 (G Good: Clock Review
  ((agenda 
   ((org-agenda-show-log 'clockcheck)
(org-agenda-clockreport-mode t)
 (B  Bad: Clock Review
  agenda 
  ((org-agenda-show-log 'clockcheck)
   (org-agenda-clockreport-mode t))
--8---cut here---end---8---

Re: [O] [BUG] [Babel] Do not try to process inline source in macro templates

[Nicolas Girard]

2013/9/2 Eric Schulte schulte.e...@gmail.com :

 I've just pushed up a fix for this issue which should now ignore inline
 source blocks on lines starting with #+ during export.  I don't know
 if there is a better way than using a regex to detect such non-exporting
 lines but this appears to work.


Thanks very much !

[O] [BUG] [Babel] Do not try to process inline source in macro templates

[Nicolas Girard]

When a buffer contains such

#+MACRO: m src_emacs-lisp[:results raw]{(do-something $1)}

macro template, calling =org-babel-execute-buffer= using =C-c C-v C-b= yields

if: No id found: $1

It seems to me that Babel shouldn't be looking for inline code within
macro templates.

Cheers,

-- 
Nicolas

[O] [Babel] org-babel-execute-buffer gives different results than org-babel-exp-non-block-elements

[Nicolas Girard]

Hi all,

One thing I've been missing for long within org-mode is transclusion ;
so eventually I came up with some preliminary code which seems
promising regarding what I have in mind.

Now, I wish I would dedicate a full thread on this subject once my
code works in a predictable way ; but for now I'm experiencing
something annoying: while evaluating my test document using
=(org-babel-execute-buffer)=, or typing =C-c C-c= over the inline
Babel non block elements works fine, exporting the same document using
=C-c C-e t U= doesn't give the same results.

Looking into Babel source, I came up with the following conclusion:
- =(org-babel-execute-buffer)= produces the results I expect ;
- the exporter calls =org-export-execute-babel-code=, which eventually triggers
  =(org-babel-exp-non-block-elements (point-min) (point-max))=. And
this latter function doesn't lead to the same results as
=(org-babel-execute-buffer)=

Could anyone give me a hand on this ?

Attached is my test document, containing both my preliminary code for
transclusion, and some tests at the bottom.

Thanks very much in advance,

cheers,
Nicolas


transclusion.org
Description: Binary data

Re: [O] [Babel] org-babel-execute-buffer gives different results than org-babel-exp-non-block-elements

[Nicolas Girard]

2013/8/22 Nicolas Goaziou n.goaz...@gmail.com:

 I get errors when trying to execute the buffer.

Hi Nicolas,

oh yes, my bad, there was a parenthesis missing. Attached is the
corrected document.

 Also, could you provide
 a minimal example?

The attached document is as minimal as you can get IMHO ; but
admittedly I've been sparing with instructions !

Once loaded:

1. Evaluate the elisp code contained in the section Code to
evaluate, either by executing =(org-babel-load-file
buffer-file-name)=, or by evaluating manually each function using =C-x
C-e=
2. Run the small tests contained in the section Transclusion tests
using =(org-babel-execute-buffer)=. This will behave as expected
3. Restore the buffer to its original contents using =C-_=
4. Now, run =(org-babel-exp-non-block-elements (point-min)
(point-max))= and compare with the behaviour in step (2.)


transclusion.org
Description: Binary data

Re: [O] [Babel] org-babel-execute-buffer gives different results than org-babel-exp-non-block-elements

[Nicolas Girard]

Sorry again for the buggy minimal example.
Please try again with the attached version. Instructions as before:

1. Evaluate the elisp code contained in the section Code to
evaluate, either by executing =(org-babel-load-file
buffer-file-name)=, or by evaluating manually each function using =C-x
C-e=
2. Run the small tests contained in the section Transclusion tests
using =(org-babel-execute-buffer)=. This will behave as expected
3. Restore the buffer to its original contents using =C-_=
4. Now, run =(org-babel-exp-non-block-elements (point-min)
(point-max))= and compare with the behaviour in step (2.)


transclusion.org
Description: Binary data

Re: [O] [Babel] org-babel-execute-buffer gives different results than org-babel-exp-non-block-elements

[Nicolas Girard]

2013/8/22 Nicolas Goaziou n.goaz...@gmail.com:
 Nicolas Girard girard.nico...@gmail.com writes:

 Sorry again for the buggy minimal example.
 Please try again with the attached version. Instructions as before:

 Still get an error: (void-function ng/org-get-entry-title).


I'm ashamed... but this time I swear I started a minimal emacs session
and got it to work. The instructions have slightly changed and are
written at the very beginning of the attached minimal document.

Thanks !


transclusion.org
Description: Binary data

Re: [O] [Babel] org-babel-execute-buffer gives different results than org-babel-exp-non-block-elements

[Nicolas Girard]

2013/8/23 Nicolas Goaziou n.goaz...@gmail.com:
 Nicolas Girard girard.nico...@gmail.com writes:

 I see.

 There is an important difference between evaluating a buffer and
 evaluating a buffer during export. In the latter, Babel has to deal with
 replacement values, i.e., code block is replaced by its results. See the
 difference between `org-export-execute-babel-code' and
 `org-babel-execute-buffer' in a buffer containing only

   src_emacs-lisp[:results raw]{(+ 1 2)}

 In this case, your code removes the code (and much more) as
 a side-effect. This confuses `org-babel-exp-non-block-elements', which
 also tries to remove it. As this fails, it removes a random part of the
 buffer instead (probably as a mean revenge).


Thanks very much for your insight ! I came to the same conclusions and
found a temporary solution, namely using the value (bufferp
org-current-export-file) to check wether the code is called by the
exporter or just Babel. Attached is a modified version of my code that
behaves differently depending of the value of (bufferp
org-current-export-file).

Do you think it could be robust enough ?

 `org-babel-exp-non-block-elements' and `org-babel-exp-process-buffer'
 could probably check if code still exists before trying to remove (and
 replace) it.


Yeah, I don't know how much work it would represent but it seems much
more appropriate that my hack-ish solution.

---
Nicolas


transclusion.org
Description: Binary data

[O] [BUG] org-org-export-as-org is missing a body-only argument

[Nicolas Girard]

As title says, the function =org-org-export-as-org= from ox-org.el is
missing a body-only argument. This absence messes up the call to
org-export-to-buffer.

Cheers,

---
Nicolas

Re: [O] Feature request: setq org-agenda-follow-indirect 'parent

[Nicolas Girard]

 In this example, in order to work on, or even decide anything about
 Todo item 1, chances are that I'd also need to see the contents of
 the References and Notes items ; so the tree I'd need to see in
 the indirect buffer should have the *parent* of Todo item 1 as root,
 instead of Todo item 1 itself.

 C-u 1 C-c C-x b

 in Todo item 1 should do.


Hi, Bastien,

thanks for your reply.

Indeed, C-u -1 C-c C-x b is what I'm looking for.
So, in a nutshell, I wish that, using the agenda with follow-mode on,
hitting up or down would trigger (org-tree-to-indirect-buffer -1).

-- 
Nicolas

Re: [O] Is it possible to automatically set the timestamp recorded in a CLOSED: annotation to a different time than now?

[Nicolas Girard]

2012/9/19 Bastien b...@altern.org:

 I introduced `org-use-last-clock-out-time-as-effective-time' which lets
 you do this automatically.  You can test it from the git master branch
 for now, it will be in the next major release.


Useful idea, indeed, thanks for implementing it !

-- 
Nicolas

Re: [O] Feature request: setq org-agenda-follow-indirect 'parent

[Nicolas Girard]

2012/3/31 Nicolas Girard girard.nico...@gmail.com:

 when browsing my TODO items in the agenda, I wish I could display then
 in an indirect buffer.
 But as I structure my stuff, displaying the tree with a TODO item as
 root is often useless.

 Indeed, within my PROJECT items, I differentiate between TODO and
 support (notes, references) children ; for instance
 #+BEGIN_SRC org
   ,* PROJECT My project
   ,** References
   ,*** Ref 1
   ,*** Ref 2
   ,** Notes
   ,*** Note 1
   ,*** Note 2
   ,** TODO Todo item 1
   ,** TODO Todo item 2
 #+END_SRC

 In this example, in order to work on, or even decide anything about
 Todo item 1, chances are that I'd also need to see the contents of
 the References and Notes items ; so the tree I'd need to see in
 the indirect buffer should have the *parent* of Todo item 1 as root,
 instead of Todo item 1 itself.

 It seems rather easy to achieve, since `org-agenda-do-context-action'
 calls `org-agenda-tree-to-indirect-buffer', which is supposed to deal
 with this case when called with a numerical prefix argument ; so I did
 give it a try but couldn't get it to work properly :-(


Hi all,
any thoughts about my request ?

Thanks in advance,
cheers,
Nicolas

Re: [O] Batch processing part of a file

[Nicolas Girard]

2012/8/30 Bastien b...@altern.org:
 Nicolas Girard girard.nico...@gmail.com writes:

 I've also noticed that, using the latest Org version from git, src
 blocks with #+header lines *below* the #+name are handled
 incorrectly, contrary to blocks whose #+header lines lie *above* the
 #+name.

 It should work correctly now, thanks!


Thanks to you, Bastien, for considering the quickest  dirtiest bug
report I've ever written !

-- 
Nicolas

Re: [O] Batch processing part of a file

[Nicolas Girard]

2012/8/29 Loris Bennett loris.benn...@fu-berlin.de:
 Loris Bennett loris.benn...@fu-berlin.de writes:

 This problem seems to be caused by the use of '#+header', so with

 ,
 | #+name: test
 | #+header: :file out.txt
 | #+begin_src sh
 | echo blah
 | #+end_src
 `

 I get the above error, but with



I've also noticed that, using the latest Org version from git, src
blocks with #+header lines *below* the #+name are handled
incorrectly, contrary to blocks whose #+header lines lie *above* the
#+name.

-- 
Nicolas

[O] Feature request: setq org-agenda-follow-indirect 'parent

[Nicolas Girard]

Hi all,

when browsing my TODO items in the agenda, I wish I could display then
in an indirect buffer.
But as I structure my stuff, displaying the tree with a TODO item as
root is often useless.

Indeed, within my PROJECT items, I differentiate between TODO and
support (notes, references) children ; for instance
#+BEGIN_SRC org
  ,* PROJECT My project
  ,** References
  ,*** Ref 1
  ,*** Ref 2
  ,** Notes
  ,*** Note 1
  ,*** Note 2
  ,** TODO Todo item 1
  ,** TODO Todo item 2
#+END_SRC

In this example, in order to work on, or even decide anything about
Todo item 1, chances are that I'd also need to see the contents of
the References and Notes items ; so the tree I'd need to see in
the indirect buffer should have the *parent* of Todo item 1 as root,
instead of Todo item 1 itself.

It seems rather easy to achieve, since `org-agenda-do-context-action'
calls `org-agenda-tree-to-indirect-buffer', which is supposed to deal
with this case when called with a numerical prefix argument ; so I did
give it a try but couldn't get it to work properly :-(

Cheers,
Nicolas

Re: [O] [PATCH] Allow org-collector to display heading indentation

[Nicolas Girard]

2012/3/31 Sebastien Vauban wxhgmqzgw...@spammotel.com:

 You may want to follow the indent convention used for clockview: \__
 string.

 Have a look at (or reuse?) the function `org-clocktable-indent-string'...


Hi Sébastien,
fair enough ; not that I like underscores much better but it makes
sense for the indentation in both tables to be similar.
I've rewritten my code in this respect.

Cheers,
Nicolas

[O] [PATCH 1/2] Simplify org-clocktable-indent-string.

[Nicolas Girard]

---
 lisp/org-clock.el |6 +-
 1 files changed, 1 insertions(+), 5 deletions(-)

diff --git a/lisp/org-clock.el b/lisp/org-clock.el
index 591f59c..be66ce6 100644
--- a/lisp/org-clock.el
+++ b/lisp/org-clock.el
@@ -2342,11 +2342,7 @@ from the dynamic block definition.
 (defun org-clocktable-indent-string (level)
   (if (= level 1)
   
-(let ((str \\__))
-  (while ( level 2)
-   (setq level (1- level)
- str (concat str ___)))
-  (concat str  
+(concat \\ (make-string (* 2 (1- level)) ?_ )  )))
 
 (defun org-clocktable-steps (params)
   Step through the range to make a number of clock tables.
-- 
1.7.8.rc1

[O] [PATCH 2/2] Allow org-collector to display heading indentation by passing ':indent t' to the propview block.

[Nicolas Girard]

---
 contrib/lisp/org-collector.el |   22 +-
 1 files changed, 17 insertions(+), 5 deletions(-)

diff --git a/contrib/lisp/org-collector.el b/contrib/lisp/org-collector.el
index da612e9..2f5e598 100644
--- a/contrib/lisp/org-collector.el
+++ b/contrib/lisp/org-collector.el
@@ -91,6 +91,7 @@
 
 ;;; Code:
 (require 'org)
+(require 'org-clock)
 (require 'org-table)
 
 (defvar org-propview-default-value 0
@@ -98,6 +99,11 @@
 value is calculated either through lack of required variables for
 a column, or through the generation of an error.)
 
+(defvar org-propview-indent-function 'org-clocktable-indent-string
+  A function called with the heading level. Should return a
+string which will be concatenated to the ITEM property when
+':indent t' is passed to the propview block.)
+
 (defun and-rest (list)
   (if (listp list)
   (if ( (length list) 1)
@@ -121,6 +127,7 @@ preceeding the dblock, then update the contents of the 
dblock.
(scope (plist-get params :scope))
(noquote (plist-get params :noquote))
(colnames (plist-get params :colnames))
+   (indent (plist-get params :indent))
(content-lines (org-split-string (plist-get params :content) \n))
id table line pos)
(save-excursion
@@ -134,8 +141,8 @@ preceeding the dblock, then update the contents of the 
dblock.
  (org-narrow-to-subtree)
  (setq stringformat (if noquote %s %S))
  (setq table (org-propview-to-table
-  (org-propview-collect cols stringformat conds match 
scope inherit 
-(if colnames colnames cols)) 
stringformat))
+  (org-propview-collect cols stringformat conds match 
scope inherit
+(if colnames colnames cols) 
indent) stringformat))
  (widen))
(setq pos (point))
(when content-lines
@@ -171,14 +178,19 @@ variables and values specified in props
 (when p (cons n p
 inherit
 
-(defun org-propview-collect (cols stringformat optional conds match scope 
inherit colnames)
+(defun org-propview-collect (cols stringformat optional conds match scope 
inherit colnames indent)
   (interactive)
   ;; collect the properties from every header
   (let* ((header-props
  (let ((org-trust-scanner-tags t) alst)
(org-map-entries
-(quote (cons (cons ITEM (org-get-heading t))
- (org-propview-get-with-inherited inherit)))
+(quote
+ (cons (cons ITEM
+ (let ((item (org-get-heading t))
+   (level (org-current-level)))
+   (concat
+(funcall org-propview-indent-function level) 
item)))
+  (org-propview-get-with-inherited inherit)))
 match scope)))
 ;; read property values
 (header-props
-- 
1.7.8.rc1

[O] [PATCH] Allow org-collector to display heading indentation

[Nicolas Girard]

Hi all,
attached is a patch which adds a new parameter indent to the
propview dynamic bloc, with the following behaviour:

#+BEGIN_SRC org
  ,* Tree
  ,:PROPERTIES:
  ,:COLUMNS: %8ITEM %4prop1 %5prop2
  ,:ID: tree
  ,:END:
  ,** A
  ,:PROPERTIES:
  ,:prop1: 10
  ,:prop2: 20
  ,:END:
  ,*** A1
  ,:PROPERTIES:
  ,:prop1: 15
  ,:prop2: 19
  ,:END:
  ,*** A2
  ,:PROPERTIES:
  ,:prop1: 20
  ,:prop2: 18
  ,:END:
  ,** B
  ,:PROPERTIES:
  ,:prop1: 25
  ,:prop2: 10
  ,:END:
  ,*** B1
  ,:PROPERTIES:
  ,:prop1: 2
  ,:prop2: 4
  ,:END:
  ,*** B2
  ,:PROPERTIES:
  ,:prop1: 3
  ,:prop2: 5
  ,:END:

#+END_SRC

#+BEGIN: propview :id tree :cols (ITEM prop1) :noquote t :indent t
| ITEM   | prop1 |
|+---|
| Tree   | 0 |
| \- A   |10 |
| \-- A1 |15 |
| \-- A2 |20 |
| \- B   |25 |
| \-- B1 | 2 |
| \-- B2 | 3 |
|+---|
||   |
#+END

I wish the indentation to be displayed with nothing but spaces, but
they would be trimmed by org-table guts ; so that's middly satisfying,
but better than nothing :-)

Cheers,

Nicolas


org-collector.el.diff
Description: Binary data

Re: [O] [PATCH] Allow org-collector to display heading indentation

[Nicolas Girard]

From eaf9e5f06279069ed1072425fd020d8f0442d04f Mon Sep 17 00:00:00 2001
From: Nicolas Girard girard.nico...@gmail.com
Date: Fri, 30 Mar 2012 22:53:13 +0200
Subject: [PATCH] Allow org-collector to display heading indentation

---
 contrib/lisp/org-collector.el |   12 +---
 1 files changed, 9 insertions(+), 3 deletions(-)

diff --git a/contrib/lisp/org-collector.el b/contrib/lisp/org-collector.el
index da612e9..2476d62 100644
--- a/contrib/lisp/org-collector.el
+++ b/contrib/lisp/org-collector.el
@@ -121,6 +121,7 @@ preceeding the dblock, then update the contents of
the dblock.
(scope (plist-get params :scope))
(noquote (plist-get params :noquote))
(colnames (plist-get params :colnames))
+   (indent (plist-get params :indent))
(content-lines (org-split-string (plist-get params :content) \n))
id table line pos)
(save-excursion
@@ -135,7 +136,7 @@ preceeding the dblock, then update the contents of
the dblock.
  (setq stringformat (if noquote %s %S))
  (setq table (org-propview-to-table
   (org-propview-collect cols stringformat conds match 
scope inherit
-(if colnames colnames cols)) 
stringformat))
+(if colnames colnames cols) 
indent) stringformat))
  (widen))
(setq pos (point))
(when content-lines
@@ -171,13 +172,18 @@ variables and values specified in props
 (when p (cons n p
 inherit

-(defun org-propview-collect (cols stringformat optional conds match
scope inherit colnames)
+(defun org-propview-collect (cols stringformat optional conds match
scope inherit colnames indent)
   (interactive)
   ;; collect the properties from every header
   (let* ((header-props
  (let ((org-trust-scanner-tags t) alst)
(org-map-entries
-(quote (cons (cons ITEM (org-get-heading t))
+(quote (cons (cons ITEM
+   (let ((item (org-get-heading t))
+ (level (- (org-current-level) 1)))
+ (if (and indent ( level 0))
+ (format \\%s %s
+ (make-string level ?- ) item) 
item)))
  (org-propview-get-with-inherited inherit)))
 match scope)))
 ;; read property values
-- 
1.7.8.rc1

Re: [O] [babel] [bug] org-babel-use-quick-and-dirty-noweb-expansion

[Nicolas Girard]

2012/3/19 Eric Schulte eric.schu...@gmx.com

 Thanks for bringing up this bug.  I'm attaching a patch to this email,
 once the current repositories issues are resolved I'll apply this patch
 to the repository.  In the interim, you can apply this patch to your
 local copy of the git repository with.


Great ! It's such a relief to be able to tangle my stuff in 8 s vs 4
to 5 minutes !
Thanks so much !

Nicolas

[O] [babel] [bug] org-babel-use-quick-and-dirty-noweb-expansion

[Nicolas Girard]

Hi all,
I've been succesfully using babel to make various literate programming work.
Unfortunately, tangling performance has dramatically decreased, to the
point of being barely usable.
I wish I could get advantage of the quick  dirty noweb expansion Eric
introduced in january, but it has an undesirable side effect. Consider the
following minimal example:

#
#+name: abc
#+begin_src latex
  Abcabc-d
#+end_src

#+name: abc-d
#+begin_src latex
  Def
#+end_src

#+begin_src latex :noweb yes :tangle test.tex
  abc
#+end_src
#

Tangling with *org-babel-use-quick-and-dirty-noweb-expansion* set to nil
gives

#
AbcDef
#

while tangling with *org-babel-use-quick-and-dirty-noweb-expansion* set to
t gives

#
AbcDef
Def
#

I'd be very happy if this bug could be tracked down.
Thanks very much in advance !
Cheers,

Nicolas

[Orgmode] Non-breaking space

[Nicolas Girard]

Hi,

How can I typeset, for instance, 100 €, in such a way that, once
exported in LaTeX, it gives: 100~€ (with a non-breaking space) ?

Thanks in advance !
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] LATEX_CLASS

[Nicolas Girard]

Hi all,
I've just noticed that it's no longer allowed to put neither '-' nor
'_' in the latex class, such as:

#+LATEX_CLASS: auto-report

I personaly find it a little bit annoying and wished to know if this
was intentional

Thanks in advance,
cheers,

Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] LATEX_CLASS

[Nicolas Girard]

2010/4/23 Carsten Dominik carsten.domi...@gmail.com:
 On Apr 23, 2010, at 6:02 PM, Nicolas Girard wrote:

 Hi all,
 I've just noticed that it's no longer

 No longer?  I don't think I changed anything here...



Well, it's weird, because I just did a git pull today, last time was
about 5 weeks ago, and I used to get this to work:
#+LATEX_CLASS: auto-report


 allowed to put neither '-' nor
 '_' in the latex class, such as:

 #+LATEX_CLASS: auto-report

 I personaly find it a little bit annoying and wished to know if this
 was intentional

 I have no objections against dashes in these names and have
 changed the regexp to allow this now.


Thanks very much Carsten !

Cheers,
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Re: [babel] org-babel: tangling to latex .sty/.cls files

[Nicolas Girard]

 Thanks very much. I believe I have just pushed a fix for that. If you
 get a chance to double-check that everything seems OK that would be
 great.


Yes, I think it's ok now.
Thanks again !

Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Another quote about Org-mode

[Nicolas Girard]

Just read this in #emacs from bozhidar... found it funny:

  LaTeX is the past, the present, the future, and everything in
between is org-mode.


Cheers,
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Re: [babel] org-babel: tangling to latex .sty/.cls files

[Nicolas Girard]

2010/3/18 Dan Davison davi...@stats.ox.ac.uk:
 Thomas S. Dye t...@tsdye.com writes:



 OK, I've gone ahead with that. No extension added now unless ':tangle yes'.


Hi Dan,

Thanks very much, but it seems to break org-babel-load-file.
From the source code of org-babel-load-file:
(org-babel-tangle-file file base-name emacs-lisp) - tangles f.org
into f ; but then
(load-file exported-file) - tries to load f.el, which doesn't exist

Cheers,
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] org-babel: tangling to latex .sty/.cls files

[Nicolas Girard]

Hi all,
a while ago Babel allowed latex code to be tangled to a file named
f.sty or f.cls ; it's currently not possible any more, because the
tangled file is named f.sty.tex or f.cls.tex.
I tried to deal with it but I'm really missing this feature a lot.
Do you think org-babel could allow this again ?
Thanks very much in advance,
cheers,
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Disabling warnings when following [[elisp:...]] links

[Nicolas Girard]

Hi,
is it possible to disable warnings when following [[elisp:...]] links
on a per-buffer basis ? I'd find this much useful !

Thanks in advance,
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: Disabling warnings when following [[elisp:...]] links

[Nicolas Girard]

2010/3/17 Mikael Fornius m...@abc.se:

 You should be able to customize variable
 `org-confirm-elisp-link-function' and to do it per-buffer basis works
 with emacs file local variables. Begin the org-file with this line:

 -*- org-confirm-elisp-link-function: nil -*-

 then re-open the file. For more info:

 (info (Emacs) Specifying File Variables)


Thanks Mikael, it's exactly what I needed !

Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] [ANN] It's not a bird, it's not a plane, it's... org-icons.el, reloaded !

[Nicolas Girard]

Hi all,

I'm pleased to announce a brand new, shiny release for org-icons.
A few minor limitations remain, but I think the code has matured
enough to be used on a daily basis.
See for yourself ! Grab it at [1] and see the following instructions
for installing.

I indend to win this year's Most Ridiculous Release Number Contest, so
I set the current one to 0.271182363. Wish me luck: I seem to have
some quite serious opponents... I dare you, Memoir ! [2].

[1] http://github.com/ngirard/org-icons
[2] http://www.ctan.org/tex-archive/macros/latex/contrib/memoir/


* Installation

1. Apply org-icons.patch on the latest org-mode code:
cd path/to/org-mode
patch -p0  path/to/org-icons/lisp/org-icons.patch
rm org.elc ; make ; sudo make install

2. Add org-icons/lisp to your load-path:
(setq load-path (cons /path/to/org-icons/lisp load-path))

3. Restart emacs

* Usage

- You can turn on `org-icons-mode' on startup by setting the
  org-startup-with-icons-mode variable to true,

(setq org-startup-with-icons-mode t)

- You can also enable or disable icon display on a per-buffer level, using

M-x org-icons-mode

- A key sequence can easily be used for this, like =C-c i= in this example:

(add-hook 'org-mode-hook
  (lambda () (local-set-key \C-ci 'org-icons-mode)))

* Configuration

Conceivably the Org Mode community will agree on how Org icons theme
should be defined, if they make sense. Org Mode's philosophy is to be
as generic as possible and it's not clear to me how to capture what
most people need while keeping in balance with flexibility.

Meanwhile, the set of icons that can be used, `org-icons-set', is a
little bit hardwired into the code.

More flexible are the functions governing which icon to draw, namely
`org-todo-state-icon-at', `org-priority-icon-at', `org-drawer-icon-at'
and `org-special-keyword-icon-at'. Looking at the source code should
be enough for you to redefine these functions to suit your needs. For
instance, you'll most probably want to write in your configuration

  (defun org-todo-state-icon-at (state priority tags)
(cond
  ...
)
  )

and instead of the dots, a set of (condition icon-name) like

  ((member SOMEDAY  tags ) state-someday)

or more complex, like

  ((equal  NEXT state)
 (if (= priority 2000) state-next-important state-next))

* Bugs and limitations

- Documentation is missing.
- No themes yet: see the introduction.
- When cycling from a TODO keyword to no keyword using S-right, the
  latest icon remains displayed.
- When loading an org buffer, font-lock-fontify-buffer is called twice
  if org-startup-with-icons-mode is set to t.
- The standard icon set isn't visually consistent enough

* Please consider...

- the code is still beta;
- any suggestion / contribution warmly welcome.


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: Bug: (org-attach-dir) doesn't honor ATTACH_DIR_INHERIT

[Nicolas Girard]

2010/2/22 Matt Lundin m...@imapmail.org:
 Nicolas Girard nicolas.gir...@nerim.net writes:


 The :ATTACH_DIR_INHERIT: property needs to be set in the parent tree,
 since that is the heading whose attach directory is being inherited.


Hi Matt,

indeed, I got this wrong. Thanks for your explanations !

Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Bug: (org-attach-dir) doesn't honor ATTACH_DIR_INHERIT

[Nicolas Girard]

Hi,
given the following test document, calling (org-attach-dir) when in b
should give '/tmp' ; currently the result is nil, which breaks C-c C-a
f.

Cheers,
Nicolas

===
* a
:PROPERTIES:
:ATTACH_DIR: /tmp
:END:
** b
:PROPERTIES:
:ATTACH_DIR_INHERIT: t
:END:


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Customizing how inactive timestamps are displayed

[Nicolas Girard]

2009/12/16 Carsten Dominik carsten.domi...@gmail.com:

 On Dec 15, 2009, at 10:57 PM, Nicolas Girard wrote:

 See ? Who said Org couldn't be sexier ?

 [*] http://www.levien.com/type/myfonts/inconsolata.html

 That *does* look nice!

 Please pull and use `org-agenda-inactive-leader'


Thanks very much, Carsten !

-- 
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Re: [PATCH] Suppress extra newlines around source code in LaTeX export

[Nicolas Girard]

2009/12/14 Carsten Dominik carsten.domi...@gmail.com:
 Actually,  I cannot reproduce this problem - I do not see the extra newline.

Hi Carsten,

you're absolutely right, I performed yet another git pull and couldn't
reproduce this either. Great !

Now, speaking of extra newlines, I'm puzzled about this: at some stage
(which I didn't identify yet, maybe when exporting to LaTeX), Org adds
an ID property to some headings in my document ; that is, for
instance,

* Aa
  * Bb
Text

becomes

* Aa
  * Bb
:PROPERTIES:
:ID: fa489059-d27e-47fb-929d-8ca9c749d079
:END:

Text


Notice the extra newline between :END: and Text. It's all good except
when exporting to LaTeX *and* the concerned heading is to be treated
as an item.
I've been thinking a bit about this special case ; and it seems to me
like, on one side, the extra newline should remain, and on the other
side, empty lines following a heading should be ignored by the LaTeX
translator when this heading is translated into an item.
What do you think ?

-- 
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] [Bug] Logbook mode doesn't honor org-log-note-headings

[Nicolas Girard]

2009/12/14 Carsten Dominik carsten.domi...@gmail.com:
 Hi Nicolas,

 On Dec 10, 2009, at 11:20 PM, Nicolas Girard wrote:

 Hi,

 Org offers the ability to customize how state changes should be
 recorded via the 'org-log-note-headings' variable; and I couldn't
 prevent myself from doing so.
 I just came to realize this was the reason why the logbook mode kept
 being desperatly silent in my agenda views...

 I think this only applies to the state changes, right?  Or is there anything
 else dependent on this?


I'm not sure I understand your question ; I think yes, and what you
just added to the documentation is self explaining, thanks !

There seems to be an extra 'because', btw:

diff --git a/lisp/org.el b/lisp/org.el
@@ -2070,7 +2070,10 @@ empty string.
+In fact, it is not a good idea to change the `state' entry, because
+because agenda log mode depends on the format of these entries.

-- 
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Agenda view forgets about including inactive timestamps when refreshed

[Nicolas Girard]

2009/12/14 Carsten Dominik carsten.domi...@gmail.com:

 On Dec 10, 2009, at 11:26 PM, Nicolas Girard wrote:

 Hi,
 after the inactive timestamps were included into the agenda view by
 typing '[', they get lost when the view is refreshed by typing 'g'.
 I'm not sure, but it looks like a bug to me.

 Yes, I have not really made this into one of the formal view
 modes, because I believe that this view is the exception, and it is
 expensive to make.

 I'd think it is not so bad to press `g [' if you need it, right?


Sure, it's harmless !

-- 
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Feature request: Remote editing inactive timestamps from the agenda view

[Nicolas Girard]

2009/12/14 Carsten Dominik carsten.domi...@gmail.com:
 Hi Nicolas,

 On Dec 10, 2009, at 11:51 PM, Nicolas Girard wrote:

 Hi,

 in the agenda view, the '' key can be used to change the timestamp
 associated with the current line.

 1. It seems inacurrately described in the manual (Change the
 timestamp associated with the current line **to today**).

 Indeed, it used to be like this, but no longer.  Fixed now

 2. When dealing with inactive timestamp, the '' key currently does
 nothing. Could it be possible to make it also work with inactive
 timestamps ?

 You mean if the entry i in the agenda because of an inactive
 time stamp?  Yes, I'd think that makes sense.  Done


Thanks Carsten, it's quite handy !

-- 
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Quoting latex code

[Nicolas Girard]

2009/12/15 andrea andrea.crott...@gmail.com:

 I want to do something which I think should be really simple.
 I'm writing a small guide of latex for org-users, useful for people
 working with me that don't know latex but must insert some symbols in
 org-files.

 So I want to create simple tables where I insert the symbol and the
 output.
 But however I insert \phi|\pi|whatever it gets always transformed into
 the symbol when exporting to pdf.

 (also \mbox doesn't work)
 How could I do to get something like this:

 literal(\phi) - \phi

 Without possibly having to write some
 #+BEGIN...
 Thanks


Hi Andrea,
what about =\phi= ?

--
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Customizing how inactive timestamps are displayed

[Nicolas Girard]

2009/12/14 Carsten Dominik carsten.domi...@gmail.com:

 On Dec 10, 2009, at 11:34 PM, Nicolas Girard wrote:

 Hi again,
 in the agenda view, inactive timestamps are displayed like:

  category: 12:50.. [ Some stuff

 Is the '[ ' intentional, or is caused by a bug in my configuration ?
 I find it a little bit disturbing, as my eyes keep looking for an
 hypothetic closing ']'...

 This is intentional, as an indication that this is indeed an
 inactive time stamp.  While I can see that you might be
 looking for the closing bracket, I also think that this is a
 quite natural way to mark inactive time stamps.  Sure, I *could* make
 this marker string a variable - what would you propose as better
 options?


Hi Carsten,

my personal taste would be some kind of horizontal sign, because it
would look closer to what I'd have drawn myself using pen  paper,
answering my own question hey, what did I do today ? (French people
tend to use dashes when writing lists).

That said, I'm using the free Inconsolata [*] font as my main font in
emacs, which offers a rich collection of various geometric shapes 
symbols. So, at no extra cost, I can enhance the aspect of my Org
buffers.

Attached is a little example to demonstrate what can be done. To get
this result:
1. I had to redefine org-agenda-format-date-aligned so that I can
replace the hardcoded lines surrounding dates with better looking ones
2. I used the Watch unicode character to represent scheduled events:
(setq org-agenda-scheduled-leaders '(⌚  ⌚ ))
3. I replaced the hardcoded '[' character denoting inactive timestamps
with a white triangle

See ? Who said Org couldn't be sexier ?

[*] http://www.levien.com/type/myfonts/inconsolata.html

-- 
Nicolas
attachment: agenda.png___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Re: [PATCH] Suppress extra newlines around source code in LaTeX export

[Nicolas Girard]

2009/12/9 Nicolas Girard nicolas.gir...@nerim.net:
 2009/12/9 Carsten Dominik carsten.domi...@gmail.com:

 diff --git a/lisp/org-exp.el b/lisp/org-exp.el
 index 4c4d540..75ee548 100644
 --- a/lisp/org-exp.el
 +++ b/lisp/org-exp.el
 @@ -2423,7 +2423,7 @@ INDENT was the original indentation of the block.
                             (concat (car org-export-latex-verbatim-wrap)
                                     rtn (cdr
 org-export-latex-verbatim-wrap)))
                          '(org-protected t))
 -                     #+END_LaTeX\n))
 +                     #+END_LaTeX))
             ((eq backend 'ascii)
              ;; This is not HTML or LaTeX, so just make it an example.
              (setq rtn (org-export-number-lines rtn 'ascii 0 0 num cont
 rpllbl fmt))


 I have fixed this part, in a different way though.


 I'm afraid there are still extra paragraphs resulting from an extra
 newline after code blocs.

 Consider the following test chunk:

 #=
 This is a new paragraph
 #+begin_src emacs-lisp
 (setq ispell-program-name aspell)
 #+end_src
 continuing after the code bloc.
 #=

 Using the freshest code, is is translated to

 %=
 This is a new paragraph
 \lstset{language=Lisp}
 \begin{lstlisting}
 (setq ispell-program-name aspell)
 \end{lstlisting}

 continuing after the code bloc.
 %=




Unfortunately this problem remains: processing

#=
This is a new paragraph
#+begin_src emacs-lisp
(setq ispell-program-name aspell)
#+end_src
continuing after the code bloc.
#=

still inserts an extra newline just before continuing (...).

Cheers,

-- 
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Re: [PATCH] Suppress extra newlines around source code in LaTeX export

[Nicolas Girard]

2009/12/10 Carsten Dominik carsten.domi...@gmail.com:

 On Dec 10, 2009, at 12:56 AM, Nicolas Girard wrote:

 2009/12/9 Nicolas Girard nicolas.gir...@nerim.net:


 Actually I do remember why I considered removing the '\\' : take this
 document:

 #=
 Level 1

 ** Level 2

 *** Level 3

  Level 4
 - itemized
 - list
 #=

 Since Level 4 is expressed as an item, the only way of getting the
 correct output is *not* to have any '\\' between Level 4 and
 itemized. That is, in LaTeX, not to have '\\' between
  \item Level 4
 and
  \begin{itemize} \item itemized \item list \end{itemize}

 OK, I am catching this case now as well.

 Let me know if it works all right now.


Hi Carsten,
this works fine now, thanks very much !

--
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Re: [PATCH] Suppress extra newlines around source code in LaTeX export

[Nicolas Girard]

 On Dec 9, 2009, at 11:50 PM, Nicolas Girard wrote:

 There's an extra space produced by the \label{} because there's no '%'
 at the end of it ; another solution is to move the \label before the
 \\

 I prefer to write

   \label{...}%

 if you can agree to that.


Sure, no problem !

--
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] [Bug] Logbook mode doesn't honor org-log-note-headings

[Nicolas Girard]

Hi,

Org offers the ability to customize how state changes should be
recorded via the 'org-log-note-headings' variable; and I couldn't
prevent myself from doing so.
I just came to realize this was the reason why the logbook mode kept
beeing desperatly silent in my agenda views...

Cheers,

-- 
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Customizing how inactive timestamps are displayed

[Nicolas Girard]

Hi again,
in the agenda view, inactive timestamps are displayed like:

  category: 12:50.. [ Some stuff

Is the '[ ' intentional, or is caused by a bug in my configuration ?
I find it a little bit disturbing, as my eyes keep looking for an
hypothetic closing ']'...
If need be, could it be possible to customize this appearance ?


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Feature request: Remote editing inactive timestamps from the agenda view

[Nicolas Girard]

Hi,

in the agenda view, the '' key can be used to change the timestamp
associated with the current line.

1. It seems inacurrately described in the manual (Change the
timestamp associated with the current line **to today**).
2. When dealing with inactive timestamp, the '' key currently does
nothing. Could it be possible to make it also work with inactive
timestamps ?

Thanks in advance,

-- 
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] [Bug] State of repeated tasks incorrectly reported in logbook mode

[Nicolas Girard]

Hi,

Despite a repeated task is logged as DONE on 2009-12-10, the status
displayed in the logbook mode for that day is TODO.
This is a bug in my humble opinion.

Cheers,
-- 
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Feature request: Display estimated end time in agenda view

[Nicolas Girard]

Hi,
When a task t is scheduled at 10:00 and has the :Effort: property set
to 0:30, it is currently displayed in the agenda view like:

  categ:10:00.. Scheduled:  TODO t

I'd find it useful if it was displayed like:

  categ:10:00-10:30 Scheduled:  TODO t


Cheers,

-- 
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Re: [PATCH] Suppress extra newlines around source code in LaTeX export

[Nicolas Girard]

2009/12/9 Carsten Dominik carsten.domi...@gmail.com:
 Hi Nicolas,

 I need additional information with respect to this patch:


 diff --git a/lisp/org-latex.el b/lisp/org-latex.el
 index ce697a3..18c2183 100644
 --- a/lisp/org-latex.el
 +++ b/lisp/org-latex.el
 @@ -877,7 +877,7 @@ If NUM, export sections as numerical sections.
                 (delete-region (point-at-bol 0) (point))
               (insert (format \\begin{%s}\n
                               (symbol-name org-export-latex-low-levels
 -            (insert (format \n\\item %s\n%s\n
 +            (insert (format \\item %s\n%s
                             heading
                             (if label (format \\label{%s} label) )))
             (insert (org-export-latex-content content))

 Why would you like to remove the \\ as well?  When itemize lists are used
 to format headlines, I think there should be a line break after the end of
 the original headline.  Otherwise the text below the headline will flow into
 the headline.  Or am I missing something here?

I think you're right ; I may have been abused by what Adobe Reader
displayed when performing my tests, as I just discovered that, for
whatever reason, it doesn't always reload the pdf file when using
Ctrl-r

Using this test document

#===
* Level 1

** Level 2

*** Level 3

 Level 4
Text
#===

the current code produces

%==
\begin{itemize}

\item Level 4\\
\label{sec-1.1.1.1}

Text
%==

There's an extra space produced by the \label{} because there's no '%'
at the end of it ; another solution is to move the \label before the
\\
There's also an extra newline before Text.
Please find attached my second proposal to fix this.




 @@ -997,7 +997,7 @@ OPT-PLIST is the options plist for current buffer.
      (org-export-apply-macros-in-string org-export-latex-append-header)
      ;; insert the title
      (format
 -      \n\n\\title{%s}\n
 +      \n\\title{%s}\n
       ;; convert the title
       (org-export-latex-content
        title '(lists tables fixed-width keywords)))

 What is the problem with additional empty lines before \\title command.
  Does that really change anything in the output?

It's not really a problem, it just seems to me like, the less extra
'\n' you see in the output of a LaTeX code generator, the more
confident you can be.

-- 
Nicolas
diff --git a/lisp/org-latex.el b/lisp/org-latex.el
index ad443aa..1657209 100644
--- a/lisp/org-latex.el
+++ b/lisp/org-latex.el
@@ -864,7 +864,7 @@ If NUM, export sections as numerical sections.
 			   (buffer-substring (point-at-bol 0) (point)))
 		 (delete-region (point-at-bol 0) (point))
 	   (insert \\begin{description}\n))
-	 (insert (format \n\\item[%s]%s~\n\n
+	 (insert (format \n\\item[%s]%s~
 			 heading
 			 (if label (format \\label{%s} label) )))
 	 (insert (org-export-latex-content content))
@@ -877,7 +877,7 @@ If NUM, export sections as numerical sections.
 		 (delete-region (point-at-bol 0) (point))
 	   (insert (format \\begin{%s}\n
 			   (symbol-name org-export-latex-low-levels
-	 (insert (format \n\\item %s\n%s\n
+	 (insert (format \n\\item %s%s~
 			 heading
 			 (if label (format \\label{%s} label) )))
 	 (insert (org-export-latex-content content))
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Re: [PATCH] Suppress extra newlines around source code in LaTeX export

[Nicolas Girard]

2009/12/9 Nicolas Girard nicolas.gir...@nerim.net:
 2009/12/9 Carsten Dominik carsten.domi...@gmail.com:
 Hi Nicolas,

 I need additional information with respect to this patch:


 diff --git a/lisp/org-latex.el b/lisp/org-latex.el
 index ce697a3..18c2183 100644
 --- a/lisp/org-latex.el
 +++ b/lisp/org-latex.el
 @@ -877,7 +877,7 @@ If NUM, export sections as numerical sections.
                 (delete-region (point-at-bol 0) (point))
               (insert (format \\begin{%s}\n
                               (symbol-name org-export-latex-low-levels
 -            (insert (format \n\\item %s\n%s\n
 +            (insert (format \\item %s\n%s
                             heading
                             (if label (format \\label{%s} label) )))
             (insert (org-export-latex-content content))

 Why would you like to remove the \\ as well?  When itemize lists are used
 to format headlines, I think there should be a line break after the end of
 the original headline.  Otherwise the text below the headline will flow into
 the headline.  Or am I missing something here?

 I think you're right ; I may have been abused by what Adobe Reader
 displayed when performing my tests, as I just discovered that, for
 whatever reason, it doesn't always reload the pdf file when using
 Ctrl-r


Actually I do remember why I considered removing the '\\' : take this document:

#=
 Level 1

** Level 2

*** Level 3

 Level 4
- itemized
- list
#=

Since Level 4 is expressed as an item, the only way of getting the
correct output is *not* to have any '\\' between Level 4 and
itemized. That is, in LaTeX, not to have '\\' between
  \item Level 4
and
  \begin{itemize} \item itemized \item list \end{itemize}

-- 
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] [BUG] Code bloc after sublist isn't exported to LaTeX

[Nicolas Girard]

Hi,

the following sample document contains 3 code blocs ; only 2 of them
are properly exported to LaTeX.

#=
* Section

- A :: alpha

  - Aa

  - Bb

#+begin_src emacs-lisp
 (message This works)
#+end_src

  #+begin_src emacs-lisp
   (message This doesn't)
  #+end_src

- B :: beta

#+begin_src emacs-lisp
  (message This works)
#+end_src
#=

-- 
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] [BUG] ':' whithin * markup incorrectly rendered in LaTeX

[Nicolas Girard]

Hi,

*BUG:* is incorrectly translated in LaTeX to
  \textbf{BUG:\}
It should be
  \textbf{BUG:}

-- 
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: [PATCH] Suppress extra newlines around source code in LaTeX export

[Nicolas Girard]

2009/12/1 Nicolas Girard nicolas.gir...@nerim.net:
 Hi,
 title says it all.


Hi,

attached is a second patch which suppresses some other extra newlines
in the LaTeX export. Let me know if  you need any explanation.

-- 
Nicolas
diff --git a/lisp/org-exp.el b/lisp/org-exp.el
index 4c4d540..75ee548 100644
--- a/lisp/org-exp.el
+++ b/lisp/org-exp.el
@@ -2423,7 +2423,7 @@ INDENT was the original indentation of the block.
 (concat (car org-export-latex-verbatim-wrap)
 rtn (cdr org-export-latex-verbatim-wrap)))
 			  '(org-protected t))
-		  #+END_LaTeX\n))
+		  #+END_LaTeX))
 	 ((eq backend 'ascii)
 	  ;; This is not HTML or LaTeX, so just make it an example.
 	  (setq rtn (org-export-number-lines rtn 'ascii 0 0 num cont rpllbl fmt))
diff --git a/lisp/org-latex.el b/lisp/org-latex.el
index ce697a3..18c2183 100644
--- a/lisp/org-latex.el
+++ b/lisp/org-latex.el
@@ -877,7 +877,7 @@ If NUM, export sections as numerical sections.
 		 (delete-region (point-at-bol 0) (point))
 	   (insert (format \\begin{%s}\n
 			   (symbol-name org-export-latex-low-levels
-	 (insert (format \n\\item %s\n%s\n
+	 (insert (format \\item %s\n%s
 			 heading
 			 (if label (format \\label{%s} label) )))
 	 (insert (org-export-latex-content content))
@@ -997,7 +997,7 @@ OPT-PLIST is the options plist for current buffer.
  (org-export-apply-macros-in-string org-export-latex-append-header)
  ;; insert the title
  (format
-  \n\n\\title{%s}\n
+  \n\\title{%s}\n
   ;; convert the title
   (org-export-latex-content
title '(lists tables fixed-width keywords)))
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] [BUG] Bad handling of \ in link names

[Nicolas Girard]

hi all,
as title says, a link such as
  [[http://www.somewhere.org][\maketitle]]
is badly handled.

-- 
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Re: [BUG] LaTeX exporter should honor empty lines

[Nicolas Girard]

2009/12/3 Carsten Dominik carsten.domi...@gmail.com:
 OK, I see now the problem, and I have fixed it.


Thanks very much !

-- 
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] [BUG] Bad handling of \ in link names

[Nicolas Girard]

2009/12/3 Nick Dokos nicholas.do...@hp.com:
 Nicolas Girard nicolas.gir...@nerim.net wrote:

 hi all,
 as title says, a link such as
   [[http://www.somewhere.org][\maketitle]]
 is badly handled.

 In what way?


By the LaTeX exporter.
It gets translated into
  \href{http://www.somewhere.org}{\maketitle}
whereas I'd have expected
  \href{http://www.somewhere.org}{\\maketitle}

-- 
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Re: [BUG] LaTeX exporter should honor empty lines

[Nicolas Girard]

2009/12/2 Carsten Dominik carsten.domi...@gmail.com:
 Hi Nicolas,

 the behavior eems to be correct to me.  C1 is indented, therefore part of
 B1.


Hi Carsten,
agreed for C1, I was getting tired yesterday night ; but that was not my point.

My point was, in the following two examples, the empty lines right
before C should be preserved in the LaTeX output.

Cheers,
Nicolas

#===
- A2
- B2

C
#===


#===
- A3
- B3


C
#===


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Feature request: org-export-format-source-code-or-example and srcname

[Nicolas Girard]

Hi,
when using the listings LaTeX package, it would be very useful if the
value of srcname was added to the output. For instance,

#+srcname: my_code_chunk
#+begin_src latex :results latex :exports code :tangle no
\usepackage{fontspec,xunicode,xltxtra}
#+end_src

would give:

\lstset{language=TeX}[caption={my\_code\_chunk}]
\begin{lstlisting}
\usepackage{fontspec,xunicode,xltxtra}
\end{lstlisting}

(note the added [caption={my\_code\_chunk}])

Cheers,
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] org-babel-tangle tangles too much !

[Nicolas Girard]

Hi,
I can't get tangle to work the way I want.
Given a file f.org which contains

=
#+srcname: a
#+begin_src emacs-lisp
(a)
#+end_src

#+srcname: b
#+begin_src emacs-lisp
a
(b)
#+end_src
=

I would like (a) to appear only once in the tangled file f.el.
All I could get is, that either (a) appears twice (default behaviour),
or (a) doesn't appear at all when I append :tangle no to #+srcname:
a.

Any thoughts ?

-- 
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: org-babel-tangle tangles too much !

[Nicolas Girard]

On Tue, 01 Dec 2009 05:43:38 -1000, Thomas S. Dye wrote :

 Your code snippet doesn't tangle at all here.  Perhaps you have a
 setting somewhere that has an effect on tangling?


I'm intending my file (username.org) to be processed by Eric's
emacs-starter-kit during init (via org-babel-load-file I guess).

As none of the other starter-kit.org seemed to bother with :tangle
yes I didn't either.

On Tue, 01 Dec 2009 11:26:28 -0500, Dan Davison wrote :

 Note that all header arguments (including :tangle) get appended to
 the #+begin_src line and *not* to the #+srcname line, although it is
 an easy mistake to make.

Sure, I've been mistaken while posting my message but havent when
performing my tests. You're right that it's quite error prone.

On Tue, 01 Dec 2009 08:53:37 -0700, Eric Schulte wrote :
 #+srcname: b
 #+begin_src emacs-lisp :noweb no

I'm afraid I don't understand the meaning of the noweb option here,
or elsewhere in threads about org-babel. On [1] it can be read that
the org-babel-tangle function (...) makes use of Noweb reference
syntax for tangling of code files ; what it means to me is that
org-babel-tangle borrowed noweb's syntax but is completely independant
from it, am I wrong ?

[1] http://orgmode.org/worg/org-contrib/babel/org-babel.php#literate-programming

 If you can make a good case for why the behavior you describe should be
 supported then we could try to add it behind something like a
 (...)
 header argument, but at first blush the option seems to present too much
 opportunity for confusion.  Maybe I'm missing something.

I for sure must also be missing something ; hopefully the following
example will get things clarified to both of us:

Using your emacs-starter-kit, here's an excerpt of how I would like my
username.org to look like:

# begin username.org
* Publishing

** Default headers and document class

As for the default headers, the associated variable is
=org-export-latex-classes=. I choose to change its contents rather
than appending to it
#
#+begin_src emacs-lisp
(setq org-export-latex-classes '(
 org-export-memoir
 org-export-scrartcl
))
#+end_src

*** Configuration for the =memoir= class

#+srcname: org-export-memoir
#+begin_src emacs-lisp
  (memoir
  latex_header_memoir
  latex_header_sections)
#+end_src

#+srcname: latex_header_memoir
#+begin_src emacs-lisp
  \\documentclass[article,a4paper]{memoir}
  latex_header_common
  memoir_correct_article
  memoir_bug_chapapp
#+end_src

=memoir='s article option do not behave correctly with sections. Let's
correct this:
#
#+srcname: memoir_correct_article
#+begin_src emacs-lisp
\\let\\subsubsection\\subsection
\\let\\subsection\\section
\\let\\section\\chapter
#+end_src
#
#+srcname: memoir_bug_chapapp
#+begin_src emacs-lisp
\\makeatletter
\\renewcommand...@chapapp}{}
\\makeatother
#+end_src

*** Configuration for the =scrartcl= class

I've been using =memoir= for quite a long time ; but =scrartcl= is now
my default class
#
#+begin_src emacs-lisp
(setq org-export-latex-default-class article)
#+end_src
#
#+srcname: org-export-scrartcl
#+begin_src emacs-lisp
(article
\\documentclass{scrartcl}
latex_header_common

latex_header_sections
)
#+end_src

*** Common configuration

#+srcname: latex_header_common
#+begin_src emacs-lisp
\\usepackage{tikz}
\\RequirePackage{graphicx}
\\DeclareGraphicsExtensions{.pdf,.png,.jpg,.ps,.eps}
\\RequirePackage[T1]{fontenc}
header_common_lang
header_common_xelatex
header_common_fonts
#+end_src

(... and so on)
# end username.org

I expect both

- C-c C-e p to export username.org to username.pdf (this works
  already), and

- org-babel-tangle to generate a proper username.el (broken yet
  because code chunks get written twice).

Is my example clear enough ?

Cheers,
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: [babel] org-babel-tangle tangles too much !

[Nicolas Girard]

2009/12/1, Dan Davison davi...@stats.ox.ac.uk:
 **thread participants: let's not forget to put [babel] in the subject
 (...)

 and then I evaluated this

 (org-babel-load-file /tmp/ng.org)

 (...)
 Does this help?


Hi Dan,

yes, it does, thanks !
I was using org-babel-tangle or org-babel-tangle-file, instead of
org-babel-load-file...

-- 
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] [PATCH] Suppress extra newlines around source code in LaTeX export

[Nicolas Girard]

Hi,
title says it all.

A single paragraph such as:

#===
Dura lex
#+begin_src emacs-lisp
(a)
#+end_src
sed lex
#===

should remain entire in the LaTeX export.

-- 
Nicolas
diff --git a/lisp/org-exp.el b/lisp/org-exp.el
index 7509ba8..4c4d540 100644
--- a/lisp/org-exp.el
+++ b/lisp/org-exp.el
@@ -2403,7 +2403,7 @@ INDENT was the original indentation of the block.
 	  (concat \n#+BEGIN_HTML\n (org-add-props rtn '(org-protected t)) \n#+END_HTML\n\n))
 	 ((eq backend 'latex)
 	  (setq rtn (org-export-number-lines rtn 'latex 0 0 num cont rpllbl fmt))
-	  (concat \n#+BEGIN_LaTeX\n
+	  (concat #+BEGIN_LaTeX\n
 		  (org-add-props
   (if org-export-latex-listings
   (concat
@@ -2423,7 +2423,7 @@ INDENT was the original indentation of the block.
 (concat (car org-export-latex-verbatim-wrap)
 rtn (cdr org-export-latex-verbatim-wrap)))
 			  '(org-protected t))
-		  #+END_LaTeX\n\n))
+		  #+END_LaTeX\n))
 	 ((eq backend 'ascii)
 	  ;; This is not HTML or LaTeX, so just make it an example.
 	  (setq rtn (org-export-number-lines rtn 'ascii 0 0 num cont rpllbl fmt))
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] [BUG] LaTeX exporter should honor empty lines

[Nicolas Girard]

The following test file

#===
- A0
- B0
C0

- A1
- B1

  C1

- A2
- B2

C2

- A3
- B3


C3
#===

translates into

%===
\begin{itemize}
\item B0
\end{itemize}
C0

\begin{itemize}
\item A1
\item B1

  C1
\item A2
\item B2
\end{itemize}
C2

\begin{itemize}
\item A3
\item B3
\end{itemize}
C3
%===

While the output for C0 and C1 is correct, the following is expected
for C2 and C3:

%===
\item A2
\item B2
\end{itemize}

C2

\begin{itemize}
\item A3
\item B3
\end{itemize}


C3
%===

( I tried to fix this for a while but gave up, sorry :-/ )

-- 
Nicolas


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: [BUG] LaTeX exporter should honor empty lines

[Nicolas Girard]

2009/12/1 Nicolas Girard nicolas.gir...@nerim.net:
 The following test file

 #===
 - A0
 - B0
 C0

 - A1
 - B1

  C1

 - A2
 - B2

 C2

 - A3
 - B3


 C3
 #===

 translates into

 %===
 \begin{itemize}
 \item B0
 \end{itemize}
 C0

 \begin{itemize}
 \item A1
 \item B1

  C1
 \item A2
 \item B2
 \end{itemize}
 C2


 While the output for C0 and C1 is correct

My bad, even the output for C1 is incorrect, it messes up with the
following list.


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] [PATCH] Make org-babel-tangle work when target-file is nil

[Nicolas Girard]

Hi all,

I'm glad to be back around there, it's been a while !

As the title says, the attached file makes org-babel-tangle work when
its target-file optional argument is nil.

Cheers,
Nicolas


patch
Description: Binary data
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: [PATCH] Make org-babel-tangle work when target-file is nil

[Nicolas Girard]

2009/11/29, Dan Davison davi...@stats.ox.ac.uk:
 Eric Schulte schulte.e...@gmail.com writes:

Hi guys,

indeed, thanks to your explanations, org-babel tangling code's
behaviour makes much more sense to me.

I've just discovered Eric's Literate Programming fork of
emacs-starter-kit [1] and find it pretty darn good ! I'm currently
using it along with org-babel to rework my Org setup from scratch and
it's working very well !

Btw Eric, why not activating
(if window-system (require 'org-mouse))
by deault in starter-kit-org.org ? Within emacs-starter-kit it makes
perfect sense to me.

Cheers,
Nicolas

[1] http://github.com/eschulte/emacs-starter-kit


___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Link to a local html file

[Nicolas Girard]

Hi,

how to create a link to a local html file, say, /path/to/file.html, so
that clicking on it opens the page in a browser ?

Thanks in advance,
Nicolas


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] org-follow-link-in-same-window

[Nicolas Girard]

Hi all,
when clicking on a link, I whish I could choose between
- following it in another window (the current behaviour, which I'm often
fine with, but not always);
- following it in the same window

I tried to create a new function, org-follow-link-in-same-window, and bind
it to a key.

As for the key binding, I couldn't get down-mouse-2 to work, as initially
expected. I tried the following bindings:

(add-hook 'org-load-hook
  '(lambda ()
 (define-key org-mouse-map [C-down-mouse-1]
'org-follow-link-in-same-window)
 (define-key org-mouse-map [down-mouse-2]
'org-follow-link-in-same-window)
 (define-key org-mouse-map [C-down-mouse-2]
'org-follow-link-in-same-window)
 (define-key org-mouse-map [s-down-mouse-1]
'org-follow-link-in-same-window)
 (define-key org-mouse-map [s-mouse-1]
'org-follow-link-in-same-window)))

I found none of them to work *but* the latest, [s-mouse-1].
(I'm not fond of incantations, so when emacs leaves me under the impression
that some kind of black magic is happening, I always feel a little upset.
Anyway, i'm digressing, and after all I'm fine with [s-mouse-1].)

Now, as for the function, I came to the following:

(defun org-follow-link-in-same-window (ev)
  (interactive e)
  (let ((org-display-internal-link-with-indirect-buffer t))
(save-excursion
  (set-buffer (window-buffer (posn-window (event-end ev
(select-window (posn-window (event-end ev)))
(org-open-at-mouse ev)))

which doesn't work. I mean, it does follow the link, but not in the same
window.

Could you please give me a hand on this ?

Thanks in advance,
Nicolas
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] org-follow-link-in-same-window

[Nicolas Girard]

2009/6/27 Carsten Dominik carsten.domi...@gmail.com

 On Jun 27, 2009, at 10:41 AM, Nicolas Girard wrote:

 (defun org-open-at-mouse-same-window (ev)
  Open file link or URL at mouse.
  (interactive e)
  (mouse-set-point ev)
  (if (eq major-mode 'org-agenda-mode)
  (org-agenda-copy-local-variable 'org-link-abbrev-alist-local))
  (let ((org-link-frame-setup
 '((vm . vm-visit-folder)
   (gnus . gnus)
   (file . find-file
(org-open-at-point)))

Thanks ! This works great !


 I found none of them to work *but* the latest, [s-mouse-1].

Now, I must have been mistaken because none of the bindings I tried
actually worked. I'm sure I could trigger my own function thanks to a
debugging message, but it was after a bit of trial and error, and I
can't see how.

Here's what I tried and which didn't work:


(add-hook 'org-load-hook
  '(lambda ()
 (define-key org-mouse-map [s-mouse-1] 
'org-open-at-mouse-same-window)
 (define-key org-mouse-map [s-down-mouse-1] 
'org-open-at-mouse-same-window)
 (define-key org-mode-map [(control button1)]
'org-open-at-mouse-same-window)
 (define-key org-mouse-map [C-down-mouse-1]
'org-open-at-mouse-same-window)
 (define-key org-mouse-map [C-down-mouse-2] 
'org-open-at-mouse-same-window)
))

I could only get the behaviour I want by de-defining
org-mouse-move-tree-start with the body of your
org-open-at-mouse-same-window function.

Nicolas


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] [ANN] org-icons.el

[Nicolas Girard]

2009/6/24 Carsten Dominik carsten.domi...@gmail.com

 Could you guys please first explain the


  ;; This part is buggy (sorry)

 comment in the patch?


Err... this just reflects my current lack of expressiveness in elisp...
don't make me blush :-/

What David meant was not to ask you to integrate a ready-to-go patch, but
just to ask you to have a first look at the changes need to be made to
org.el, and tell us if you'd be inclined to accept them, when they are
ready.

The changes only consists in adding more hooks to org's font locking
mechanism --- at least that's the idea ; the probability of mistakes in my
implementation is above 100%...

Nicolas
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] FR: Ability to override the header in custom stuck projects view

[Nicolas Girard]

2009/6/22 Carsten Dominik carsten.domi...@gmail.com


 On Jun 18, 2009, at 4:49 PM, Nicolas Girard wrote:

  Hi,
 stuck projects views can be used for many things beyond their initial
 purpose.
 It would be nice to be able to override the header when building a
 custom view -- currently it is set to List of stuck projects: .


 `org-agenda-overriding-header' is now also honored by the stuck project
 list.


Thanks very much !

Nicolas
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Use of display properties as a caching mechanism

[Nicolas Girard]

When hacking the org-icons stuff, I came to realize that emacs allows
to attach any set or property/value to any part of a buffer.

It seems to me like org-mode could perfectly use this as a caching mechanism.
What bout storing time-expensive informations as special properties
attached to the first '*' of a heading ?
The price to pay would be to enforce the consistency of this cache --
as with any cache, after all; as a benefit, this may boost org-mode's
performances.
What do you think ?

Nicolas


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] [ANN] org-icons.el

[Nicolas Girard]

2009/6/24 Carsten Dominik carsten.domi...@gmail.com


 On Jun 24, 2009, at 11:41 AM, Nicolas Girard wrote:

  2009/6/24 Carsten Dominik carsten.domi...@gmail.com
 Could you guys please first explain the


  ;; This part is buggy (sorry)

 comment in the patch?

 Err... this just reflects my current lack of expressiveness in elisp...
 don't make me blush :-/


 I am not complaining, no need to blush.

 The patch looks good.  It does not add any hooks though, it
 moves some of the font-lock functionality into special functions
 that will then be overwritten by the org-icons package.


Actually I tried to mimic the already existing code, e.g.
org-font-lock-add-priority-faces.



 A bit of
 a brute force approach, but it may actually be the right thing
 for this purpose.


I'm unsure it's the best approach either. I'm wondering that all these
(while (re-search-forward)) could slow things down.

I'm not sure I fully understand the font-locking code, but it seems like it
performs several -- possibly many -- regexp searches on one part of the
buffer, alternatively adding or removing text properties, right ?

I'm just wondering, could this be rewritten as one or several state
machines, that would trigger text properties addition/removal only once for
a given part of the buffer ?




 I think I can easily apply the patch - I even like the fact that
 it cleans up the font locking a bit and moves stuff into functions.

 But if this patch is preliminary, keep working on it and give me
 a more complete version when done.


Well, thanks for your support !
By the way, you didn't give your opinion on using icons yourself. Please
confess us, are you a text-only addicted kind of guy, or a flashy, glossy
icons amateur...?


Nicolas
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Test

[Nicolas Girard]

Please ignore. I can't seem to post to the mailing-list


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] [ANN] org-icons.el

[Nicolas Girard]

Hi all,

a while ago, David mentionned that at least two people from the
#org-mode IRC channel would be interested in having pretty icons in
org-mode buffers. I have to confess I'm the second one :-)

After a little experimentation, I ended up with the results shown in
these screenshots [1] [2].

The code can be found on github [3]. Currently, it is not based
on overlays, like David's linkd.el, but on display properties. It is
still unclear which of the approach is the best, but as David
offered his help and is by far more skilled in elisp than I,
hopefully these kind of implementation details will be solved
quickly and the code will become actually useable.

As for the icons, I make them from scratch using Inkscape and the
Tango [4] colour palette.

So, what do you think ? Is this a direction you'd want org-mode
to go ? Please, share your feedback  suggestions !

Also, I was thinking that putting such kind of screenshots in org-mode's
website could make us gain a little more votes...

Cheers,
Nicolas

[1] 
http://github.com/ngirard/org-icons/blob/20ab287cd6ab5a5bb3fc8dfc6524f3dd1ab29b2e/example/screenshot1.png
[2] 
http://github.com/ngirard/org-icons/blob/20ab287cd6ab5a5bb3fc8dfc6524f3dd1ab29b2e/example/screenshot2.png
[3] http://github.com/ngirard/org-icons/tree/master
[4] http://tango.freedesktop.org/Tango_Icon_Theme_Guidelines


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Documentation updates for hooks and function variables

[Nicolas Girard]

Hi,
The hooks and function variables are currently not documented in the
manual ; instead, the reader is redirected to a Worg page [1] which is
outdated.

[1] http://orgmode.org/worg/org-configs/org-hooks.php

My proposal is that such documentation takes place in the manual
(possibly also in Worg) and is kept up-to-date.

The following shell (perhaps bash-specific) code allows to do so. It
only consists in helper functions. These functions need emacsclient to
be running.

Assuming the path to org-mode source is path,
generate_doc org $path
outputs the documentation in org format, and
generate_doc texi $path
outputs the documentation in texinfo format.

Of course, this is just a usage suggestion. Feel free to adapt this
code the way you like.

Cheers,
Nicolas

-

function search_vars_in_elisp_matching () {
local path=$1
local expr=${2:--}
find ${path} -type f -name *.el|xargs grep
defvar\|defcustom|grep -- ${expr}|cut -d\( -f2|cut -d\  -f2|cut
-d\) -f1|sort|uniq
}

function source_file_for_var() {
local path=$1
local symbol=${2}
find ${path} -type f -name *.el|xargs grep
defvar\|defcustom|grep ${symbol}|cut -d\: -f1|xargs basename
}

function emacs_msg() {
local msg=$1
emacsclient -eval (message ${msg})|sed -e 's/^//' -e 's/$//'
}

function get_docstring () {
local symbol=$1
local nodoc=No documentation string.
emacs_msg (if (functionp '${symbol})
(or (documentation '${symbol}) \${nodoc}\)
(or (documentation-property '${symbol}
'variable-documentation) \${nodoc}\)
)
}

function org_visit_section(){
local level=$1
local name=$2
local stars=$(printf %${level}s ' '|tr ' ' '*')
echo ${stars} ${name}
}

function org_visit_symbol (){
local symbol=$1
local sourcefile=$2
org_visit_section 2 =${symbol}=
echo -e Defined in /${sourcefile}/
#+begin_example
$(get_docstring ${symbol})
#+end_example


}

function texi_visit_section(){
local level=$1
local name=$2
local cmd=
case ${level} in
  1) cmd=@section;;
  2) cmd=@subsection;;
  3) cmd=@subsubsection;;
esac
echo -e ${cmd} ${name}\n
}

function texi_visit_symbol (){
local symbol=$1
local sourcefile=$2
texi_visit_section 2 @code{${symbol}}
echo -e Defined in @code{${sourcefile}}

$(get_docstring ${symbol})


}

function generate_doc (){
local format=$1
local path=$2
${format}_visit_section 1 Hooks
search_vars_in_elisp_matching ${path} -hook | head -2 | while
read symbol; do
${format}_visit_symbol $symbol $(source_file_for_var . $symbol)
done
${format}_visit_section 1 Function variables
search_vars_in_elisp_matching ${path} -function | head -2 |
while read symbol; do
${format}_visit_symbol $symbol $(source_file_for_var . $symbol)
done
}


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] Re: Documentation updates for hooks and function variables

[Nicolas Girard]

2009/6/20 Nicolas Girard

 The hooks and function variables are currently not documented in the manual



${format}_visit_section 1 Function variables

should be replaced with

${format}_visit_section 1 Function variables
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] make install-info

[Nicolas Girard]

Hi,
i just noticed two things related to org-mode's info manual:

1) currently, running
make install
doesn't install an updated version of the info manual. I'd suggest to
get the install target to depend on install-info so that
installing a new version of org-mode also installs the appropriate
info manual ;

2) on my system, make install-info is broken. I have
install-info --version
install-info (GNU texinfo) 4.12

and make install-info outputs:

if [ ! -d /usr/local/share/info ]; then mkdir -p
/usr/local/share/info; else true; fi ;
cp -p doc/org /usr/local/share/info
install-info --info-file=doc/org --info-dir=/usr/local/share/info
Syntaxe : install-info [options ...] [--] nom-fichier

Options :
[...]
make: *** [install-info] Erreur 1

--
Nicolas


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] [patch] Link abbreviations : left-trim the tag

[Nicolas Girard]

Hi,
the following patch left-trims the tag in a link abbreviation ; this
allows to write
[[google: org-mode]]
for better readability.

--
Nicolas


diff --git a/lisp/org.el b/lisp/org.el
index 07d790f..8aef3c7 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -6830,7 +6830,7 @@ call CMD.

 (defun org-link-expand-abbrev (link)
   Apply replacements as defined in `org-link-abbrev-alist.
-  (if (string-match ^\\([a-zA-Z][-_a-zA-Z0-9]*\\)\\(::?\\(.*\\)\\)?$ link)
+  (if (string-match ^\\([a-zA-Z][-_a-zA-Z0-9]*\\)\\(::?[
\t]*\\(.*\\)\\)?$ link)
   (let* ((key (match-string 1 link))
 (as (or (assoc key org-link-abbrev-alist-local)
 (assoc key org-link-abbrev-alist)))


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] org-exp-blocks: what about previewing blocks ?

[Nicolas Girard]

2009/6/18 Carsten Dominik carsten.domi...@gmail.com


 On Jun 17, 2009, at 2:40 AM, Nicolas Girard wrote:

  Hi all,

 currently the code in org-exp-blocks is intended for pre-processing only.
 It seems to me like org-mode would gain a very powerful feature, if
 blocks could also be previewed in their own buffer, using the same
 mechanism as the org-format-latex function.
 What do you think ?


 I don't see how this could be done in a general way.  I guess you mean in
 particular
 the graphics blocks like ditaa?


Yes. For any block type bt, if it makes sense, it would be possible to write
such org-block-bt-generate-image(body) that takes the block as argument
and returns the path of the image it produced.

Then:
- for exporting: the existing org-export-blocks-format-bt functions would
simply call their respective org-block-bt-generate-image and work the same
;
- for previewing a block of type bt: if such org-block-bt-generate-image
exists, call it and display it the same way org-format-latex does

Wouldn't it be great ?

Nicolas
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] FR: Ability to override the header in custom stuck projects view

[Nicolas Girard]

Hi,
stuck projects views can be used for many things beyond their initial purpose.
It would be nice to be able to override the header when building a
custom view -- currently it is set to List of stuck projects: .

Many thanks in advance,
Nicolas


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Using org-mode and git to make a wiki

[Nicolas Girard]

2009/6/17 David Libert libert.da...@gmail.com

 I only started learning about org-mode in the last few days.  I have been
 reading documentation about it and am very impressed by the system.

 I have been wondering about the possibilties if using org-mode and git to
 run an improved style of wiki.



Hi David,
what about Blorgit...?
http://orgmode.org/worg/blorgit.php

Nicolas
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

[Orgmode] #+LATEX_HEADER: does not seem to work

[Nicolas Girard]

Hi,
as title says: using the trunk version of org-mode,
I couldn't get
   #+LATEX_HEADER:
to work.

Cheers,
Nicolas


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode