Re: [O] Problem with floating holidays
John Burns epel...@comcast.net writes: I am having problems with org-float and floating holidays, in particular the holiday of Thanksgiving, as an example. I have the following entry in my data file: * Anniversaries and Holidays #+CATEGORY: Holiday %%(org-float t 4 4) Thanksgiving I know that if I leave this in my file the agenda will show it every fourth Thursday of every month. How do I tell it that I only want it to happen in the month of November? I tried to enter the month 11 after the last 4 so that it appears as: %%(org-float t 4 4 11) Thanksgiving. This did not give me a correct result either. I have reviewed the forums and the org manual for the answer, but could not find it. My Emacs version is 23.3.1 and my Org-Mode version is 7.7. I hope that someone out there has the answer. Thanking You In Advance, John You tried the 11 at the wrong position, try %%(org-float 11 4 4) Thanksgiving Regards, Philipp
Re: [O] subtree-export limitations
Nicolas Goaziou n.goaz...@gmail.com writes: Philipp Kroos philipp.kr...@t-online.de writes: That said, I'm fine with the situation, but I'ld suggest a note in the documentation that makes this limitation to subtree-exports clear (and possibly points out the workarounds). What do you think? Sure. What should be written in that note? Where to put it? Or, better, do you want to provide a patch for that? Regards, In general, I'ld want to, yes. But now i've realized that this concerns the users of contrib/* only.. The main documentation is sufficient for the standard, I think. Are there attempts to port the documentation to the new features already? Best regards, Philipp
Re: [O] subtree-export limitations
Ok, thanks to both of you. I'll stick with the workarounds pointed out by Alan for now. Anyway, I'm still curious if it wouldn't be feasible to treat subtree-options more similar to inbuffer-options? Maybe I'll have a look at that in some spare time, though I think my understanding of the concepts might be insufficient yet. Any further clues on this topic are much appreciated therfore! Best regards, Philipp Suvayu Ali fatkasuvayu+li...@gmail.com writes: On Fri, Nov 16, 2012 at 04:45:35PM +0100, Philipp Kroos wrote: So would be any other EXPORT_OPTIONS-line. The responsible function is org-export--get-subtree-options, which builds a list of already seen keywords. The lists members are then ignored if seen again. Is there any particular reason why this is done? Since Alan gave you a workaround, I will try to answer the why. I believe the reason behind this behaviour is properties are not designed to accumulate values. I believe there is a special case treatment for certain babel uses; as I'm hazy on the details, you have to look in the archives from about a year back (my memory tells me September 2011 to December 2011). You should look for discussions involving Rainer(?) and Eric Schulte. Hope this helps.
Re: [O] subtree-export limitations
Nicolas Goaziou n.goaz...@gmail.com writes: Nicolas Goaziou n.goaz...@gmail.com writes: It might support Property+ syntax, but it looks like this is Babel-specific (no sign of such syntax in org.el, where property API is defined). I will look into it (unless you want to do it). Well, scratch that: it already support :property+: syntax. I.e. try to export subtree with: * Test export :PROPERTIES: :export_latex_header: header1 :export_latex_header+: header2 :END: Test Amazing! I didn't even know about the property+-syntax... Now that's not as good as it *could* get since the headerlines are separated by space rather than newline, but it's another very useful option for a workaround at least. After all, I think that a complete solution to this problem would break the consistency of properties, like you said, or would have to introduce yet another kind of syntax, what is clearly no option. That said, I'm fine with the situation, but I'ld suggest a note in the documentation that makes this limitation to subtree-exports clear (and possibly points out the workarounds). What do you think? Philipp
[O] subtree-export limitations
Hi,
currently the support for subtree export is somewhat limited due to the
fact that individual EXPORT_* options are allowed only once.
I.e., in the following the second latex-header-property will be ignored:
* Some subtree
:PROPERTIES:
:LATEX_CLASS: scrartcl
:EXPORT_OPTIONS: toc:nil
:EXPORT_LATEX_HEADER: \usepackage[ngerman]{babel}
:EXPORT_LATEX_HEADER: \usepackage{xcolor}
:END:
So would be any other EXPORT_OPTIONS-line. The responsible function is
org-export--get-subtree-options, which builds a list of already seen
keywords. The lists members are then ignored if seen again.
Is there any particular reason why this is done?
Sorry if this is documented or discussed somewhere already, I couldn't
find any reference that explains this behaviour.
Best regards,
Philipp
Re: [O] Bug ? LaTeX exporter does not export subsections from included files
Hi,
I tried with both the old exporter (emacs -Q) and the new.
The old one exports correctly on my side, here's the relevant part:
#+BEGIN_LaTeX
This is Bar.
\subsection{Bar 1}
\label{sec-2-1}
This is Bar's first part.
\subsection{Bar 2}
\label{sec-2-2}
And here is the second one.
#+END_LaTeX
I think the behaviour in the new exporter has been changed to a better:
The included trees are changed in depth according to the structure they
are imported to, so with the new exporter the included file should start
at level1 as well, e.g.
...
This is Bar
* Bar 1
...
This makes the files more usable on their own as well, which is a great
improvement!
I hope this assumption is correct.
Regards, Philipp
Sébastien Delafond sdelaf...@gmail.com writes:
On 2012-10-08, Sébastien Delafond sdelaf...@gmail.com wrote:
Since the update to org-mode 7.9.1-1, the LaTeX export does not work
completely anymore with included files.
No idea at all on this one ? :)
Cheers,
--Seb
Re: [O] agenda view of repeated time-ranges
William Léchelle william.leche...@ens-lyon.fr writes: Hi, On Fri, 26 Oct 2012 15:05:07 +0200, Philipp Kroos spake thus: I want some events to show up every week with start and end-time in the agenda. Is it possible to combine a time-range with a repeater? I think I tried every combination of range and repeater, but I can only get one of both to work. Hi :) Did you try 2012-10-31 Mi 15:00-17:00 +1w ? No, I didn't :) Thank you! #+begin_src org ** Weekly meeting 2012-10-31 Mi 15:00--2012-10-31 Mi 17:00 this doesn't repeat #+end_src org
[O] agenda view of repeated time-ranges
Hi, I want some events to show up every week with start and end-time in the agenda. Is it possible to combine a time-range with a repeater? I think I tried every combination of range and repeater, but I can only get one of both to work. Example: #+begin_src org ** Weekly meeting 2012-10-31 Mi 15:00--2012-10-31 Mi 17:00 this doesn't repeat ** Weekly meeting 2012-10-31 Mi 15:00 +1w--2012-10-31 Mi 17:00 +1w this neither ** Weekly meeting 2012-10-31 Mi 15:00 +1w this does, but it has no range #+end_src org Best regards, Philipp
[O] bug#12702: bug#12702: 24.2; Orgmode Refile complains Not bookmark format
Hi, Bastien b...@altern.org writes: Hi Jonathan, Jonathan Schaeffer jonathan.schaef...@univ-brest.fr writes: I'll submit a post on Archlinux forum to see if someone can reproduce this. You can also try reporting your problem to the emacs-orgmode mailing list: https://lists.gnu.org/mailman/listinfo/emacs-orgmode There are some ArchLinux Org-mode users there. I'm on Arch so I checked it with my emacs from the repositories. I can reproduce it, but I think it's unrelated to Archlinux. If I enter the org-buffer with C-x b, M-x org-mode, M-x toggle-debug-on-error shows that the error (wrong-type-argument arryp nil) goes back to org-refile-check-position in org.el. The let-form sets `file` to (nth 1 refile-pointer), which is `nil` *if* the buffer was loaded like mentioned. This value is given to find-buffer-visiting, from where file-truename eventually throws the error. If the file is visited with C-x f, `file` is set to the correct value (current directory + filename) and the refiling is correct. Best, Philipp
Re: [O] hidden-subtree-error
Hi, sorry, I missed your answer till tidying up my mailbox was due today ;) This error doesn't prevent anything from working, so I haven't looked into it much deeper yet. Anyway, last time I even forgot the obvious step to investigate my .emacs first. Now I could narrow down the reason for the message to these lines: #+BEGIN_SRC emacs-lisp (add-hook 'org-mode-hook (global-set-key (kbd ESC down) 'org-metaleft)) (add-hook 'org-mode-hook (global-set-key (kbd ESC up) 'org-metaright)) #+END_SRC These bindings are ignored if i use `local-set-key` (why?), but the file-mode-specification error still comes up. Best regards, Philipp On Tue, Sep 18, 2012 at 03:29:37PM +0200, Bastien wrote: Hi Philipp, Philipp Kroos philipp.kr...@t-online.de writes: for the following file I get the errormessage `File mode specification error: (error Hidden subtree, open with TAB or use subtree command M-S-left/right)`. * Level 1 text ** Nested Level 2 othertext Is this a user-error? I don't know how to reproduce this error -- can you give a more detailed recipe? Thanks, -- Bastien
Re: [O] hidden-subtree-error
Hi, I just pulled from master. $ emacs -Q -l minimal-init.el M-x version M-x org-version C-x C-f minimal-org.org C-x b *Messages* RET Org-mode version 7.9.2 (release_7.9.2-347-gd79227 @ /home/philipp/Lisp/elisp/org-mode/lisp/) GNU Emacs 24.2.1 (i686-pc-linux-gnu, GTK+ Version 3.4.4) of 2012-08-29 on shirley.hoetzel.info File mode specification error: (error Hidden subtree, open with TAB or use subtree command M-S-left/right) with minimal-init.el: (setq org-mode-home ~/Lisp/elisp/org-mode) (add-to-list 'load-path (concat org-mode-home /lisp)) (add-to-list 'load-path (concat org-mode-home /contrib/lisp)) (add-hook 'org-mode-hook (local-set-key (kbd ESC down) 'org-metaleft)) (add-hook 'org-mode-hook (local-set-key (kbd ESC up) 'org-metaright)) and minimal-org.org: * Head 1 ** Head 2 The same happens if I don't add the git-version to load-path, i.e., with Org-mode version 7.8.11 Thank you, Philipp On Sun, Sep 30, 2012 at 07:47:14PM +0200, Bastien wrote: Hi Philipp, Philipp Kroos philipp.kr...@t-online.de writes: sorry, I missed your answer till tidying up my mailbox was due today ;) This error doesn't prevent anything from working, so I haven't looked into it much deeper yet. Anyway, last time I even forgot the obvious step to investigate my .emacs first. Now I could narrow down the reason for the message to these lines: #+BEGIN_SRC emacs-lisp (add-hook 'org-mode-hook (global-set-key (kbd ESC down) 'org-metaleft)) (add-hook 'org-mode-hook (global-set-key (kbd ESC up) 'org-metaright)) #+END_SRC These bindings are ignored if i use `local-set-key` (why?), but the file-mode-specification error still comes up. I still cannot reproduce this error. What version of Org are you using? -- Bastien
Re: [O] hidden-subtree-error
Oh my. It's fixed... I should add a function to the hooks, right? So this works (add-hook 'org-mode-hook (lambda () (local-set-key ... as expected. Thanks, sorry :) On Sun, Sep 30, 2012 at 11:23:08PM +0200, Bastien wrote: Hi Philipp, Philipp Kroos philipp.kr...@t-online.de writes: The same happens if I don't add the git-version to load-path, i.e., with Org-mode version 7.8.11 I still cannot reproduce this. The error is only displayed when I use M-left/right on a subtree that has folded children. Maybe someone else can reproduce. -- Bastien
Re: [O] New exporter doesn't like #+LaTeX_CLASS
There's a new var, org-e-latex-classes.
Philipp
On Mon, Sep 24, 2012 at 10:46:26AM -0700, Richard Stanton wrote:
To get my favorite default sty files loaded with org mode, I have a set of
LaTeX commands defined as rhs in org-export-latex-classes. This has always
worked fine in the past, and continues to work fine with the old exporter,
but when I include the line
#+LaTeX_CLASS: rhs
And process using org-export-dispatch, not only does it not load in the
preamble I want, but it doesn't seem even to load most of the default
packages, resulting in error messages like
! Undefined control sequence.
l.6 \hypersetup
{
! LaTeX Error: Missing \begin{document}.
See the LaTeX manual or LaTeX Companion for explanation.
Type H return for immediate help.
...
By the way, this is with Org-mode version 7.9.1 (release_7.9.1-325-g2150a9 @
/Applications/Emacs.app/Contents/Resources/site-lisp/org-mode/lisp/)
Thanks.
Richard Stanton
Re: [O] Sending commits to Org
Hi, I think you're still on master when you make your changes. git maintains your *local copy* of master as 'master', whereas the original, unchanged upstream branch master is still available as 'origin/master'. You create a patch against a different branch, and since you are on 'master' which differs from 'origin/master', it works like you described. If you first create a branch on your side and switch to it before making changes, you can run format-patch against your local copy of master as well. That is, #+begin_src sh git branch local git checkout local # make your changes git commit -m Your message git format-patch master #+end_src ^^ This is also the procedure described in http://orgmode.org/worg/org-contribute.html#sec-4 under *Sending commits, and it should work fine this way. philipp On Thu, Sep 20, 2012 at 01:40:55PM +0200, Sebastien Vauban wrote: Hello, Just a Git question that puzzles me for long about how to send commits per email to Org ML? In the documentation (http://orgmode.org/worg/org-contribute.html), it's written: #+begin_src sh git commit -m Your message git format-patch master #+end_src ^^ When I follow it, there is no 0001-patch.txt file created... I must write: #+begin_src sh git format-patch origin/master #+end_src ^ for such patch files to be created. Is it a documentation bug, or some feature of my (Git) installation? Best regards, Seb -- Sebastien Vauban
[O] [PATCH] org-e-latex--collect-errors
Hi, the attached patch tries to solve two issues: - Currently, org-e-latex--collect-errors only finds errors in pdf.*latex-logs. I removed the `pdf`, cause most of the time I'm using xelatex which wouldn't match. I don't know if this is generic enough for all engines though. - Occasionally, I'm running into errors currently not matched (Like 'Runaway argument'). What about the customizable org-e-latex-known-errors introduced in the patch that would allow the user to adjust the matcher to his needs and the used engine? This also makes the code more concise. What do you think about this? (The first customizable I ever wrote, I think it's correct like this, is it?) Thanks, Philipp From 0ea78f6ffa3a53e0e07b3df6d532e48cf1b2df7c Mon Sep 17 00:00:00 2001 From: Philipp Kroos philipp.kr...@t-online.de Date: Sat, 15 Sep 2012 13:11:58 +0200 Subject: [PATCH] org-e-latex: Introduced org-e-latex-known-errors * contrib/lisp/org-e-latex.el: new customizable org-e-latex-known-errors is an alist of possible errors, taken from org-e-latex--collect-errors * contrib/lisp/org-e-latex.el (org-e-latex--collect-errors): More concise code. The previous explicit search for errors is replaced by an iteration over the alist org-e-latex-known-errors. --- contrib/lisp/org-e-latex.el | 42 ++ 1 Datei geändert, 26 Zeilen hinzugefügt(+), 16 Zeilen entfernt(-) diff --git a/contrib/lisp/org-e-latex.el b/contrib/lisp/org-e-latex.el index 458579c..2e0604f 100644 --- a/contrib/lisp/org-e-latex.el +++ b/contrib/lisp/org-e-latex.el @@ -2698,6 +2698,26 @@ Return PDF file name or an error if it couldn't be produced. pdffile)) (set-window-configuration wconfig + +(defcustom org-e-latex-known-errors + '((Reference.*?undefined . [undefined reference]) +(Citation.*?undefined . [undefined citation]) +(Undefined control sequence . [undefined control sequence]) +(^! LaTeX.*?Error . [LaTeX error]) +(^! Package.*?Error . [package error]) +(Runaway argument . Runaway argument)) + Alist of regular expressions and associated messages for the user. + The regular expressions are used to find possible errors in + the log of a latex-run. + + :group 'org-export-e-latex + :type '(repeat + (cons + (string :tag Regexp) + (string :tag Message + + + (defun org-e-latex--collect-errors (buffer) Collect some kind of errors from \pdflatex\ command output. @@ -2709,26 +2729,16 @@ none. (save-excursion (goto-char (point-max)) ;; Find final pdflatex run. - (when (re-search-backward ^[ \t]*This is pdf.*?TeX.*?Version nil t) + (when (re-search-backward ^[ \t]*This is .*?TeX.*?Version nil t) (let ((case-fold-search t) (errors )) - (when (save-excursion - (re-search-forward Reference.*?undefined nil t)) - (setq errors (concat errors [undefined reference]))) - (when (save-excursion - (re-search-forward Citation.*?undefined nil t)) - (setq errors (concat errors [undefined citation]))) - (when (save-excursion - (re-search-forward Undefined control sequence nil t)) - (setq errors (concat errors [undefined control sequence]))) - (when (save-excursion - (re-search-forward ^! LaTeX.*?Error nil t)) - (setq errors (concat errors [LaTeX error]))) - (when (save-excursion - (re-search-forward ^! Package.*?Error nil t)) - (setq errors (concat errors [package error]))) + (dolist (latex-error org-e-latex-known-errors) + (when (save-excursion + (re-search-forward (car latex-error) nil t)) + (setq errors (concat errors (cdr latex-error) (and (org-string-nw-p errors) (org-trim errors))) + (provide 'org-e-latex) ;;; org-e-latex.el ends here -- 1.7.12
Re: [O] Dumb question for beamer in org mode
I guess you can customize `org-beamer-outline-frame-title` or
`org-e-beamer-outline-frame-title`, depending on the exporter you use.
Another option, which I currently use is to rebind
`org-export-latex-title-command` or `org-e-latex-title-command` to
and typeset the titleframe manually.
Hope it helps.
On Sat, Sep 15, 2012 at 11:33:51AM +0200, Erich Neuwirth wrote:
I am writing my first presentation in org mode for beamer.
I cannot find a way of replacing the word outline
(which is used on the automatically created toc slide)
with a German word.
I am using
#+LATEX_HEADER: \usepackage[ngerman]{babel}
but m guess is that the word outline is added by org, not by LeTeX.
Can anybody help?
Re: [O] [PATCH] org-e-latex--collect-errors
Yes, you're completely right. I missed that. Should be better now, I moved the defcustom to the end of the compilation-customs-block. Thank you, Philipp On Sat, Sep 15, 2012 at 02:28:05PM +0200, Nicolas Goaziou wrote: Hello, Philipp Kroos philipp.kr...@t-online.de writes: the attached patch tries to solve two issues: - Currently, org-e-latex--collect-errors only finds errors in pdf.*latex-logs. I removed the `pdf`, cause most of the time I'm using xelatex which wouldn't match. I don't know if this is generic enough for all engines though. - Occasionally, I'm running into errors currently not matched (Like 'Runaway argument'). What about the customizable org-e-latex-known-errors introduced in the patch that would allow the user to adjust the matcher to his needs and the used engine? This also makes the code more concise. What do you think about this? (The first customizable I ever wrote, I think it's correct like this, is it?) I think this patch is good, but would you mind moving your defcustom in the appropriate section within org-e-latex.el ? Also, there are spurious blank lines in this patch. Could you remove them too? Thank you. Regards, -- Nicolas Goaziou From 493b2fa1914fff5e5eaf7875f1489e996efb92ca Mon Sep 17 00:00:00 2001 From: Philipp Kroos philipp.kr...@t-online.de Date: Sat, 15 Sep 2012 14:58:49 +0200 Subject: [PATCH] org-e-latex: Introduced org-e-latex-known-errors * contrib/lisp/org-e-latex.el: new customizable org-e-latex-known-errors is an alist of possible errors, taken from org-e-latex--collect-errors * contrib/lisp/org-e-latex.el (org-e-latex--collect-errors): More concise code. The previous explicit search for errors is replaced by an iteration over the alist org-e-latex-known-errors. --- contrib/lisp/org-e-latex.el | 36 1 Datei geändert, 20 Zeilen hinzugefügt(+), 16 Zeilen entfernt(-) diff --git a/contrib/lisp/org-e-latex.el b/contrib/lisp/org-e-latex.el index 458579c..66a4d9d 100644 --- a/contrib/lisp/org-e-latex.el +++ b/contrib/lisp/org-e-latex.el @@ -820,6 +820,21 @@ These are the .aux, .log, .out, and .toc files. :group 'org-export-e-latex :type 'boolean) +(defcustom org-e-latex-known-errors + '((Reference.*?undefined . [undefined reference]) +(Citation.*?undefined . [undefined citation]) +(Undefined control sequence . [undefined control sequence]) +(^! LaTeX.*?Error . [LaTeX error]) +(^! Package.*?Error . [package error]) +(Runaway argument . Runaway argument)) + Alist of regular expressions and associated messages for the user. + The regular expressions are used to find possible errors in + the log of a latex-run. + :group 'org-export-e-latex + :type '(repeat + (cons + (string :tag Regexp) + (string :tag Message ;;; Internal Functions @@ -2709,24 +2724,13 @@ none. (save-excursion (goto-char (point-max)) ;; Find final pdflatex run. - (when (re-search-backward ^[ \t]*This is pdf.*?TeX.*?Version nil t) + (when (re-search-backward ^[ \t]*This is .*?TeX.*?Version nil t) (let ((case-fold-search t) (errors )) - (when (save-excursion - (re-search-forward Reference.*?undefined nil t)) - (setq errors (concat errors [undefined reference]))) - (when (save-excursion - (re-search-forward Citation.*?undefined nil t)) - (setq errors (concat errors [undefined citation]))) - (when (save-excursion - (re-search-forward Undefined control sequence nil t)) - (setq errors (concat errors [undefined control sequence]))) - (when (save-excursion - (re-search-forward ^! LaTeX.*?Error nil t)) - (setq errors (concat errors [LaTeX error]))) - (when (save-excursion - (re-search-forward ^! Package.*?Error nil t)) - (setq errors (concat errors [package error]))) + (dolist (latex-error org-e-latex-known-errors) + (when (save-excursion + (re-search-forward (car latex-error) nil t)) + (setq errors (concat errors (cdr latex-error) (and (org-string-nw-p errors) (org-trim errors))) -- 1.7.12
[O] [PATCH] for an unquoted list in org-e-latex
Hi, see the patch ;) PS: Do I have to sign the fsf-formula for such patches? Sry, I'm still new to the open and free software-community, but I'm willing to help, though I can't support anything financially currently. From d4401405af9e78971b728bcc03342964de397860 Mon Sep 17 00:00:00 2001 From: Philipp Kroos philipp.kr...@t-online.de Date: Wed, 12 Sep 2012 10:45:02 +0200 Subject: [PATCH] * org-e-latex.el (org-e-latex-export-block): fixed typo '(LATEX TEX) was not quoted. TINYCHANGE --- contrib/lisp/org-e-latex.el | 2 +- 1 Datei geändert, 1 Zeile hinzugefügt(+), 1 Zeile entfernt(-) diff --git a/contrib/lisp/org-e-latex.el b/contrib/lisp/org-e-latex.el index 17bdad9..a0ca7dc 100644 --- a/contrib/lisp/org-e-latex.el +++ b/contrib/lisp/org-e-latex.el @@ -1209,7 +1209,7 @@ information. (defun org-e-latex-export-block (export-block contents info) Transcode a EXPORT-BLOCK element from Org to LaTeX. CONTENTS is nil. INFO is a plist holding contextual information. - (when (member (org-element-property :type export-block) (LATEX TEX)) + (when (member (org-element-property :type export-block) '(LATEX TEX)) (org-remove-indentation (org-element-property :value export-block -- 1.7.12
[O] hidden-subtree-error
Hi, for the following file I get the errormessage `File mode specification error: (error Hidden subtree, open with TAB or use subtree command M-S-left/right)`. * Level 1 text ** Nested Level 2 othertext Is this a user-error? I'm on the HEAD of the git-repository. With (toggle-debug-on-error) the backtrace is Debugger entered--Lisp error: (error Hidden subtree, open with TAB or use subtree command M-S-left/right) signal(error (Hidden subtree, open with TAB or use subtree command M-S-left/right)) error(Hidden subtree, open with TAB or use subtree command M-S-left/right) org-metaright() run-hooks(change-major-mode-after-body-hook text-mode-hook outline-mode-hook org-mode-hook) apply(run-hooks (change-major-mode-after-body-hook text-mode-hook outline-mode-hook org-mode-hook)) run-mode-hooks(org-mode-hook) org-mode() set-auto-mode-0(org-mode nil) set-auto-mode() normal-mode(t) after-find-file(nil t) find-file-noselect-1(#buffer test.org /tmp/test.org nil nil /tmp/test.org (300 2055)) find-file-noselect(/tmp/test.org nil nil t) find-file(/tmp/test.org t) call-interactively(find-file nil nil) Best regards, Philipp
[O] e-beamer-patch
Hi,
while trying the new e-beamer I ran into a type-error which occurs when
org-e-beamer-outline-frame-options is left at its default value `nil'.
The attached patch is a possible solution that works for me, though a
more general check in org-e-beamer--normalize-arguments may be more
appropriate (in case I'm not just missing to set a certain option
right).
Regards,
Philipp
From 9514f0b3b63659df676b72442283c8b43cfbcadb Mon Sep 17 00:00:00 2001
From: Philipp Kroos philipp.kr...@t-online.de
Date: Wed, 22 Aug 2012 14:25:20 +0200
Subject: [PATCH] e-beamer: Fix a type-error with normalize-argument
* org-e-beamer.el (org-e-beamer-template): Make sure
`org-e-beamer--normalize-argument' is not called with `nil'
when formatting the toc.
The error occured when org-e-beamer-outline-frame-options
has got no value (the default).
---
contrib/lisp/org-e-beamer.el | 6 --
1 Datei geändert, 4 Zeilen hinzugefügt(+), 2 Zeilen entfernt(-)
diff --git a/contrib/lisp/org-e-beamer.el b/contrib/lisp/org-e-beamer.el
index af5b8ff..9096531 100644
--- a/contrib/lisp/org-e-beamer.el
+++ b/contrib/lisp/org-e-beamer.el
@@ -815,8 +815,10 @@ holding export options.
(when depth
(concat
(format \\begin{frame}%s{%s}\n
- (org-e-beamer--normalize-argument
- org-e-beamer-outline-frame-options 'option)
+ (if org-e-beamer-outline-frame-options
+ (org-e-beamer--normalize-argument
+ org-e-beamer-outline-frame-options 'option)
+ )
org-e-beamer-outline-frame-title)
(when (wholenump depth)
(format \\setcounter{tocdepth}{%d}\n depth))
--
1.7.11.4
Re: [O] add entries to *emphasis-alist
It worked using customize, thanks. And thanks for the explanation, Nick. At least my approach to set the value would not work at all without an explicit call to org-set-emph-re, since it relied on the variable being already defined. It might be of minor interest, anyway, I've attached a patch-suggestion that would clearify the usage sufficiently, at least for me... Best regards, Philipp On Fri, Aug 17, 2012 at 03:50:35PM -0400, Nick Dokos wrote: Sebastien Vauban wxhgmqzgw...@spammotel.com wrote: You have to make that customization *before* loading Org in your .emacs file. Weird, never really understood why, but that's like that. The point is that the value of org-emphasis-alist (as well as the value of org-emphasis-regexp-components) is used in order to calculate the value of org-emph-re by calling the function org-set-emph-re afterwards: it's org-emph-re that's used for the all the gory calculations, not org-emphasis-alist, which just provides a nicer interface. So if you arrange to call the org-set-emph-re function afterwards, you can change org-emphasis-alist at any time. Customize makes it easy, in that it does that automatically (see the :set property of org-emphasis-alist). If you do the setq before loading org, then what happens is that when the defcustom is encountered, the value of the :set property (a function) is called: the modified value of org-emphasis-alist is then used to calculate org-emph-re, instead of the original default. If you do it after, none of that happens and it's as if you never changed it. Nick PS BTW, the docstring for the variable says: Use customize to modify this, or restart Emacs after changing it but I'm not sure that's correct: if you change the variable in one session, the value is not going to be propagated to the next session, unless you use customize or put the setq in .emacs. In the latter case, it's not going to work unless you do it the way Seb describes: set it before loading Org. So restarting emacs is *not* enough. Am I missing something? diff --git a/lisp/org.el b/lisp/org.el index 3bf338d..c70d94d 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -3770,7 +3770,9 @@ characters, the face to be used by font-lock for highlighting in Org-mode Emacs buffers, and the HTML tags to be used for this. For LaTeX export, see the variable `org-export-latex-emphasis-alist'. For DocBook export, see the variable `org-export-docbook-emphasis-alist'. -Use customize to modify this, or restart Emacs after changing it. +The value of org-emphasis-alist is used to calculate a regular expression +during startup; changing it manually may not have an effect. +You should use customize to modify this. Otherwise, see `org-set-emph-re'. :group 'org-appearance :set 'org-set-emph-re :type '(repeat
Re: [O] add entries to *emphasis-alist
Well, sorry.. Before sending the mail I read the documentation on http://orgmode.org/worg/org-contribute.html#sec-4 regarding correct submission of patches... and did it wrong. So just for the records, here it is again. Hopefully, if I can contribute a `real' patch someday, the format will be right ;) Regards, philipp On Sun, Aug 19, 2012 at 01:38:10PM +0200, Nicolas Goaziou wrote: Hello, Philipp Kroos philipp.kr...@t-online.de writes: It worked using customize, thanks. And thanks for the explanation, Nick. At least my approach to set the value would not work at all without an explicit call to org-set-emph-re, since it relied on the variable being already defined. It might be of minor interest, anyway, I've attached a patch-suggestion that would clearify the usage sufficiently, at least for me... At some point, emphasis markers will be hard-coded anyway. Though, it will be easy to change their meaning during the export process. Regards, -- Nicolas Goaziou From 6bd616854ccb981693c2178c5a9c0378cf3954aa Mon Sep 17 00:00:00 2001 From: Philipp Kroos philipp.kr...@t-online.de Date: Sun, 19 Aug 2012 14:34:56 +0200 Subject: [PATCH] Minor change of documentation * lisp/org.el org-emphasis-alist: Clearified the documentation The value is not changeable with a setq-form, the customization-interface should be used. The change describes that. TINYCHANGE --- lisp/org.el | 4 +++- 1 Datei geändert, 3 Zeilen hinzugefügt(+), 1 Zeile entfernt(-) diff --git a/lisp/org.el b/lisp/org.el index 3bf338d..c70d94d 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -3770,7 +3770,9 @@ characters, the face to be used by font-lock for highlighting in Org-mode Emacs buffers, and the HTML tags to be used for this. For LaTeX export, see the variable `org-export-latex-emphasis-alist'. For DocBook export, see the variable `org-export-docbook-emphasis-alist'. -Use customize to modify this, or restart Emacs after changing it. +The value of org-emphasis-alist is used to calculate a regular expression +during startup; changing it manually may not have an effect. +You should use customize to modify this. Otherwise, see `org-set-emph-re'. :group 'org-appearance :set 'org-set-emph-re :type '(repeat -- 1.7.11.4
[O] add entries to *emphasis-alist
Hi,
is it still possible to add items to the emphasis alists?
I'm preparing a presentation with orgmode/beamer and try to get a markup
for alert using '@'.
According to some (old..) thread
(http://lists.gnu.org/archive/html/emacs-orgmode/2010-01/msg00592.html)
I added an entry to org-emhasis-alist and
org-export-latex-emphasis-alist, see below.
Unfortunately, this is not working, '@noise@' is exported to '@noise@'
literally.
I had a quick look at the source in org-latex.el and if I understand it
correctly, the fontification is done in org-export-latex-fontify
according to matches with org-emph-re, defined in org.el. But
org-emph-re doesn't match with '@'- consequently, the markup is ignored.
So do I have to redefine org-emph-re as well or is there any other trick?
I'm using the current org from git.
Thanks all!
;; this is how I add the entries to the lists
(setq org-emphasis-alist
(append org-emphasis-alist
'((@ org-warning b /b
(setq org-export-latex-emphasis-alist
(append org-export-latex-emphasis-alist
'((@ \\alert{%s} nil
;; this is a minimal example
#+LaTeX_CLASS: beamer
#+LaTeX_CLASS_OPTIONS: [presentation]
#+BEAMER_FRAME_LEVEL: 1
* Testsection
** with some important @noise@
