Re: [O] worg latex example "11 Styling the Frontmatter"
Hi Myles,
Thanks for making me look more closely at this. There are two things:
1) #+BEGIN_abstract ... #+END_abstract requires org-special-blocks. So,
#+BEGIN_SRC emacs-lisp :exports none :results silent
(require 'org-special-blocks)
(defun org-export-latex-no-toc (depth)
(when depth
(format "%% Org-mode is exporting headings to %s levels.\n"
depth)))
(setq org-export-latex-format-toc-function 'org-export-latex-no-toc)
#+END_SRC
2) The abstract text ends up in the title because there is no export
option template at the top of your org file. With point at the start of
the buffer, C-c C-e t.
Then, if you export to LaTeX or pdf, all should be well.
I don't know about the two org versions, but have seen posts to the list
where odd behavior was caused by old installations lurking where the
newer one could see. Have you switched installation methods in the last
year or so? From what I'm able to understand, that is sometimes the
culprit.
hth,
Tom
Myles English writes:
>>> On Thu, 08 Mar 2012 09:01:01 -1000, Thomas S Dye said:
>
> > Aloha Myles, Your example works for me with emacs -q. I had to
> > change the \input{} command to \input{title}, since I'm not working
> > at /home/myles. I saved the tex file to title.tex, put it in the
> > same directory as the org file, evaluated the source block
> > (with :results silent), and exported. I got a 2 page pdf with FOO
> > on the first page and a second page with all the rest.
>
> > I'm not sure what is going wrong at your end, but suspect the
> > \input{} command might not be picking up your .tex file. Do you see
> > something in the .log file produced by LaTeX?
>
> > All the best, Tom
>
> > Myles English writes:
>
> On Thu, 08 Mar 2012 16:29:36 +, Myles English said:
> >>
> >> > Hi, I am trying to get a custom title page and abstract before
> >> the > TOC in a pdf.
> >>
> >> > Worg has an example on this page:
> >>
> >> > http://orgmode.org/worg/org-tutorials/org-latex-export.html
> >>
> >> > at the section titled "11 Styling the Frontmatter" However, the >
> >> example doesn't work for me as expected.
> >>
> >> > To reproduce:
> >>
> >> > + save the attached files (testAbs.org, title.tex) in the same >
> >> directory + open testAbs.org and do "C-c e d" to export to pdf
> >>
> >> > I would expect the Abstract and text to be shown in the final pdf
> >> > but it is absent.
> >>
> >> > If I put a character between the lines #+LATEX_HEADER >
> >> and #+BEGIN_abstract then the abstract title and text are shown as
> >> > expected.
> >>
> >> > The above is using release_7.8.03-566-gf8efc63. Am I doing >
> >> something wrong?
>
> Tom,
>
> Thanks very much for checking it. It does pick up the title.tex file
> and I don't get a log file but the testAbs.tex file (see below) shows
> that the abstract title is missing and the abstract text is entered as
> the \title{}.
>
> If I start emacs -q then execute this block, it seems to report that
> orgmode is a mixture of version 7.7 and 7.8.
>
> #+BEGIN_SRC emacs-lisp :exports none
> (add-to-list 'load-path
>"~/.emacs.d/plugins/org-mode/lisp")
> (require 'org-install)
> (org-version)
> #+END_SRC
>
> #+results:
> : Org-mode version 7.7 (release_7.8.03.566.gf8efc)
>
> Does that look normal? Exporting as before then gives the file below.
>
> Myles
>
>
> File testAbs.tex contains:
>
> % Created 2012-03-09 Fri 01:11
> \documentclass[11pt]{article}
> \usepackage[utf8]{inputenc}
> \usepackage[T1]{fontenc}
> \usepackage{fixltx2e}
> \usepackage{graphicx}
> \usepackage{longtable}
> \usepackage{float}
> \usepackage{wrapfig}
> \usepackage{soul}
> \usepackage{textcomp}
> \usepackage{marvosym}
> \usepackage{wasysym}
> \usepackage{latexsym}
> \usepackage{amssymb}
> \usepackage{hyperref}
> \tolerance=1000
> \input{title.tex}
> \providecommand{\alert}[1]{\textbf{#1}}
>
> \title{Here is my abstract, it is a fine abstract.}
> \author{}
> \date{\today}
> \hypersetup{
> pdfkeywords={},
> pdfsubject={},
> pdfcreator={Emacs Org-mode version 7.7}}
>
> \begin{document}
>
> \maketitle
>
> % Org-mode is exporting headings to 3 levels.
> \tableofcontents
> \listoftables
> \listoffigures
>
> \section{Foo}
> \label{sec-1}
>
> foo
> \section{Bar}
> \label{sec-2}
>
> bar
> \section{src}
> \label{sec-3}
>
> \end{document}
>
>
--
Thomas S. Dye
http://www.tsdye.com
Re: [O] org tables
Hi Peter, Peter Salazar writes: > Is there a way to get org to wrap text within a table cell? I want to > be able to enter long text entries into cells without expanding column > width. > > Also, is there a way to merge cells—say, three cells vertically? This question sounded familiar, so I dug up this ancient post from the list which offers some answers: http://permalink.gmane.org/gmane.emacs.orgmode/10478 The link to the manual in the email is broken. The relevant section of the manual is: 3.2 Column width and alignment (info "(org) Column width and alignment") Best, Matt
Re: [O] O[PATCH] org-export-generic table exporting
Well thank you! I apologize for the late reply, my coursework has a hold on me, but I was getting worried when no one responded immediately :-). I think the next step would be editing the configs for generic exporting to other mediums to support the tables (which HTML would be beyond trivial with the variables I included), but I am waiting for the lords of org-mode to either approve this patch or suggest changes first. Also, I have been using this modification to handle meeting minutes for my fraternity for the past month and I have not run into a hiccup yet, so http://i.imgur.com/xzfgp.jpg . On Wed, Feb 15, 2012 at 5:55 PM, Wes Hardaker wrote: > > On Tue, 7 Feb 2012 23:44:42 -0500, Tom Alexander < > tomalexan...@paphus.com> said: > > TA> I noticed that the org-export-generic.el script had options for basic > TA> features like checkboxes but not for tables, which were locked into > TA> ascii exporting. The attached patch creates many variables to allow > TA> users to change the table formatting (much like how there are > TA> variables like ":body-list-checkbox-done"). I also created a generic > TA> exporter named "mediawiki" that demonstrates use of the table > TA> exporting. > > Awesome! > > TA> This is my first post to this mailing list, and my first ever > TA> contribution to an open-source project so I look forward to feedback > TA> and be kind when you point out any sort of mailing list etiquette I > TA> might have broken. > > Well, I think you've certainly given a good first shot at a > contribution! > > [Hopefully someone with write access will apply it soon] > -- > Wes Hardaker > My Pictures: http://capturedonearth.com/ > My Thoughts: http://pontifications.hardakers.net/ > -- Tom Alexander HS - Secretary Alpha Sigma Phi; Beta Psi Chapter Rensselaer Polytechnic Institute Class of 2013
Re: [O] Bug: 3 bugs and 2 proposals on ascii/html export [7.8.03]
Hi Bastien, * Bastien wrote on 2012-03-09 at 03:09 (+0100): > Mathias Bauer writes: > > Thanks for this report -- next time, please consider sending > one mail per bug/request, it makes issues easier to track. ok, I'll do so - even for small bugs. Promised :-) > > Headlines without tags are underlined in a wrong manner. > > It's one character too long. > > It's a matter of taste. I like this additionnal character and > I think Carsten added it intentionally. Hm, yes it is. I just wondered because the strings of the title and the toc headline have a different underlining. > > --snip-- > > ...Some section with TAG at the end > class="tag">some_tag... > > --snip-- > > > > Isn't a single space enough for separating the heading's text > > and the tag? Beside their number, the additional three (why > > not five or n?) " " seem a little bit freaky to me... > > They _are_ freaky :) But they are also needed. > > Even if the tags display is taken care of by the CSS, we must > prevent collapsing the tags with the previous strings in case > the CSS is not available -- just think of what the HTML page > should look like with w3m/lynx. Thanks for your explanation. I completely missed text based browsers. And ordinary spaces are _really_ not enough for them? Concerning CSS I'm digging into the docs ... but tomorrow :-) Regards, Mathias
[O] org tables
Hey everyone, Is there a way to get org to wrap text within a table cell? I want to be able to enter long text entries into cells without expanding column width. Also, is there a way to merge cells—say, three cells vertically? Finally, orgtbl-mode is broken in markdown-mode. Does anyone know a solution? Thanks, Pater
Re: [O] org-mode as an accountability system?
Thank you all for your suggestions. I'm going to work on incorporating them into my system. I'll let you know how it turns out! On Mon, Mar 5, 2012 at 6:44 AM, Darlan Cavalcante Moreira wrote: > > Also, if you have anything in your agenda that you don't want to send to > him you can use tags to restrict what is shown in the agenda before you > copy/export it. > > -- > Darlan > > At Sun, 4 Mar 2012 14:08:40 + (UTC), > Memnon Anon wrote: > > > > Hi Peter, > > > > Peter Salazar writes: > > > > > My committed actions for a day consist of: > > > > > > a) TODOs for the projects I'm working on > > > b) random errands that need to be done that day > > > c) daily habits (e.g. meditating, exercising) > > > > > > I don't believe org-agenda can support me in doing this, because I > > > require: > > > > > > a) a way to quickly enter the random tasks for that day (without > > > having to "schedule" each one for today) > > > b) more importantly: a way to record, store, and e-mail my list of > > > which tasks I've done and not done at the end of the night > > > > I am not sure why you don't use the agenda, there really should be no > > need to compile this data manually. > > > > Flow: > > - Enter your task with capture. This *is* a quick way, and you should be > > able to setup a binding that schedules the new task to today by > > default. Put the tasks wherever they should live in your org cosmos. > > - At the beginning of the day, start your agenda for today. > > Copy and paste it, export it to html, whatever. Send it to your > > college. > > - Work through your tasks. If you can't finish a task, don't mark it > > didnotdo, but simple reschedule it for tomorrow; the change will be > > reflected in your log drawer. > > - At the end of the day, or early next day, start the agenda and use > > org-agenda-log-mode, probably with C-u. > > - `C-u l' should show you all there is, given it is properly configured: > > Task you finished, tasks you did not finish and hence rescheduled for > > later, even your sections (teaching, habits, random tasks) can be > > reflected with categories. Just copy and paste it in your email and > > you are done. > > > > > Macro question: Is there a better way to manage my accountability > > > system, rather than doing it manually? Again, I don't see a way to do > > > it using agenda. > > > > > > hth > > > > Memnon > > > > > >
Re: [O] Participating in Google Summer of Code 2012
Dear all, The Free Software Foundation will vouch for Org as a new organization. Is there any Googler reading this list? If so, is this Googler ready to vouch for Org-mode as a new organization? That would help a lot! In the meantime, please have a look to the last version of the ideas page and suggest improvements wildly: http://orgmode.org/worg/org-contrib/gsoc2012/orgmode-gsoc2012-ideas.html Thanks! -- Bastien
Re: [O] Bug: 3 bugs and 2 proposals on ascii/html export [7.8.03]
Hi Mathias, Mathias Bauer writes: > I just played with org's export functionality and following > minimal org file. This results in three minor bugs and two > proposals/questions on org's behavior. Thanks for this report -- next time, please consider sending one mail per bug/request, it makes issues easier to track. > ** Bug 1: Underlining the headlines > > Headlines without tags are underlined in a wrong manner. It's > one character too long. It's a matter of taste. I like this additionnal character and I think Carsten added it intentionally. > ** Question/Proposal > > As default, all level 1 headlines are underlined by - characters > and level 2 headlines with =. Wouldn't it be more logical the > other way round: the lower the level, the more important the > headline and hence the "bigger" its underlining? (Of course the > user can change the variable org-export-ascii-underline.) Unless many users think this is illogical, I won't change the default. > * HTML export > > ** Question/Proposal > > --snip-- > ...Some section with TAG at the end class="tag">some_tag... > --snip-- > > Isn't a single space enough for separating the heading's text and > the tag? Beside their number, the additional three (why not five > or n?) " " seem a little bit freaky to me... They _are_ freaky :) But they are also needed. Even if the tags display is taken care of by the CSS, we must prevent collapsing the tags with the previous strings in case the CSS is not available -- just think of what the HTML page should look like with w3m/lynx. > ** Bug 2: Exporting the tag into the toc > > Adding "#+OPTIONS: tags:t" results in the following exported toc: > > --snip-- > ...Some section with TAG at the end > some_tag > --snip-- > > There is a space inside the ... just before the tag > name which should not be there. Fixed, thanks. > ** Bug 3: Exporting the TODO keywords > > --snip-- > ... TODO Some section with a TODO > keyword > --snip-- > > There is a space inside the ... just before the TODO > keyword which should not be there. Fixed, thanks. -- Bastien
Re: [O] worg latex example "11 Styling the Frontmatter"
>> On Thu, 08 Mar 2012 13:39:28 -0500, Nick Dokos said:
> Myles English wrote:
>>
>> So the two files are:
>>
>> ,--- testAbs.org
>> -- | #+LATEX_HEADER:
>> \input{/home/myles/tmp/bugs/title.tex} | #+BEGIN_abstract | Here is
>> my abstract, it is a fine abstract. | #+END_abstract | #+LATEX:
>> \tableofcontents | #+LATEX: \listoftables | #+LATEX:
>> \listoffigures | | * Foo | foo | | * Bar | bar | | #+BEGIN_SRC
>> emacs-lisp :exports none | (defun org-export-latex-no-toc (depth)
>> (when depth (format "%% Org-mode | is exporting headings to %s
>> levels.\n" depth))) (setq | org-export-latex-format-toc-function
>> 'org-export-latex-no-toc) | #+END_SRC
>> `
>>
>> ,--title.tex | |
>> \renewcommand\maketitle{\begin{titlepage}% | FOO | \end{titlepage}%
>> } `---
>>
> You have commented out the closing brace in title.tex. It should be
> \renewcommand\maketitle{\begin{titlepage}% FOO \end{titlepage}% }
> Nick
Thanks for noticing that, I have changed it and still get the strange
behaviour described in my previous post.
Any other ideas?
Myles
Re: [O] worg latex example "11 Styling the Frontmatter"
>> On Thu, 08 Mar 2012 09:01:01 -1000, Thomas S Dye said:
> Aloha Myles, Your example works for me with emacs -q. I had to
> change the \input{} command to \input{title}, since I'm not working
> at /home/myles. I saved the tex file to title.tex, put it in the
> same directory as the org file, evaluated the source block
> (with :results silent), and exported. I got a 2 page pdf with FOO
> on the first page and a second page with all the rest.
> I'm not sure what is going wrong at your end, but suspect the
> \input{} command might not be picking up your .tex file. Do you see
> something in the .log file produced by LaTeX?
> All the best, Tom
> Myles English writes:
On Thu, 08 Mar 2012 16:29:36 +, Myles English said:
>>
>> > Hi, I am trying to get a custom title page and abstract before
>> the > TOC in a pdf.
>>
>> > Worg has an example on this page:
>>
>> > http://orgmode.org/worg/org-tutorials/org-latex-export.html
>>
>> > at the section titled "11 Styling the Frontmatter" However, the >
>> example doesn't work for me as expected.
>>
>> > To reproduce:
>>
>> > + save the attached files (testAbs.org, title.tex) in the same >
>> directory + open testAbs.org and do "C-c e d" to export to pdf
>>
>> > I would expect the Abstract and text to be shown in the final pdf
>> > but it is absent.
>>
>> > If I put a character between the lines #+LATEX_HEADER >
>> and #+BEGIN_abstract then the abstract title and text are shown as
>> > expected.
>>
>> > The above is using release_7.8.03-566-gf8efc63. Am I doing >
>> something wrong?
Tom,
Thanks very much for checking it. It does pick up the title.tex file
and I don't get a log file but the testAbs.tex file (see below) shows
that the abstract title is missing and the abstract text is entered as
the \title{}.
If I start emacs -q then execute this block, it seems to report that
orgmode is a mixture of version 7.7 and 7.8.
#+BEGIN_SRC emacs-lisp :exports none
(add-to-list 'load-path
"~/.emacs.d/plugins/org-mode/lisp")
(require 'org-install)
(org-version)
#+END_SRC
#+results:
: Org-mode version 7.7 (release_7.8.03.566.gf8efc)
Does that look normal? Exporting as before then gives the file below.
Myles
File testAbs.tex contains:
% Created 2012-03-09 Fri 01:11
\documentclass[11pt]{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{fixltx2e}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{float}
\usepackage{wrapfig}
\usepackage{soul}
\usepackage{textcomp}
\usepackage{marvosym}
\usepackage{wasysym}
\usepackage{latexsym}
\usepackage{amssymb}
\usepackage{hyperref}
\tolerance=1000
\input{title.tex}
\providecommand{\alert}[1]{\textbf{#1}}
\title{Here is my abstract, it is a fine abstract.}
\author{}
\date{\today}
\hypersetup{
pdfkeywords={},
pdfsubject={},
pdfcreator={Emacs Org-mode version 7.7}}
\begin{document}
\maketitle
% Org-mode is exporting headings to 3 levels.
\tableofcontents
\listoftables
\listoffigures
\section{Foo}
\label{sec-1}
foo
\section{Bar}
\label{sec-2}
bar
\section{src}
\label{sec-3}
\end{document}
[O] Bug: 3 bugs and 2 proposals on ascii/html export [7.8.03]
Hi! I just played with org's export functionality and following minimal org file. This results in three minor bugs and two proposals/questions on org's behavior. file1.org #+STARTUP: showeverything #+OPTIONS: author:nil email:nil timestamp:nil * Some section Some text. * TODO Some section with a TODO keyword Some text. * DONE Some section with another TODO keyword Some text. * Some section with TAG at the end :some_tag: Some text. * TODO Some section with TODO keyword and TAG at the end :another_tag: Some text. --- * ASCII/Latin-1/UTF-8 export ** Bug 1: Underlining the headlines Headlines without tags are underlined in a wrong manner. It's one character too long. ** Question/Proposal As default, all level 1 headlines are underlined by - characters and level 2 headlines with =. Wouldn't it be more logical the other way round: the lower the level, the more important the headline and hence the "bigger" its underlining? (Of course the user can change the variable org-export-ascii-underline.) * HTML export ** Question/Proposal --snip-- ...Some section with TAG at the end some_tag... --snip-- Isn't a single space enough for separating the heading's text and the tag? Beside their number, the additional three (why not five or n?) " " seem a little bit freaky to me... To keep things even more flexible, couldn't the blank and the " " be skipped both and could the CSS "tag" class be modified instead. Unfortunately, I don't know enough of CSS yet to check if that will be possible at all. For the table of contents we will have a similar phenomenon if an additional "#+OPTIONS: tags:t" is added. The separation between text and tag in this case consists of three " " and *no* space before. ** Bug 2: Exporting the tag into the toc Adding "#+OPTIONS: tags:t" results in the following exported toc: --snip-- ...Some section with TAG at the end some_tag --snip-- There is a space inside the ... just before the tag name which should not be there. ** Bug 3: Exporting the TODO keywords --snip-- ... TODO Some section with a TODO keyword --snip-- There is a space inside the ... just before the TODO keyword which should not be there. Could you please consider fixing these bugs. Thanks for this wonderful piece of software :-) Mathias P.S. For proving the above topics I used the proposed minimal org installation. So nothing in the following settings report has something to do with my personal configuration. But if it's the will of (org-submit-bug-report)... :-) Emacs : GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0) of 2010-12-11 on raven, modified by Debian Package: Org-mode version 7.8.03 current state: == (setq org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars) org-speed-command-hook '(org-speed-command-default-hook org-babel-speed-command-hook) org-metaup-hook '(org-babel-load-in-session-maybe) org-after-todo-state-change-hook '(org-clock-out-if-current) org-export-latex-format-toc-function 'org-export-latex-format-toc-default org-tab-first-hook '(org-hide-block-toggle-maybe org-src-native-tab-command-maybe) org-src-mode-hook '(org-src-babel-configure-edit-buffer org-src-mode-configure-edit-buffer) org-confirm-shell-link-function 'yes-or-no-p org-export-first-hook '(org-beamer-initialize-open-trackers) org-agenda-before-write-hook '(org-agenda-add-entry-text) org-blank-before-new-entry nil org-babel-pre-tangle-hook '(save-buffer) org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers org-cycle-show-empty-lines org-optimize-window-after-visibility-change) org-export-preprocess-before-normalizing-links-hook '(org-remove-file-link-modifiers) org-mode-hook '(#[nil "\300\301\302\303\304$\207" [org-add-hook change-major-mode-hook org-show-block-all append local] 5] org-babel-hide-all-hashes) org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point org-babel-execute-safely-maybe) org-confirm-elisp-link-function 'yes-or-no-p org-export-interblocks '((lob org-babel-exp-lob-one-liners) (src org-babel-exp-inline-src-blocks)) org-clock-out-hook '(org-clock-remove-empty-clock-drawer) org-occur-hook '(org-first-headline-recenter) org-export-preprocess-before-selecting-backend-code-hook '(org-beamer-select-beamer-code) org-export-latex-final-hook '(org-beamer-amend-header org-beamer-fix-toc org-beamer-auto-fragile-frames org-beamer-place-default-actions-fo
[O] [PATCH] org-store-link: Fixed a bug where source block edit buffers were not recognized
attached. >From 134c2ba772081ee7ca356b0dcabeb131bcb41b3b Mon Sep 17 00:00:00 2001 From: Ilya Shlyakhter Date: Thu, 8 Mar 2012 17:25:18 -0500 Subject: [PATCH 2/2] org-store-link: Fixed a bug where source block edit buffers were not recognized * lisp/org.el (org-store-link): Use a new predicate from org-src.el to test whether we're in a source block edit buffer. * lisp/org-src.el (org-src-edit-buffer-p): New predicate to tell if we're in a source block edit buffer. TINYCHANGE --- lisp/org-src.el |9 + lisp/org.el |2 +- 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/lisp/org-src.el b/lisp/org-src.el index 9cd56d2..e08fe89 100644 --- a/lisp/org-src.el +++ b/lisp/org-src.el @@ -374,6 +374,15 @@ buffer." "Construct the buffer name for a source editing buffer." (concat "*Org Src " org-buffer-name "[ " lang " ]*")) +(defun org-src-edit-buffer-p (&optional buffer) + "Test whether BUFFER (or the current buffer if BUFFER is nil) +is a source block editing buffer." + (let ((buffer (org-base-buffer (or buffer (current-buffer) +(and (buffer-name buffer) +(string-match "\\`*Org Src " (buffer-name buffer)) +(local-variable-p 'org-edit-src-beg-marker buffer) +(local-variable-p 'org-edit-src-end-marker buffer + (defun org-edit-src-find-buffer (beg end) "Find a source editing buffer that is already editing the region BEG to END." (catch 'exit diff --git a/lisp/org.el b/lisp/org.el index e4fb497..6074a01 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -8684,7 +8684,7 @@ For file links, arg negates `org-context-in-file-links'." (setq link (plist-get org-store-link-plist :link) desc (or (plist-get org-store-link-plist :description) link))) - ((equal (buffer-name) "*Org Edit Src Example*") + ((org-src-edit-buffer-p) (let (label gc) (while (or (not label) (save-excursion -- 1.7.9.3
Re: [O] How to reduce width of section separators in agenda view?
Nick Dokos writes: > Richard Stanton wrote: > >> This works fine, but I notice that each section of the agenda view is >> separated by a line of “=” signs 132 characters long, and when I print in >> portrait mode, these wrap onto the next line. How can I shorten these lines >> to only 80 characters wide? >> >> Thanks for any suggestions. >> > > Check out the variable org-agenda-block-separator. C-h v > org-agenda-block-separator RET says: > Or just turn them off with org-agenda-compact-blocks. Regards, Bernt
Re: [O] [PATCH] imenu: Added a check that looking-at succeeds before using the match results.
On 3/8/2012 2:39 PM, Achim Gratz wrote: Your patch got completely mangled, try again as an attachment of type (text/plain). here, also at http://ilya.cc/imenu.patch >From e3e6e7135663fb34a5318565e5663dd27fa7ce45 Mon Sep 17 00:00:00 2001 From: Ilya Shlyakhter Date: Thu, 8 Mar 2012 14:15:12 -0500 Subject: [PATCH] imenu: Added a check that looking-at succeeds before using the match results. * lisp/org.el (org-imenu-get-tree): Check that looking-at succeeds before using match results. TINYCHANGE --- lisp/org.el |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index ad63213..e4fb497 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -21250,8 +21250,8 @@ Show the heading too, if it is currently invisible." (goto-char (point-max)) (while (re-search-backward re nil t) (setq level (org-reduced-level (funcall outline-level))) - (when (<= level n) - (looking-at org-complex-heading-regexp) + (when (and (<= level n) +(looking-at org-complex-heading-regexp)) (setq head (org-link-display-format (org-match-string-no-properties 4)) m (org-imenu-new-marker)) -- 1.7.9.3
Re: [O] Orgmode markups inside LaTeX fragments
On Thu, Mar 8, 2012 at 16:55, Truong Nghiem wrote: > If there is any solution or workaround for my problem, please let me know. If these custom commands are analogs of commands like section and such, you can always define your own LaTeX_CLASS. The manual has information on how to do that. GL -- Suvayu Open source is the future. It sets us free.
Re: [O] Problem with babel and R + lattice
Drat. I meant to add that when I run the code exactly as I have it
from R directly, it works. I literally copy and paste my org-mode
babel block code line by line into a terminal and obtain the proper
output via tikz. *That's* the perplexing part. What would be working
directly from R and not from Org-mode?
For reference, I've generated plenty of stuff just like this via
org-mode/babel. Come to think of it, even another lattice plot.
Not sure how to pinpoint what's goofy about this specific plot.
John
On Thu, Mar 8, 2012 at 2:40 PM, John Hendy wrote:
> I have an R block like so:
>
> #+begin_src R
>
> library(lattice)
> library(tikzDevice)
>
> =bunch of code=
>
> barchart(side$name~side$x2,groups=side$type,horiz=T,
> xlim=c(0,0.75),col=c("lightblue","yellow"),xlab="Product
> Performance (2-box)")
>
> dev.off()
> tools::texi2dvi("bar-2b.tex",pdf=T)
>
> #+end_src
>
> The resultant tex file is empty where the tikz code should be and
> texi2dvi fails. Any suggestions? If I change my plot to base graphics
> with barplot, it works. I'm thinking this is a lattice/babel issue?
>
>
> Thanks for any input,
> John
[O] Problem with babel and R + lattice
I have an R block like so:
#+begin_src R
library(lattice)
library(tikzDevice)
=bunch of code=
barchart(side$name~side$x2,groups=side$type,horiz=T,
xlim=c(0,0.75),col=c("lightblue","yellow"),xlab="Product
Performance (2-box)")
dev.off()
tools::texi2dvi("bar-2b.tex",pdf=T)
#+end_src
The resultant tex file is empty where the tikz code should be and
texi2dvi fails. Any suggestions? If I change my plot to base graphics
with barplot, it works. I'm thinking this is a lattice/babel issue?
Thanks for any input,
John
Re: [O] BUG(?): #+BINDing org-export-publishing-directory only affects HTML output, not PDF or Babel results
On 3/8/12 7:38 AM, A. Major wrote: Thanks, but the "dir" PROPERTY appears to affect the target directory for babel's results, neither the HTML nor the PDF output are influenced that way. Yes, that's why I said "this part of the problem". Combining BIND and the "dir" PROPERTY, I can get HTML and babel files in the right place, but not the PDF. Any other suggestions? :) Yep. Change three characters in org-latex.el. Problem solved. Maybe. :) The attached patch addresses a difference between the latex and html exporters, enabling the user to choose a different output directory for latex/PDF export by binding org-export-publishing directory, just as was already possible for html export. If there's a latex user following this thread who understands the ways of the latex exporter, could you have a look to see that it doesn't screw up anything else before I submit a properly formatted patch? Yours, Christian diff --git a/lisp/org-latex.el b/lisp/org-latex.el index 03664b4..759fad4 100644 --- a/lisp/org-latex.el +++ b/lisp/org-latex.el @@ -870,7 +870,7 @@ when PUB-DIR is set, use this as the publishing directory." (concat (file-name-as-directory (or pub-dir -(org-export-directory :LaTeX ext-plist))) +(org-export-directory :LaTeX opt-plist))) (file-name-sans-extension (or (and subtree-p (org-entry-get rbeg "EXPORT_FILE_NAME" t)) diff --git a/lisp/org-latex.el b/lisp/org-latex.el index 03664b4..759fad4 100644 --- a/lisp/org-latex.el +++ b/lisp/org-latex.el @@ -870,7 +870,7 @@ when PUB-DIR is set, use this as the publishing directory." (concat (file-name-as-directory (or pub-dir -(org-export-directory :LaTeX ext-plist))) +(org-export-directory :LaTeX opt-plist))) (file-name-sans-extension (or (and subtree-p (org-entry-get rbeg "EXPORT_FILE_NAME" t))
Re: [O] [PATCH] imenu: Added a check that looking-at succeeds before using the match results.
Your patch got completely mangled, try again as an attachment of type (text/plain). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada
[O] [Babel] : Bug in org-tangle with :comments, patch included
Hi all, When I tangle a source block with ":comments yes" any spaces in the sub-heading in which the block is found are replaced with "%2520" instead of "%20". As a consequence when I "org-babel-detangle" the correct heading is not found. As an example given the following org file: * Babel Tangling ** Test Source 1 #+begin_src c :tangle /tmp/source1.txt :comments yes nothing #+end_src running "org-babel-tangle" generates the following source: /* [[file:~/WorkingFiles/Org.org::*Test%2520Source%25201][Test-Source-1:1]] */ nothing /* Test-Source-1:1 ends here */ The problem is in the "org-babel-spec-to-string" function which takes the correctly escaped link generated by "org-store-link": "[[file:~/WorkingFiles/Org.org::*Test%20Source%201][Test-Source-1:1]]" and escapes it again with "org-link-escape" which yielding the erroneous: "[[file:~/WorkingFiles/Org.org::*Test%2520Source%25201][Test-Source-1:1]]". I have included a patch that removes the call to "org-link-escape" and that fixes it on my machine. A grep of my current source tree shows that "org-babel-spec-to-string" is only called from "org-babel-tangle". I don't know if any other contribs are using this function. -deech From 249f60fe17913db08f81bca40d12e114f66db4b6 Mon Sep 17 00:00:00 2001 From: Deech Date: Thu, 8 Mar 2012 13:25:14 -0600 Subject: [PATCH 3/3] The link generated by org-store-link is escaped twice when tangling with ":comments yes" flag. --- lisp/ob-tangle.el |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lisp/ob-tangle.el b/lisp/ob-tangle.el index 15c0518..e629c12 100644 --- a/lisp/ob-tangle.el +++ b/lisp/ob-tangle.el @@ -381,7 +381,7 @@ form (start-line file link source-name params body comment)" (let* ((start-line (nth 0 spec)) (file (nth 1 spec)) - (link (org-link-escape (nth 2 spec))) + (link (nth 2 spec)) (source-name (nth 3 spec)) (body (nth 5 spec)) (comment (nth 6 spec)) -- 1.7.4.1
[O] [PATCH] imenu: Added a check that looking-at succeeds before using the match results.
* lisp/org.el (org-imenu-get-tree): Check that looking-at succeeds before using match results. TINYCHANGE --- lisp/org.el |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index ad63213..e4fb497 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -21250,8 +21250,8 @@ Show the heading too, if it is currently invisible." (goto-char (point-max)) (while (re-search-backward re nil t) (setq level (org-reduced-level (funcall outline-level))) - (when (<= level n) - (looking-at org-complex-heading-regexp) + (when (and (<= level n) +(looking-at org-complex-heading-regexp)) (setq head (org-link-display-format (org-match-string-no-properties 4)) m (org-imenu-new-marker)) -- 1.7.9.3
Re: [O] worg latex example "11 Styling the Frontmatter"
Aloha Myles,
Your example works for me with emacs -q. I had to change the \input{}
command to \input{title}, since I'm not working at /home/myles. I saved
the tex file to title.tex, put it in the same directory as the org file,
evaluated the source block (with :results silent), and exported. I got
a 2 page pdf with FOO on the first page and a second page with all the
rest.
I'm not sure what is going wrong at your end, but suspect the \input{}
command might not be picking up your .tex file. Do you see something in
the .log file produced by LaTeX?
All the best,
Tom
Myles English writes:
>>> On Thu, 08 Mar 2012 16:29:36 +, Myles English said:
>
> > Hi, I am trying to get a custom title page and abstract before the
> > TOC in a pdf.
>
> > Worg has an example on this page:
>
> > http://orgmode.org/worg/org-tutorials/org-latex-export.html
>
> > at the section titled "11 Styling the Frontmatter" However, the
> > example doesn't work for me as expected.
>
> > To reproduce:
>
> > + save the attached files (testAbs.org, title.tex) in the same
> > directory + open testAbs.org and do "C-c e d" to export to pdf
>
> > I would expect the Abstract and text to be shown in the final pdf
> > but it is absent.
>
> > If I put a character between the lines #+LATEX_HEADER
> > and #+BEGIN_abstract then the abstract title and text are shown as
> > expected.
>
> > The above is using release_7.8.03-566-gf8efc63. Am I doing
> > something wrong?
>
> > Thanks,
>
> > Myles
>
> So the two files are:
>
> ,--- testAbs.org --
> | #+LATEX_HEADER: \input{/home/myles/tmp/bugs/title.tex}
> | #+BEGIN_abstract
> | Here is my abstract, it is a fine abstract.
> | #+END_abstract
> | #+LATEX: \tableofcontents
> | #+LATEX: \listoftables
> | #+LATEX: \listoffigures
> |
> | * Foo
> | foo
> |
> | * Bar
> | bar
> |
> | #+BEGIN_SRC emacs-lisp :exports none
> | (defun org-export-latex-no-toc (depth) (when depth (format "%% Org-mode
> | is exporting headings to %s levels.\n" depth))) (setq
> | org-export-latex-format-toc-function 'org-export-latex-no-toc)
> | #+END_SRC
> `
>
> ,--title.tex
> |
> | \renewcommand\maketitle{\begin{titlepage}%
> | FOO
> | \end{titlepage}% }
> `---
>
> Myles
>
>
--
Thomas S. Dye
http://www.tsdye.com
Re: [O] worg latex example "11 Styling the Frontmatter"
Myles English wrote:
>
> So the two files are:
>
> ,--- testAbs.org --
> | #+LATEX_HEADER: \input{/home/myles/tmp/bugs/title.tex}
> | #+BEGIN_abstract
> | Here is my abstract, it is a fine abstract.
> | #+END_abstract
> | #+LATEX: \tableofcontents
> | #+LATEX: \listoftables
> | #+LATEX: \listoffigures
> |
> | * Foo
> | foo
> |
> | * Bar
> | bar
> |
> | #+BEGIN_SRC emacs-lisp :exports none
> | (defun org-export-latex-no-toc (depth) (when depth (format "%% Org-mode
> | is exporting headings to %s levels.\n" depth))) (setq
> | org-export-latex-format-toc-function 'org-export-latex-no-toc)
> | #+END_SRC
> `
>
> ,--title.tex
> |
> | \renewcommand\maketitle{\begin{titlepage}%
> | FOO
> | \end{titlepage}% }
> `---
>
You have commented out the closing brace in title.tex. It should be
--8<---cut here---start->8---
\renewcommand\maketitle{\begin{titlepage}%
FOO
\end{titlepage}%
}
--8<---cut here---end--->8---
Nick
Re: [O] How to reduce width of section separators in agenda view?
Richard Stanton wrote:
> I have an agenda view set up as an org-agenda-custom-command,
>
> ("H" "Office and Home Lists"
>
> ((agenda)
>
> (tags-todo "OFFICE")
>
> (tags-todo "HOME")
>
> (tags-todo "COMPUTER")))
>
> This works fine, but I notice that each section of the agenda view is
> separated by a line of “=” signs 132 characters long, and when I print in
> portrait mode, these wrap onto the next line. How can I shorten these lines
> to only 80 characters wide?
>
> Thanks for any suggestions.
>
Check out the variable org-agenda-block-separator. C-h v
org-agenda-block-separator RET says:
,
| org-agenda-block-separator is a variable defined in `org-agenda.el'.
| Its value is 61
|
| Documentation:
| The separator between blocks in the agenda.
| If this is a string, it will be used as the separator, with a newline added.
| If it is a character, it will be repeated to fill the window width.
| If nil the separator is disabled. In `org-agenda-custom-commands' this
| addresses the separator between the current and the previous block.
|
| You can customize this variable.
`
(61 is '=')
So you can customize it and set it to a string of your choice, or you
can display the block agenda in a window of width <= 80 chars and then
print the window. Both suggestions untested but I hope one or the other
or both work.
Nick
Re: [O] Sort order of TODO entries
On Thu, 08 Mar 2012 10:52:05 -0500 Bernt Hansen wrote: > Detlef Steuer writes: > > > Dear ORGers. > > > > recently I started to priorize my TODO items. > > (May be that implies failure of my GTD setup, but I don't want to > > discuss that ... ) > > > > I found org sorts TODOs in the following way in my agenda view: > > > > TODO [#A] > > TODO [#B] > > TODO/WAITING > > TODO [#C] > > > > I don't understand the reasoning in putting TODOs without priority or > > WAITING without priority before priority #C. > > > > Conceptually "no priority" (for me) means "not decided how important or > > not important at all, but would like to work on it", In contrast "#C" > > means "must be done, but do #A and #B first". > > They don't have 'no priority' -- they have the default priority which is > probably [#C]. You can set the default using variables. > > See: > org-default-priority >The default priority of TODO items. > org-highest-priority >The highest priority of TODO items. A character like ?A, ?B etc. > org-lowest-priority >The lowest priority of TODO items. A character like ?A, ?B etc. > > You're free to change the default to Z or something as long as you also > set org-lowest-priority appropriately. Thank you both! Sorry for not getting it from the fine manual. 56 min from asking a question to two perfect answers! Just great! Detlef > > Regards, > Bernt > > > > > > It would IMHO feel much more natural to sort > > > > #A, #B, #C, no priority. > > > > Is that (easily) possible? > > > > SETUP: > > Org-mode version 7.8.03 (release_7.8.03.553.g62a63) > > emacs GNU Emacs 23.2.1 (x86_64-suse-linux-gnu) of 2011-02-22 on build34 > > > > Thx > > Detlef > >
[O] How to reduce width of section separators in agenda view?
I have an agenda view set up as an org-agenda-custom-command,
("H" "Office and Home Lists"
((agenda)
(tags-todo "OFFICE")
(tags-todo "HOME")
(tags-todo "COMPUTER")))
This works fine, but I notice that each section of the agenda view is separated
by a line of "=" signs 132 characters long, and when I print in portrait mode,
these wrap onto the next line. How can I shorten these lines to only 80
characters wide?
Thanks for any suggestions.
Richard Stanton
Re: [O] ConTeXt export
From: David Rogers To:nicholas.do...@hp.com Cc: Sebastien Vauban, emacs-orgmode@gnu.org Subject: Re: [O] ConTeXt export Message-ID:<8762el3bxr@gmail.com> Content-Type: text/plain; format=flowed Nick Dokos writes: Can ConTeXt handle a LaTeX program? No it can't, not that I'm aware of anyway. While both LaTeX and ConTeXt inherit from plain TeX, and therefore look somewhat similar cosmetically, they don't work the same. (e.g. ConTeXt does not use LaTeX packages, the .tex files differ in essentials and not just in details, etc.) -- David I also think it would need a ne exporter. On the other hand it might prevent running in the too many packages trap of LaTeX. To be honest, I do not know how man people really use ConTeXt. Best Markus
Re: [O] Problem loading a symlink'ed file in Emacs batch
If you are using NTemacs rather than the one supplied by Cygwin it simply doesn't know about symlinks. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf Blofeld V1.15B11: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] worg latex example "11 Styling the Frontmatter"
>> On Thu, 08 Mar 2012 16:29:36 +, Myles English said:
> Hi, I am trying to get a custom title page and abstract before the
> TOC in a pdf.
> Worg has an example on this page:
> http://orgmode.org/worg/org-tutorials/org-latex-export.html
> at the section titled "11 Styling the Frontmatter" However, the
> example doesn't work for me as expected.
> To reproduce:
> + save the attached files (testAbs.org, title.tex) in the same
> directory + open testAbs.org and do "C-c e d" to export to pdf
> I would expect the Abstract and text to be shown in the final pdf
> but it is absent.
> If I put a character between the lines #+LATEX_HEADER
> and #+BEGIN_abstract then the abstract title and text are shown as
> expected.
> The above is using release_7.8.03-566-gf8efc63. Am I doing
> something wrong?
> Thanks,
> Myles
So the two files are:
,--- testAbs.org --
| #+LATEX_HEADER: \input{/home/myles/tmp/bugs/title.tex}
| #+BEGIN_abstract
| Here is my abstract, it is a fine abstract.
| #+END_abstract
| #+LATEX: \tableofcontents
| #+LATEX: \listoftables
| #+LATEX: \listoffigures
|
| * Foo
| foo
|
| * Bar
| bar
|
| #+BEGIN_SRC emacs-lisp :exports none
| (defun org-export-latex-no-toc (depth) (when depth (format "%% Org-mode
| is exporting headings to %s levels.\n" depth))) (setq
| org-export-latex-format-toc-function 'org-export-latex-no-toc)
| #+END_SRC
`
,--title.tex
|
| \renewcommand\maketitle{\begin{titlepage}%
| FOO
| \end{titlepage}% }
`---
Myles
[O] worg latex example "11 Styling the Frontmatter"
Hi,
I am trying to get a custom title page and abstract before the TOC in a
pdf.
Worg has an example on this page:
http://orgmode.org/worg/org-tutorials/org-latex-export.html
at the section titled "11 Styling the Frontmatter"
However, the example doesn't work for me as expected.
To reproduce:
+ save the attached files (testAbs.org, title.tex) in the same directory
+ open testAbs.org and do "C-c e d" to export to pdf
I would expect the Abstract and text to be shown in the final pdf but it
is absent.
If I put a character between the lines #+LATEX_HEADER
and #+BEGIN_abstract then the abstract title and text are shown as
expected.
The above is using release_7.8.03-566-gf8efc63. Am I doing something
wrong?
Thanks,
Myles
#+LATEX_HEADER: \input{/home/myles/tmp/bugs/title.tex}
#+BEGIN_abstract
Here is my abstract, it is a fine abstract.
#+END_abstract
#+LATEX: \tableofcontents
#+LATEX: \listoftables
#+LATEX: \listoffigures
* Foo
foo
* Bar
bar
#+BEGIN_SRC emacs-lisp :exports none
(defun org-export-latex-no-toc (depth)
(when depth
(format "%% Org-mode is exporting headings to %s levels.\n"
depth)))
(setq org-export-latex-format-toc-function 'org-export-latex-no-toc)
#+END_SRC
#+RESULTS:
: org-export-latex-no-toc
(add-to-list 'load-path
"~/.emacs.d/plugins/org-mode/lisp")
(require 'org-install)
\renewcommand\maketitle{\begin{titlepage}%
FOO
\end{titlepage}%
}
Re: [O] Orgmode markups inside LaTeX fragments
Hi Bastien,
My use-case is that I need to write a document that needs to be output
to various styles (all using LaTeX). Each style may use a different
class and set of packages. And each defines a different set of
commands, with different syntax, to format the contents (they are not
standard as \section, etc.) Of course I don't want to re-write the
same contents for each style, so I defined a common command interface
such that I could write the contents as
\contentBlockOne{\textbf{Bold text}}
and implemented the interface for each specific style.
That has been working very well until I need to also output the
contents to HTML. I thought it would be great to migrate the contents
to orgmode, then export to LaTeX or HTML. But I need to re-use the
common interface, so I defined orgmode macros to be able to write:
{{{contentBlockOne(*Bold text*)}}}
or
{{{contentBlockOneBegin}}} *Bold text* {{{contentBlockOneEnd}}}
The macros will be expanded to LaTeX commands or HTML markups accordingly.
The problem is that orgmode markups inside LaTeX or HTML fragments are
not converted. And I cannot use \textbf because it will not be
translated to HTML.
However, I've just discovered that while markups like *bold*,
/italic/... are not converted, other markups like lists are. For
example:
\mycommand{*Bold*
- Item 1
- Item 2
}
is exported as
\mycommand{\textbf{Bold}
\begin{itemize}
\item Item 1
\item Item 2
\end{itemize}
}
So it seems a bit inconsistent.
If there is any solution or workaround for my problem, please let me know.
Thanks,
--
Truong Nghiem
On Thu, Mar 8, 2012 at 7:46 AM, Bastien wrote:
> Hi Truong,
>
> Truong Nghiem writes:
>
>> Is there any way to turn on orgmode markups inside LaTeX fragments for
>> export? For example, when I write
>> \mycommand{*Bold text*}
>> in an org file and export it to LaTeX, I would like to have
>> \mycommand{\textbf{Bold text}}
>> Currently it is exported as-is (verbatim):
>> \mycommand{*Bold text*}
>
> There is no way to achieve this right now, and I think it would be
> confusing to support mixed syntax. But I'm open to better use-cases.
>
> Thanks,
>
> --
> Bastien
Re: [O] Sort order of TODO entries
Hi Detlef, Detlef Steuer writes: > I don't understand the reasoning in putting TODOs without priority or > WAITING without priority before priority #C. > > Conceptually "no priority" (for me) means "not decided how important or > not important at all, but would like to work on it", In contrast "#C" > means "must be done, but do #A and #B first". > > It would IMHO feel much more natural to sort > > #A, #B, #C, no priority. Currently, org gives items with no priority a default priority of B. ,[ (info "(org) Priorities") | By default, Org mode supports three priorities: `A', `B', and `C'. `A' | is the highest priority. An entry without a cookie is treated just | like priority `B'. Priorities make a difference only for sorting in | the agenda (*note Weekly/daily agenda::); outside the agenda, they have | no inherent meaning to Org mode. ` > Is that (easily) possible? You can modify how the agenda sorts priorities with a custom function. Here's a quick hack that seems to work: (defun my-org-get-priority () (save-match-data (if (not (string-match org-priority-regexp s)) -1000 (* 1000 (- org-lowest-priority (string-to-char (match-string 2 s))) (setq org-get-priority-function 'my-org-get-priority) Best, Matt
Re: [O] Sort order of TODO entries
Detlef Steuer writes: > Dear ORGers. > > recently I started to priorize my TODO items. > (May be that implies failure of my GTD setup, but I don't want to > discuss that ... ) > > I found org sorts TODOs in the following way in my agenda view: > > TODO [#A] > TODO [#B] > TODO/WAITING > TODO [#C] > > I don't understand the reasoning in putting TODOs without priority or > WAITING without priority before priority #C. > > Conceptually "no priority" (for me) means "not decided how important or > not important at all, but would like to work on it", In contrast "#C" > means "must be done, but do #A and #B first". They don't have 'no priority' -- they have the default priority which is probably [#C]. You can set the default using variables. See: org-default-priority The default priority of TODO items. org-highest-priority The highest priority of TODO items. A character like ?A, ?B etc. org-lowest-priority The lowest priority of TODO items. A character like ?A, ?B etc. You're free to change the default to Z or something as long as you also set org-lowest-priority appropriately. Regards, Bernt > > It would IMHO feel much more natural to sort > > #A, #B, #C, no priority. > > Is that (easily) possible? > > SETUP: > Org-mode version 7.8.03 (release_7.8.03.553.g62a63) > emacs GNU Emacs 23.2.1 (x86_64-suse-linux-gnu) of 2011-02-22 on build34 > > Thx > Detlef
[O] Sort order of TODO entries
Dear ORGers. recently I started to priorize my TODO items. (May be that implies failure of my GTD setup, but I don't want to discuss that ... ) I found org sorts TODOs in the following way in my agenda view: TODO [#A] TODO [#B] TODO/WAITING TODO [#C] I don't understand the reasoning in putting TODOs without priority or WAITING without priority before priority #C. Conceptually "no priority" (for me) means "not decided how important or not important at all, but would like to work on it", In contrast "#C" means "must be done, but do #A and #B first". It would IMHO feel much more natural to sort #A, #B, #C, no priority. Is that (easily) possible? SETUP: Org-mode version 7.8.03 (release_7.8.03.553.g62a63) emacs GNU Emacs 23.2.1 (x86_64-suse-linux-gnu) of 2011-02-22 on build34 Thx Detlef
[O] [o] capture - function-finding-location in TARGET: return value?
Hello, I am trying to write a function to find the location where capture will put the captured item. The manual states, that a target configuration like : (file+function "path/to/file" function-finding-location) is possible. My question is, what is the function supposed to reurn? - a string with the headline - a location in the buffer - ... I searched the manual but did not find an answer. Thanks. -- Mit freundlichen Grüßen / Best regards Thomas Holst DGS-EC/ESE4 Tel. +49 (711) 811-40681 PC-Fax +49 (711) 811-5182208
[O] Problem loading a symlink'ed file in Emacs batch
Hello,
I have a `org-init.el' file in my home directory, with common settings used
when in batch mode.
That works well when that file is a regular file:
--8<---cut here---start->8---
sva@MEDIACENTER$ make html
Exporting file /cygdrive/c/home/sva/file.txt to HTML...
emacs --batch -Q --eval "(setq debug-on-error t) (add-to-list 'load-path
\""~/src/org-mode/lisp"\") (add-to-list 'load-path
\""~/src/org-mode/contrib/lisp"\")" -l "~/org-init.el" file.txt -f
org-export-as-html
Emacs 24.0.93.1
Org-mode version 7.8.03
OVERVIEW
Loading vc-svn...
Loading vc-git...
Exporting...
Exporting...
Saving file c:/home/sva/file.html...
Wrote c:/home/sva/file.html
HTML export done, pushed to kill ring and clipboard
--8<---cut here---end--->8---
However, if I put it somewhere, and make a symlink from my home directory to
its real place, Emacs fails loading it:
--8<---cut here---start->8---
sva@MEDIACENTER$ make html
Exporting file /cygdrive/c/home/sva/file.txt to HTML...
emacs --batch -Q --eval "(setq debug-on-error t) (add-to-list 'load-path
\""~/src/org-mode/lisp"\") (add-to-list 'load-path
\""~/src/org-mode/contrib/lisp"\")" -l "~/org-init.el" file.txt -f
org-export-as-html
Debugger entered--Lisp error: (void-variable !ÿþ/)
eval-buffer(# nil "c:/home/sva/org-init.el" nil t) ; Reading
at buffer position 14
load-with-code-conversion("c:/home/sva/org-init.el" "c:/home/sva/org-init.el"
nil t)
load("c:/home/sva/org-init.el" nil t)
command-line-1(("--eval" "(setq debug-on-error t) (add-to-list 'load-path
\"~/src/org-mode/lisp\") (add-to-list 'load-path
\"~/src/org-mode/contrib/lisp\")" "-l" "~/org-init.el" "file.txt" "-f"
"org-export-as-html"))
command-line()
normal-top-level()
Makefile:33: recipe for target `file.html' failed
make: *** [file.html] Error 127
--8<---cut here---end--->8---
I find this very strange, as I thought the symlink feature would be
transparent for upper applications. This does not seem to be the case, though.
Any idea on how to circumvent this, if possible?
Best regards,
Seb
--
Sebastien Vauban
[O] orgstruct++ does not lurk silently in the shadow (was: orgstuct++ does not lurk silently in the shadow)
Christopher Schmidt writes: [...] > (info "(org)Orgstruct mode") says that one is allowed to use > orgtbl-mode in message-mode. Unfortunately this does not work as > expected. Typo - I meant orgstruct-mode of course. Christopher
Re: [O] Org is 100% trusted !
Bastien writes: > The page mentions that Org is available for MacOSX, but > doesn't say anything about other platforms. > > Org is available for all platforms that can run Emacs. I would love to seem them include the list :) ┏━━━┫ Wikipedia on Emacs ┃ ┃ Emacs has become one of the most ported non-trivial computer ┃ programs. It runs on a wide variety of operating systems, including most ┃ Unix-like systems (GNU/Linux, the various BSDs, Solaris, AIX, HP-UX, ┃ IRIX, Mac OS X, etc.), DOS, Microsoft Windows and ┃ OpenVMS. ┗━━━ –Rasmus -- And let me remind you also that moderation in the pursuit of justice is no virtue
Re: [O] [patch] Add autoload for org-version
Hi Sébastien, "Sebastien Vauban" writes: > I don't know if this is correct and sufficient, so please amend if > not... Applied, thanks. The only missing part in your patch is a Changelog message. Best, -- Bastien
Re: [O] Org-mode workshop: has anyone done this already?
Karl Voit writes: > * Puneeth Chaganti wrote: >> >> Venkatesh Choppella (cc-ed) and I have done a basic workshop [1]. But >> this was a very basic workshop and it looks like you wish to do a much >> more advance one. Also, Venkatesh teaches a course in his university >> that introduces students to Org-mode [2], which might be of some help. >> >> [1] - https://github.com/vxc/org-mode-ws >> [2] - http://pascal.iiit.ac.in/~itws2 > > Very good startup material - thank you! > > I'll probably use your material as a starting point and extend it a > bit. If you are interested in following the status of my material, > please watch my repository on GitHub[3]. > > 3. https://github.com/novoid/org-mode-workshop Later this month I will be giving a talk on the use of code blocks in Org-mode. I haven't yet begun preparing the slides, but when I do they will live at https://github.com/eschulte/babel-presentation. Cheers, -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] Org is 100% trusted !
Hi Vera, "Vera Zubor - DownloadAtlas.com" writes: > we have done new complete security tests. To assure our users that > > Org is clean and safe to install, we awarded your software again with > > our DownloadAtlas.com 100% Safe award. If you want to notify your > > users about this certification, you can display this award on your > > website. > Thanks. I like the "Limitations: not specified" on this page: http://www.downloadatlas.com/open-source-e62b5b68.html#awards The page mentions that Org is available for MacOSX, but doesn't say anything about other platforms. Org is available for all platforms that can run Emacs. Thanks in advance for fixing this. Best, -- Bastien
Re: [O] suggestion for the manual: mention the "#+BEGIN_SRC org" trick when describing drawers and plainlists
Ilya Shlyakhter writes: > p.s. it _would_ be good to have an option, when exporting a > "#+BEGIN_SRC org" block, to use the Org export settings from the main > Org file, rather than exporting a fontified copy of the Org buffer for > the block. Is there a way to do that currently? > Try exporting the results of the block rather than the code with ":exports results". You may need to play with some results headings as well, see the manual for the possibilities. Cheers, > > On Wed, Mar 7, 2012 at 8:13 PM, Ilya Shlyakhter wrote: > >> In Org, entry text can't have substructure (other than drawers and plain >> lists): you can't have an entry that >> has some text, then a subtree, then more text. >> I just (re-)discovered that you can get around that by using "#+BEGIN_SRC >> org" to include arbitrary org >> subtrees in the middle of entry text. That's useful not just when >> writing in Org about Org, but anytime you want >> to insert an extended sidenote in the middle of an entry. As with all >> source blocks, you edit it in its native (Org) >> mode and it exports correctly. You can copy links from the main Org and >> past them into the nested Org. >> >> Just wish I'd learned this sooner :) So, maybe mention this in the manual >> in the sections on drawers and plainlists. >> >> ilya >> >> -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] [PATCH] Fix (wrong-type-argument integer-or-marker-p nil) in org-agenda-get-todos.
Hi Adam, Adam Spiers writes: > org-get-category can sometimes invoke org-refresh-category-properties > which can perform a re-search-forward which destroys the existing > match data. When called from org-agenda-get-todos, this can result in > its subsequent call to (match-beginning 2) to return nil, which when > passed as the first parameter to buffer-string causes the above error. I fixed this by saving match data in `org-get-category'. Thanks for spotting this! -- Bastien
Re: [O] suggestion for the manual: mention the "#+BEGIN_SRC org" trick when describing drawers and plainlists
On 3/8/2012 7:53 AM, Ilya Shlyakhter wrote: - when exporting to HTML, I want to run the HTML exporter on the nested org buffer and insert its results -- rather than inserting a boxed version of the Org source. p.s. one solution could be to run the HTML exporter on the nested org and show the result inside an IFRAME within the main org's HTML export.
Re: [O] suggestion for the manual: mention the "#+BEGIN_SRC org" trick when describing drawers and plainlists
On 3/8/2012 2:32 AM, Sebastien Vauban wrote: In Org, entry text can't have substructure (other than drawers and plain lists): you can't have an entry that has some text, then a subtree, then more text. Take a look at "inline tasks". I think that's more what you're after... Thanks -- looked at inline tasks and at http://orgmode.org/worg/org-faq.html#closing-outline-sections but that's not quite what I want. I really do want a "nested org" -- something like a drawer or a plainlist, which is fully part of the entry and can be org-cycled but has substructure. Inline tasks do not nest. Using #+BEGIN_SRC org / #+END_SRC does exactly what I want during editing -- lets me enter a "side note" that can be easily folded away (like a drawer), is completely within the entry (unlike solutions from org-faq that add extra headlines), can have substructure (like plain lists) but is a full-featured org without plainlists' limitations. Two problems with this so far: - org-store-link does not work when editing this nested org block under C-' . Ideally, it would store a link that when followed would open this source block for editing in its native org-mode (as with C-') and then find the link within that. - when exporting to HTML, I want to run the HTML exporter on the nested org buffer and insert its results -- rather than inserting a boxed version of the Org source. (This boxed version shows the hidden asterisks in outlines, and its colors do not quite match the ones in the Emacs buffer, among other things.) thanks for help, ilya
Re: [O] [PATCH] Fix typos
Hi Adam, Adam Spiers writes: > --- > lisp/org-agenda.el |2 +- > lisp/org-list.el |2 +- > lisp/org.el|2 +- > 3 files changed, 3 insertions(+), 3 deletions(-) Applied, thanks! -- Bastien
Re: [O] Orgmode markups inside LaTeX fragments
Hi Truong,
Truong Nghiem writes:
> Is there any way to turn on orgmode markups inside LaTeX fragments for
> export? For example, when I write
> \mycommand{*Bold text*}
> in an org file and export it to LaTeX, I would like to have
> \mycommand{\textbf{Bold text}}
> Currently it is exported as-is (verbatim):
> \mycommand{*Bold text*}
There is no way to achieve this right now, and I think it would be
confusing to support mixed syntax. But I'm open to better use-cases.
Thanks,
--
Bastien
Re: [O] [PATCH] Add example demonstrating LaTeX_CLASS_OPTIONS
suvayu ali writes: > Sorry the previous patch was buggy. I forgot to escape a brace. This > patch supersedes the last one. Applied, thanks! -- Bastien
Re: [O] [PATCH] Add example demonstrating LaTeX_CLASS_OPTIONS
Hi,
Sorry the previous patch was buggy. I forgot to escape a brace. This
patch supersedes the last one.
Thanks,
On Thu, Mar 8, 2012 at 01:41, suvayu ali wrote:
> Hi,
>
> This is adds a small example to better illustrate the use of
> LaTeX_CLASS_OPTIONS. Thanks to Nick for encouraging me to submit this.
>
> Thanks,
>
> --
> Suvayu
>
> Open source is the future. It sets us free.
--
Suvayu
Open source is the future. It sets us free.
From 6d7719bdb3d190ff0b2854bc781ddfec7b1382d1 Mon Sep 17 00:00:00 2001
From: Suvayu Ali
Date: Thu, 8 Mar 2012 01:31:05 +0100
Subject: [PATCH] Add example demonstrating LaTeX_CLASS_OPTIONS
* org.texi (Header and sectioning): Add example demonstrating how to use
"LaTeX_CLASS_OPTIONS".
TINY CHANGE
---
doc/org.texi | 21 -
1 files changed, 16 insertions(+), 5 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 33ffe28..68836e0 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -10361,11 +10361,22 @@ @subsection Header and sectioning structure
@code{org-export-latex-default-packages-alist} and
@code{org-export-latex-packages-alist} are spliced.}, and allows you to
define the sectioning structure for each class. You can also define your own
-classes there. @code{#+LaTeX_CLASS_OPTIONS} or a @code{LaTeX_CLASS_OPTIONS}
-property can specify the options for the @code{\documentclass} macro. You
-can also use @code{#+LaTeX_HEADER: \usepackage@{xyz@}} to add lines to the
-header. See the docstring of @code{org-export-latex-classes} for more
-information.
+classes there. @code{#+LaTeX_CLASS_OPTIONS} or a @code{:LaTeX_CLASS_OPTIONS:}
+property can specify the options for the @code{\documentclass} macro. The
+options to documentclass have to be provided, as expected by @LaTeX{}, within
+square brackets. You can also use @code{#+LaTeX_HEADER: \usepackage@{xyz@}}
+to add lines to the header. See the docstring of
+@code{org-export-latex-classes} for more information. An example is shown
+below.
+
+@example
+#+LaTeX_CLASS: article
+#+LaTeX_CLASS_OPTIONS: [a4paper]
+#+LaTeX_HEADER: \usepackage@{xyz@}
+
+* Headline 1
+ some text
+@end example
@node Quoting @LaTeX{} code, Tables in @LaTeX{} export, Header and sectioning, @LaTeX{} and PDF export
@subsection Quoting @LaTeX{} code
--
1.7.7.6
Re: [O] Org-mode workshop: has anyone done this already?
* Puneeth Chaganti wrote: > > Venkatesh Choppella (cc-ed) and I have done a basic workshop [1]. But > this was a very basic workshop and it looks like you wish to do a much > more advance one. Also, Venkatesh teaches a course in his university > that introduces students to Org-mode [2], which might be of some help. > > [1] - https://github.com/vxc/org-mode-ws > [2] - http://pascal.iiit.ac.in/~itws2 Very good startup material - thank you! I'll probably use your material as a starting point and extend it a bit. If you are interested in following the status of my material, please watch my repository on GitHub[3]. 3. https://github.com/novoid/org-mode-workshop -- Karl Voit
Re: [O] Org-mode workshop: has anyone done this already?
* Thorsten wrote: > Karl Voit writes: > >> It will be held in German only anyway ... > > In what part of Germany? No part of Germany at all. Graz :-) > Is that open to the public - and free? No. It is for our «Interne Weiterbildung» (internal education program) of our university where employees, students, and external people can attend. > Sounds interesting. I try to make sure that it will be interesting :-) -- Karl Voit
Re: [O] Solution for compatible file linking?
> > Hi everyone, > > I'm using orgmode in a multi OS environment. (OS X, Linux & Windows) > Most of the time I carry a USB-drive or stick. > I try to keep all linked files inside the same directory structure > used on all OS's. > > Does anyone have a solution to keep links in Orgmode files intact > between OS's? > I realize the mount point is crucial in this respect. > But on Windows systems, the drive letter can change quite at random... > > Or could windows shellinks > (http://msdn.microsoft.com/en-us/library/windows/desktop/bb776891%28v=vs.85%29.aspx) > or IUniformResourceLocator (http://support.microsoft.com/kb/229092) > provide a solution? (I have not investigated this yet) > > Thanks! > > Erwin > > Erwin Panen fastmail.fm> writes: Maybe running a portable app webserver might be a solution? Could this serve up "a uniform" file location for linking from within orgmode? Just a thought. Erwin
[O] [PATCH] Allow customization of date and time format
>From d4d2f7f32e659269c885a934a131c7aea1ec4798 Mon Sep 17 00:00:00 2001 From: Sebastien Vauban Date: Thu, 8 Mar 2012 11:04:00 +0100 Subject: [PATCH] Allow customization of date and time format Allow customization of date and time format * org-html.el (org-export-as-html): Use a variable format string for export of date and time. --- lisp/org-html.el |7 ++- 1 files changed, 6 insertions(+), 1 deletions(-) diff --git a/lisp/org-html.el b/lisp/org-html.el index bd133b3..72c0e37 100644 --- a/lisp/org-html.el +++ b/lisp/org-html.el @@ -653,6 +653,11 @@ postamble DIV." (string :tag " Div for the content:") (string :tag "Div for the postamble:"))) +(defvar org-export-html-date-format-string "%Y-%m-%dT%R%z" + "The string used to format date and time. + +Default is an extended format of the ISO 8601 specification.") + ;;; Hooks (defvar org-export-html-after-blockquotes-hook nil @@ -1285,7 +1290,7 @@ PUB-DIR is set, use this as the publishing directory." ((and date (string-match "%" date)) (setq date (format-time-string date))) (date) - (t (setq date (format-time-string "%Y-%m-%d %T %Z" + (t (setq date (format-time-string org-export-html-date-format-string ;; Get the language-dependent settings (setq lang-words (or (assoc language org-export-language-setup) -- 1.7.9 Best regards, Seb -- Sebastien Vauban
[O] Solution for compatible file linking?
Hi everyone, I'm using orgmode in a multi OS environment. (OS X, Linux & Windows) Most of the time I carry a USB-drive or stick. I try to keep all linked files inside the same directory structure used on all OS's. Does anyone have a solution to keep links in Orgmode files intact between OS's? I realize the mount point is crucial in this respect. But on Windows systems, the drive letter can change quite at random... Or could windows shellinks (http://msdn.microsoft.com/en-us/library/windows/desktop/bb776891%28v=vs.85%29.aspx) or IUniformResourceLocator (http://support.microsoft.com/kb/229092) provide a solution? (I have not investigated this yet) Thanks! Erwin
[O] orgstuct++ does not lurk silently in the shadow
Hi gurus, I have a problem with Org-mode version 7.8.03 (release_7.8.03.351.g47eb3) on GNU Emacs 24.0.94.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.9) of 2012-03-08. (info "(org)Orgstruct mode") says that one is allowed to use orgtbl-mode in message-mode. Unfortunately this does not work as expected. Recipe: emacs -q C-x m M-q # fill-paragraph ignores the message header eval: (add-hook 'message-mode-hook 'turn-on-orgstruct++) C-x m M-q # fill-paragraph does ignore the message header The bug is caused by fill-paragraph-function not being set back to message-fill-paragraph when orgstruct-hijacker-command-22 falls back to fill-paragraph. Christopher
