Re: [O] page break after TOC?
John Hendy wrote: > I'd like my page1 to be on a separate page from the TOC. How do I > insert a pagebreak to do this? If I do it here: > ,--- > | * Section 1 > | \newpage > | test in section 1 > `--- > > I get the TOC, then the Section 1 title, then a page break, and then the text. > > Assuming you are talking about LaTeX export only, I would define my own class: * copy the system article.cls to myarticle.cls (wherever in my local tree LaTeX can find it; the current directory is the last resort but not very convenient - in my case LaTeX searches in /home/nick/.texmf-config/tex, so I created a directory in there /home/nick/.texmf-config/tex/latex/base and copied it in there - don't forget to run texhash or equivalent) * modify the definition of \tableofcontents to add a \newpage at the end * modify org-export-latex-classes by duplicating the article section and changing article->myarticle in one of them The above steps are one-time only. Then whenever you want the behavior, change the class that org exports to: #+LaTeX_CLASS: myarticle Nick
Re: [O] Using orgmode to take "inline notes" for research
Erik Iverson writes:
> If you export to HTML, you should be able to export your notes with a
> CSS class to style your notes as differently from the text as you
> like.
>
I like the following for offsetting quotes, may work well for notes...
#+begin_src css
blockquote {
border-left: 1px solid gray;
padding-left: 4px; }
#+end_src
--
Eric Schulte
http://cs.unm.edu/~eschulte/
[O] Re: export options toc:t depends on num:t
John Hendy writes: > Hi, > > > Maybe this is obvious to most, but I was puzzled by it. It seems that > ,--- > | #+options: toc:t > `--- > > will not function when paired with: > ,--- > | #+options: toc:t num:nil > `--- > Anyway, if these two are necessary, perhaps the manual could be > updated (http://orgmode.org/manual/Export-options.html#Export-options): > ,--- > | toc: turn on/off table of contents, or set level limit > (integer); requires num:t or no setting (t is default for num) > `--- > > Or something to that effect. Is this a LaTeX specific behaviour? I don't see anything odd with HTML export. Jambunathan K. --
Re: [O] Re: Using orgmode to take "inline notes" for research
I agree this is interesting. Another option is an annotation mechanism with unbreakable bidirectional links -- ID markers work for this. You can stick the markers anywhere. If the thing to be annotated is read-only, I have other ideas. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com/2010/12/welcome-to-kafka-pandemic-two-forces_9182.html I support the Whittemore-Peterson Institute (WPI) === I want to see the original (pre-hold) Lo et al. 2010 NIH/FDA/Harvard MRV paper.
Re: [O] Using orgmode to take "inline notes" for research
If you export to HTML, you should be able to export your notes with a CSS class to style your notes as differently from the text as you like. On 04/05/2011 10:32 PM, Eric Schulte wrote: Hi John, Interesting use case, I definitely see the utility. I think that blocks may be an appropriate solution, for example if you enclose your notes in "notes" blocks, then it should be easy to control whether or not they are exported... Using the following code, you can control whether notes enclosed in "notes" blcks will be exported by changing the value of the *export-my-notes* variable, when it is nil your notes will not be exported, when t they will be exported as quoted text. #+begin_src emacs-lisp (defvar *export-my-notes* nil) (defun org-exp-block-process-notes (body&rest headers) (if *export-my-notes* (format "\n#+begin_quote\n%s\n#+end_quote\n" body) "")) (org-export-blocks-add-block '(notes org-exp-block-process-notes nil)) #+end_src Hope this Helps -- Eric This works for me with the attached Org-mode file. John Hendy writes: Hi, One thing I really like to use orgmode for is research. Lately, there's a mass of stuff on-line that I've been reading though and am about to start reading through a series of articles and had the idea to yank them into org for "inline notes." My current experiment has been: - wget the website page - run a custom script of simple sed stuff to get the major stuff converted ( &-> /,"e; -> ", etc.) - turn things into headlines where applicable - manually tweak the rest What I'd like to do is find some way to take notes in the article and would like some suggestions from anyone who's done this. On one hand, I see the idea of keeping a separate headline for notes, and for a series of articles, my file might look like this: ,--- | * Article 1 | ** Notes on article 1 | * Article 2 | ** Notes on article 2 `--- One advantage to this is that I could very easily add :noexport: to my notes and print off a hard copy of the article if I want it, and it would also be easy to tag my notes :notes: and then replace-string to turn the Article :export: into :noexport: and :notes: into :export:. Then I'd have an easy to print copy of my notes for each article. On the other hand, I like quoting when I use notes, and could see it as advantageous to have something like: ,--- | * Article 1 | It goes along and says x, y, and z. | --- Me: that's interesting and here are my thoughts. | | It continues along saying all kinds of other things and my comments are interjected whenever I want. `--- I think that might be more useful for studying things later, as I get to see an "annotated" version with my thoughts at the time I read it. What it *doesn't* allow for is the easy printing of both the article and the notes separately if I want. Would someone suggest a way that I might be able to have the best of both worlds? Some of my own not-at-all-hashed-out-ideas included: - using footnotes since org has easy ways to jump from one to another, but this would be tough when it came to actual footnotes, which there will definitely be plenty of. - highlighting the text I want to quote and then using refile somehow to send it off to my notes section with my comments. This would be cool if I could, at the same time, add an org-mode link to and from the notes and original section, but also if I could turn that link off when I export to PDF so I don't have hypertext to a non-existent link if I don't export my notes as well. Part of the reason that keeping notes/article separate is that I have others interested in the articles and, if I need to send them a copy, I want to get my junk out of there and have the original. I suppose I could just keep two copies, though? I think this idea could be useful to others and actually wouldn't doubt if someone has an awesome setup for something like this already. Thanks for any suggestions! John
[O] Re: Using orgmode to take "inline notes" for research
Jeff Horn wrote > Have you tried using org-inline-task without a TODO keyword? These super-deep > "headlines" aren't > treated as headlines, so they don't break doc structure, but they are > foldable, and unlike COMMENT keyword headlines, > they're printable. The only problem I've run into is have a lot to say in an > inline note. In that case, one could just insert plaintext > between the pseudo-headings of the inline note (try it to see what I mean). > I haven't tried printing these long notes, but I imagine it would work. My org-modules seems to have org-inlinetask But I dont seem to see any of these variables available in my emacs emacs version 23 org version 7.5
Re: [O] Using orgmode to take "inline notes" for research
Hi John, Interesting use case, I definitely see the utility. I think that blocks may be an appropriate solution, for example if you enclose your notes in "notes" blocks, then it should be easy to control whether or not they are exported... Using the following code, you can control whether notes enclosed in "notes" blcks will be exported by changing the value of the *export-my-notes* variable, when it is nil your notes will not be exported, when t they will be exported as quoted text. #+begin_src emacs-lisp (defvar *export-my-notes* nil) (defun org-exp-block-process-notes (body &rest headers) (if *export-my-notes* (format "\n#+begin_quote\n%s\n#+end_quote\n" body) "")) (org-export-blocks-add-block '(notes org-exp-block-process-notes nil)) #+end_src Hope this Helps -- Eric This works for me with the attached Org-mode file. * top Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enimad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. #+begin_notes eric's notes on lorem #+end_notes Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enimad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. John Hendy writes: > Hi, > > > One thing I really like to use orgmode for is research. Lately, > there's a mass of stuff on-line that I've been reading though and am > about to start reading through a series of articles and had the idea > to yank them into org for "inline notes." > > My current experiment has been: > - wget the website page > - run a custom script of simple sed stuff to get the major stuff > converted ( & -> /, "e; -> ", etc.) > - turn things into headlines where applicable > - manually tweak the rest > > What I'd like to do is find some way to take notes in the article and > would like some suggestions from anyone who's done this. On one hand, > I see the idea of keeping a separate headline for notes, and for a > series of articles, my file might look like this: > ,--- > | * Article 1 > | ** Notes on article 1 > | * Article 2 > | ** Notes on article 2 > `--- > > One advantage to this is that I could very easily add :noexport: to my > notes and print off a hard copy of the article if I want it, and it > would also be easy to tag my notes :notes: and then replace-string to > turn the Article :export: into :noexport: and :notes: into :export:. > Then I'd have an easy to print copy of my notes for each article. > > On the other hand, I like quoting when I use notes, and could see it > as advantageous to have something like: > ,--- > | * Article 1 > | It goes along and says x, y, and z. > | --- Me: that's interesting and here are my thoughts. > | > | It continues along saying all kinds of other things and my comments > are interjected whenever I want. > `--- > > I think that might be more useful for studying things later, as I get > to see an "annotated" version with my thoughts at the time I read it. > What it *doesn't* allow for is the easy printing of both the article > and the notes separately if I want. > > Would someone suggest a way that I might be able to have the best of > both worlds? Some of my own not-at-all-hashed-out-ideas included: > - using footnotes since org has easy ways to jump from one to another, > but this would be tough when it came to actual footnotes, which there > will definitely be plenty of. > > - highlighting the text I want to quote and then using refile somehow > to send it off to my notes section with my comments. This would be > cool if I could, at the same time, add an org-mode link to and from > the notes and original section, but also if I could turn that link off > when I export to PDF so I don't have hypertext to a non-existent link > if I don't export my notes as well. > > Part of the reason that keeping notes/article separate is that I have > others interested in the articles and, if I need to send them a copy, > I want to get my junk out of there and have the original. I suppose I > could just keep two copies, though? > > I think this idea could be useful to others and actually wouldn't > doubt if someone has an awesome setup for something like this already. > > > Thanks for any suggestions! > John > > -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] Using orgmode to take "inline notes" for research
Have you tried using org-inline-task without a TODO keyword? These super-deep "headlines" aren't treated as headlines, so they don't break doc structure, but they are foldable, and unlike COMMENT keyword headlines, they're printable. The only problem I've run into is have a lot to say in an inline note. In that case, one could just insert plaintext between the pseudo-headings of the inline note (try it to see what I mean). I haven't tried printing these long notes, but I imagine it would work. On Tue, Apr 5, 2011 at 10:02 PM, John Hendy wrote: > Hi, > > > One thing I really like to use orgmode for is research. Lately, > there's a mass of stuff on-line that I've been reading though and am > about to start reading through a series of articles and had the idea > to yank them into org for "inline notes." > > My current experiment has been: > - wget the website page > - run a custom script of simple sed stuff to get the major stuff > converted ( & -> /, "e; -> ", etc.) > - turn things into headlines where applicable > - manually tweak the rest > > What I'd like to do is find some way to take notes in the article and > would like some suggestions from anyone who's done this. On one hand, > I see the idea of keeping a separate headline for notes, and for a > series of articles, my file might look like this: > ,--- > | * Article 1 > | ** Notes on article 1 > | * Article 2 > | ** Notes on article 2 > `--- > > One advantage to this is that I could very easily add :noexport: to my > notes and print off a hard copy of the article if I want it, and it > would also be easy to tag my notes :notes: and then replace-string to > turn the Article :export: into :noexport: and :notes: into :export:. > Then I'd have an easy to print copy of my notes for each article. > > On the other hand, I like quoting when I use notes, and could see it > as advantageous to have something like: > ,--- > | * Article 1 > | It goes along and says x, y, and z. > | --- Me: that's interesting and here are my thoughts. > | > | It continues along saying all kinds of other things and my comments > are interjected whenever I want. > `--- > > I think that might be more useful for studying things later, as I get > to see an "annotated" version with my thoughts at the time I read it. > What it *doesn't* allow for is the easy printing of both the article > and the notes separately if I want. > > Would someone suggest a way that I might be able to have the best of > both worlds? Some of my own not-at-all-hashed-out-ideas included: > - using footnotes since org has easy ways to jump from one to another, > but this would be tough when it came to actual footnotes, which there > will definitely be plenty of. > > - highlighting the text I want to quote and then using refile somehow > to send it off to my notes section with my comments. This would be > cool if I could, at the same time, add an org-mode link to and from > the notes and original section, but also if I could turn that link off > when I export to PDF so I don't have hypertext to a non-existent link > if I don't export my notes as well. > > Part of the reason that keeping notes/article separate is that I have > others interested in the articles and, if I need to send them a copy, > I want to get my junk out of there and have the original. I suppose I > could just keep two copies, though? > > I think this idea could be useful to others and actually wouldn't > doubt if someone has an awesome setup for something like this already. > > > Thanks for any suggestions! > John > > -- Jeffrey Horn http://www.failuretorefrain.com/jeff/
[O] page break after TOC?
I'd like my page1 to be on a separate page from the TOC. How do I insert a pagebreak to do this? If I do it here: ,--- | * Section 1 | \newpage | test in section 1 `--- I get the TOC, then the Section 1 title, then a page break, and then the text. Thanks! John
[O] export options toc:t depends on num:t
Hi, Maybe this is obvious to most, but I was puzzled by it. It seems that ,--- | #+options: toc:t `--- will not function when paired with: ,--- | #+options: toc:t num:nil `--- I didn't know that. I say that perhaps it's obvious, because I guess when the toc does show up, it's format is: ,--- | 1 Section 1 pg# | 2 Section 2 pg# | ... `--- But I wouldn't think it would be impossible to just have: ,--- | Section 1 pg# | Section 2 pg# | ... `--- Anyway, if these two are necessary, perhaps the manual could be updated (http://orgmode.org/manual/Export-options.html#Export-options): ,--- | toc: turn on/off table of contents, or set level limit (integer); requires num:t or no setting (t is default for num) `--- Or something to that effect. John
[O] Using orgmode to take "inline notes" for research
Hi, One thing I really like to use orgmode for is research. Lately, there's a mass of stuff on-line that I've been reading though and am about to start reading through a series of articles and had the idea to yank them into org for "inline notes." My current experiment has been: - wget the website page - run a custom script of simple sed stuff to get the major stuff converted ( & -> /, "e; -> ", etc.) - turn things into headlines where applicable - manually tweak the rest What I'd like to do is find some way to take notes in the article and would like some suggestions from anyone who's done this. On one hand, I see the idea of keeping a separate headline for notes, and for a series of articles, my file might look like this: ,--- | * Article 1 | ** Notes on article 1 | * Article 2 | ** Notes on article 2 `--- One advantage to this is that I could very easily add :noexport: to my notes and print off a hard copy of the article if I want it, and it would also be easy to tag my notes :notes: and then replace-string to turn the Article :export: into :noexport: and :notes: into :export:. Then I'd have an easy to print copy of my notes for each article. On the other hand, I like quoting when I use notes, and could see it as advantageous to have something like: ,--- | * Article 1 | It goes along and says x, y, and z. | --- Me: that's interesting and here are my thoughts. | | It continues along saying all kinds of other things and my comments are interjected whenever I want. `--- I think that might be more useful for studying things later, as I get to see an "annotated" version with my thoughts at the time I read it. What it *doesn't* allow for is the easy printing of both the article and the notes separately if I want. Would someone suggest a way that I might be able to have the best of both worlds? Some of my own not-at-all-hashed-out-ideas included: - using footnotes since org has easy ways to jump from one to another, but this would be tough when it came to actual footnotes, which there will definitely be plenty of. - highlighting the text I want to quote and then using refile somehow to send it off to my notes section with my comments. This would be cool if I could, at the same time, add an org-mode link to and from the notes and original section, but also if I could turn that link off when I export to PDF so I don't have hypertext to a non-existent link if I don't export my notes as well. Part of the reason that keeping notes/article separate is that I have others interested in the articles and, if I need to send them a copy, I want to get my junk out of there and have the original. I suppose I could just keep two copies, though? I think this idea could be useful to others and actually wouldn't doubt if someone has an awesome setup for something like this already. Thanks for any suggestions! John
[O] italics inside quotation marks -> LaTeX not working
Hi,
When exporting to LaTeX/PDF and using org-mode markup for italics
inside quotation marks, the /'s are getting left alone. So...
,---
| /word/
`---
works fine, but
,---
| He said, "/word/"
`---
Does not.
Any suggestions on this? I could convert everything to \emph{}, but
that makes for uglier reading when using the org file itself.
Thanks,
John
Re: [O] org-kill-line sometimes crashes emacs
Thomas Jack wrote:
> Steps to reproduce:
>
> Include an entry like this in your org-capture-templates:
> ("t" "Todo" entry (file+headline "~/org/gtd.org" "Tasks")
> "* TODO %?\n %i\n %a")
>
> Now, delete everything in ~/org/gtd.org except for a lone "Tasks" headline.
>
> Put point on the next line, and start a capture with the template
> above. Move point down to the beginning of the line with the "Tasks"
> link, and C-k (org-kill-line).
>
> For me, emacs crashes with "Fatal error (6)Aborted". If I first modify
> the link and undo the changes, there is no crash.
>
> Can anyone else reproduce?
>
Yes, I can. What version of emacs are you using?
Mine is: GNU Emacs 24.0.50.1 (x86_64-unknown-linux-gnu, GTK+ Version
2.22.0) of 2011-03-16. I'll update
I tried running emacs under gdb, but I cannot reproduce it in that
situation. Nasty.
Nick
PS. I tried it with the following minimal.emacs by invoking emacs like
this:
emacs -Q -l ~/minimal.emacs
--8<---cut here---start->8---
;;; constant part
(add-to-list 'load-path (expand-file-name "~/src/emacs/org/org-mode/lisp"))
(add-to-list 'auto-mode-alist '("\\.\\(org\\|org_archive\\|txt\\)$" . org-mode))
(require 'org-install)
(global-set-key "\C-cl" 'org-store-link)
(global-set-key "\C-ca" 'org-agenda)
(setq org-capture-templates
'( ("T" "Todo" entry (file+headline "~/org/gtd.org" "Tasks") "* TODO %?\n %i\n
%a")))
--8<---cut here---end--->8---
[O] [PATCH] Problem with html export of description list items
Ethan Ligon are.berkeley.edu> writes: > > I've just stumbled across what I regard as a bug in the html export of > description list items. > > The problem has to do with whether the specification of a description > list includes a trailing space or not; i.e., whether "- Item ::" is > treated the same way as "- Item :: ". LaTeX export treats these as > identical. Html export gets confused about what the description list > item is, and winds up generating a "???" for the description. > Having done the work to describe the problem, it wasn't hard to find a solution. In this case that's a one character change to a regexp in org-html.el. Here's the patch: diff --git a/lisp/org-html.el b/lisp/org-html.el index d19d88b..005a0f7 100644 --- a/lisp/org-html.el +++ b/lisp/org-html.el @@ -2501,7 +2501,7 @@ the alist of previous items." (concat "[ \t]*\\(\\S-+[ \t]*\\)" "\\(?:\\[@\\(?:start:\\)?\\([0-9]+\\|[A-Za-z]\\)\\]\\)?" "\\(?:\\(\\[[ X-]\\]\\)[ \t]+\\)?" - "\\(?:\\(.*\\)[ \t]+::[ \t]+\\)?" + "\\(?:\\(.*\\)[ \t]+::[ \t]*\\)?" "\\(.*\\)") line) (let* ((checkbox (match-string 3 line)) (desc-tag (or (match-string 4 line) "???"))
[O] [Bug] Problem with html export of description list items
I've just stumbled across what I regard as a bug in the html export of
description list items.
The problem has to do with whether the specification of a description
list includes a trailing space or not; i.e., whether "- Item ::" is
treated the same way as "- Item :: ". LaTeX export treats these as
identical. Html export gets confused about what the description list
item is, and winds up generating a "???" for the description.
Here's an example.
#+begin_src org
* Illustration of bug in html export
- Has a space after the colons :: so will work in latex and html
- No space after the colons ::so won't work in html
- Has a terminating space ::
- So it works in both html and latex export!
- Even though it's difficult to distinguish from the next example.
- Lacks a terminating space ::
- *Doesn't* work in html export, does in latex.
#+end_src
The relevant bit of the html export
#+begin_src html
Illustration of bug in
html export
This has a space after the colonsso will work
???This doesn't have a space after the colons ::so won't work
Has a terminating space
So it works in both html and latex export!
Even though it's difficult to distinguish from the next example.
???Lacks a terminating space ::
Doesn't work in html export, does in latex.
#+end_src
The relevant bit of the latex export looks like this:
#+begin_src latex
\vspace*{1cm}
\section{Illustration of bug in html export}
\label{sec-1}
\begin{description}
\item[This has a space after the colons] so will work
\item[This doesn't have a space after the colons] so won't work
\item[Has a terminating space]
\begin{itemize}
\item So it works in both html and latex export!
\item Even though it's difficult to distinguish from the next example.
\end{itemize}
\item[Lacks a terminating space]
\begin{itemize}
\item \textbf{Doesn't} work in html export, does in latex.
\end{itemize}
\end{description}
#+end_src
Thanks for any help!
-Ethan Ligon
[O] org-kill-line sometimes crashes emacs
Steps to reproduce:
Include an entry like this in your org-capture-templates:
("t" "Todo" entry (file+headline "~/org/gtd.org" "Tasks")
"* TODO %?\n %i\n %a")
Now, delete everything in ~/org/gtd.org except for a lone "Tasks" headline.
Put point on the next line, and start a capture with the template
above. Move point down to the beginning of the line with the "Tasks"
link, and C-k (org-kill-line).
For me, emacs crashes with "Fatal error (6)Aborted". If I first modify
the link and undo the changes, there is no crash.
Can anyone else reproduce?
[O] Bug: datetree capture from agenda [7.5 (release_7.5.135.g7021f.dirty)]
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
Launch Emacs with no startup files
$ emacs -Q
; evaluate these 2 forms in the *scratch* buffer
(require 'org-install)
(setq org-capture-templates
'(("h" "Journal headline" entry (file+datetree "/tmp/journal.org"))
("n" "Journal note" plain (file+datetree "/tmp/journal.org"
; follow this sequence
M-x org-agenda
a ; for current week or day agenda
k c ; agenda action for capture
h ; to add a headline entry in journal for today
[...] ; add some text and C-c C-c to save
k c
n ; add a note in journal for today
[...] ; add some text and save
b ; back one week
k c
h ; add a headline entry in journal for one week ago
[...]
b ; go back one more week
k c
n ; add a note in journal for two weeks ago
[...]
Look at the journal file created.
I would expect to see a date tree with a note entry under the
date two weeks ago, a headline entry under the date one week ago
and a note and headline entry under today's date.
What I see is the date tree correctly constructed. The note and
headline under today's date are correct filed. The headline
entry from one week ago is correctly filed. The date headline
from two weeks ago is correctly created but the text of the note
entry itself is wrongly appended at the end of the file under
today's date.
That doesn't seem right to me.
Thanks,
Phil
Emacs : GNU Emacs 24.0.50.3 (x86_64-apple-darwin10.6.0, NS
apple-appkit-1038.35)
of 2011-02-17 on bo
Package: Org-mode version 7.5 (release_7.5.135.g7021f.dirty)
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-capture-templates '(("h" "Journal headline" entry (file+datetree
"~/tmp/journal.org"))
("n" "Journal note" plain (file+datetree
"~/tmp/journal.org")))
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-export-blocks-postblock-hook '(org-exp-res/src-name-cleanup)
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-babel-hide-result-toggle-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-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 '((lambda nil
(org-add-hook (quote change-major-mode-hook) (quote
org-show-block-all) (quote append) (quote local)))
(lambda nil
(org-add-hook (quote change-major-mode-hook) (quote
org-babel-show-result-all) (quote append) (quote local)))
org-babel-result-hide-spec 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-occur-hook '(org-first-headline-recenter)
org-from-is-user-regexp "|\\"
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-for-lists)
org-metadown-hook '(org-babel-pop-to-session-maybe)
org-export-blocks '((src org-babel-exp-src-block nil) (comment
org-export-blocks-format-comment t)
(ditaa org-export-blocks-format-ditaa nil) (dot
org-export-blocks-format-dot nil))
)
Re: [O] Re: unnumbered subsections in latex export
On Wed, Apr 6, 2011 at 00:57, Eric S Fraga wrote:
> Aankhen writes:
>
> [...]
>
>> Thank you for the clarifications. I’m going to talk a bit more about
>> HTML as that’s where I have the most experience. I am in agreement
>> with you when you say that builtin support for acronyms would be
>> useful (although I feel it would be good to generalize it to
>> abbreviations, if that can also be supported in other backends). When
>> you have the following markup:
>>
>> ,
>> | HTML is a
>> | language for marking up documents. The most current version
>> | of HTML is 4.01.
>> | The successor to HTML, HTML5, is currently under development.
>> `
>>
>> The expansion is invisible by default; it shows up in a tooltip when
>> you hover over the text. You can try a live example to see for
>> yourself.[1] In this way, the expansion is always there when you need
>> it (and you can distinguish between multiple terms sharing the same
>> acronym, should the need ever arise), but it takes up no space if you
>> don’t.
>
> There are those of us that, for one reason or another, do *not* use a
> mouse or any other graphical pointer. Tooltips do not appear ever in
> those cases. I would like a solution that does not rely on any
> particular graphical interface paradigm, basically!
>
> Of course, I know that I am in the minority here... but accessibility is
> always an important factor and one that should not be ignored, IMO.
Yes, I absolutely understand the concern, and I must confess I had
overlooked it. I’m not certain how text-based browsers deal with
‘title’ attributes in general. I see that Lynx, for one, can make use
of them on links.[1] Unfortunately, I can’t find any material on other
text mode browsers. Everything I read points at them mostly ignoring
‘title’. Ideally, text mode browsers would provide a way to get at
it, as there is nothing tying the attribute to a graphical interface;
in practice, it would seem that they took the easy way out.
Understandable, given the rampant abuse of the tag.
>
>> I would suggest that, were Org to gain support for acronyms and/or
>> abbreviations, they be exported in HTML using ‘abbr’ (‘acronym’ is
>> deprecated thanks to HTML5) with the ‘title’ defined for each
>> occurrence, and with CSS to ensure consistent rendering, along these
>> lines:
>>
>> ,
>> | abbr { font-variant: small-caps; border-bottom: 1px dashed; cursor: help; }
>> `
>
> Does this still rely on tooltips?
Yes. This CSS is only meant to standardize the presentation across
graphical browsers. It is entirely possible to use CSS to display the
expansion, I’m just not sure of the utility (and it relies on the
browser not throwing away CSS):
,
| abbr[title]:after, acronym[title]:after { content: " [" attr(title) "]"; }
`
It defeats the purpose of the exercise in any case.
>> I can see the argument for having a list at the end and linking each
>> definition instead. I feel that’s less convenient, however, as (a) it
>> means temporarily losing your place in the document and (b) bunched-up
>> anchors at the end of a document are a pain. Of course,
>> alternatively, each acronym/abbreviation could be marked up only at
>> the first occurrence; that seems like it would be easy to implement as
>> a configuration option.
>
> I would like a combination of both, whenever possible: fully expanded
> def'n in the text at the first occurrence and links to the list of
> abbreviations/acronyms at the end for subsequent occurrences (modulo the
> problems with double-links etc, for which I cannot propose a solution
> unfortunately).
Taking into consideration the fact that text-based browsers seem to
ignore ‘title’, I can only agree with you. How about something like
this:
,
| I’m going to introduce a new TLA (Three-Letter
| Acronym). This TLA is a very
| special TLA as it comes straight from my
| heart.
| ⋮
| Acronyms & abbreviations
|
| TLA
| Three-Letter Acronym
| YAAA
| Yet Another Alliterative Acronym
| Dr.
| Doctor
|
`
In case of a nested link, maybe a break in the outer link could solve it:
,
| Let us read http://www.w3.org/TR/html401/";>the
| HTML[def]http://www.w3.org/TR/html401/";>
| specification together.
`
Not particularly pretty, but it seems to get the job done. Just one option.
At any rate, thanks for pointing this out.
Aankhen
[1]: http://diveintoaccessibility.org/day_14_adding_titles_to_links.html
[O] New features for the exporters?
Hi Eric, Aankhen and al., Just answering very quickly on one sole idea of the exchanged ones in this thread: Eric S Fraga wrote: > Aankhen writes: >> The expansion is invisible by default; it shows up in a tooltip when you >> hover over the text. You can try a live example to see for yourself.[1] In >> this way, the expansion is always there when you need it (and you can >> distinguish between multiple terms sharing the same acronym, should the >> need ever arise), but it takes up no space if you don’t. > > There are those of us that, for one reason or another, do *not* use a mouse > or any other graphical pointer. Tooltips do not appear ever in those cases. > I would like a solution that does not rely on any particular graphical > interface paradigm, basically! > > Of course, I know that I am in the minority here... but accessibility is > always an important factor and one that should not be ignored, IMO. I don't think you're part of the minority. Anyway, there are good reasons to have tooltips (on a wish-basis), but other good reasons to have the list of acronyms at the end of the document (on a wish-basis): to get a readable and very accessible document when printed! Best regards, Seb -- Sébastien Vauban
[O] Bug: babel sql: no results are returned if the first would be NULL [7.5]
Hello,
When returning results from a postgresql database, if the first value is
NULL then no results are returned.
Versions: orgmode git commit c01c2ad Fri Mar 18, postgresql 9.0.3.
This works as expected:
#+begin_src sql :engine postgresql :cmdline -d postgres
SELECT 1 as A, NULL as B;
#+end_src
#+results:
| a | b |
| 1 | |
#+begin_src sql :engine postgresql :cmdline -d postgres
SELECT 1 as A, 1 as B;
#+end_src
#+results:
| a | b |
| 1 | 1 |
When the first value is NULL then only the column names are returned:
#+begin_src sql :engine postgresql :cmdline -d postgres
SELECT NULL as A,1 as B;
#+end_src
#+results:
| a | b |
|---+---|
whereas I would have expected this:
#+begin_example
| a | b |
| | 1 |
#+end_example
A slightly unsatisfactory workaround using coalesce, is:
#+begin_src sql :engine postgresql :cmdline -d postgres
SELECT coalesce(NULL,'NULL') as A,1 as B;
#+end_src
#+results:
| a| b |
| NULL | 1 |
Also, this may be unrelated, when trying to return tuples only, using
"-t", this happens:
#+begin_src sql :engine postgresql :cmdline -d postgres -t
SELECT NULL as A,1 as B;
#+end_src
#+results:
| | | | | |
|---+---+---+---+---|
| | | | | |
Thanks,
Myles
Emacs : GNU Emacs 23.3.1 (x86_64-unknown-linux-gnu, GTK+ Version
2.22.1) of 2011-03-10 on bitzer.hoetzel.info
Package: Org-mode version 7.5
current state:
==
(setq
org-log-done 'time
org-export-preprocess-before-backend-specifics-hook
'(org-inlinetask-export-handler) org-clock-in-switch-to-state
'bh/clock-in-to-next org-agenda-insert-diary-extract-time t
org-export-latex-after-initial-vars-hook
'(org-beamer-after-initial-vars) org-todo-keyword-faces
'(("TODO" :foreground "red" :weight bold) ("NEXT" :foreground
"blue" :weight bold) ("WAITING" :foreground "yellow" :weight bold)
("DONE" :foreground "forest green" :weight bold) ("MAYBE" :foreground
"goldenrod" :weight bold) ("CANCELLED" :foreground "orangered" :weight
bold)) org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook) org-agenda-custom-commands '(("w" "Tasks
waiting on something" tags "waiting/!" ((org-use-tag-inheritance nil)
(org-agenda-todo-ignore-scheduled nil)
(org-agenda-todo-ignore-deadlines nil)
(org-agenda-todo-ignore-with-date nil) (org-agenda-overriding-header
"Waiting tasks")) ) ("r" "Refile New Notes and Tasks" tags
"LEVEL=2+refile" ((org-agenda-todo-ignore-with-date nil)
(org-agenda-todo-ignore-deadlines nil)
(org-agenda-todo-ignore-scheduled nil) (org-agenda-overriding-header
"Refilable tasks")) )
("N" "Notes" tags
"note" ((org-agenda-overriding-header "Notes"))) ("n" "Next" tags-todo
"-WAITING-CANCELLED/!NEXT" ((org-agenda-overriding-header "Next
Tasks"))) ("u" "Unscheduled Next" tags-todo
"-WAITING-CANCELLED-SCHEDULED={.}/!NEXT" ((org-agenda-overriding-header
"Unscheduled NEXT items: "))) ("p" "Projects" tags-todo
"LEVEL=2-refile|LEVEL=1+refile/!-DONE-CANCELLED-WAITING-MAYBE"
((org-agenda-skip-function (quote
bh/skip-non-projects)) (org-agenda-overriding-header "Projects"))
)
("o" "Other (Non-Project) tasks" tags-todo
"LEVEL=2-refile|LEVEL=1+refile/!-DONE-CANCELLED-WAITING-MAYBE"
((org-agenda-skip-function (quote
bh/skip-projects)) (org-agenda-overriding-header "Other non-project
tasks")) )
("A" "Archivable tasks" tags
"LEVEL=2-refile/DONE|CANCELLED" ((org-agenda-overriding-header "Tasks
to Archive"))) ("h" "Habits" tags-todo "STYLE=\"habit\""
((org-agenda-todo-ignore-with-date nil)
(org-agenda-todo-ignore-scheduled nil)
(org-agenda-todo-ignore-deadlines nil) (org-agenda-overriding-header
"Habits")) ) ("#" "Stuck Projects" tags-todo
"LEVEL=2-refile|LEVEL=1+refile/!-DONE-CANCELLED" ((org-agenda-skip-function
(quote bh/skip-non-stuck-projects)) (org-agenda-overriding-header
"Stuck projects")) )
("c" "Select default clocking task" tags
"LEVEL=2-refile" ((org-agenda-skip-function
(quote (org-agenda-skip-subtree-if
(quote notregexp) "^\\*\\* Organisation")))
(org-agenda-overriding-header "Set default clocking task with C-u C-u
I")) ) )
org-agenda-files '("~/org/gtd.org" "~/org/phd.org" "~/org/rh.org"
"~/org/home.org" "~/org/notes/refile.org" "~/org/diary.org"
"~/org/thesisPlan/thesis_plan.org"
"~/docs/relKpaper/org/model_runs.org"
"~/org/papers/shm/linked_nodes.org" "~/org/papers/prov/prov.org")
org-agenda-include-diary t org-babel-load-languages '((R . t)
(emacs-lisp . t) (org . t) (sql . t) (python . t) (sh . t) (latex . t)
(ledger . t)) org-clock-into-drawer "CLOCK" org-metaup-hook
'(org-babel-load-in-session-maybe)
org-export-preprocess-after-blockquote-hook
'(org-special-blocks-make-special-cookies)
org-after-todo-state-change-hook '(org-clock-out-i
[O] [agenda] %% questions
Hi all The items 2 and 4 in the following example are not shown in the agenda with today's release_7.5-135-g7021f70. Question about item 2: Is this a bug since the items 1 and 3 are shown? Question about item 4: The user manual tells that %% must start at the first column. What would be required to allow indentation? * item 1: shown SCHEDULED: <%%(diary-float t 2 1) 12:00> * item 2: not shown <%%(diary-float t 2 1) 12:00> * item 3: shown <%%(diary-float t 2 1)> * item 4: not shown %%(diary-anniversary 04 05 2000) item 4 is %d years old * item 5: shown %%(diary-anniversary 04 05 2000) item 5 is %d years old Michael
Re: [O] Re: unnumbered subsections in latex export
Aankhen writes:
[...]
> Thank you for the clarifications. I’m going to talk a bit more about
> HTML as that’s where I have the most experience. I am in agreement
> with you when you say that builtin support for acronyms would be
> useful (although I feel it would be good to generalize it to
> abbreviations, if that can also be supported in other backends). When
> you have the following markup:
>
> ,
> | HTML is a
> | language for marking up documents. The most current version
> | of HTML is 4.01.
> | The successor to HTML, HTML5, is currently under development.
> `
>
> The expansion is invisible by default; it shows up in a tooltip when
> you hover over the text. You can try a live example to see for
> yourself.[1] In this way, the expansion is always there when you need
> it (and you can distinguish between multiple terms sharing the same
> acronym, should the need ever arise), but it takes up no space if you
> don’t.
There are those of us that, for one reason or another, do *not* use a
mouse or any other graphical pointer. Tooltips do not appear ever in
those cases. I would like a solution that does not rely on any
particular graphical interface paradigm, basically!
Of course, I know that I am in the minority here... but accessibility is
always an important factor and one that should not be ignored, IMO.
> I would suggest that, were Org to gain support for acronyms and/or
> abbreviations, they be exported in HTML using ‘abbr’ (‘acronym’ is
> deprecated thanks to HTML5) with the ‘title’ defined for each
> occurrence, and with CSS to ensure consistent rendering, along these
> lines:
>
> ,
> | abbr { font-variant: small-caps; border-bottom: 1px dashed; cursor: help; }
> `
Does this still rely on tooltips?
> I can see the argument for having a list at the end and linking each
> definition instead. I feel that’s less convenient, however, as (a) it
> means temporarily losing your place in the document and (b) bunched-up
> anchors at the end of a document are a pain. Of course,
> alternatively, each acronym/abbreviation could be marked up only at
> the first occurrence; that seems like it would be easy to implement as
> a configuration option.
I would like a combination of both, whenever possible: fully expanded
def'n in the text at the first occurrence and links to the list of
abbreviations/acronyms at the end for subsequent occurrences (modulo the
problems with double-links etc, for which I cannot propose a solution
unfortunately).
Thanks,
eric
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.134.gb869b)
Re: [O] Re: unnumbered subsections in latex export
Hi Sébastien,
2011/4/5 Sébastien Vauban :
> Aankhen wrote:
>> [snip]
>> Acronyms are natively supported in HTML. That is all.
>
> Thanks for reporting this. Wasn't aware of it. Though, that does not alter the
> need (at least, what I consider so) for acronyms handling in/from Org.
>
> Let's clarify what I'm talking about -- I know, I should have done it earlier.
>
> I want to be able to say, in my Org file, that DNS is an acronym, for example.
> I'm thinking -- brainstorming! -- at a solution _such as_ adding accolades
> around the acronyms:
>
> --8<---cut here---start->8---
> This paper talks about {DNS} clients and {DNS} servers...
> --8<---cut here---end--->8---
>
> In LaTeX, this should have to be translated to:
>
> --8<---cut here---start->8---
> This paper talks about \acro{DNS} clients and \acro{DNS} servers...
> --8<---cut here---end--->8---
>
> And the effects would be that:
>
> 1. the first occurrence of the acronym would be expanded in the PDF, while
> others not -- this is customizable!
>
> 2. every occurrence would be a link to the list of acronyms, at the end of the
> document.
>
> In HTML, I would expect internal links to a list of acronyms at the end of the
> document.
>
> I was thinking at preprocessing, because some smart things need to be done:
>
> - expanding the first occurrence of the acronym (if wished) with its
> definition, not the following;
>
> - in the list, at the end of the document, only list acronym definitions for
> the acronyms that have been used in the document.
Thank you for the clarifications. I’m going to talk a bit more about
HTML as that’s where I have the most experience. I am in agreement
with you when you say that builtin support for acronyms would be
useful (although I feel it would be good to generalize it to
abbreviations, if that can also be supported in other backends). When
you have the following markup:
,
| HTML is a
| language for marking up documents. The most current version
| of HTML is 4.01.
| The successor to HTML, HTML5, is currently under development.
`
The expansion is invisible by default; it shows up in a tooltip when
you hover over the text. You can try a live example to see for
yourself.[1] In this way, the expansion is always there when you need
it (and you can distinguish between multiple terms sharing the same
acronym, should the need ever arise), but it takes up no space if you
don’t.
I would suggest that, were Org to gain support for acronyms and/or
abbreviations, they be exported in HTML using ‘abbr’ (‘acronym’ is
deprecated thanks to HTML5) with the ‘title’ defined for each
occurrence, and with CSS to ensure consistent rendering, along these
lines:
,
| abbr { font-variant: small-caps; border-bottom: 1px dashed; cursor: help; }
`
I can see the argument for having a list at the end and linking each
definition instead. I feel that’s less convenient, however, as (a) it
means temporarily losing your place in the document and (b) bunched-up
anchors at the end of a document are a pain. Of course,
alternatively, each acronym/abbreviation could be marked up only at
the first occurrence; that seems like it would be easy to implement as
a configuration option.
> For the readability of the Org buffer, and for the behavior that we could
> expect, maybe a new link type would make it?
The only thing is, links can’t be nested, can they? I’m thinking of a
situation like ‘read the HTML 4.01 specification online’, where the
entire text is a link and ‘HTML’ is an abbreviation. I suppose this
might not be a particularly important use case.
> I would expect a similar treatment for the bibliography: having some built-in
> representation for that in Org, and have the exporters make it to both LaTeX
> and HTML (and ...).
I have no experience or opinions when it comes to bibliographies, so
I’ll abstain from commenting beyond saying that it seems logical to
have a centralized database at least within an Org file. :-)
Aankhen
[1]: https://developer.mozilla.org/en/HTML/Element/acronym
[O] org-babel ocaml List append problems
I have just discovered org-babel supports ocaml and I've just started to learn it. My problem is when appending two lists together, when run through org-babel returns a error message. I would try and run this code [3;2;3] @ [3;2;3;4;5];; and get a error message saying "Invalid function: 3" Is there a solution to this as the code should work? James
Re: [O] [Bug][BABEL][R] Headers of the tables are not recognized during the export.
"Eric Schulte" writes: >> > > Thanks for catching this, I've just pushed up a fix for this issue. The > column headers were being lost during the export processing. > >> >> >> Also if I use :cache yes header. The html export recomputes the block. >> Wouldn't it be reasonable to have the exporter take into account the :cache >> header? >> > > The exporter *does* take into account the :cache header, however, due to > the error above, the values of the inputs to the block of R code were > different on export than on interactive evaluation, so the cache was > invalidated as if the contents of the table had changed. Thanks Eric for your work. This all org-babel thing is just amassing. Vitalie. > > Cheers -- Eric > >> >> Thanks, >> Vitalie.
Re: [O] Why are special properties like CLOSED etc. not in the properties drawer?
Hi all For many use cases I would like one of both opposites: 1) the option to have e. g. CLOSED: as :CLOSED: in a drawer and on its own line as mentioned before 2) the option to have e. g. :CATEGORY: without any drawer, like: * holidays :CATEGORY: holiday ** xmas <2011-12-25 Sun> ** new year <2012-01-01 Sun> instead of first looking at: * holidays :PROPERTIES:... ** xmas and then navigate to :PROPERTIES: to open it: * holidays :PROPERTIES: :CATEGORY: holiday :END: ** xmas To see the category directly, of course there are `C-u C-u C-u ', column view and maybe more, but these might not always be preferred. As a coincidence or not in the choice of the property for the example above, :CATEGORY: is the only special property that is allowed as a key in the properties drawer, see http://orgmode.org/manual/Special-properties.html and it is also the only special property that can not live (yet?) outside this drawer. Michael On Tue, Apr 5, 2011 at 13:36, Marcel van der Boom wrote: > Hi, > > I've been wondering about this for a bit. It would make things a bit > more consistent for me if all properties are in the 'properties'-drawer. > Or am I missing something here?
Re: [O] Re: Update org-mode
On 05/04/11 16:31, Dror Atariah wrote: Let me summarize the steps I carried out eventually, to use the package manager. Note, I am using emacs 23 based editor which was shipped with org-mode 6.33. * Updating Follow the steps: ** Intsall the package manager *** Download the =packages.el= file from http://repo.or.cz/w/emacs.git/blob_plain/1a0a666f941c99882093d7bd08ced15033bc3f0c:/lisp/emacs-lisp/package.el. Save in in =~/Library/elisp= for example. *** Add the following code to the =.emacs=: #+BEGIN_SRC elisp (setq load-path (cons "~/Library/elisp" load-path)) (require 'package) (package-initialize) #+END_SRC *** Verify To verify this part, in /emacs/ hit =M-x list-packages RET org=. Here you should see a list of optional packages. /Note:/ you may ignore the warning: =failed to download org-mode archive=. ** Updating org-mode *** Enter the =list-packages= Hit =M-x list-packages RET=. In there mark for installation by =i= the org package and the =x= for the actual installation. *** Restart emacs *** Verify Hit =M-x locate-library RET org= to verify the installation. You should now have org-mode up and running. Thank you all! Dror Glad you got it working. Thanks for posting the follow up to the list, which will probably help someone in future. Ian.
Re: [O] Re: orgmode manual improvement suggestion.
[Noch ein mal: I forgot to copy the list. Apologies... to Izzie in particular who is receiving multiple instances. At least, I edited this version down a bit.] Izzie wrote: > ... > I was hoping org mode documentation had been made with org mode, I wasn't > expecting a texi file format I had not been introduced to yet. I can use it > to > generate the manual, but I can't jump into modifying the source. > Texinfo format predates org by 20 years or so and is the GNU software standard for documentation. Since org is GNU software, it has to conform to the standard. It might be possible to do a texinfo exporter but a) nobody has done that (yet) and b) it would be a lot of effort to rewrite the documentation in org. > > Thanks. how come this is not part of the manual ? It is a good practice to > provide information about where to find the manual and how to produce a > specific format (especially when not providing it). > *Which* manual? It *is* part of the texinfo manual. If you are saying why is it not part of the org manual, why should it be? It has nothing to do with org. A link in the Documentation section of org might be warranted however: ``Org mode manuals are written in texinfo and they are part of the distribution: doc/org.texi and doc/orgguide.texi, although depending on how you get org, they may be in one of many different places. If you want to produce documentation in different formats, please see http://www.gnu.org/software/texinfo/manual/texinfo/html_node/Output-Formats.html#Output-Formats";>here.'' > > > And that the single page version of "the compact Org-mode Guide" is > > > missing. > > > > But I don't know whether the single page document ever was (or should > > be) available from the orgmode site, so I'm not sure I'd characterize is > > as "missing": Matt and/or Jason would know better. > > It's actually available as a pdf download but this is not what I expected (a > single html page) so I deemed it "missing". I usually expect to find both > single page html and one page per section html versions along with gzipped > versions (for those who want to download it). > > IMHO the current "Documentation" section found at http://orgmode.org/ could > use > a quick rewrite. It might be related to english not being my native language > but when I read "read the online manual" I understand that there is a > different > offline version. Rewritten to "read the manual online" this potential > confusion > is no more (at least for me). > > There's also a lack of consistency, for the guide it says: > * Read the online compact guide or download it as a PDF document. (...) > > while for the manual the same info is broken into two different sections: > > * Read the online manual. (...) > * Download the manual as a 200-page PDF document. > > Starting the entries with "Read", "Download", "Buy" helps scanning through > the > section by providing info right away, out of luck the specific version i was > looking for is the one which doesn't follow this pattern: > > * You can also have the entire manual in a single monolithic file. > > I had the online manual open which offers no easily found way to get to the > place where other versions of the manual can be found, so I headed for the > orgmode website, scanned the documentation section and missed the single html > page version I was looking for, because it breaks the pattern. As I am > expecting this version to be found I read the whole section from the > beginning > and missed it again, for some reason "single monolithic page" didn't fire up > my > brain looking for a "single html page", At this point I still assume the > single > html page version exists and can be found in this section so I started again > from the top and clicked each link one after the other until I finally found > it. > > Leading to this improvement suggestion thread. > These sound like reasonable questiions/suggestions to me and I'm sure the webmasters will consider them carefully (just don't expect immediate gratification: they all do it in their spare time.) Nick
Re: [O] Re: Why are special properties like CLOSED etc. not in the properties drawer?
On Tue, Apr 5, 2011 at 4:52 PM, Bernt Hansen wrote: > Marcel van der Boom writes: > > > I've been wondering about this for a bit. It would make things a bit > > more consistent for me if all properties are in the 'properties'-drawer. > > Or am I missing something here? > > The main reason I can think of is that this is historical. CLOSED: was > invented long before anyone thought about the need for drawers. > > Drawers are an added feature that is not needed to be able to make > org-mode useful. I don't think there should be a requirement for having > a drawer when you mark a task done just to record the CLOSED date. > Having an option to enable this behaviour would be fine with me. > I stumbled recently over this old message which may have relevancy for this http://thread.gmane.org/gmane.emacs.orgmode/3783 Juri > > The idea of including timestamps in property drawers is a fairly recent > development in org-mode. >
[O] Re: starting ispell process during latex export
05/04/11 17:37, Chris Beard > This looks like it may be a multidisciplinary problem, but this > mailing list has provided good solutions for these things in the past, > so I figured it would be the first place to check. > > I've been exporting latex documents via org-mode, but I noticed that > the editing mode (after C-c ') was LaTeX mode without the Auctex > options that I had used on a different emacs setup. So I installed > Auctex (it now edits in pdflatex mode), but since then exporting to > Latex has been *very* slow. In fact, the whole emacs freezes up, and > the minibuffer keeps giving me these "Starting new Ispell process > [default] ..." messages. I turned on debug-on-error, but I don't get a > backtrace buffer (but I'm not very experienced at debugging in emacs, > so this may not mean anything). Here's a sample from the *Messages* > buffer: Presumably, you're activating flyspell for auctex in your .emacs and that messes with the intermediate buffers org uses. If you're not sure where you're activating flyspell, you could try M-x debug-on-entry to trace the problem back to its source.
[O] starting ispell process during latex export
This looks like it may be a multidisciplinary problem, but this mailing list has provided good solutions for these things in the past, so I figured it would be the first place to check. I've been exporting latex documents via org-mode, but I noticed that the editing mode (after C-c ') was LaTeX mode without the Auctex options that I had used on a different emacs setup. So I installed Auctex (it now edits in pdflatex mode), but since then exporting to Latex has been *very* slow. In fact, the whole emacs freezes up, and the minibuffer keeps giving me these "Starting new Ispell process [default] ..." messages. I turned on debug-on-error, but I don't get a backtrace buffer (but I'm not very experienced at debugging in emacs, so this may not mean anything). Here's a sample from the *Messages* buffer: org-babel-exp processing... Starting new Ispell process [default] ... Enabling Flyspell mode gave an error Starting new Ispell process [default] ... Enabling Flyspell mode gave an error Position saved to mark ring, go back with M-x org-mark-ring-goto. org-babel-exp processing... Starting new Ispell process [default] ... Enabling Flyspell mode gave an error Starting new Ispell process [default] ... Enabling Flyspell mode gave an error org-babel-exp processing... Starting new Ispell process [default] ... Enabling Flyspell mode gave an error Starting new Ispell process [default] ... Enabling Flyspell mode gave an error org-babel-exp processing... Does anyone have advice on fixing this? Thank you Chris
[O] Re: Update org-mode
Let me summarize the steps I carried out eventually, to use the package manager. Note, I am using emacs 23 based editor which was shipped with org-mode 6.33. * Updating Follow the steps: ** Intsall the package manager *** Download the =packages.el= file from http://repo.or.cz/w/emacs.git/blob_plain/1a0a666f941c99882093d7bd08ced15033bc3f0c:/lisp/emacs-lisp/package.el. Save in in =~/Library/elisp= for example. *** Add the following code to the =.emacs=: #+BEGIN_SRC elisp (setq load-path (cons "~/Library/elisp" load-path)) (require 'package) (package-initialize) #+END_SRC *** Verify To verify this part, in /emacs/ hit =M-x list-packages RET org=. Here you should see a list of optional packages. /Note:/ you may ignore the warning: =failed to download org-mode archive=. ** Updating org-mode *** Enter the =list-packages= Hit =M-x list-packages RET=. In there mark for installation by =i= the org package and the =x= for the actual installation. *** Restart emacs *** Verify Hit =M-x locate-library RET org= to verify the installation. You should now have org-mode up and running. Thank you all! Dror On Apr 1, 2011, at 18:24 PM, Jambunathan K wrote: > Dror Atariah writes: > >> I tried to follow the update process described here: >> http://orgmode.org/worg/org-faq.html under: >> How do I keep current with bleeding edge development? > > Search for ELPA in FAQ. Maybe that will work well for you ... >
[O] Re: Why are special properties like CLOSED etc. not in the properties drawer?
Marcel van der Boom writes: > I've been wondering about this for a bit. It would make things a bit > more consistent for me if all properties are in the 'properties'-drawer. > Or am I missing something here? The main reason I can think of is that this is historical. CLOSED: was invented long before anyone thought about the need for drawers. Drawers are an added feature that is not needed to be able to make org-mode useful. I don't think there should be a requirement for having a drawer when you mark a task done just to record the CLOSED date. Having an option to enable this behaviour would be fine with me. The idea of including timestamps in property drawers is a fairly recent development in org-mode. -Bernt
[O] Why are special properties like CLOSED etc. not in the properties drawer?
Hi, I've been wondering about this for a bit. It would make things a bit more consistent for me if all properties are in the 'properties'-drawer. Or am I missing something here? marcel -- Marcel van der Boom -- http://hsdev.com/mvdb.vcf HS-Development BV-- http://www.hsdev.com So! web applications -- http://make-it-so.info Cobra build -- http://cobra.mrblog.nl
[O] org-agenda-log-mode doesn't list past scheduled items if org-agenda-skip-scheduled-if-done is t
I guess my use case is pretty common: I use org-agenda to keep track of
appointments, and use org-agenda-skip-scheduled-if-done to avoid
displaying past appointments. If I want to review what I did last week
for instance, I'd like the SCHEDULED dates to appear in
org-agenda-log-mode, not the dates where I closed the TODO entry. But
org-agenda-log-mode-items only has support for closed, clock and state
changes. A nice feature would be a 'scheduled option, which would
display done entries that have a SCHEDULED tag.
I tried to implement it, but got stuck at date handling (apparently, the
problem is that SCHEDULED items use <> syntax, while CLOSED uses
[]. Not sure why.) Could someone take a look at it?
I'm attaching a very preliminary attempt to implement it, in case anyone
is interested. It's buggy because of the date issues.
diff --git a/lisp/org/org-agenda.el b/lisp/org/org-agenda.el
index 9adc180..89c9dde 100644
--- a/lisp/org/org-agenda.el
+++ b/lisp/org/org-agenda.el
@@ -4733,6 +4733,7 @@ be skipped."
(list
(if (memq 'closed items) (concat "\\<" org-closed-string))
(if (memq 'clock items) (concat "\\<" org-clock-string))
+ (if (memq 'scheduled items) (concat "\\<" org-scheduled-string))
(if (memq 'state items) "- State \"\\([a-zA-Z0-9]+\\)\".*?"
(parts-re (if parts (mapconcat 'identity parts "\\|")
(error "`org-agenda-log-mode-items' is empty")))
@@ -4744,10 +4745,10 @@ be skipped."
(format-time-string
(car org-time-stamp-formats)
(apply 'encode-time ; DATE bound by calendar
- (list 0 0 0 (nth 1 date) (car date) (nth 2 date
+ (list 0 0 0 (nth 1 date) (car date) (nth 2 date
1 11
(org-agenda-search-headline-for-time nil)
- marker hdmarker priority category tags closedp statep clockp state
+ marker hdmarker priority category tags closedp statep clockp scheduledp state
ee txt extra timestr rest clocked)
(goto-char (point-min))
(while (re-search-forward regexp nil t)
@@ -4755,8 +4756,9 @@ be skipped."
(org-agenda-skip)
(setq marker (org-agenda-new-marker (match-beginning 0))
closedp (equal (match-string 1) org-closed-string)
+ scheduledp (equal (match-string 1) org-scheduled-string)
statep (equal (string-to-char (match-string 1)) ?-)
- clockp (not (or closedp statep))
+ clockp (not (or closedp scheduledp statep))
state (and statep (match-string 2))
category (org-get-category (match-beginning 0))
timestr (buffer-substring (match-beginning 0) (point-at-eol))
@@ -4765,7 +4767,7 @@ be skipped."
;; substring should only run to end of time stamp
(setq rest (substring timestr (match-end 0))
timestr (substring timestr 0 (match-end 0)))
- (if (and (not closedp) (not statep)
+ (if (and (not closedp) (not statep) (not scheduledp)
(string-match "\\([0-9]\\{1,2\\}:[0-9]\\{2\\}\\)\\].*?\\([0-9]\\{1,2\\}:[0-9]\\{2\\}\\)" rest))
(progn (setq timestr (concat (substring timestr 0 -1)
"-" (match-string 1 rest) "]"))
@@ -4780,6 +4782,9 @@ be skipped."
(setq extra (match-string 1
(clockp
(and (looking-at ".*\n[ \t]*-[ \t]+\\([^-\n \t].*?\\)[ \t]*$")
+ (setq extra (match-string 1
+ (scheduledp
+ (and (looking-at ".*\n[ \t]*-[ \t]+\\([^-\n \t].*?\\)[ \t]*$")
(setq extra (match-string 1)
(if (not (re-search-backward "^\\*+ " nil t))
(setq txt org-agenda-no-heading-message)
@@ -4788,6 +4793,8 @@ be skipped."
tags (org-get-tags-at))
(looking-at "\\*+[ \t]+\\([^\r\n]+\\)")
(setq txt (match-string 1))
+ (if (and scheduledp (not (string-match (regexp-opt org-done-keywords-for-agenda) txt)))
+ (throw :skip nil))
(when extra
(if (string-match "\\([ \t]+\\)\\(:[^ \n\t]*?:\\)[ \t]*$" txt)
(setq txt (concat (substring txt 0 (match-beginning 1))
@@ -4796,8 +4803,9 @@ be skipped."
(setq txt (org-format-agenda-item
(cond
(closedp "Closed:")
- (statep (concat "State: (" state ")"))
- (t (concat "Clocked: (" clocked ")")))
+ (scheduledp "Scheduled:")
+ (statep (concat "State: (" state ")"))
+ (t (concat "Clocked: (" clocked ")")))
txt category tags timestr)))
(setq priority 10)
(org-add-props txt props
[O] Re: unnumbered subsections in latex export
Hi Aankhen,
Aankhen wrote:
> 2011/4/4 Sébastien Vauban :
>> [snip]
>>
>> When discussing exporters and features, two things that come up to my mind
>> as missing as a "general Org feature":
>>
>> - bibliography :: works for LaTeX[1], not for HTML export.
>> - acronyms :: idem.
>>
>> Maybe those should be made available for general Org usage by making them
>> somehow part of the preprocessing?
>
> FWIW, acronyms wouldn’t need any preprocessing for HTML export. Or maybe
> they would: HTML has both ‘acronym’ and ‘abbr’ (abbreviation) elements, the
> distinction between them being a little hard to make. Could go the other way
> and provide both in Org and combine them where there’s no distinction, I
> suppose.
>
> Uhm, anyway. Acronyms are natively supported in HTML. That is all.
Thanks for reporting this. Wasn't aware of it. Though, that does not alter the
need (at least, what I consider so) for acronyms handling in/from Org.
Let's clarify what I'm talking about -- I know, I should have done it earlier.
I want to be able to say, in my Org file, that DNS is an acronym, for example.
I'm thinking -- brainstorming! -- at a solution _such as_ adding accolades
around the acronyms:
--8<---cut here---start->8---
This paper talks about {DNS} clients and {DNS} servers...
--8<---cut here---end--->8---
In LaTeX, this should have to be translated to:
--8<---cut here---start->8---
This paper talks about \acro{DNS} clients and \acro{DNS} servers...
--8<---cut here---end--->8---
And the effects would be that:
1. the first occurrence of the acronym would be expanded in the PDF, while
others not -- this is customizable!
2. every occurrence would be a link to the list of acronyms, at the end of the
document.
In HTML, I would expect internal links to a list of acronyms at the end of the
document.
I was thinking at preprocessing, because some smart things need to be done:
- expanding the first occurrence of the acronym (if wished) with its
definition, not the following;
- in the list, at the end of the document, only list acronym definitions for
the acronyms that have been used in the document.
For the readability of the Org buffer, and for the behavior that we could
expect, maybe a new link type would make it?
I would expect a similar treatment for the bibliography: having some built-in
representation for that in Org, and have the exporters make it to both LaTeX
and HTML (and ...).
Comments welcome!
Best regards,
Seb
--
Sébastien Vauban
[O] Re: [taskjuggler] small edits to org-taskjuggler.el for tj3
Christian Egli writes:
>> * in org-taskjuggler-open-project, the duration is never calculated
>> (default is always used).
>
> Good catch and thanks for your patch. Unfortunately the patch causes
> problems with my export. The duration is now correctly calculated,
> however the root task now also has an end attribute which causes
> problems down the road and TJ2 tells me that "End of task foo does not
> fit into the project time frame. Try using a later project end date".
> But no matter how much I put the end date into the future the issue
> remains. If I remove the end attribute from the root task it seems to
> work.
The following patch seems to work. If you're OK with it I will commit.
diff --git a/lisp/org-taskjuggler.el b/lisp/org-taskjuggler.el
index f891634..20bd91f 100644
--- a/lisp/org-taskjuggler.el
+++ b/lisp/org-taskjuggler.el
@@ -553,11 +553,11 @@ specified it is calculated
(headline (cdr (assoc "headline" project)))
(version (cdr (assoc "version" project)))
(start (cdr (assoc "start" project)))
- (end (cdr (assoc "end" project
+ (period (or (cdr (assoc "period" project))
+ (format "%s +%sd" start
org-export-taskjuggler-default-project-duration
(insert
- (format "project %s \"%s\" \"%s\" %s +%sd {\n }\n"
-unique-id headline version start
-org-export-taskjuggler-default-project-duration
+ (format "project %s \"%s\" \"%s\" %s {\n }\n"
+unique-id headline version period
(defun org-taskjuggler-filter-and-join (items)
"Filter all nil elements from ITEMS and join the remaining ones
Thanks
Christian
--
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland
[O] Re: orgmode manual improvement suggestion.
Nick Dokos hp.com> writes: > If you download an org distribution (through git or a tar file or what > have you), you should be able to find the doc/org.texi file which is > used to generate the manual. Found it. In debian it's gzipped and located in /usr/share/doc/org-mode/ where I found both org.texi.gz and orgguide.texi.gz I was hoping org mode documentation had been made with org mode, I wasn't expecting a texi file format I had not been introduced to yet. I can use it to generate the manual, but I can't jump into modifying the source. > The following page > >http://www.gnu.org/software/texinfo/manual/texinfo/html_node/Output- Formats.html#Output-Formats > > describes briefly how to produce each output format from the texi file. Thanks. how come this is not part of the manual ? It is a good practice to provide information about where to find the manual and how to produce a specific format (especially when not providing it). > > And that the single page version of "the compact Org-mode Guide" is > > missing. > > But I don't know whether the single page document ever was (or should > be) available from the orgmode site, so I'm not sure I'd characterize is > as "missing": Matt and/or Jason would know better. It's actually available as a pdf download but this is not what I expected (a single html page) so I deemed it "missing". I usually expect to find both single page html and one page per section html versions along with gzipped versions (for those who want to download it). IMHO the current "Documentation" section found at http://orgmode.org/ could use a quick rewrite. It might be related to english not being my native language but when I read "read the online manual" I understand that there is a different offline version. Rewritten to "read the manual online" this potential confusion is no more (at least for me). There's also a lack of consistency, for the guide it says: * Read the online compact guide or download it as a PDF document. (...) while for the manual the same info is broken into two different sections: * Read the online manual. (...) * Download the manual as a 200-page PDF document. Starting the entries with "Read", "Download", "Buy" helps scanning through the section by providing info right away, out of luck the specific version i was looking for is the one which doesn't follow this pattern: * You can also have the entire manual in a single monolithic file. I had the online manual open which offers no easily found way to get to the place where other versions of the manual can be found, so I headed for the orgmode website, scanned the documentation section and missed the single html page version I was looking for, because it breaks the pattern. As I am expecting this version to be found I read the whole section from the beginning and missed it again, for some reason "single monolithic page" didn't fire up my brain looking for a "single html page", At this point I still assume the single html page version exists and can be found in this section so I started again from the top and clicked each link one after the other until I finally found it. Leading to this improvement suggestion thread.
Re: [O] what happened to the #+OPTIONS: \n:t ?
On Apr 5, 2011, at 10:15 AM, katepano wrote: > Dear Dominik. > I see your point and it is accepted, of course. I admit, I should write my > email more clearly. Anyway, thanks for your time. > > On the other hand I really would like to see #+OPTIONS: \n:t working, if this > possible and do not cause much frustration. If you read the threads I have linked to you will see that this is not at all simple. An option like this would always be a dirty hack that forces a backend into a state it was not made for. Using special markup and environments for code, poems, you name it, on the other hand, is perfectly fine. - Carsten > > thanks anyway > > Katepano > > On 04/05/2011 11:04 AM, Carsten Dominik wrote: >> Dear katepano, >> >> as you can see, it has taken 11 emails on a high volume email list >> to get the answer to your simple question. More than 1100 people have >> subscribed to this mailing list, an unknown number of people >> read it on aggregators like gmane. That is a lot of time and energy >> spent unnecessarily. >> >> Please take more care when formulating a question to the list >> and try to give all necessary information from the start. >> Here is an example on how you *could* have formulated your >> initial mail: >> >> >> >> >> >> Dear Org- mode people, >> >> I am trying to write a poem in Orgmode, but when I am exporting >> the poem to LaTeX or HTML, all the line breaks are lost! I would like >> to export the poem with the line break preserved. >> >> I have studied the manual and have found that >> >>#+OPTIONS: \n:t >> >> might be a way to achieve what I want. But the feature is marked as >> DOES NOT WORK in the manual. Does anyone know why this is the case? >> I have also search for "preserve breaks" in the mailing list archive: >> >> http://search.gmane.org/?query=preserve+breaks&author=&group=gmane.emacs.orgmode&sort=relevance&DEFAULTOP=and&xP=org%09mode >> >> and found a number of threads which match this query, but the results >> have been confusing to me. So I am wondering if someone here could >> enlighten me what the best way is to achieve my goal. >> >> Here is an example Org-file: >> >> #+STARTUP: showall >> #+TITLE: 5-006 Τσιγάρο ατέλειωτο >> #+OPTIONS: H:3 num:nil toc:nil \n:t >> >> *Συνθέτης:* Σωκράτης Μάλαμας >> *Στιχουργός:* Γιώργος Αθανασόπουλος >> *Έτος:* 1993 >> >> #+BEGIN_QUOTE >> Θα περπατήσω μοναχός κι αυτό το βράδυ >> μήπως και βρω της λησμονιάς σου το νερό >> και σε υπόγεια σκοτεινά θα βρω σημάδι >> μ' ένα ποτήρι ως της αυγής τον πανικό >> #+END_QUOTE >> >> >> I guess you would have gotten the right reply immediately. >> >> >> On Apr 4, 2011, at 4:42 PM, katepano wrote: >> >>> what happen to the #+OPTIONS: \n:t ? we need it back please!!! why it does >>> not work >>> >>> By the way nobody responded to my message!!! >>> >>> http://www.mail-archive.com/emacs-orgmode@gnu.org/msg40104.html >>> why? is it a stupid question or it can't be implemented? >> >> That was actually a much better message, and, as Bastien indicates, >> there is no simple answer/solution at this time. >> >> Regards >> >> - Carsten >> >> >>> Regards >>> >>> katepano >>> >> - Carsten >> >> >> >> - Carsten
Re: [O] what happened to the #+OPTIONS: \n:t ?
Dear Dominik. I see your point and it is accepted, of course. I admit, I should write my email more clearly. Anyway, thanks for your time. On the other hand I really would like to see #+OPTIONS: \n:t working, if this possible and do not cause much frustration. thanks anyway Katepano On 04/05/2011 11:04 AM, Carsten Dominik wrote: Dear katepano, as you can see, it has taken 11 emails on a high volume email list to get the answer to your simple question. More than 1100 people have subscribed to this mailing list, an unknown number of people read it on aggregators like gmane. That is a lot of time and energy spent unnecessarily. Please take more care when formulating a question to the list and try to give all necessary information from the start. Here is an example on how you *could* have formulated your initial mail: Dear Org- mode people, I am trying to write a poem in Orgmode, but when I am exporting the poem to LaTeX or HTML, all the line breaks are lost! I would like to export the poem with the line break preserved. I have studied the manual and have found that #+OPTIONS: \n:t might be a way to achieve what I want. But the feature is marked as DOES NOT WORK in the manual. Does anyone know why this is the case? I have also search for "preserve breaks" in the mailing list archive: http://search.gmane.org/?query=preserve+breaks&author=&group=gmane.emacs.orgmode&sort=relevance&DEFAULTOP=and&xP=org%09mode and found a number of threads which match this query, but the results have been confusing to me. So I am wondering if someone here could enlighten me what the best way is to achieve my goal. Here is an example Org-file: #+STARTUP: showall #+TITLE: 5-006 Τσιγάρο ατέλειωτο #+OPTIONS: H:3 num:nil toc:nil \n:t *Συνθέτης:* Σωκράτης Μάλαμας *Στιχουργός:* Γιώργος Αθανασόπουλος *Έτος:* 1993 #+BEGIN_QUOTE Θα περπατήσω μοναχός κι αυτό το βράδυ μήπως και βρω της λησμονιάς σου το νερό και σε υπόγεια σκοτεινά θα βρω σημάδι μ' ένα ποτήρι ως της αυγής τον πανικό #+END_QUOTE I guess you would have gotten the right reply immediately. On Apr 4, 2011, at 4:42 PM, katepano wrote: what happen to the #+OPTIONS: \n:t ? we need it back please!!! why it does not work By the way nobody responded to my message!!! http://www.mail-archive.com/emacs-orgmode@gnu.org/msg40104.html why? is it a stupid question or it can't be implemented? That was actually a much better message, and, as Bastien indicates, there is no simple answer/solution at this time. Regards - Carsten Regards katepano - Carsten
Re: [O] Re: what happened to the #+OPTIONS: \n:t ?
On Apr 5, 2011, at 9:56 AM, katepano wrote: > thanks for the tip, this is true, but not entirely the same . . . In what way is it not the same? Of cause it is not the same because it does preserve line breaks. Why do you not like this solution as much? I would argue that in fact it is a *much better* solution than a dumb preserve-all-linebreaks setting because - it allows you to have normal text before and after the poem - it wraps the output into a paragraph with class "verse", so you can add CSS styling to it without changing other formatting - it is cleaner in every possible way. - Carsten > Katepano > > On 04/05/2011 10:52 AM, Christian Moe wrote: >> You just need BEGIN_VERSE ... END_VERSE instead of _QUOTE. >> >> cm >> >> On 4/5/11 9:31 AM, katepano wrote: >>> Actually it is very simple . . . it misses the at the end of >>> the lines >>> check the attachments (the song is in greek but I think will give you >>> the idea) >>> Katepano >>> >>> >>> On 04/05/2011 10:18 AM, Jambunathan K wrote: Hello > First of all I need<#+OPTIONS: \n:t> because when I export an org > file which has song lyrics in it I want to preserve the lines but > accept css for nice printing (and singing afterwards). Can you give an example of an org file, the html export as it is today, the html export as you want it to be and may be the css file? Jambunathan K. >> >> > - Carsten
Re: [O] what happened to the #+OPTIONS: \n:t ?
Dear katepano, as you can see, it has taken 11 emails on a high volume email list to get the answer to your simple question. More than 1100 people have subscribed to this mailing list, an unknown number of people read it on aggregators like gmane. That is a lot of time and energy spent unnecessarily. Please take more care when formulating a question to the list and try to give all necessary information from the start. Here is an example on how you *could* have formulated your initial mail: Dear Org- mode people, I am trying to write a poem in Orgmode, but when I am exporting the poem to LaTeX or HTML, all the line breaks are lost! I would like to export the poem with the line break preserved. I have studied the manual and have found that #+OPTIONS: \n:t might be a way to achieve what I want. But the feature is marked as DOES NOT WORK in the manual. Does anyone know why this is the case? I have also search for "preserve breaks" in the mailing list archive: http://search.gmane.org/?query=preserve+breaks&author=&group=gmane.emacs.orgmode&sort=relevance&DEFAULTOP=and&xP=org%09mode and found a number of threads which match this query, but the results have been confusing to me. So I am wondering if someone here could enlighten me what the best way is to achieve my goal. Here is an example Org-file: #+STARTUP: showall #+TITLE: 5-006 Τσιγάρο ατέλειωτο #+OPTIONS: H:3 num:nil toc:nil \n:t *Συνθέτης:* Σωκράτης Μάλαμας *Στιχουργός:* Γιώργος Αθανασόπουλος *Έτος:* 1993 #+BEGIN_QUOTE Θα περπατήσω μοναχός κι αυτό το βράδυ μήπως και βρω της λησμονιάς σου το νερό και σε υπόγεια σκοτεινά θα βρω σημάδι μ' ένα ποτήρι ως της αυγής τον πανικό #+END_QUOTE I guess you would have gotten the right reply immediately. On Apr 4, 2011, at 4:42 PM, katepano wrote: > what happen to the #+OPTIONS: \n:t ? we need it back please!!! why it does > not work > > By the way nobody responded to my message!!! > > http://www.mail-archive.com/emacs-orgmode@gnu.org/msg40104.html > why? is it a stupid question or it can't be implemented? That was actually a much better message, and, as Bastien indicates, there is no simple answer/solution at this time. Regards - Carsten > > Regards > > katepano > - Carsten
Re: [O] Re: what happened to the #+OPTIONS: \n:t ?
thanks for the tip, this is true, but not entirely the same . . . Katepano On 04/05/2011 10:52 AM, Christian Moe wrote: You just need BEGIN_VERSE ... END_VERSE instead of _QUOTE. cm On 4/5/11 9:31 AM, katepano wrote: Actually it is very simple . . . it misses the at the end of the lines check the attachments (the song is in greek but I think will give you the idea) Katepano On 04/05/2011 10:18 AM, Jambunathan K wrote: Hello First of all I need<#+OPTIONS: \n:t> because when I export an org file which has song lyrics in it I want to preserve the lines but accept css for nice printing (and singing afterwards). Can you give an example of an org file, the html export as it is today, the html export as you want it to be and may be the css file? Jambunathan K.
Re: [O] Re: what happened to the #+OPTIONS: \n:t ?
You just need BEGIN_VERSE ... END_VERSE instead of _QUOTE. cm On 4/5/11 9:31 AM, katepano wrote: Actually it is very simple . . . it misses the at the end of the lines check the attachments (the song is in greek but I think will give you the idea) Katepano On 04/05/2011 10:18 AM, Jambunathan K wrote: Hello First of all I need<#+OPTIONS: \n:t> because when I export an org file which has song lyrics in it I want to preserve the lines but accept css for nice printing (and singing afterwards). Can you give an example of an org file, the html export as it is today, the html export as you want it to be and may be the css file? Jambunathan K.
[O] Re: [taskjuggler] small edits to org-taskjuggler.el for tj3
Hi Gregory "Sullivan, Gregory (US SSA)" writes: > Appended is a patch with a couple of small changes to > org-taskjuggler.el, addressing the following issues: Thanks for your patch. > General: > > * in org-taskjuggler-open-project, the duration is never calculated > (default is always used). Good catch and thanks for your patch. Unfortunately the patch causes problems with my export. The duration is now correctly calculated, however the root task now also has an end attribute which causes problems down the road and TJ2 tells me that "End of task foo does not fit into the project time frame. Try using a later project end date". But no matter how much I put the end date into the future the issue remains. If I remove the end attribute from the root task it seems to work. This might be an inherent problem with the fact that the exporter uses the root task also as a container for project specific information. > Specific to tj3: > * the reports need a "formats" attribute > * I wasn't sure about how best to maintain backwards compatibility > with the default report strings, as I override the taskjuggler version > in the .org file (not in my .emacs file). The reports are a problem. Right now they are defined in a custom definition. To maintain backwards compatibility we could probably just add a new custom definition for tj3 reports and use that one if we're exporting to tj3. > * for tj3, I found that I needed to put a "scheduling" property in the > top level task, with value "asap". TaskJuggler III v0.0.11 Are you suggesting we should insert this automatically? Shouldn't this be at the users discretion? Thanks -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
[O] Re: what happened to the #+OPTIONS: \n:t ?
Hello > First of all I need <#+OPTIONS: \n:t> because when I export an org > file which has song lyrics in it I want to preserve the lines but > accept css for nice printing (and singing afterwards). Can you give an example of an org file, the html export as it is today, the html export as you want it to be and may be the css file? Jambunathan K.
Re: [O] what happened to the #+OPTIONS: \n:t ?
Thanks all for your responses, let me clarify a bit . . . First of all I need <#+OPTIONS: \n:t> because when I export an org file which has song lyrics in it I want to preserve the lines but accept css for nice printing (and singing afterwards). Regarding, the other question, that of exporting, I need it because some software like blosxom can use a date stamp in the filename to present in a "timely" hierarchical manner the content (due to plugin http://www.enilnomi.net/download.html#permtimez ). If it could be done, a whole blog site (based on blosxom or derivatives) could be written as source org files and published automatically. I know probably blosxom is not good for bloging publicly but for personal use in ones PC is excellent (I use it for journal, tips and hacks database, study notes, book notes, songs database etc etc) But do not bother, if it can't be done, ok. Actually I tried to do something myself, either through the org-publish.el or org-export-generic.el without much success :( Well, thanks again Katepano On 04/04/2011 08:44 PM, Nick Dokos wrote: katepano wrote: what happen to the #+OPTIONS: \n:t ? we need it back please!!! Why? what's the use case? why it does not work By the way nobody responded to my message!!! http://www.mail-archive.com/emacs-orgmode@gnu.org/msg40104.html why? is it a stupid question or it can't be implemented? [the question in that message is about exporting to a file with a different file name than the default, in particular consisting partly of a datestamp] Neither - but it is not the way it works currently. Again, if you can present a compelling use case, maybe somebody will implement it (but maybe not). You are always free to implement it yourself. Nick
