Re: [O] Temp files are not deleted after beamer export with source code blocks
Hello, James Harkins jamshar...@gmail.com writes: On Friday, November 8, 2013 12:21:21 AM HKT, Nicolas Goaziou wrote: Here's an update which should properly remove these files. Could you confirm it? Yes, working fine. Thanks. Applied then. Thank you for the feedback. Regards, -- Nicolas Goaziou
Re: [O] org mode and eev
Hi Eduardo, eduardoo...@gmail.com writes: I am the author of eev... Nice! I knew I had seen you around here ;-) How can I help? Your message already answered one question I had, but I have still one pending. I still know far less about org-mode than I would like to - maybe because I have been using Emacs in a very idiosyncratic way for ages 8-\ - but it seems trivial to create code blocks that can be executed by both org and eev. Here is a example - just replace each * below with a real char 15. This was my first question: '*' are not '*' so they won't interfere with org-mode. This is great. (Quick question: how do I enter such a char 15 star?) ;; 3. Now the char 15s will be displayed as red star glyphs, and the ;; code block above can be executed both with org's `C-c C-c' and with ;; eev's f8. Try to type f8 on each line below, starting on the ;; first one with the (eepitch-shell): * (eepitch-shell) * (eepitch-kill) * (eepitch-shell) #+begin_src sh rm -Rv /tmp/eev/ mkdir /tmp/eev/ cd /tmp/eev/ wget http://angg.twu.net/eev-current/eev2.tgz tar -xvzf eev2.tgz #+end_src This works great because '#' is a comment prefix for shell, so the begin_src lines won't be processed. I want to use eev with other toplevels, and so I cannot rely on this. Is it possible to tweak eepitch so that lines starting with #+begin_src and #+end_src are not sent at all? Thanks, Alan
[O] [OT] for German speaking readers: free LaTeX-Referenz
Forwarded from Dante mailing list: herbert.v...@fu-berlin.de writes: Hallo zusammen, auf einigen WEB-Seiten wird bereits für http://www.lehmanns.de/latex-referenz geworben. In Zusammenarbeit mit Lehmanns Media kann diese Referenz (32 Seiten) allen kostenlos zugeschickt werden. Sie steht auch zum Download auf der Seite zur Verfügung. Ein entsprechender Hinweis in anderen Newsgruppen/Mailinglisten/... ist ausdrücklich erwünscht. Diese Referenz wird der nächsten Ausgabe der TeXnischen Komödie beiliegen, sodass Mitglieder von DANTE e.V. sie automatisch erhalten. Diese wird gegen Ende November im Briefkasten liegen. Herbert -- Michael http://www.strey.biz
[O] Release 8.2.2
Hi all, I've just released Org 8.2.2, a bugfix release. Thanks all for your contributions! -- Bastien
Re: [O] [PATCH] [Babel] Add line number to Processing code block... message
Hi Bastien, Bastien wrote: Sebastien Vauban sva-n...@mygooglest.com writes: I thought that the rule was: Add TINYCHANGE if less than 20 (trivial) lines; otherwise, you need to assign copyright to the FSF -- and, *if you signed the FSF papers, you don't need anymore to add TINYCHANGE, whichever the length of the change.* Is this wrong now? No, that's correct, but I forgot you signed the FSF papers as you don't appear on http://orgmode.org/worg/org-contribute.html -- can you put your name there? It's already in there (since some years): I'm #113 in your list of current contributors. Best regards, Seb -- Sebastien Vauban
Re: [O] [PATCH] [Babel] Add line number to Processing code block... message
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: It's already in there (since some years): I'm #113 in your list of current contributors. Yes, indeed, sorry! (Was looking for Séb, not Seb...) -- Bastien
Re: [O] BEAMER_HEADER in `org-latex-classes'
Hello, Nicolas Goaziou wrote: Sebastien Vauban sva-n...@mygooglest.com writes: In the `org-latex-classes' documentation (and in the Org Beamer documentation), I don't see how to include or exclude lines passed through the #+BEAMER_HEADER keyword. Is there a solution for those lines? These lines are included in [EXTRA] placeholder, like LATEX_HEADER. True. Confirmed ;-) I'd then propose the attached patch for the documentation. BTW, what's the difference between #+LATEX_HEADER and #+LATEX_HEADER_EXTRA lines, if both end up under the same umbrella ([EXTRA])? Couldn't we suppress the #+LATEX_HEADER_EXTRA keyword? Best regards, Seb From 6b6e9c06e1933820a0f0a1837dc1ea3e8a090c55 Mon Sep 17 00:00:00 2001 From: Sebastien Vauban sva-n...@mygooglest.com Date: Fri, 8 Nov 2013 10:27:57 +0100 Subject: [PATCH] Add #+BEAMER_HEADER keyword line in [EXTRA] * ox-latex.el (org-latex-classes): Add BEAMER_HEADER in the documentation string. --- lisp/ox-latex.el |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el index ae78260..cf53c38 100644 --- a/lisp/ox-latex.el +++ b/lisp/ox-latex.el @@ -241,8 +241,8 @@ macro-like placeholders. [NO-DEFAULT-PACKAGES] do not include any of the default packages [PACKAGES] \\usepackage statements for packages [NO-PACKAGES] do not include the packages - [EXTRA] the stuff from #+LATEX_HEADER(_EXTRA) - [NO-EXTRA] do not include #+LATEX_HEADER(_EXTRA) stuff + [EXTRA] the stuff from #+LATEX/BEAMER_HEADER(_EXTRA) + [NO-EXTRA] do not include #+LATEX/BEAMER_HEADER(_EXTRA) stuff So a header like -- 1.7.9 -- Sebastien Vauban
Re: [O] narrowing to subtree in navi-mode
Matt Price mopto...@gmail.com writes: On Thu, Nov 7, 2013 at 4:37 PM, Thorsten Jolitz tjol...@gmail.com wrote: Matt Price mopto...@gmail.com writes: [...] I would like to keep the full tree visible in the navi-mode buffer while narrowing the original org buffer. I wonder if this is possible? In particular, I wonder if I am confronting an underlying limitation in occur-mode, on which navi-mode is based. Actually navi-mode does nothing special wrt to narrowing, and a quick search in occur-mode (replace.el) gave no match for 'narrow' or 'restriction' or so. I think this is just basic Emacs behaviour for most functions to only act on the visible parts of the buffer. I would try to (partly) achieve your goal with visibility cycling: with point in the *Navi* buffer, use BACKTAB to globally cycle the associated Org-buffer into the states OVERVIEW or CONTENTS, then move point in the *Navi* buffer to the headline your are interested in and use TAB to locally cycle this headline to state SHOW ALL. Not a perfect solution, but yields a folded Org file with only one headline unfolded, while all navi searches still act on the whole file. Let me try to explain better the effect I'm trying for. The idea behind org-writers-room is to achieve a mostly distraction-free environment for writing, but which preserves some elements of the context into which the piece you are currently writing actually fits. To this end, I was hoping to have: (a) a GUIDE window which shows the whole structure of the file (really, the buffer) on which you are working. You should be able to collapse this out to arbitrary levels. But I think it's important that the whole outline be visibleat any given moment. Obviously navi-mode is great for this. This description reminds me very much of http://www.gnu.org/software/emacs/manual/html_node/speedbar/ which I did not really use in practise, but which seems to offer a kind of explorer for Emacs and might just do what you want. (b) a MAIN window which shows *only the part of the file you are currently working on*. This could be a chapter (of your dissertation or of a novel), a section, or even a paragraph. I want to restrict the visibility of other sections because having the other text in the window will detract from the main point of this mode, which is to help the writer focus. (c) a META window which shows some set of properties that is relevant to the particular work. I think this should always include a synopsis, and other properties will be specific to the genre or individual work. It might be nice to include tags here also but that is a more ambitious goal. Ok, now I understand you goals better. Again, this reminds me very much of ECB, so you try to build a kind of IDE for writers instead of programmers. I'm thinking the way to do this would be to avoid narrowing the main org buffer at all. Instead, I should write a function based on navi-goto-occurence-other-window (or a defadvice for that function? I'm not sure which is cleaner) to which I would bind both RET and o. Somehow I never 'advise' functions, so I can't really comment on that, but this sounds like a good idea The new function would travel to the desired occurence in the main org buffer (which would be opened in window MAIN rather than in a new window), then quickly create an indirect buffer narrowed to the subtree and switch-to-buffer in the same MAIN window. again this sounds like a reasonable approach It all seems rather elaborate but it would solve my problem I htink. If you see any problems with this strategy, or a less ugly way to do the same thing, I would of course appreciate the guidance. you might want to look at ECB, speedbar and alikes if they don't offer out-of-the-box what you want. navi-mode is for very flexible and very efficient buffer navigation and exploration as well as for a kind of buffer-remote-control. It might be very well suited for you needs, but there are quite a lot of alternatives too. -- cheers, Thorsten
Re: [O] BEAMER_HEADER in `org-latex-classes'
Hello, Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: I'd then propose the attached patch for the documentation. Thank you for the patch. BTW, what's the difference between #+LATEX_HEADER and #+LATEX_HEADER_EXTRA lines, if both end up under the same umbrella ([EXTRA])? Couldn't we suppress the #+LATEX_HEADER_EXTRA keyword? According to section 12.7.2 in manual, LATEX_HEADER_EXTRA will not be loaded when previewing LaTeX snippets, unlike to LATEX_HEADER. * ox-latex.el (org-latex-classes): Add BEAMER_HEADER in the documentation string. `beamer' is a different back-end than `latex', or to put it differently, `latex' back-end is not supposed to know about `beamer'. That's why no reference to `beamer' appears in `org-latex-classes'. If documentation is needed, I think it should go in the manual, as a footnote close to the reference to BEAMER_HEADER. Regards, -- Nicolas Goaziou
Re: [O] BEAMER_HEADER in `org-latex-classes'
Hello, Nicolas Goaziou wrote: Sebastien Vauban sva-n...@mygooglest.com writes: I'd then propose the attached patch for the documentation. Thank you for the patch. BTW, what's the difference between #+LATEX_HEADER and #+LATEX_HEADER_EXTRA lines, if both end up under the same umbrella ([EXTRA])? Couldn't we suppress the #+LATEX_HEADER_EXTRA keyword? According to section 12.7.2 in manual, LATEX_HEADER_EXTRA will not be loaded when previewing LaTeX snippets, unlike to LATEX_HEADER. Shouldn't the similar principle be applied to BEAMER_HEADER, that is have a BEAMER_HEADER_EXTRA keyword as well? * ox-latex.el (org-latex-classes): Add BEAMER_HEADER in the documentation string. `beamer' is a different back-end than `latex', or to put it differently, `latex' back-end is not supposed to know about `beamer'. I understand. That's why no reference to `beamer' appears in `org-latex-classes'. Though, this is only true as long as ox-beamer is not loaded. Because ox-beamer does add beamer to `org-latex-classes' (which is right IMO). If documentation is needed, I think it should go in the manual, as a footnote close to the reference to BEAMER_HEADER. OK. Best regards, Seb -- Sebastien Vauban
Re: [O] BEAMER_HEADER in `org-latex-classes'
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: Shouldn't the similar principle be applied to BEAMER_HEADER, that is have a BEAMER_HEADER_EXTRA keyword as well? Snippets previewing calls `latex' back-end (class used in `org-format-latex-header' is article, not beamer). Therefore #+BEAMER_HEADER will not be applied to the generated document and BEAMER_HEADER_EXTRA doesn't make much sense. That's why no reference to `beamer' appears in `org-latex-classes'. Though, this is only true as long as ox-beamer is not loaded. Because ox-beamer does add beamer to `org-latex-classes' (which is right IMO). I meant that no reference appears in `org-latex-classes' docstring. Regards, -- Nicolas Goaziou
Re: [O] [PATCH] Add check for assignment to hline relative references in table formulas.
Hi Achim On Thu, Nov 7, 2013 at 8:37 PM, Achim Gratz strom...@nexgo.de wrote: I've fixed the failing test since it wasn't checking hline expressions and hence should not have relied on undocumented behaviour in the first place. I agree that testing of LHS hline ref range and testing of something else (in this case comparison) at the same time in the same ert-deftest has also disadvantages. But why did you only remove test coverage of LHS hline ref range instead of move it into a new ert-deftest? Michael
Re: [O] BEAMER_HEADER in `org-latex-classes'
Nicolas Goaziou wrote: Sebastien Vauban writes: Shouldn't the similar principle be applied to BEAMER_HEADER, that is have a BEAMER_HEADER_EXTRA keyword as well? Snippets previewing calls `latex' back-end (class used in `org-format-latex-header' is article, not beamer). Therefore #+BEAMER_HEADER will not be applied to the generated document and BEAMER_HEADER_EXTRA doesn't make much sense. Understood, now... That's why no reference to `beamer' appears in `org-latex-classes'. Though, this is only true as long as ox-beamer is not loaded. Because ox-beamer does add beamer to `org-latex-classes' (which is right IMO). I meant that no reference appears in `org-latex-classes' docstring. Clear. Thanks. Best regards, Seb -- Sebastien Vauban
Re: [O] org mode and eev
On Fri, Nov 8, 2013 at 6:29 AM, Alan Schmitt alan.schm...@polytechnique.org wrote: Hi Eduardo, eduardoo...@gmail.com writes: I am the author of eev... Nice! I knew I had seen you around here ;-) How can I help? Your message already answered one question I had, but I have still one pending. I still know far less about org-mode than I would like to - maybe because I have been using Emacs in a very idiosyncratic way for ages 8-\ - but it seems trivial to create code blocks that can be executed by both org and eev. Here is a example - just replace each * below with a real char 15. This was my first question: '*' are not '*' so they won't interfere with org-mode. This is great. (Quick question: how do I enter such a char 15 star?) ;; 3. Now the char 15s will be displayed as red star glyphs, and the ;; code block above can be executed both with org's `C-c C-c' and with ;; eev's f8. Try to type f8 on each line below, starting on the ;; first one with the (eepitch-shell): * (eepitch-shell) * (eepitch-kill) * (eepitch-shell) #+begin_src sh rm -Rv /tmp/eev/ mkdir /tmp/eev/ cd /tmp/eev/ wget http://angg.twu.net/eev-current/eev2.tgz tar -xvzf eev2.tgz #+end_src This works great because '#' is a comment prefix for shell, so the begin_src lines won't be processed. I want to use eev with other toplevels, and so I cannot rely on this. Is it possible to tweak eepitch so that lines starting with #+begin_src and #+end_src are not sent at all? Thanks, Alan About the char 15s / red stars: I spent many years inserting them all by hand with C-q C-o... Now there is an easier way to create what I call eepitch blocks, which are the things like these: * (eepitch-foobar) * (eepitch-kill) * (eepitch-foobar) The easier way is to create an eepitch block for foobar as above is to type foobar in a line and then type M-T (meta-shift-t). Note that all these things are explained here, (find-eepitch-intro) http://angg.twu.net/eev-intros/find-eepitch-intro.html and that we should definitely create a sandboxed tutorial like that for using eev with Org... I'm saying we just because I'll need help with (at least) some details! About ignoring the #+ lines: this can be done by changing eepitch-comment-regexp, but there a default way that already works, which is to skip the #+ lines with down instead of typing f8 on them... Cheers! Eduardo
[O] Bug: Is radio tables broken?
I tried to use the LaTeX radio tables that I included in a file that I set up a year ago. When point was in the first cell of the table, C-c C-c gave C-c C-c can do nothing useful at this location. I copied the LaTeX radio table (section A.6.2) from the manual into a scratch.org file, put the point in the first cell, C-c C-c 'd with the same result. Out of curiosity I changed one of the Days number for January, C-c C-c'd the TBLFM: and again the same message. Is there a bug or what am I missing in the manual? Charlie Millar
Re: [O] Bug: Is radio tables broken?
On 11/8/2013 10:24 AM, Charles Millar wrote: I tried to use the LaTeX radio tables that I included in a file that I set up a year ago. When point was in the first cell of the table, C-c C-c gave C-c C-c can do nothing useful at this location. I copied the LaTeX radio table (section A.6.2) from the manual into a scratch.org file, put the point in the first cell, C-c C-c 'd with the same result. Out of curiosity I changed one of the Days number for January, C-c C-c'd the TBLFM: and again the same message. Is there a bug or what am I missing in the manual? Forgot to mention that GNU Emacs 24.3.1 (i386-mingw-nt6.0.6002) of 2013-03-17 on MARVIN Org-mode version 8.2.2 (release_8.2.2-180-g71152d @ c:/cygwin/home/owner/.elisp/org-mode/lisp/) on Windows Vista Home Premium SP2
[O] Option for special block
Hello,
I try to get the following in LaTeX:
--8---cut here---start-8---
\begin{definition}[Physiologie]
...
\end{definition}
--8---cut here---end---8---
I've tried many variants, but none outputs the optional parameter (in square
brackets).
--8---cut here---start-8---
#+begin_definition [Physiologie]
...
#+end_definition
#+begin_definition :options [Physiologie]
...
#+end_definition
#+begin_definition :options {Physiologie}
...
#+end_definition
--8---cut here---end---8---
Am I missing something?
Best regards,
Seb
--
Sebastien Vauban
Re: [O] Option for special block
Hello,
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org
writes:
Hello,
I try to get the following in LaTeX:
\begin{definition}[Physiologie] ... \end{definition}
I've tried many variants, but none outputs the optional parameter (in square
brackets).
#+attr_latex: :options [Physiologie]
#+begin_definition
...
#+end_definition
Regards,
--
Nicolas Goaziou
[O] makefile target: update to latest release?
Hi all, before attemting to implement the script I was wondering if there exists a makefile target that updates the repository to the latest release? I was thinking something along the lines of: current=... # determine the current version git checkout master git pull origin master latest=... # determine latest release from git log git log --oneline $current...$latest git checkout --branch $latest $latest make clean autoloads I looked at `mk/targets.mk` but didn't find anything similar. Kind regards, Miro
[O] Fwd: set global visibility set to CONTENTS in a defun?
sorry, forgot to cc to group. -- Forwarded message -- From: Matt Price mopto...@gmail.com Date: Fri, Nov 8, 2013 at 2:30 PM Subject: Re: set global visibility set to CONTENTS in a defun? To: Bastien b...@gnu.org Hi Bastien, ... sorry for hte delay on this, I have changed my code so many times and so fruitlessly that I stilll don't have a good example to point you to, On Mon, Nov 4, 2013 at 6:21 AM, Bastien b...@gnu.org wrote: Hi Matt, Matt Price mopto...@gmail.com writes: I am sure it's possible to do this ,but I can't seem to figure out how to set the global visibility level of org headings to a pre-specified level in a list function. (org-global-cycle) cycles the visibility among OVERVIEW -- CONTENTS -- ALL it accepts an optional argument, but whatever I put in the argument (number, string, whatever) has the effet of setting visibility to OVERVIEW, e.g.. I'm sure there's a trick I'm missing, could someone please tell me what it is? Mhh... hard to give good hints without a better idea of what your defun does -- can you share more about it? What I mostly wanted was to write an interactive defun that would switch to an org buffer and then automatically set the visibility (either the global visibility or the visibility of the active subtree) to an arbitrary desired level. org-cycle does not seem to be a reliable way to do this because you can't just pass the desired visibility level as an argument -- or at least, I an't figure out how to do this. The same is true for org-global-cycle. I'm not sure, does that clarify what I'm asking? Thanks as always for your help, Matt in my org-writers-room (git Thanks, -- Bastien
Re: [O] [ANN] Improved Flyspell check
Hello Nicolas, Nicolas Goaziou wrote: Eric Schulte schulte.e...@gmail.com writes: I've been using this since it was sent, and I haven't noticed any bad behavior. Thanks for the feedback. BTW, I tried to add `org-self-insert-command' to `flyspell-delayed-commands', since `self-insert-command' belongs to `flyspell-default-delayed-commands', but I didn't notice any improvement. Does this change anything for you? Do I have to write something special for having the Org-enhanced Flyspelling? I do have some configuration which I can reduce to this: --8---cut here---start-8--- ;; Org-mode (add-to-list 'load-path ~/Public/Repositories/org-mode/testing) (add-to-list 'load-path ~/Public/Repositories/org-mode/contrib/lisp) (add-to-list 'load-path ~/Public/Repositories/org-mode/lisp) (setq ispell-dictionary francais) (setq ispell-program-name aspell) ;; enable on-the-fly spell checking (add-hook 'text-mode-hook (lambda () (flyspell-mode 1))) ;; prevent flyspell from finding mistakes in the code (add-hook 'prog-mode-hook (lambda () ;; `ispell-comments-and-strings' (flyspell-prog-mode))) --8---cut here---end---8--- Though, when opening the following Org file ... --8---cut here---start-8--- #+TITLE: ECM pour Flyspell #+Time-stamp: 2013-11-08 #+DESCRIPTION: #+KEYWORDS: #+LANGUAGE: en * Développement :PROPERTIES: :CATEGORY: Dev :END: ** DONE Engager firme de relations publiques :mail: DEADLINE: 2013-02-14 Thu :LOGBOOK: CLOCK: [2013-02-05 Tue 09:00]--[2013-02-05 Tue 10:11] = 1:11 - State TODO- STRT [2013-02-05 Tue 17:48] - State TODO- STRT [2013-08-19 Mon 15:16] :END: ** TODO Appeler Laura pour bug dans le code shell :phone: Le bout de code suivant a un problème. #+begin_src sh wher command #+end_src --8---cut here---end---8--- ... many Org keywords are still underlined (such as TITLE, KEYWORDS, PROPERTIES, LOGBOOK, and code inside #+begin/end_src). Demo at http://screencast.com/t/zRDTt99M3ey. Best regards, Seb PS- Environment: - GNU Emacs 24.3.50.1 (i686-pc-mingw32) of 2013-10-19 on LEG570 - Org-mode version 8.2.1 (release_8.2.1-202-gea797e.dirty @ ~/Public/Repositories/org-mode/lisp/) -- Sebastien Vauban
[O] documentation request for timestamps
I do not know how these are intended to behave and tests are showing inconsistent results. It might help if these explained whether timestamp, ts, and tsia up and down refer to untagged timestamps only, or all timestamps including deadline, scheduled, and closed. It might also help to explain which are the missing ones, such as closed up and down, any active regardless of whether tagged up and down, etc. Are those intended to be implemented or must they be done in user code? It might also help to explain what happens to repeaters. I am getting extremely strange results. Most recently, an untagged active timestamp showed up with scheduled above and below, as if it had been scheduled. Here is the existing documentation: === timestamp-up Sort by any timestamp, early first timestamp-down Sort by any timestamp, late first scheduled-up Sort by scheduled timestamp, early first scheduled-down Sort by scheduled timestamp, late first deadline-upSort by deadline timestamp, early first deadline-down Sort by deadline timestamp, late first ts-up Sort by active timestamp, early first ts-downSort by active timestamp, late first tsia-upSort by inactive timestamp, early first tsia-down Sort by inactive timestamp, late first === I ask because I am trying to get this result for today: ;; i want this after time-up: ;; untagged inactive down ;; closed down ;; untagged active down ;; including repeater if repeats today ;; deadline down ;; including repeater if repeats today ;; scheduled down ;; including repeater if repeats today ;; ;; all repeater types (.+ ++ +) should be extrapolated ;; to today and show if they repeat today. However, they should ;; not show tomorrow if they also repeat tomorrow. ;; ;; the extrapolated most recent repeater value should be ;; used in scheduled and deadline sorting. Thanks. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. Denmark: free Karina Hansen NOW.
Re: [O] Bug: Is radio tables broken?
Charles Millar mill...@verizon.net writes: I tried to use the LaTeX radio tables that I included in a file that I set up a year ago. When point was in the first cell of the table, C-c C-c gave C-c C-c can do nothing useful at this location. I copied the LaTeX radio table (section A.6.2) from the manual into a scratch.org file, put the point in the first cell, C-c C-c 'd with the same result. Out of curiosity I changed one of the Days number for January, C-c C-c'd the TBLFM: and again the same message. Is there a bug or what am I missing in the manual? You need to turn on orgtbl-mode as a minor mode: M-x orgtbl-mode But putting the example in an org document misses the point I think: the idea is that you have a *LaTeX document* (not an org one), but you want to be able to create a table using org syntax and to then automatically create the LaTeX table from the org table. So you add the code into your LaTeX document, turn on orgtbl-mode as a minor mode and then press C-c C-c on the ORGTBL: SEND line which turns the org table into a LaTeX table and inserts it at the spot specified with the BEGIN/END RECEIVE ORGTBL stufff. Nick
[O] Customize group, strange behaviour of group org export latex
Hello, I have a question about latex export option and its customization. If I browse the org export latex group directly after opening emacs and a .org file the list only give Option Org Export and it looks like this (observe that I have not done latex export yet: | [ ]-- Group Org Export XML | [-]-\ Group Org Export LaTeX | | |--- Option Org Latex Default Packages Alist | | |--- Option Org Latex Packages Alist | | |--- Option Org Export With Tex Macros | | |--- Option Org Export With Latex Fragments | | |--- Option Org Export Latex Default Class | | |--- Option Org Export Latex Classes | | |--- Option Org Export Latex Emphasis Alist | | |--- Option Org Export Latex Title Command | | |--- Option Org Export Latex Import Inbuffer Stuff | | |--- Option Org Export Latex Date Format | | |--- Option Org Export Latex Todo Keyword Markup | | |--- Option Org Export Latex Timestamp Markup | | |--- Option Org Export Latex Timestamp Keyword Markup | | |--- Option Org Export Latex Tables Verbatim | | |--- Option Org Export Latex Tables Centered | | |--- Option Org Export Latex Tables Column Borders | | |--- Option Org Export Latex Low Levels | | |--- Option Org Export Latex List Parameters | | |--- Option Org Export Latex Verbatim Wrap | | |--- Option Org Export Latex Listings | | |--- Option Org Export Latex Listings Langs | | |--- Option Org Export Latex Remove From Headlines | | |--- Option Org Export Latex Image Default Option | | |--- Option Org Export Latex Inline Image Extensions | | |--- Option Org Export Latex Coding System | | [-]-\ Group Org Export LaTeX | | | `--- Option Org Export Pdf Remove Logfiles | | `--- Option Org Latex To Pdf Process | [-]-\ Group Org Export LaTeX | | `--- Option Org Export Pdf Remove Logfiles | [+]-- Group Org Export ASCII However, if I do one latex export, a group of Option Org Latex Classes is added to the list, then the list looks like this: | [ ]-- Group Org Export XML | [-]-\ Group Org Export LaTeX | | |--- Option Org Latex Default Packages Alist | | |--- Option Org Latex Packages Alist | | |--- Option Org Export With Tex Macros | | |--- Option Org Export With Latex Fragments | | |--- Option Org Export Latex Default Class | | |--- Option Org Export Latex Classes | | |--- Option Org Export Latex Emphasis Alist | | |--- Option Org Export Latex Title Command | | |--- Option Org Export Latex Import Inbuffer Stuff | | |--- Option Org Export Latex Date Format | | |--- Option Org Export Latex Todo Keyword Markup | | |--- Option Org Export Latex Timestamp Markup | | |--- Option Org Export Latex Timestamp Keyword Markup | | |--- Option Org Export Latex Tables Verbatim | | |--- Option Org Export Latex Tables Centered | | |--- Option Org Export Latex Tables Column Borders | | |--- Option Org Export Latex Low Levels | | |--- Option Org Export Latex List Parameters | | |--- Option Org Export Latex Verbatim Wrap | | |--- Option Org Export Latex Listings | | |--- Option Org Export Latex Listings Langs | | |--- Option Org Export Latex Remove From Headlines | | |--- Option Org Export Latex Image Default Option | | |--- Option Org Export Latex Inline Image Extensions | | |--- Option Org Export Latex Coding System | | [+]-- Group Org Export LaTeX | | |--- Option Org Latex To Pdf Process | | |--- Option Org Latex Default Class | | |--- Option Org Latex Classes | | |--- Option Org Latex Inputenc Alist | | |--- Option Org Latex Title Command | | |--- Option Org Latex Toc Command | | |--- Option Org Latex With Hyperref | | |--- Option Org Latex Format Headline Function | | |--- Option Org Latex Footnote Separator | | |--- Option Org Latex Active Timestamp Format | | |--- Option Org Latex Inactive Timestamp Format | | |--- Option Org Latex Diary Timestamp Format | | |--- Option Org Latex Image Default Option | | |--- Option Org Latex Image Default Width | | |--- Option Org Latex Image Default Height | | |--- Option Org Latex Default Figure Position | | |--- Option Org Latex Inline Image Rules | | |--- Option Org Latex Link With Unknown Path Format | | |--- Option Org Latex Default Table Environment | | |--- Option Org Latex Default Table Mode | | |--- Option Org Latex Tables Centered | | |--- Option Org Latex Tables Booktabs | | |--- Option Org Latex Table Caption Above | | |--- Option Org Latex Table Scientific Notation | | |--- Option Org Latex Text Markup Alist | | |--- Option Org Latex Format Drawer Function | | |--- Option Org Latex Format Inlinetask Function | | |---
Re: [O] [ANN] Improved Flyspell check
Hello, Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: Nicolas Goaziou wrote: Eric Schulte schulte.eric-re5jqeeqqe8avxtiumw...@public.gmane.org writes: I've been using this since it was sent, and I haven't noticed any bad behavior. Thanks for the feedback. BTW, I tried to add `org-self-insert-command' to `flyspell-delayed-commands', since `self-insert-command' belongs to `flyspell-default-delayed-commands', but I didn't notice any improvement. Does this change anything for you? Do I have to write something special for having the Org-enhanced Flyspelling? You don't need anything special once the patch is applied (on master branch). You may need to reload Org or restart Flyspell, though. Regards, -- Nicolas Goaziou
Re: [O] Bug: Is radio tables broken?
Nick On 11/8/2013 3:56 PM, Nick Dokos wrote: Charles Millar mill...@verizon.net writes: I tried to use the LaTeX radio tables that I included in a file that I set up a year ago. When point was in the first cell of the table, C-c C-c gave C-c C-c can do nothing useful at this location. I copied the LaTeX radio table (section A.6.2) from the manual into a scratch.org file, put the point in the first cell, C-c C-c 'd with the same result. Out of curiosity I changed one of the Days number for January, C-c C-c'd the TBLFM: and again the same message. Is there a bug or what am I missing in the manual? You need to turn on orgtbl-mode as a minor mode: M-x orgtbl-mode But putting the example in an org document misses the point I think: the idea is that you have a *LaTeX document* (not an org one), but you want to be able to create a table using org syntax and to then automatically create the LaTeX table from the org table. So you add the code into your LaTeX document, turn on orgtbl-mode as a minor mode and then press C-c C-c on the ORGTBL: SEND line which turns the org table into a LaTeX table and inserts it at the spot specified with the BEGIN/END RECEIVE ORGTBL stufff. Nick Thanks. I obviously forgot the procedure. I used org mode for the entire file. When it came time to use the radio tables I would M-x tex-mode and then M-x orgtbl-mode and proceeded from there. Charlie
Re: [O] makefile target: update to latest release?
Hi Miro, before attemting to implement the script I was wondering if there exists a makefile target that updates the repository to the latest release? You may want to take a look at http://orgmode.org/worg/dev/org-build-system.html in particular the targets under Compatibility and Convenience. Best, Josiah
[O] Help using ECB with Org!
Hello, Does anyone out there use ECB with org-mode buffers? On Thorsten's suggestion, I am trying out ECB (I had thought about this earlier but gave up when ecb wouldn't load -- turned out I had dead symlinks from 2009 in /usr/share/emacs/lisp/cedet/ !) with org-mode buffers. ECB is clearly very powerful and I can see it wil lbe very useful to me, but I'm not yet sure that it is the solution I am looking for with my org-writers-room. ECB defines a series of tree-buffer windows, by default on the left-hand sid. I want to customize theleft-hand display so it shows only (1) a guide window -- this will show all the org-mode headings in the main org buffer. This is provided by default in the methods window (which could use some improved fontifiation but is otherwise gerat) (2) a narrowed main window that shows only the subtree one is working on (3) a metadata window whih shows only the PROPERTIES drawer of the urrent subtree. This should be an indirect buffer narrowed to the inside of hte PROPERTIES drawer and probably with some special feature, like making the property names read-only, giving some keybindings to move to previous and next properties,possibly doing some fancier stuff with fontification. ECB works great for 1, but I am running into problems with 2 and 3. (2) -- narrowing. By default ecb allows the user to right-click on a heading in the Methods window and choose jump to tag and narrow. However, when I choose this (using either an org buffer or a lisp buffer) the buffer doesn't actually narrow. Has anyone else noticed this issue? (3) metadata. To make this work I will have to write my own ecb window functions (essentially, I will want the new netadata window to display the narrowed indirect buffer mentioned above). The ECB documentqtion is OK but it doesn't really say how to make this work. Has anyone tried it, or can anyone point me to some good example codes? Thank you! Matt
Re: [O] [ANN] Improved Flyspell check
Hello, Nicolas Goaziou wrote: Sebastien Vauban writes: Nicolas Goaziou wrote: Eric Schulte schulte.e...@gmail.com writes: I've been using this since it was sent, and I haven't noticed any bad behavior. Thanks for the feedback. BTW, I tried to add `org-self-insert-command' to `flyspell-delayed-commands', since `self-insert-command' belongs to `flyspell-default-delayed-commands', but I didn't notice any improvement. Does this change anything for you? Do I have to write something special for having the Org-enhanced Flyspelling? You don't need anything special once the patch is applied (on master branch). You may need to reload Org or restart Flyspell, though. You mean it isn't applied yet? Because I already reloaded Emacs a ton of times today -- for different tests. Best regards, Seb -- Sebastien Vauban
Re: [O] [ANN] Improved Flyspell check
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: You mean it isn't applied yet? Because I already reloaded Emacs a ton of times today -- for different tests. No it isn't applied yet. Meanwhile, you can test it by applying the second patch in this thread. Regards, -- Nicolas Goaziou
[O] Guess correct dictionary for Ispell
Hello, In case that can be useful for someone, here is how I detect which dictionary to use on a file basis: --8---cut here---start-8--- (defun my-org-switch-language () Switch language if a `#+LANGUAGE:' Org meta-tag is on top 8 lines. (save-excursion (goto-line (1+ 8)) (let (lang (dico-alist '((fr . francais) (en . american (when (re-search-backward #\\+LANGUAGE: +\\([[:alpha:]_]*\\) 1 t) (setq lang (match-string 1)) (ispell-change-dictionary (cdr (assoc lang dico-alist))) (add-hook 'org-mode-hook 'my-org-switch-language) --8---cut here---end---8--- Best regards, Seb -- Sebastien Vauban
Re: [O] freemind export?
Deas Jambunathan, I found the bug: Windows-Emacs was missing the libxml2 library. I got the libxml2-2.7.8.-w32-bin.zip, copied the content of /bin into Emacs' /bin directory and now the formatting works. I think it would be nice to have the level 0 node (title) formatted as p style=text-align: center but that can probably done by using the style system. BTW: Freeplane messes the UTF-8 characters up when importing, that's why I use freemind. Thanks for your work, Christof 2013/11/5 Jambunathan K kjambunat...@gmail.com Christof Spitz christof.sp...@gmail.com writes: 1. could you send me the variable settings of the exporter in your . emacs? No customization at my end. emacs -Q -l ~/.emacs-minimal --8---cut here---start-8--- kjambunathan@debian-6:~$ cat .emacs-minimal (add-to-list 'load-path ~/src/org-mode/lisp/) (require 'org-loaddefs) (add-to-list 'load-path ~/src/org-mode/contrib/lisp/) (require 'ox-freemind) --8---cut here---end---8--- C-c C-e f f 2. could you send me / or point me to the latest version of ox-freemind.el that you are using? I am using whatever that comes with Org-mode right now, with only change: Do a add (require 'cl). My version: http://repo.or.cz/w/org-mode/org-kjn.git http://repo.or.cz/w/org-mode/org-kjn.git/blob_plain/01db56d04ad8842da74c358ae6e27fe8147f6808:/contrib/lisp/ox-freemind.el Org-mode version: http://orgmode.org/w/?p=org-mode.git;a=blob_plain;f=contrib/lisp/ox-freemind.el;hb=HEAD
Re: [O] Guess correct dictionary for Ispell
Aloha Seb, John Kitchin posted some code to the list a while back that uses Nicolas' parser for querying the values of keywords and other elements. I modified his code slightly to include keywords assigned in property drawers. Using this would save your code from having to re-search and presumably would remove the limitation that the tag be one of the first 8 lines of the file. I'm not sure you need this, but I've found it to be generally helpful. All the best, Tom #+name: jk-keywords #+header: :results silent #+begin_src emacs-lisp (defun jk-org-kwds () parse the buffer and return a cons list of (property . value) from lines like: #+PROPERTY: value (org-element-map (org-element-parse-buffer 'element) '(keyword node-property) (lambda (keyword) (cons (org-element-property :key keyword) (org-element-property :value keyword) (defun jk-org-kwd (KEYWORD) get the value of a KEYWORD in the form of #+KEYWORD: value (cdr (assoc KEYWORD (jk-org-kwds #+end_src #+name: test-properties #+begin_src emacs-lisp (jk-org-kwd LANGUAGE) #+end_src #+results: test-properties : en Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: Hello, In case that can be useful for someone, here is how I detect which dictionary to use on a file basis: (defun my-org-switch-language () Switch language if a `#+LANGUAGE:' Org meta-tag is on top 8 lines. (save-excursion (goto-line (1+ 8)) (let (lang (dico-alist '((fr . francais) (en . american (when (re-search-backward #\\+LANGUAGE: +\\([[:alpha:]_]*\\) 1 t) (setq lang (match-string 1)) (ispell-change-dictionary (cdr (assoc lang dico-alist))) (add-hook 'org-mode-hook 'my-org-switch-language) Best regards, Seb -- Thomas S. Dye http://www.tsdye.com
[O] org-element-property syntax (turning strings into keyword symbols)
Hi, I'm trying to write a query that will check to see if the current element has any of several properties set; the properties are defined in a defcustom so I don't know in advance which properties I'm interested in. So I have the following code which INSERTS properties: (defcustom org-writers-room-properties '((Synopsis . Put a short summary here) (Role in Book . Describe what you want this section to accomplish) (Characters . who is in this section)) alist of properties to be inserted automatically on heading creation :group 'org-writers-room :type 'alist) (defun org-wr-main-heading-hook () Adds a properties drawer populates it with several properties. Intended to be used with org-insert-heading-hook, but is also interactive. (interactive) (save-excursion (dolist (this-property org-writers-room-properties) (org-set-property (car this-property) (cdr this-property)) ) (org-flag-drawer 'nil) (select-window (window-with-name guide)) (org-cycle-hide-drawers 'all) ) ) This works fine. Now when I come back to this buffer I want to check whether any of the properties are actually there. So I am trying something like this: (let ((hasprops nil)) (dolist prop org-writers-room-properties (if (org-element-property (car prop) (org-element-at-point)) (setq hasprops t)) (if (hasprops) (etc.)) However this doesn't work because (1) the car of prop (which is in fact the property name) is not necessarily capitalized and (2) the property parameter of org-element-property is not a string, but a keyword symbol. Somehow I have to turn my string into the appropriate keyword symbol. Does anyone know how to do this? Thank you! Matt
Re: [O] libxml-parse-xml-region: Raise runtime error, don't return nil
Emacs did return a runtime error, it was simply my mistake not to have noticed it in the Message buffer. 2013/11/9 Jambunathan K kjambunat...@gmail.com Christof Christof Spitz christof.sp...@gmail.com writes: I found the bug: Windows-Emacs was missing the libxml2 library. I got the libxml2-2.7.8.-w32-bin.zip, copied the content of /bin into Emacs' /bin directory and now the formatting works. This should have been very difficult to track down. ox-freemind.el does invoke `libxml-parse-xml-region'. I think Emacs should raise a runtime error (and not return nil) if the above API is called but libxml is unavailable. ps: This bug is a good excuse to audit other such wrapper calls (if there are any) and make sure that they don't fall silently.
Re: [O] org-element-property syntax (turning strings into keyword symbols)
Hello, Matt Price mopto...@gmail.com writes: This works fine. Now when I come back to this buffer I want to check whether any of the properties are actually there. So I am trying something like this: (let ((hasprops nil)) (dolist prop org-writers-room-properties (if (org-element-property (car prop) (org-element-at-point)) (setq hasprops t)) (if (hasprops) (etc.)) However this doesn't work because (1) the car of prop (which is in fact the property name) is not necessarily capitalized and Then `upcase' the property name first. I assume you will only refer to user-defined properties so their equivalent keyword will always be in upper cases. (2) the property parameter of org-element-property is not a string, but a keyword symbol. Somehow I have to turn my string into the appropriate keyword symbol. Does anyone know how to do this? Use `intern'. For efficiency reasons, I also suggest to store `org-element-at-point' in a variable instead of computing it again each time you are looking for a property: (let ((hashprops nil) (element (org-element-at-point))) (dolist (prop org-writers-room-properties) (if (org-element-property (intern (concat : (upcase prop))) element) ...))) Regards, -- Nicolas Goaziou
