Re: [O] Exporting to groff, now in org-export.el ...
Hello, Luis Anaya papoan...@hotmail.com writes: First release (?!) of the org-e-groff.el is available. I still need to do more testing but it manages to export from org. Thanks for that new back-end. The code is in the same github location, http://github.com/papoanaya/emacs_utils. I see this is based on org-e-latex.el. While this is a fast way to have a back-end running in the short term, it adds a lot of useless code (for example footnote handling is very specific and, as such, probably wrong on your back-end) and I'm not sure it will be a win in the long run. For future back-ends, I suggest to use an incremental approach, starting from scratch and adding features and transcoders step by step. Complexity can wait. Also, the way e-latex handles attributes isn't an example to follow: it uses key=value instead of :key value. If you use the latter, you can benefit from `org-export-read-attribute' function. Speaking of attributes, org-e-groff.el has to add ATTR_GROFF to both `org-element-affiliated-keywords' and `org-element-multiple-keywords'. One thing I have not managed to export are the deadlines/scheduled dates. The code to export and add the appropriate markup is completed, but that code is not running. By default, planning info are not exported. See `org-export-with-planning' variable. I am aware that there is a flag at org-export.el to control the output, but they are all t. Before I go all crazy on this, I need to ask if this is a feature to control its output or am I missing something that I should take a look. Are you talking about org-export-with-* variables? Some of them have a nil value (planning is an example). What do you want to know about them? Regards, -- Nicolas Goaziou
Re: [O] new exporter
Hello, Achim Gratz strom...@nexgo.de writes: The patch fixes things in that it will now consistently compile, but it doesn't work correctly anymore, compiled or otherwise. Ok, I misunderstood your answer: I thought you had solved the problem. I'm not sure what you intended the macroexpansion to be at the place of use, hence my suggestion to check these macros again. I will look more carefully at the `org-export-with-current-buffer-copy' macro, but, since I cannot reproduce the compilation error it may be hard to find the mistake. Regards, -- Nicolas Goaziou
Re: [O] new exporter
Nicolas Goaziou writes: Ok, I misunderstood your answer: I thought you had solved the problem. I thought that too at first, but it didn't survive closer scrutiny... I'm not sure what you intended the macroexpansion to be at the place of use, hence my suggestion to check these macros again. I will look more carefully at the `org-export-with-current-buffer-copy' macro, but, since I cannot reproduce the compilation error it may be hard to find the mistake. I gave a very detailed example of how to arrive at the error. Additionally, even if I change the order of compilation so that I don't get the error during compilation itself, the result doesn't survive the test suite since the compiled bytecode is actually wrong. I've tested this with several Emacs versions. So when you say you can't reproduce it you must be doing something quite different, would you care to explain what that is? Compiling from the edit buffer doesn't count since it is non-reproduceable by default (although if you knew what packages you've loaded it may give a hint on what is amiss). Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
Re: [O] local-set-key: Key sequence C-c SPC a starts with non-prefix key C-c SPC
@Nick thanks, that's a good question! I using orgmode started a short time ago with the configuration lines I randomly found in the internet, and since I'm also using smex http://www.emacswiki.org/Smex, I hadn't matured the need for a quicker access to the agenda. but it definitely makes more sense to make it global @Jambunathan thanks for the suggestion, very useful!
Re: [O] Exporting to groff, now in org-export.el ...
Correcting myself, Speaking of attributes, org-e-groff.el has to add ATTR_GROFF to both `org-element-affiliated-keywords' and `org-element-multiple-keywords'. Please scratch that. No need to register attr keywords anymore since last commit.
Re: [O] R and babel on Windows problem
Achim Gratz strom...@nexgo.de writes: John Hendy writes: (setq org-babel-R-command C:/Progra~1/R/R-2.15.0/bin/R) Same error. Also, curiously, =M-x customize-variable RET org-babel-R TAB= yields no results... is this the right variable? That variable doesn't seem to have acustomize interface. Might be worth a bug report. I just pushed up a change which defines the `org-babel-R-command' variable using a defcustom, so it should now be customizable. -- Eric Schulte http://cs.unm.edu/~eschulte
[O] [ANN] Beamer back-end for org-export in contrib/
Hello,
For the adventurous among you, I installed org-e-beamer.el in contrib.
Quoting file comments:
This library implements both a Beamer back-end, derived from the LaTeX
one and a minor mode easing structure edition of the document.
Depending on the desired output format, three commands are provided for
export: `org-e-beamer-export-as-latex' (temporary buffer),
`org-e-beamer-export-to-latex' (tex file) and
`org-e-beamer-export-to-pdf' (pdf file).
On top of buffer keywords supported by `e-latex' back-end (see
`org-e-latex-options-alist'), this back-end introduces the following
keywords: BEAMER_THEME, BEAMER_COLOR_THEME, BEAMER_FONT_THEME,
BEAMER_INNER_THEME and BEAMER_OUTER_THEME. All accept options in
square brackets.
Moreover, headlines now fall into three categories: sectioning elements,
frames and blocks.
- Like `e-latex' back-end sectioning elements are still set through
`org-e-latex-classes' variable.
- Headlines become frames when their level is equal to
`org-e-beamer-frame-level' (or H value in the OPTIONS line).
Though, if an headline in the current tree has a BEAMER_env (see
below) property set to frame, its level overrides the variable.
- All frames' children become block environments. Special block types
can be enforced by setting headline's BEAMER_env property to an
appropriate value (see `org-e-beamer-environments-default' for
supported value and `org-e-beamer-environments-extra' for adding
more).
- As a special case, if the BEAMER_env property is set to either
appendix, note or noteNH, the headline will become,
respectively, an appendix, a note (within frame or between frame,
depending on its level) and a note with its title ignored.
Also, an headline with an ignoreheading value will have its contents
only inserted in the output. This special value is useful to have
data between frames, or to properly close a column environment.
Along with BEAMER_env, headlines also support BEAMER_act and
BEAMER_opt properties. The former is translated as an overlay/action
specification (or a default overlay specification when enclosed within
square brackets) whereas the latter specifies options for the current
frame (fragile option is added automatically, though).
Every plain list has support for `:overlay' attribute (through
ATTR_BEAMER affiliated keyword). Also, ordered (resp. description)
lists make use of `:template' (resp. `:long-text') attribute.
Eventually, an export snippet with a value enclosed within angular
brackets put at the beginning of an element or object whose type is
among `bold', `item', `link', `radio-target' and `target' will control
its overlay specifications. As an example[fn:1],
*@@e-beamer:2-@@some emphasized text*
will be translated as
\alert2-{some emphasized text}
You can call `org-e-beamer-export-as-latex' on any document, but you may
want to add a beamer entry in `org-e-latex-classes' with:
(add-to-list 'org-e-latex-classes
'(beamer
\\documentclass\[presentation\]\{beamer\}
(\\section\{%s\} . \\section*\{%s\})
(\\subsection\{%s\} . \\subsection*\{%s\})
(\\subsubsection\{%s\} . \\subsubsection*\{%s\})))
Then use #+LATEX_CLASS: beamer in your document.
Also, on the minor changes list, syntax for BEAMER_THEME and alike is,
for example:
#+BEAMER_THEME: Rochester [height=20pt]
or,
#+BEAMER_THEME: Madrid
I've dropped the BEAMER_extra property for headlines and
`org-beamer-inherited-properties' as I wasn't sure to completely
understand their goal. I will insert them back if someone can provide
examples.
Feedback is welcome.
Regards,
[fn:1] Note that `org-export-snippet-translation-alist' can help
shortening the syntax to something like: @@b:2-@@
--
Nicolas Goaziou
[O] Custom Agenda Command - change clock/closed?
I have a custom agenda command that shows what happened today. I'd like to be able to toggle the showing of closed items on the fly. Here's my custom agenda command: (setq org-agenda-custom-commands '((7 Timeline ((agenda )) ((org-agenda-ndays 1) (org-agenda-show-log t) (org-agenda-log-mode-items '(clock closed)) (org-agenda-clockreport-mode t) (org-agenda-entry-types '()) However, when I run this agenda view, and I set the value org-agenda-log-mode-items '(clock) then I still see the closed items. Is there a way to remove the closed items on the fly with a custom agenda view, or is a custom agenda view basically set in stone once it's run? Thanks, --Nate
Re: [O] [ANN] Beamer back-end for org-export in contrib/
Hi Nicolas,
On Sat, Jun 30, 2012 at 4:59 PM, Nicolas Goaziou n.goaz...@gmail.com wrote:
Hello,
[...]
- Headlines become frames when their level is equal to
`org-e-beamer-frame-level' (or H value in the OPTIONS line).
Though, if an headline in the current tree has a BEAMER_env (see
below) property set to frame, its level overrides the variable.
The sectioning works wonderfully!
[...]
On top of buffer keywords supported by `e-latex' back-end (see
`org-e-latex-options-alist'), this back-end introduces the following
keywords: BEAMER_THEME, BEAMER_COLOR_THEME, BEAMER_FONT_THEME,
BEAMER_INNER_THEME and BEAMER_OUTER_THEME. All accept options in
square brackets.
I tried a few of these out, works very well.
[...]
Along with BEAMER_env, headlines also support BEAMER_act and
BEAMER_opt properties. The former is translated as an overlay/action
specification (or a default overlay specification when enclosed within
square brackets) whereas the latter specifies options for the current
frame (fragile option is added automatically, though).
I tried a few these too, works well. I recall you saying you would add
more overlay support gradually; I would like to say it would be nice if
there is support for replace-like overlays (e.g. \only or \onslide). It
would be great if I can wrap blocks in these. To illustrate what I mean,
I can produce the above effect with the following ugly hack:
#+OPTIONS: H:2
* Section
** Frame title
Some more text
#+LATEX: \only1{%
*** Example block :B_exampleblock:
:PROPERTIES:
:BEAMER_env: exampleblock
:END:
Some example text
*** ignore:B_ignoreheading:
:PROPERTIES:
:BEAMER_env: ignoreheading
:END:
#+LATEX: }
#+LATEX: \only2{%
*** Theorem block :B_theorem:
:PROPERTIES:
:BEAMER_env: theorem
:END:
Some bla bla ∀ \mathcal{R}
*** ignore:B_ignoreheading:
:PROPERTIES:
:BEAMER_env: ignoreheading
:END:
#+LATEX: }
Every plain list has support for `:overlay' attribute (through
ATTR_BEAMER affiliated keyword). Also, ordered (resp. description)
lists make use of `:template' (resp. `:long-text') attribute.
I wasn't clear what you meant here. Could you give an example? Did you
mean I can specify overlay specification for list items with the above
mechanism? I'm not clear on the syntax here.
I have another feature request (for the distant future) with regards to
lists; I would like to put tikz nodes in list items. I have tried that
in the past with very limited success. For an example, you can look
here:
http://www.texample.net/tikz/examples/connecting-text-and-graphics/
Eventually, an export snippet with a value enclosed within angular
brackets put at the beginning of an element or object whose type is
among `bold', `item', `link', `radio-target' and `target' will control
its overlay specifications. As an example[fn:1],
*@@e-beamer:2-@@some emphasized text*
will be translated as
\alert2-{some emphasized text}
Again, this works wonderfully.
[...]
Also, on the minor changes list, syntax for BEAMER_THEME and alike is,
for example:
#+BEAMER_THEME: Rochester [height=20pt]
I presume the beamer options go like the following?
#+LATEX_CLASS_OPTIONS: [smaller,presentation]
I have a question; are subtree exports supported yet?
Great work!
Cheers,
--
Suvayu
Open source is the future. It sets us free.
[O] Bug: Bug report about html export, wrong attachments [7.8.03]
Sorry I sent the wrong files (I forgot to insert the png) here are the correct ones, as tar files export-org-ok.tgz Description: GNU Unix tar archive export-org-nook.tgz Description: GNU Unix tar archive
Re: [O] Exporting to groff, now in org-export.el ...
Hi: I see this is based on org-e-latex.el. While this is a fast way to have a back-end running in the short term, it adds a lot of useless code (for example footnote handling is very specific and, as such, probably wrong on your back-end) and I'm not sure it will be a win in the long run. True. I wanted to get something going to get the feel of the routine. I know that there is a lot of latex specific code, and I will clean it up as testing goes on. In terms of foot notes. I did adjust to the way GROFF uses them, but when I tested them nothing came out. The way it works is to insert a .FS/.FE pair on the text to be footnoted. GROFF will place the text in the footnote and automatically add the marker in the location that the .FS/.FE marks where placed. Well, it is not working... so needs to be fixed :) [chomp... good suggestions!] Speaking of attributes, org-e-groff.el has to add ATTR_GROFF to both `org-element-affiliated-keywords' and `org-element-multiple-keywords'. One thing I have not managed to export are the deadlines/scheduled dates. The code to export and add the appropriate markup is completed, but that code is not running. By default, planning info are not exported. See `org-export-with-planning' variable. I suspected that there was a variable that controlled it; but I was not sure, thanks for clarifying. Are you talking about org-export-with-* variables? Some of them have a nil value (planning is an example). What do you want to know about them? I thought that these were used to control the export of the planning information. But you already answered my question. Luis
