[O] BABEL -- PROPERTY?
Hi, Eric. In a recent thread (Failure exporting with emacs --batch) on this list, you mentioned: #+BABEL :exports results One item to note is that the #+BABEL: syntax is now deprecated, try replacing the above line with the following. #+PROPERTY: exports results I've seen the extended discussion on this list about this change, but I haven't been able to follow the details. It seems that there were various proposals and counter proposals. Can you (or others) clarify a couple of things for me? (1) Does deprecated mean that the BABEL line will be gone from Org-mode 7.8? (2) I typically use the following BABEL line: #+BABEL: :session *R* :cache yes :results output verbatim :exports both :tangle How would I express that using the PROPERTY syntax? Thanks, -- Mike
Re: [O] New feature branch: org-xhtml-and-org-odt
Bastien b...@altern.org writes: Hi Joakim, joa...@verona.se writes: I have a project at github called inkmacs, which integrates inkscape, org-mode, and emacs: https://github.com/jave/inkmacs There I support interactive transfer of org nodes to inkscapes text nodes. My current code to extract the org nodes is not beautiful and I though maybe org-lparse improves the situation? Along with org-lparse.el, the next release will contain a proper Org parser in contrib/ -- it will do what you want. I let Nicolas publicly announce this code when he thinks it's mature enough. Interesting. Is this available in a branch somewhere? Meanwhile I'll have a look at org-lparse. Thanks, -- Joakim Verona
Re: [O] New feature branch: org-xhtml-and-org-odt
Hi Joakim, joa...@verona.se writes: Interesting. Is this available in a branch somewhere? Meanwhile I'll have a look at org-lparse. Not yet. org-lparse is a line parser, currently used for the ODT exporter, and planned to be used for the HTML exporter (which is already based on line parsing, but does not use an external parser.) The parser from Nicolas stores an Org buffer (or region) into a list, reflecting the structure of all the elements and their properties. Maybe you saw the slides I presented at the GNU Hackers meeting, I presented an sneak preview of an early prototype by Nicolas - see http://lumiere.ens.fr/~guerry/emacs-orgmode-gnu-hackers-meeting-2011.html See slide 19. HTH, -- Bastien
Re: [O] BABEL -- PROPERTY?
On 11/16/11 9:21 AM, Michael Hannon wrote: (2) I typically use the following BABEL line: #+BABEL: :session *R* :cache yes :results output verbatim :exports both :tangle How would I express that using the PROPERTY syntax? #+PROPERTY: session *R* #+PROPERTY: cache yes #+PROPERTY: results output verbatim etc. Or if you've got everything under the same (parent) heading: * Top-level heading :PROPERTIES: :session: *R* :cache: yes :results: output verbatim :exports: both :tangle: yes :END: hth, Christian
Re: [O] BABEL -- PROPERTY?
Hi Michael, Michael Hannon wrote: Hi, Eric. In a recent thread (Failure exporting with emacs --batch) on this list, you mentioned: #+BABEL :exports results One item to note is that the #+BABEL: syntax is now deprecated, try replacing the above line with the following. #+PROPERTY: exports results I've seen the extended discussion on this list about this change, but I haven't been able to follow the details. It seems that there were various proposals and counter proposals. Can you (or others) clarify a couple of things for me? (1) Does deprecated mean that the BABEL line will be gone from Org-mode 7.8? Yes. (2) I typically use the following BABEL line: #+BABEL: :session *R* :cache yes :results output verbatim :exports both :tangle How would I express that using the PROPERTY syntax? #+PROPERTY: session *R* #+PROPERTY: cache yes #+PROPERTY: results output verbatim #+PROPERTY: exports both #+PROPERTY: tangle yes Note that I added a yes value for the tangle property. That was missing from your BABEL line. Best regards, Seb -- Sebastien Vauban
Re: [O] New feature branch: org-xhtml-and-org-odt
Bastien b...@altern.org writes: Hi Joakim, joa...@verona.se writes: Interesting. Is this available in a branch somewhere? Meanwhile I'll have a look at org-lparse. Not yet. org-lparse is a line parser, currently used for the ODT exporter, and planned to be used for the HTML exporter (which is already based on line parsing, but does not use an external parser.) The parser from Nicolas stores an Org buffer (or region) into a list, reflecting the structure of all the elements and their properties. Maybe you saw the slides I presented at the GNU Hackers meeting, I presented an sneak preview of an early prototype by Nicolas - see http://lumiere.ens.fr/~guerry/emacs-orgmode-gnu-hackers-meeting-2011.html See slide 19. HTH, Yes, I saw the presentation and the idea seems nice. However it would be nice if the code could be put under public scrutiny regardless of its current state. For instance, Semantic(part of CEDET in the Emacs core) implements on the fly parse tree generators for a number of languages and it also has proof of concept support for emacs outlines, of which org is a descendant. So it would be nice to know if the org parser re-uses Semantic or if it chooses another path. If Semantic was used we could also use SRecode as a template language to implement other formats. I could certainly use it in my application. Even if the new org parser doesn't reuse the parser part of semantic, Wisent, we could probably still hook it into Semantic. Anyway, we are all busy so it would be nice to reduce wasted effort. -- Joakim Verona
[O] Org-mode latex-export minted problem
Hi,
I'm having a hard time configuring org-mode LaTeX export to work with minted
package for code listings. I put
#+LaTeX_HEADER: \usepackage{minted}
#+LaTeX_HEADER: \usemintedstyle{emacs}
in the header of my org mode file, and then
#+BEGIN_SRC haskell :exports code
some haskell code here
#+END_SRC
when I wanted to put the code listing. My .emacs has a proper minted
configuration for org-mode set, too:
; minted latex export
(setq org-export-latex-listings 'minted)
(setq org-export-latex-minted-options
'((frame lines)
(fontsize \\scriptsize)
(linenos )))
(setq org-latex-to-pdf-process
'(pdflatex -shell-escape -interaction nonstopmode %s
pdflatex -shell-escape -interaction nonstopmode %s
pdflatex -shell-escape -interaction nonstopmode %s))
but whenever I export the org-mode buffer to LaTeX, I get my listings wrapped
around \begin{lstlisting} and \end{lstlisting}.
What am I missing here?
cheers;
Piotr
--
Dept. of Computer Engineering, Bergen University College
Postboks 7030, 5020 Bergen, Norway
(+47) 55 58 75 88
http://soundandcomplete.com
Re: [O] Org-mode latex-export minted problem
Piotr Kaźmierczak p.h.kazmierc...@gmail.com writes:
Hi,
I'm having a hard time configuring org-mode LaTeX export to work with minted
package for code listings. I put
#+LaTeX_HEADER: \usepackage{minted}
#+LaTeX_HEADER: \usemintedstyle{emacs}
in the header of my org mode file, and then
#+BEGIN_SRC haskell :exports code
some haskell code here
#+END_SRC
when I wanted to put the code listing. My .emacs has a proper minted
configuration for org-mode set, too:
; minted latex export
(setq org-export-latex-listings 'minted)
(setq org-export-latex-minted-options
'((frame lines)
(fontsize \\scriptsize)
(linenos )))
(setq org-latex-to-pdf-process
'(pdflatex -shell-escape -interaction nonstopmode %s
pdflatex -shell-escape -interaction nonstopmode %s
pdflatex -shell-escape -interaction nonstopmode %s))
Hi Piotr,
Try and narrow down the problem:
1. Start Emacs with the -q option,
2. Open test.org, which is
* Test minted export
#+begin_src emacs-lisp
;; minted latex export
(setq org-export-latex-listings 'minted
org-export-latex-minted-options
'((frame lines)
(fontsize \\scriptsize)
(linenos )))
#+end_src
3. Evaluate the emacs-lisp block in test.org
4. Press C-c C-e L
With me, this outputs the src block correctly, namely as
\begin{minted}[frame=lines,fontsize=\scriptsize,linenos]{common-lisp}
; minted latex export
(setq org-export-latex-listings 'minted
org-export-latex-minted-options
'((frame lines)
(fontsize \\scriptsize)
(linenos )))
\end{minted}
If you get the same output, something else in your .emacs or custom.el
or so must play you parts, if not, you may have to check your org mode
version.
Regards, Niels.
--
http://pft.github.com/
[O] Tags grouping
Hello! I just looked at http://lumiere.ens.fr/~guerry/emacs-orgmode-gnu-hackers-meeting-2011.html and wanted to express my excitement about the suggested tags grouping-future improvement! Just out of curiosity, what is the intended functionality? Should groups be able to be groups of groups? Is there any thought of a kind of n-depth search through these tags? i.e. given the following tags: #+TAGS: contexts: home work town. #+TAGS: work: project_A project_B. would a search for the tag contexts return the headings with that tag, return the headings of all the tags in the contexts group or would it return all the tags at n depths? This gives reason for some interesting thoughts i.m.o Regards Gustav
Re: [O] BABEL -- PROPERTY?
Sebastien Vauban wxhgmqzgw...@spammotel.com wrote: (1) Does deprecated mean that the BABEL line will be gone from Org-mode= 7.8? Yes. AFAIK, if you are pulling from the git repo, it's already gone: it's been gone since Oct. 20 or so. Nick
[O] Question regarding remote references in tables
Hi, I'm trying to copy the values of a column in one table to another table in. If I understand the manual correctly, this should be possible with remote references. But I can't get it to work. In the example below, if I evaluate the table formula, column 2 of table bar is copied into column 3. Cheers, Viktor * Source table #+TBLNAME: foo | Query | Time | |---+--| | 1 | 123 | | 2 | 234 | | 3 | 345 | * Reference table #+TBLNAME: bar | Query | Garbage | Old Time | |---+-+--| | 1 | a | | | 2 | b | | | 3 | c | | #+TBLFM: $3=remote(foo,$2) * Expected | Query | Garbage | Old Time | |---+-+--| | 1 | a | 123 | | 2 | b | 234 | | 3 | c | 345 | * Produced | Query | Garbage | Old Time | |---+-+--| | 1 | a | a| | 2 | b | b| | 3 | c | c|
Re: [O] Question regarding remote references in tables
Viktor Rosenfeld listuse...@googlemail.com wrote: Hi, I'm trying to copy the values of a column in one table to another table in. If I understand the manual correctly, this should be possible with remote references. But I can't get it to work. In the example below, if I evaluate the table formula, column 2 of table bar is copied into column 3. Cheers, Viktor * Source table #+TBLNAME: foo | Query | Time | |---+--| | 1 | 123 | | 2 | 234 | | 3 | 345 | * Reference table #+TBLNAME: bar | Query | Garbage | Old Time | |---+-+--| | 1 | a | | | 2 | b | | | 3 | c | | #+TBLFM: $3=remote(foo,$2) The manual says: $3 = remote(FOO, @@#$2) copy column 2 from table FOO into column 3 of the current table and that works. Nick * Expected | Query | Garbage | Old Time | |---+-+--| | 1 | a | 123 | | 2 | b | 234 | | 3 | c | 345 | * Produced | Query | Garbage | Old Time | |---+-+--| | 1 | a | a| | 2 | b | b| | 3 | c | c|
Re: [O] Question regarding remote references in tables
Nick Dokos nicholas.do...@hp.com wrote: Viktor Rosenfeld listuse...@googlemail.com wrote: Hi, I'm trying to copy the values of a column in one table to another table in. If I understand the manual correctly, this should be possible with remote references. But I can't get it to work. In the example below, if I evaluate the table formula, column 2 of table bar is copied into column 3. Cheers, Viktor * Source table #+TBLNAME: foo | Query | Time | |---+--| | 1 | 123 | | 2 | 234 | | 3 | 345 | * Reference table #+TBLNAME: bar | Query | Garbage | Old Time | |---+-+--| | 1 | a | | | 2 | b | | | 3 | c | | #+TBLFM: $3=remote(foo,$2) The manual says: $3 = remote(FOO, @@#$2) copy column 2 from table FOO into column 3 of the current table and that works. A quick look shows (modulo mistakes) that the difference is that the second form matches org-table-range-regexp, whereas the first one does not: I'm not sure if that changed recently and/or whether it's deliberate. Nick
Re: [O] Question regarding remote references in tables
Nick Dokos wrote: The manual says: $3 = remote(FOO, @@#$2) copy column 2 from table FOO into column 3 of the current table and that works. Thank you, Nick. Wer lesen kann, ist klar im Vorteil. (Those who can read are at a clear advantage -- a German saying that is appropriate here I guess.) Cheers, Viktor
Re: [O] BABEL -- PROPERTY?
(2) I typically use the following BABEL line: #+BABEL: :session *R* :cache yes :results output verbatim :exports both :tangle How would I express that using the PROPERTY syntax? #+PROPERTY: session *R* #+PROPERTY: cache yes #+PROPERTY: results output verbatim etc. Or if you've got everything under the same (parent) heading: * Top-level heading :PROPERTIES: :session: *R* :cache: yes :results: output verbatim :exports: both :tangle: yes :END: Thanks, Christian. That seems simple enough. I had a vague recollection that there was at one time a proposal to have some kind of continuation lines for multiple properties. -- Mike
Re: [O] BABEL -- PROPERTY?
Michael Hannon jm_han...@yahoo.com writes: (2) I typically use the following BABEL line: #+BABEL: :session *R* :cache yes :results output verbatim :exports both :tangle How would I express that using the PROPERTY syntax? #+PROPERTY: session *R* #+PROPERTY: cache yes #+PROPERTY: results output verbatim etc. Or if you've got everything under the same (parent) heading: * Top-level heading :PROPERTIES: :session: *R* :cache: yes :results: output verbatim :exports: both :tangle: yes :END: Thanks, Christian. That seems simple enough. I had a vague recollection that there was at one time a proposal to have some kind of continuation lines for multiple properties. That is the case and the (now implemented) result of these discussions is best described in the commit message shown here. http://orgmode.org/w/?p=org-mode.git;a=commit;h=3af89e696a32afcc39f2e3bdb6132ac588d530ae Best -- Eric -- Mike -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] BABEL -- PROPERTY?
[...] (1) Does deprecated mean that the BABEL line will be gone from Org-mode 7.8? Yes. Hi, Seb. Thanks for confirming this. (2) I typically use the following BABEL line: #+BABEL: :session *R* :cache yes :results output verbatim :exports both :tangle How would I express that using the PROPERTY syntax? #+PROPERTY: session *R* #+PROPERTY: cache yes #+PROPERTY: results output verbatim #+PROPERTY: exports both #+PROPERTY: tangle yes Note that I added a yes value for the tangle property. That was missing from your BABEL line. Interesting. This is a digression, but in my version of Emacs (23.2.1, linux, 64-bit) if I try to copy a long line -- one that extends beyond the border of the window -- by doing, say: C-a C-SPACE C-e M-w I don't get the whole line. The copied text doesn't stop at the visible border of the window, but neither does it get all the way to the end of the line. Hence, in some of my files the BABEL line DOES include the yes in :tangle yes, but in others, where I evidently didn't pay enough attention when doing the copy, the yes is missing. Thanks again. -- Mike
Re: [O] BABEL -- PROPERTY?
(1) Does deprecated mean that the BABEL line will be gone from Org-mode= 7.8? Yes. AFAIK, if you are pulling from the git repo, it's already gone: it's been gone since Oct. 20 or so. Heh. Thanks, Nick. I AM running with a copy from the git repo, but I've been afraid to pull any fresh copies lately, for fear of breaking my set-up. (It's also true that I haven't had any compelling reason to get, or git, a new copy lately, so this behavior is perhaps not quite as stupid as it must seem.) -- Mike
Re: [O] regenerating agendas automatically if any .org files change
I think that that would also work. I will just have to disable emacs-server. On Fri, Nov 11, 2011 at 6:30 PM, Herbert Sitz hes...@gmail.com wrote: Viktor Rosenfeld listuser36 at googlemail.com writes: AFAIK, there can only be one agenda view (an expert correct me, if I'm wrong). But you can multiple blocks in the agenda. Search for Office block agenda in: http://orgmode.org/worg/org-tutorials/org-custom-agenda-commands.html Cheers, Viktor I assume an agenda view with multiple blocks would work for OP. But given his intended use could he not also just start up several independent Emacs instances on his B machine, each to show a different agenda view? -- Herb
Re: [O] BABEL -- PROPERTY?
[...] I had a vague recollection that there was at one time a proposal to have some kind of continuation lines for multiple properties. That is the case and the (now implemented) result of these discussions is best described in the commit message shown here. http://orgmode.org/w/?p=org-mode.git;a=commit;h=3af89e696a32afcc39f2e3bdb6132a Thanks, Eric. -- Mike
Re: [O] BABEL -- PROPERTY?
Hi Michael, Michael Hannon wrote: (2) I typically use the following BABEL line: #+BABEL: :session *R* :cache yes :results output verbatim :exports both :tangle How would I express that using the PROPERTY syntax? #+PROPERTY: tangle yes Note that I added a yes value for the tangle property. That was missing from your BABEL line. Interesting. This is a digression, but in my version of Emacs (23.2.1, linux, 64-bit) if I try to copy a long line -- one that extends beyond the border of the window -- by doing, say: C-a C-SPACE C-e M-w I don't get the whole line. The copied text doesn't stop at the visible border of the window, but neither does it get all the way to the end of the line. Following up your digression... I've seen the same funny root problem when doing `C-e' on long lines on my Windows Emacs (23.3, I think -- I run different versions at different moments). Indeed, `C-e' sometimes does go further than the visible screen limit, but doesn't land at the end of the physical line. I thought it could be something in my (very) long .emacs file. Thanks for showing me it's not my config that's in cause! Best regards, Seb -- Sebastien Vauban
Re: [O] BABEL -- PROPERTY?
Sebastien Vauban wxhgmqzgw...@spammotel.com wrote: Hi Michael, Michael Hannon wrote: (2) I typically use the following BABEL line: #+BABEL: :session *R* :cache yes :results output verbatim :exports both :tangle How would I express that using the PROPERTY syntax? #+PROPERTY: tangle yes Note that I added a yes value for the tangle property. That was missing from your BABEL line. Interesting. This is a digression, but in my version of Emacs (23.2.1, linux, 64-bit) if I try to copy a long line -- one that extends beyond the border of the window -- by doing, say: C-a C-SPACE C-e M-w I don't get the whole line. The copied text doesn't stop at the visible border of the window, but neither does it get all the way to the end of the line. Following up your digression... I've seen the same funny root problem when doing `C-e' on long lines on my Windows Emacs (23.3, I think -- I run different versions at different moments). Indeed, `C-e' sometimes does go further than the visible screen limit, but doesn't land at the end of the physical line. I thought it could be something in my (very) long .emacs file. Thanks for showing me it's not my config that's in cause! C-e is bound to org-end-of-line which does the stutter step when you have a wide buffer in a narrow window: it stops at the first previously invisible character[fn:1]. If you have a very wide screen (e.g. a table with a hundred columns or something like that) it might take a few steps before you get to the end of the line. But the main reason for org-end-of-line's existence is its behavior on headlines (and the setting of org-special-ctrl-a/e is very relevant). C-h f org-end-of-line RET and C-h v org-special-ctrl-a/e RET make for enlightening reading. Nick Footnotes: [fn:1] well, it's invisible if truncate-lines is t - part of the problem of describing the bahavior is the settings of all these flags. Tables look ugly if wrapped, so you probably want truncate-lines set to t anyway.
Re: [O] BABEL -- PROPERTY?
[...] C-e is bound to org-end-of-line which does the stutter step when you have a wide buffer in a narrow window: it stops at the first previously invisible character[fn:1]. If you have a very wide screen (e.g. a table with a hundred columns or something like that) it might take a few steps before you get to the end of the line. But the main reason for org-end-of-line's existence is its behavior on headlines (and the setting of org-special-ctrl-a/e is very relevant). C-h f org-end-of-line RET and C-h v org-special-ctrl-a/e RET make for enlightening reading. Thanks, Nick. It never occurred to me to check for remapping of C-e, etc. -- Mike
