Re: [O] How do I create a drawer?
Hi Nicolas, Nicolas Goaziou writes: > Therefore, I suggest the following draft of a patch, that mostly reverts > commit splitting `org-insert-property-drawer' and makes > `org-insert-drawer' more user friendly. It provides the following > facilities: > > - headline inclusion check, > - drawer insertion without requiring an headline above, > - skip trailing blank lines (i.e. to wrap buffer around a just marked > paragraph), > - Ignore system drawer's names in completion list. > > What do you think? I think it's good -- thanks for the patch. I just pushed a slightly modified version of it, adding `C-c C-x d' as a keybinding for `org-insert-drawer', and adding the possibility to call `org-insert-property-drawer' from `org-insert-drawer' directly using a prefix argument. I agree special drawers should not be offered in the completion table, but it's still using to be able to quickly insert a property drawer, especially in combination with property completion. Anyway, I think we moved in the right direction. Thanks again! -- Bastien
Re: [O] Possible bug in org-cycle with property drawer
Hi Nick,
Nick Dokos writes:
> That's it: I had a
>
> #+DRAWERS: JUNK GARBAGE TRASH
>
> line in the file (and I didn't report it in the original email: blush!
> sorry about that). Without it, the property drawer behaves normally.
Thinking again about your problem, I don't find it natural to
have #+DRAWERS /replacing/ existing drawers specified in `org-drawers',
instead of just adding new ones.
Do you agree?
The attached patch implements a new meaning for #+DRAWERS, as a way
to declare "additional" drawers.
Let me know what you think, thanks!
>From 00d19d068708bda1b3a647c06d457936a12ed20d Mon Sep 17 00:00:00 2001
From: Bastien Guerry
Date: Thu, 26 Jan 2012 09:42:04 +0100
Subject: [PATCH] Let #+DRAWERS append new drawers to `org-drawers', instead
of replacing them.
* org.el (org-set-regexps-and-options): Set the value of
`org-drawers' by adding the value of the infile #+DRAWERS
option to that of the existing `org-drawers'.
* org.texi (Drawers): Clearly states that #+DRAWERS will add
drawers to the one originally listed in `org-drawers'.
---
doc/org.texi |8
lisp/org.el |2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index a285cca..d374dfb 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -1773,8 +1773,8 @@ numerically, alphabetically, by time, or by custom function.
Sometimes you want to keep information associated with an entry, but you
normally don't want to see it. For this, Org mode has @emph{drawers}.
Drawers need to be configured with the variable
-@code{org-drawers}@footnote{You can define drawers on a per-file basis
-with a line like @code{#+DRAWERS: HIDDEN PROPERTIES STATE}}. Drawers
+@code{org-drawers}@footnote{You can define additional drawers on a
+per-file basis with a line like @code{#+DRAWERS: HIDDEN STATE}}. Drawers
look like this:
@example
@@ -14433,8 +14433,8 @@ Set tags that can be inherited by any entry in the file, including the
top-level entries.
@item #+DRAWERS: NAME1 .
@vindex org-drawers
-Set the file-local set of drawers. The corresponding global variable is
-@code{org-drawers}.
+Set the file-local set of additional drawers. The corresponding global
+variable is @code{org-drawers}.
@item #+LINK: linkword replace
@vindex org-link-abbrev-alist
These lines (several are allowed) specify link abbreviations.
diff --git a/lisp/org.el b/lisp/org.el
index 7a68b73..5bc9aeb 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -4547,7 +4547,7 @@ but the stars and the body are.")
(mapcar (lambda (x) (org-split-string x ":"))
(org-split-string value)))
((equal key "DRAWERS")
- (setq drawers (org-split-string value splitre)))
+ (setq drawers (append org-drawers (org-split-string value splitre
((equal key "CONSTANTS")
(setq const (append const (org-split-string value splitre
((equal key "STARTUP")
--
1.7.8.4
--
Bastien
[O] Bug: A missing colon in the template defaults [7.8.03 (release_7.8.03.237.g674bb)]
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.
A colon following the INCLUDE keyword shouldn't be omitted from
org-structure-template-alist. Here is a patch to fix the remedy.
--- lisp/org.el.orig2012-01-26 09:56:56.0 +0900
+++ lisp/org.el 2012-01-26 10:17:42.0 +0900
@@ -11048,7 +11048,7 @@
("A" "#+ASCII: ")
("i" "#+INDEX: ?"
"#+INDEX: ?")
-("I" "#+INCLUDE %file ?"
+("I" "#+INCLUDE: %file ?"
"")
)
"Structure completion elements.
Emacs : GNU Emacs 23.3.1 (x86_64-apple-darwin10.6.0, NS apple-appkit-1038.35)
of 2011-03-12 on swallow.local
Package: Org-mode version 7.8.03 (release_7.8.03.237.g674bb)
--
Takahiro Noda
[O] Bug: A missing colon in the template defaults [7.8.03 (release_7.8.03.237.g674bb)]
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.
Hi,
I found a minor error in org.el. A colon following the INCLUDE keyword
shouldn't be omitted from org-structure-template-alist. Here is a
patch to fix the remedy.
--- lisp/org.el.orig2012-01-26 09:56:56.0 +0900
+++ lisp/org.el 2012-01-26 10:17:42.0 +0900
@@ -11048,7 +11048,7 @@
("A" "#+ASCII: ")
("i" "#+INDEX: ?"
"#+INDEX: ?")
-("I" "#+INCLUDE %file ?"
+("I" "#+INCLUDE: %file ?"
"")
)
"Structure completion elements.
Emacs : GNU Emacs 23.3.1 (x86_64-apple-darwin10.6.0, NS apple-appkit-1038.35)
of 2011-03-12 on swallow.local
Package: Org-mode version 7.8.03 (release_7.8.03.237.g674bb)
--
Best,
Takahiro Noda
Re: [O] Bug: A missing colon in the template defaults [7.8.03 (release_7.8.03.237.g674bb)]
Hi Takahiro, Takahiro Noda writes: > I found a minor error in org.el. A colon following the INCLUDE keyword > shouldn't be omitted from org-structure-template-alist. Here is a > patch to fix the remedy. Applied, thanks! -- Bastien
[O] org mode in press
Hi all, this just came into my inbox: http://www.jstatsoft.org/v46/i03 Great work! Big thanks to the authors. - Andreas
Re: [O] [PATCH] add support for configurable nested lists in org-export-generic
Hi Rob, Bastien writes: > Rob Giardina writes: > >> diff --git a/contrib/lisp/org-export-generic.el >> b/contrib/lisp/org-export-generic.el >> index 12bbcdb..97b9134 100644 >> --- a/contrib/lisp/org-export-generic.el >> +++ b/contrib/lisp/org-export-generic.el > > can you resubmit this patch using git format-patch and adding > a commit message and a ChangeLog? I've discarded this patch now -- if you want it to be applied, I'm okay, but please make sure it applies against latest git and provide a ChangeLog entry. See http://orgmode.org/worg/org-contribute.html#sec-4 for details. Thanks, -- Bastien
[O] BUG: C-c l when file has an attachment
*Org mode version I'm using:* 7.8.03 *What's the issue:* C-c l automatically creates ID property and copies the ID instead of heading. Happens if I have another file attached to my file. * Steps to reproduce the issue:* In an org file, do C-c C-a n and save the new attachment. Now try doing C-c l on any heading in original file. Regards, Pawan
Re: [O] Wrapping of e-mail address in table when exporting to pdf through latex
Johnny writes:
> Hi,
>
> I have some e-mail addresses in a table that I want to export to pdf
> thorugh latex. However, the e-mail addresses do not wrap nicely (not at
> all) in the table, is there any way to make the latex export from org
> enable wrapping?
>
> Example:
>
>#+ATTR_LaTeX: align=llp{2cm}
> | ITEM| Comment| e-mail |
> |-++--|
> | Listed item | Some text here | this.email@shouldbe.wrapped |
> | || |
>
> Thanks!
As you are alluding, this is more a latex problem than an org
one. Getting an email address to wrap is difficult. The only solution
I can think of is to suggest a hyphenation point in each email address
you have in the table.
You can suggest hyphenation points using "\-", as in:
| Listed item | Some text here | this.email@\-shouldbe.wrapped |
This works, but is not pretty... but I don't think you have much in the
way of alternative options!
HTH,
eric
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1
: using Org-mode version 7.8.03 (release_7.8.03.237.g674bb)
Re: [O] [ANN] ASCII back-end for new export engine
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> I think that your understanding of the new exporter architecture is
>> intimate and secure. I'm happy to follow your lead here.
>
> I know for sure my way around the new exporter, but my LaTeX skills
> aren't on par with that knowledge.
>
> Anyway, I've pushed a commit which tries to create smart links.
>
> Basically, links without a description pointing to an headline will be
> turned into \ref{headline-label}, unless headline's numbering is off, in
> which case they become \hyperref[headline-label]{headline-title}.
>
> Nothing is changed for links providing their own description, and links
> not pointing to headlines.
>
> That should remove the need for a variable.
>
> What do you think about it?
I think this is a very nice solution, especially the handling of links
to sections with and without numbering.
Thanks,
eric
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1
: using Org-mode version 7.8.03 (release_7.8.03.237.g674bb)
Re: [O] Possible bug in org-cycle with property drawer
Bastien writes: > Nick Dokos writes: > >> I start emacs with a minimal .emacs and an empty org file, insert >> a headline and insert a property drawer with >> org-insert-property-drawer. > > Note that a similar problem can occur with `org-insert-drawer' if > the inserted drawer is not known as such in the current buffer. > > The solution I'm inclined to implement is to ask the user if she > wants any unknown drawer to be added to `org-drawers'. > > What do you think? Yes, I think this would be a good idea. I had the same behaviour that Nick reported and I did not understand the cause of this behaviour as I had no DRAWERS option anywhere in my file! Of course, I didn't necessarily read any documentation . -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1 : using Org-mode version 7.8.03 (release_7.8.03.237.g674bb)
Re: [O] Multiple agenda buffers at g...@github.com:7max/org-mode.git
Hi Max,
how did you select the variables that should become buffer-local?
You might have too many in your list, for example org-last-heading-marker...
Cheers
- Carsten
On 25.1.2012, at 21:45, Max Mikhanosha wrote:
> I had put my initial implementation of multiple agenda buffers and
> sticky agenda support on g...@github.com:7max/org-mode.git branch
> multiple-agenda-buffers.
>
> To enable, use M-x org-toggle-sticky-agenda
>
> In order to take full advantage of the sticky agenda, you need to give
> your various agendas different buffer names, you can do it by
> including `org-agenda-buffer-name' into the list of bound variables in
> `org-agenda-custom-commands'
>
> For example:
>
> (setq org-agenda-custom-commands
> '(("a" "Agenda and NEXT (priority)"
> ((agenda ""
> ((org-agenda-span 'day)))
> (tags-todo "/!NEXT"
> ((org-agenda-overriding-header "Next Tasks")
> (org-agenda-tags-todo-honor-ignore-options t)
> (org-agenda-todo-ignore-scheduled t)
> (org-agenda-todo-ignore-deadlines t)
> (org-tags-match-list-sublevels t)
> (org-agenda-sorting-strategy
> '(priority-down category-keep)
> ((org-agenda-buffer-name "*Agenda*")))
>("t" "TODO entries"
> todo ""
> ((org-agenda-buffer-name "*Todo List*")
>
>
> When sticky agenda is enabled, most of org-agenda Emacs variables
> become buffer local, and org-agenda-quit is changed to bury the buffer
> instead of killing it. Correspondingly org-agenda will show previously
> buried buffer if it exists, instead of re-generating it.
>
> This allows user to have many "mini-agendas" and switch between them
> rapidly
>
> I would appreciate any bug-reports about things not working, and of
> course patches or fixes for them. The most likely cause of any
> breakage is that `org-agenda-local-vars' list needs adjusting and/or
> fixing.
>
> Regards
> Max
Re: [O] Multiple agenda buffers at g...@github.com:7max/org-mode.git
I realize that I may have too many, my initial approach was to start
with some obvious one, then test and keep adding to the list.
But the bugs that shows up are hard to reproduce, and subtle, and it
was slow going, and I was sure I'm missing some.
So I went the other direction, and made a list of vars by grepping
org-agenda.el for "(defvar ", and tested again, and it was easier
to eliminate the variables from the list, since any variables that
caused problems usually throw error (due to global value being NIL),
instead of doing something subtly wrong that is hard to notice.
At Thu, 26 Jan 2012 09:50:22 +, Carsten Dominik wrote:
>
> Hi Max,
>
> how did you select the variables that should become buffer-local?
> You might have too many in your list, for example org-last-heading-marker...
>
> Cheers
>
> - Carsten
>
> On 25.1.2012, at 21:45, Max Mikhanosha wrote:
>
> > I had put my initial implementation of multiple agenda buffers and
> > sticky agenda support on g...@github.com:7max/org-mode.git branch
> > multiple-agenda-buffers.
> >
> > To enable, use M-x org-toggle-sticky-agenda
> >
> > In order to take full advantage of the sticky agenda, you need to give
> > your various agendas different buffer names, you can do it by
> > including `org-agenda-buffer-name' into the list of bound variables in
> > `org-agenda-custom-commands'
> >
> > For example:
> >
> > (setq org-agenda-custom-commands
> > '(("a" "Agenda and NEXT (priority)"
> > ((agenda ""
> > ((org-agenda-span 'day)))
> > (tags-todo "/!NEXT"
> > ((org-agenda-overriding-header "Next Tasks")
> > (org-agenda-tags-todo-honor-ignore-options t)
> > (org-agenda-todo-ignore-scheduled t)
> > (org-agenda-todo-ignore-deadlines t)
> > (org-tags-match-list-sublevels t)
> > (org-agenda-sorting-strategy
> > '(priority-down category-keep)
> > ((org-agenda-buffer-name "*Agenda*")))
> >("t" "TODO entries"
> > todo ""
> > ((org-agenda-buffer-name "*Todo List*")
> >
> >
> > When sticky agenda is enabled, most of org-agenda Emacs variables
> > become buffer local, and org-agenda-quit is changed to bury the buffer
> > instead of killing it. Correspondingly org-agenda will show previously
> > buried buffer if it exists, instead of re-generating it.
> >
> > This allows user to have many "mini-agendas" and switch between them
> > rapidly
> >
> > I would appreciate any bug-reports about things not working, and of
> > course patches or fixes for them. The most likely cause of any
> > breakage is that `org-agenda-local-vars' list needs adjusting and/or
> > fixing.
> >
> > Regards
> > Max
>
Re: [O] Multiple agenda buffers at g...@github.com:7max/org-mode.git
On 26.1.2012, at 11:17, Max Mikhanosha wrote:
> I realize that I may have too many, my initial approach was to start
> with some obvious one, then test and keep adding to the list.
>
> But the bugs that shows up are hard to reproduce, and subtle, and it
> was slow going, and I was sure I'm missing some.
>
> So I went the other direction, and made a list of vars by grepping
> org-agenda.el for "(defvar ", and tested again, and it was easier
> to eliminate the variables from the list, since any variables that
> caused problems usually throw error (due to global value being NIL),
> instead of doing something subtly wrong that is hard to notice.
OK, I will go through that list...
- Carsten
>
> At Thu, 26 Jan 2012 09:50:22 +, Carsten Dominik wrote:
>>
>> Hi Max,
>>
>> how did you select the variables that should become buffer-local?
>> You might have too many in your list, for example org-last-heading-marker...
>>
>> Cheers
>>
>> - Carsten
>>
>> On 25.1.2012, at 21:45, Max Mikhanosha wrote:
>>
>>> I had put my initial implementation of multiple agenda buffers and
>>> sticky agenda support on g...@github.com:7max/org-mode.git branch
>>> multiple-agenda-buffers.
>>>
>>> To enable, use M-x org-toggle-sticky-agenda
>>>
>>> In order to take full advantage of the sticky agenda, you need to give
>>> your various agendas different buffer names, you can do it by
>>> including `org-agenda-buffer-name' into the list of bound variables in
>>> `org-agenda-custom-commands'
>>>
>>> For example:
>>>
>>> (setq org-agenda-custom-commands
>>> '(("a" "Agenda and NEXT (priority)"
>>>((agenda ""
>>> ((org-agenda-span 'day)))
>>> (tags-todo "/!NEXT"
>>>((org-agenda-overriding-header "Next Tasks")
>>> (org-agenda-tags-todo-honor-ignore-options t)
>>> (org-agenda-todo-ignore-scheduled t)
>>> (org-agenda-todo-ignore-deadlines t)
>>> (org-tags-match-list-sublevels t)
>>> (org-agenda-sorting-strategy
>>> '(priority-down category-keep)
>>>((org-agenda-buffer-name "*Agenda*")))
>>> ("t" "TODO entries"
>>>todo ""
>>>((org-agenda-buffer-name "*Todo List*")
>>>
>>>
>>> When sticky agenda is enabled, most of org-agenda Emacs variables
>>> become buffer local, and org-agenda-quit is changed to bury the buffer
>>> instead of killing it. Correspondingly org-agenda will show previously
>>> buried buffer if it exists, instead of re-generating it.
>>>
>>> This allows user to have many "mini-agendas" and switch between them
>>> rapidly
>>>
>>> I would appreciate any bug-reports about things not working, and of
>>> course patches or fixes for them. The most likely cause of any
>>> breakage is that `org-agenda-local-vars' list needs adjusting and/or
>>> fixing.
>>>
>>> Regards
>>> Max
>>
>
Re: [O] Multiple agenda buffers at g...@github.com:7max/org-mode.git
I had committed a change that activates local variables, only if
org-agenda-sticky is turned on, hopefully making it completely safe to
test for people..
Now if something is screwed up, and you are in a hurry, you can turn
sticky agenda off and get on with normal org-mode usage, and then send
bug report later.
At Thu, 26 Jan 2012 06:17:45 -0500,
Max Mikhanosha wrote:
>
> I realize that I may have too many, my initial approach was to start
> with some obvious one, then test and keep adding to the list.
>
> But the bugs that shows up are hard to reproduce, and subtle, and it
> was slow going, and I was sure I'm missing some.
>
> So I went the other direction, and made a list of vars by grepping
> org-agenda.el for "(defvar ", and tested again, and it was easier
> to eliminate the variables from the list, since any variables that
> caused problems usually throw error (due to global value being NIL),
> instead of doing something subtly wrong that is hard to notice.
>
> At Thu, 26 Jan 2012 09:50:22 +, Carsten Dominik wrote:
> >
> > Hi Max,
> >
> > how did you select the variables that should become buffer-local?
> > You might have too many in your list, for example org-last-heading-marker...
> >
> > Cheers
> >
> > - Carsten
> >
> > On 25.1.2012, at 21:45, Max Mikhanosha wrote:
> >
> > > I had put my initial implementation of multiple agenda buffers and
> > > sticky agenda support on g...@github.com:7max/org-mode.git branch
> > > multiple-agenda-buffers.
> > >
> > > To enable, use M-x org-toggle-sticky-agenda
> > >
> > > In order to take full advantage of the sticky agenda, you need to give
> > > your various agendas different buffer names, you can do it by
> > > including `org-agenda-buffer-name' into the list of bound variables in
> > > `org-agenda-custom-commands'
> > >
> > > For example:
> > >
> > > (setq org-agenda-custom-commands
> > > '(("a" "Agenda and NEXT (priority)"
> > > ((agenda ""
> > > ((org-agenda-span 'day)))
> > > (tags-todo "/!NEXT"
> > > ((org-agenda-overriding-header "Next Tasks")
> > > (org-agenda-tags-todo-honor-ignore-options t)
> > > (org-agenda-todo-ignore-scheduled t)
> > > (org-agenda-todo-ignore-deadlines t)
> > > (org-tags-match-list-sublevels t)
> > > (org-agenda-sorting-strategy
> > > '(priority-down category-keep)
> > > ((org-agenda-buffer-name "*Agenda*")))
> > >("t" "TODO entries"
> > > todo ""
> > > ((org-agenda-buffer-name "*Todo List*")
> > >
> > >
> > > When sticky agenda is enabled, most of org-agenda Emacs variables
> > > become buffer local, and org-agenda-quit is changed to bury the buffer
> > > instead of killing it. Correspondingly org-agenda will show previously
> > > buried buffer if it exists, instead of re-generating it.
> > >
> > > This allows user to have many "mini-agendas" and switch between them
> > > rapidly
> > >
> > > I would appreciate any bug-reports about things not working, and of
> > > course patches or fixes for them. The most likely cause of any
> > > breakage is that `org-agenda-local-vars' list needs adjusting and/or
> > > fixing.
> > >
> > > Regards
> > > Max
> >
>
Re: [O] Wrapping of e-mail address in table when exporting to pdf through latex
Eric S Fraga writes:
> Johnny writes:
>
>> Hi,
>>
>> I have some e-mail addresses in a table that I want to export to pdf
>> thorugh latex. However, the e-mail addresses do not wrap nicely (not at
>> all) in the table, is there any way to make the latex export from org
>> enable wrapping?
>>
>> Example:
>>
>>#+ATTR_LaTeX: align=llp{2cm}
>> | ITEM| Comment| e-mail |
>> |-++--|
>> | Listed item | Some text here | this.email@shouldbe.wrapped |
>> | || |
>>
>> Thanks!
>
> As you are alluding, this is more a latex problem than an org
> one. Getting an email address to wrap is difficult. The only solution
> I can think of is to suggest a hyphenation point in each email address
> you have in the table.
>
> You can suggest hyphenation points using "\-", as in:
>
> | Listed item | Some text here | this.email@\-shouldbe.wrapped |
>
> This works, but is not pretty... but I don't think you have much in the
> way of alternative options!
>
> HTH,
> eric
The hyperref package provides a LaTeX solution, the briefest of which is
the \url{} command (and the \nolinkurl{} variant).
#+ATTR_LaTeX: align=llp{2cm}
| ITEM | Comment | e-mail
|
|--+---+-|
| ~url~ cmd| e-mail is a dead link |
\url{this.email@shouldbe.wrapped} |
| ~nolinkurl~ cmd | e-mail is just text |
\nolinkurl{this.email@shouldbe.wrapped} |
| ~mailto:~ syntax | e-mail is an mailto: link |
mailto:this.email@shouldbe.wrapped |
*** Notes for the mailto syntax
For the ~mailto:~ syntax to work the variable
~org-export-latex-href-format~ needs to use the ~url~ command instead of
~href~
(http://article.gmane.org/gmane.emacs.orgmode/44911/match=href+latex+link+url)
: (setq org-export-latex-href-format "\url{%s}")
While I prefer the ~mailto:~ syntax as more the `orgmode way', there are
two possible issues:
- config :: It requires a change to *all* LaTeX link exports
- display :: The ~mailto:~ string is also exported
I do not know what other solutions are currently possible to resolve those
issues.
--
Tim Burt
www.rketburt.org
"It is healthful to every sane man to utter the art within him;" -- GK
Chesterton
Re: [O] [babel][patch] BUG in inline source blocks
Hi,
Andreas Leha writes:
> Hi all,
>
> I experience unexpected behaviour when an inline source block is not
> preceded by whitespace.
>
> Example:
> ===
> * Test inline
> This is a functional inline src_R{print("source block")}.
>
> This (src_R{print("here")}) is not.
> ===
>
> Regards,
> Andreas
I can confirm this behaviour and provide a patch to allow for inline
source blocks to be preceded by punctuation, or, for instance, enclosed
in parenthesis, as in Andreas' example. Patch is attached for
consideration.
Best, Martyn
>From ce7ccfe97ce640f47ed83cdb2fdb6ffa8a6d3c54 Mon Sep 17 00:00:00 2001
From: Martyn Jago
Date: Thu, 26 Jan 2012 13:22:25 +
Subject: [PATCH] Fix for where inline source block is not preceded by whitespace but by
punctuation (reported by Andreas Leha).
* lisp/ob.el: Fix for where inline source block is not preceded by
whitespace but by punctuation.
* testing/lisp/test-ob.el: Regression test, testing inline source
block preceded by point, equality, and enclosed in parenthesis and
brackets.
---
lisp/ob.el | 21 -
testing/lisp/test-ob.el | 44
2 files changed, 56 insertions(+), 9 deletions(-)
diff --git a/lisp/ob.el b/lisp/ob.el
index 70c258f..fbf032b 100644
--- a/lisp/ob.el
+++ b/lisp/ob.el
@@ -170,24 +170,27 @@ not match KEY should be returned."
(defun org-babel-get-inline-src-block-matches()
"Set match data if within body of an inline source block.
Returns non-nil if match-data set"
- (let ((src-at-0-p (save-excursion
+ (let* ((src-at-0-p (save-excursion
(beginning-of-line 1)
(string= "src" (thing-at-point 'word
(first-line-p (= 1 (line-number-at-pos)))
- (orig (point)))
-(let ((search-for (cond ((and src-at-0-p first-line-p "src_"))
- (first-line-p "[ \t]src_")
- (t "[ \f\t\n\r\v]src_")))
- (lower-limit (if first-line-p
- nil
- (- (point-at-bol) 1
+ (orig (point))
+ (search-for (cond ((and src-at-0-p first-line-p "src_"))
+ (first-line-p "[ \t[:punct:]]src_")
+ (t "[ \f\t\n\r\v[:punct:]]src_")))
+ (lower-limit (if first-line-p
+ nil
+ (- (point-at-bol) 1
+ (message "src-at-0-p = %S" src-at-0-p)
+ (message "first-line-p = %S" src-at-0-p)
+ (message "search-for = %S" search-for)
(save-excursion
(when (or (and src-at-0-p (bobp))
(and (re-search-forward "}" (point-at-eol) t)
(re-search-backward search-for lower-limit t)
(> orig (point
(when (looking-at org-babel-inline-src-block-regexp)
- t ))
+ t )
(defvar org-babel-inline-lob-one-liner-regexp)
(defun org-babel-get-lob-one-liner-matches()
diff --git a/testing/lisp/test-ob.el b/testing/lisp/test-ob.el
index 7dccd22..fb38ead 100644
--- a/testing/lisp/test-ob.el
+++ b/testing/lisp/test-ob.el
@@ -430,6 +430,50 @@ this is simple"
(buffer-substring-no-properties
(point-min) (point-max)))
+(ert-deftest test-org-babel/inline-src_blk-preceded-punct ()
+ "Test inline source block where preceded by punctuation"
+
+ ;; inline-src-blk preceded by point
+ (let ((test-line ".src_emacs-lisp[ :results verbatim ]{ \"x\" }"))
+(org-test-with-temp-text
+ test-line
+ (forward-char 1)
+ (org-ctrl-c-ctrl-c)
+ (should (string= (concat test-line " =\"x\"=")
+ (buffer-substring-no-properties
+ (point-min) (point-max))
+
+ ;; inline-src-blk preceded by equality
+ (let ((test-line "=src_emacs-lisp[ :results verbatim ]{ \"x\" }"))
+(org-test-with-temp-text
+ test-line
+ (forward-char 1)
+ (org-ctrl-c-ctrl-c)
+ (should (string= (concat test-line " =\"x\"=")
+ (buffer-substring-no-properties
+ (point-min) (point-max))
+
+ ;; inline-src-blk enclosed within parenthesis
+ (let ((test-line "(src_emacs-lisp[ :results verbatim ]{ \"x\" }"))
+(org-test-with-temp-text
+ (concat test-line ")")
+ (forward-char 1)
+ (org-ctrl-c-ctrl-c)
+ (should (string= (concat test-line " =\"x\"=)" )
+ (buffer-substring-no-properties
+ (point-min) (point-max))
+
+ ;; inline-src-blk enclosed within parenthesis
+ (let ((test-line "{src_emacs-lisp[ :results verbatim ]{ \"x\" }"))
+(org-test-with-temp-text
+ (concat test-line "}")
+ (forward-char 1)
+ (org-ctrl-c-ctrl-c)
+ (should (string= (concat test-line " =\"x\"=}")
+ (buffer-substring-no-properties
+ (point-min) (point-max))
+
+ )
(ert-deftest test-org-babel/combining-scalar-and-raw-result-types ()
(org-test-with-temp-text-in-file "
--
1.7.3.4
[O] org-support-shift-select and aquamacs
Hello, I'm trying to use shift selection in the text part of org files, so I set "org-support-shift-select" to "t". Unfortunately it does not work: nothing happens when I try to select text using shift and arrow keys. I'm using Aquamacs 3 (compiled yesterday) and org-mode from git (compiled this morning). How can I figure out what is going on? Thanks a lot, Alan
Re: [O] Possible bug in org-cycle with property drawer
Bastien wrote: > Hi Nick, > > Nick Dokos writes: > > > That's it: I had a > > > > #+DRAWERS: JUNK GARBAGE TRASH > > > > line in the file (and I didn't report it in the original email: blush! > > sorry about that). Without it, the property drawer behaves normally. > > Thinking again about your problem, I don't find it natural to > have #+DRAWERS /replacing/ existing drawers specified in `org-drawers', > instead of just adding new ones. > > Do you agree? > > The attached patch implements a new meaning for #+DRAWERS, as a way > to declare "additional" drawers. > > Let me know what you think, thanks! > If I've learnt anything from watching the list over the years, it's that somebody will have a need to replace existing drawers, so be prepared for that :-) That said, I can't think of any reason why adding to existing drawers, instead of replacing them, would lead to problems. So I'm inclined to agree with you. One question that might arise: are multiple #+DRAWERS lines legal? and if so, what do they do? I'll try to take the patch for a spin but I'm not sure when I'll be able to do it. Thanks, Nick
Re: [O] [ANN] ASCII back-end for new export engine
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> I think that your understanding of the new exporter architecture is
>> intimate and secure. I'm happy to follow your lead here.
>
> I know for sure my way around the new exporter, but my LaTeX skills
> aren't on par with that knowledge.
>
> Anyway, I've pushed a commit which tries to create smart links.
>
> Basically, links without a description pointing to an headline will be
> turned into \ref{headline-label}, unless headline's numbering is off, in
> which case they become \hyperref[headline-label]{headline-title}.
>
> Nothing is changed for links providing their own description, and links
> not pointing to headlines.
>
> That should remove the need for a variable.
>
> What do you think about it?
>
Yes, this seems to work nicely. Thanks!
You mentioned unnumbered headlines. I wonder, would it be possible (or
useful) to have the num: option take an integer (like toc:)? As I
understand it now, its value is either nil or not nil. It doesn't
manipulate \secnumdepth, but instead uses \section*, etc. In LaTeX,
section* means not only that the section isn't numbered, but also that
it doesn't go into the table of contents. There are many times when it
is useful to put unnumbered sections in the table of contents.
I've been doing #+LaTeX_HEADER: \setcounter{secnumdepth}{1}, and this
works fine. However, it would be nicer to do num: 1.
A way to set individual headings as numbered or unnumbered would be
deluxe. Perhaps this is possible, but I haven't found it?
>> It looks like a terrific example of the power of your parser.
>
> No, its (albeit useless) power is revealed by the fact that "\n:t" is
> now supported in LaTeX (and ASCII). Such a feat was close to impossible
> with the previous engine.
>
> More seriously, being recursive, the new engine can export thinks like
> "some *text /with nested/ emphasis*" and even "*/important/*".
>
It looks like there will need to be many changes to the documentation.
> And, more importantly, it is mostly made of independent parts, for
> easier maintenance. For example, if I want to fix or improve links in
> e-latex back-end, I know I have to start diving in
> `org-e-latex-link'. That function may call other internal functions,
> but, at least, I have a starting point. That will also be true for any
> other back-end to come.
>
>
> Regards,
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Re: [O] org mode in press
Andreas Leha wrote: > Hi all, > > this just came into my inbox: > http://www.jstatsoft.org/v46/i03 > > Great work! Big thanks to the authors. > I remember reading it with great pleasure back when Eric posted it to the list: beautiful stuff. I look forward to rereading it. Congratulations! Nick
Re: [O] org-support-shift-select and aquamacs
On 26 Jan 2012, at 14:41, Alan Schmitt wrote: Hello, I'm trying to use shift selection in the text part of org files, so I set "org-support-shift-select" to "t". Unfortunately it does not work: nothing happens when I try to select text using shift and arrow keys. I'm using Aquamacs 3 (compiled yesterday) and org-mode from git (compiled this morning). How can I figure out what is going on? With the help of David Reitter on the Aquamacs-devel mailing list, I finally found out what is going on. Aquamacs turns on some parts of cua-mode, which is not recognized by org-support-shift-select. The solution is to add (cua-mode 0) in my preference file. Alan
Re: [O] Multiple agenda buffers at g...@github.com:7max/org-mode.git
At Thu, 26 Jan 2012 06:39:45 -0500,
Found that switching to weekly/daily view was broken, and committed
removal of org-agenda-overriding-restriction and
org-agenda-overriding-arguments from the local var list.
Max Mikhanosha wrote:
>
> I had committed a change that activates local variables, only if
> org-agenda-sticky is turned on, hopefully making it completely safe to
> test for people..
>
> Now if something is screwed up, and you are in a hurry, you can turn
> sticky agenda off and get on with normal org-mode usage, and then send
> bug report later.
>
> At Thu, 26 Jan 2012 06:17:45 -0500,
> Max Mikhanosha wrote:
> >
> > I realize that I may have too many, my initial approach was to start
> > with some obvious one, then test and keep adding to the list.
> >
> > But the bugs that shows up are hard to reproduce, and subtle, and it
> > was slow going, and I was sure I'm missing some.
> >
> > So I went the other direction, and made a list of vars by grepping
> > org-agenda.el for "(defvar ", and tested again, and it was easier
> > to eliminate the variables from the list, since any variables that
> > caused problems usually throw error (due to global value being NIL),
> > instead of doing something subtly wrong that is hard to notice.
> >
> > At Thu, 26 Jan 2012 09:50:22 +, Carsten Dominik wrote:
> > >
> > > Hi Max,
> > >
> > > how did you select the variables that should become buffer-local?
> > > You might have too many in your list, for example
> > > org-last-heading-marker...
> > >
> > > Cheers
> > >
> > > - Carsten
> > >
> > > On 25.1.2012, at 21:45, Max Mikhanosha wrote:
> > >
> > > > I had put my initial implementation of multiple agenda buffers and
> > > > sticky agenda support on g...@github.com:7max/org-mode.git branch
> > > > multiple-agenda-buffers.
> > > >
> > > > To enable, use M-x org-toggle-sticky-agenda
> > > >
> > > > In order to take full advantage of the sticky agenda, you need to give
> > > > your various agendas different buffer names, you can do it by
> > > > including `org-agenda-buffer-name' into the list of bound variables in
> > > > `org-agenda-custom-commands'
> > > >
> > > > For example:
> > > >
> > > > (setq org-agenda-custom-commands
> > > > '(("a" "Agenda and NEXT (priority)"
> > > > ((agenda ""
> > > > ((org-agenda-span 'day)))
> > > > (tags-todo "/!NEXT"
> > > > ((org-agenda-overriding-header "Next Tasks")
> > > > (org-agenda-tags-todo-honor-ignore-options t)
> > > > (org-agenda-todo-ignore-scheduled t)
> > > > (org-agenda-todo-ignore-deadlines t)
> > > > (org-tags-match-list-sublevels t)
> > > > (org-agenda-sorting-strategy
> > > > '(priority-down category-keep)
> > > > ((org-agenda-buffer-name "*Agenda*")))
> > > >("t" "TODO entries"
> > > > todo ""
> > > > ((org-agenda-buffer-name "*Todo List*")
> > > >
> > > >
> > > > When sticky agenda is enabled, most of org-agenda Emacs variables
> > > > become buffer local, and org-agenda-quit is changed to bury the buffer
> > > > instead of killing it. Correspondingly org-agenda will show previously
> > > > buried buffer if it exists, instead of re-generating it.
> > > >
> > > > This allows user to have many "mini-agendas" and switch between them
> > > > rapidly
> > > >
> > > > I would appreciate any bug-reports about things not working, and of
> > > > course patches or fixes for them. The most likely cause of any
> > > > breakage is that `org-agenda-local-vars' list needs adjusting and/or
> > > > fixing.
> > > >
> > > > Regards
> > > > Max
> > >
> >
>
Re: [O] [ANN] ASCII back-end for new export engine
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> You mentioned unnumbered headlines. I wonder, would it be possible (or
> useful) to have the num: option take an integer (like toc:)? As I
> understand it now, its value is either nil or not nil. It doesn't
> manipulate \secnumdepth, but instead uses \section*, etc. In LaTeX,
> section* means not only that the section isn't numbered, but also that
> it doesn't go into the table of contents. There are many times when it
> is useful to put unnumbered sections in the table of contents.
>
> I've been doing #+LaTeX_HEADER: \setcounter{secnumdepth}{1}, and this
> works fine. However, it would be nicer to do num: 1.
I have no objection to implement limited numbering in both LaTeX and
ASCII back-ends, but I'd like to know if it can be handled consistently
in every other major back-end, too. I'm CC-ing Jambunathan to know his
opinion about it.
> A way to set individual headings as numbered or unnumbered would be
> deluxe. Perhaps this is possible, but I haven't found it?
It would require to modify Org's syntax (how to tell which headline has
to be numbered and which has not?). It is not possible at the moment.
Regards,
--
Nicolas Goaziou
[O] [TABLE-OF-CONTENTS] with ODT exporter?
I'm using Org-mode version 7.8.02. I'd like to move the table of contents using [TABLE-OF-CONTENTS] as documented in (org)Top:: > *Note Markup:: > *Note Structural markup elements:: > Table of contents. I'm exporting to ODT, and the table of contents always shows up just after the title information, no matter where I put [TABLE-OF-CONTENTS], and the string [TABLE-OF-CONTENTS] shows up in the ODT document. I assume this means that [TABLE-OF-CONTENTS] isn't supported in the ODT exporter. Is it coming any time soon? Thanks. -Dave
Re: [O] Possible bug in org-cycle with property drawer
Bastien writes: > Thinking again about your problem, I don't find it natural to > have #+DRAWERS /replacing/ existing drawers specified in `org-drawers', > instead of just adding new ones. Well, if one had defined a lot of drawers in their configuration and wanted the list to be trimmed in a few documents... Personally I never customize org-drawer, based on the principle that local configuration shouldn't render documents invalid in a different environment. Based on that principle, if you do configure the drawers for a document, you should provide the complete list and not just some additional configuration, so the current behaviour is perfect. If you change it, I'd now need a way to specify that I do not want to import the local configuration. I'd rather have an extension to #+KEYWORD to import their existing global counterpart, where appropriate. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] [ANN] ASCII back-end for new export engine
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> You mentioned unnumbered headlines. I wonder, would it be possible (or
>> useful) to have the num: option take an integer (like toc:)? As I
>> understand it now, its value is either nil or not nil. It doesn't
>> manipulate \secnumdepth, but instead uses \section*, etc. In LaTeX,
>> section* means not only that the section isn't numbered, but also that
>> it doesn't go into the table of contents. There are many times when it
>> is useful to put unnumbered sections in the table of contents.
>>
>> I've been doing #+LaTeX_HEADER: \setcounter{secnumdepth}{1}, and this
>> works fine. However, it would be nicer to do num: 1.
>
> I have no objection to implement limited numbering in both LaTeX and
> ASCII back-ends, but I'd like to know if it can be handled consistently
> in every other major back-end, too. I'm CC-ing Jambunathan to know his
> opinion about it.
>
>> A way to set individual headings as numbered or unnumbered would be
>> deluxe. Perhaps this is possible, but I haven't found it?
>
> It would require to modify Org's syntax (how to tell which headline has
> to be numbered and which has not?). It is not possible at the moment.
Could this be achieved without a syntax change by adding a new LaTeX
attribute, similar to inparaenum and friends?
#+attr_latex: *
* An Unnumbered Heading
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Re: [O] [ANN] ASCII back-end for new export engine
t...@tsdye.com (Thomas S. Dye) writes: > Nicolas Goaziou writes: > >> t...@tsdye.com (Thomas S. Dye) writes: >>> A way to set individual headings as numbered or unnumbered would be >>> deluxe. Perhaps this is possible, but I haven't found it? >> >> It would require to modify Org's syntax (how to tell which headline has >> to be numbered and which has not?). It is not possible at the moment. > > Could this be achieved without a syntax change by adding a new LaTeX > attribute, similar to inparaenum and friends? > > #+attr_latex: * > * An Unnumbered Heading No. Headlines, along with items, keywords and sections, can't have affiliated keywords. Though, they have properties. It may be done with: :PROPERTIES: :NUMBERING: nil :END: But it's still new syntax. It could also be narrowed to :LATEX_NUMBERING: nil, but I think that this feature, if implemented, should be available for every major back-end, much like "num:1". Regards, -- Nicolas Goaziou
Re: [O] [ANN] ASCII back-end for new export engine
Nicolas Goaziou writes: > But it's still new syntax. It could also be narrowed > to :LATEX_NUMBERING: nil, but I think that this feature, if implemented, > should be available for every major back-end, much like "num:1". Unless I miss something, if "num:*" would be allowed in addition to integers, the LaTeX crowd would be pleased, no terribly new syntax would be needed and all other backends could take note to skip numbering that headline. Maybe one could throw in "nil" and "none" as an alias for "*". Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Re: [O] [babel][patch] BUG in inline source blocks
Martyn Jago writes:
> Hi,
>
> Andreas Leha writes:
>
>> Hi all,
>>
>> I experience unexpected behaviour when an inline source block is not
>> preceded by whitespace.
>>
>> Example:
>> ===
>> * Test inline
>> This is a functional inline src_R{print("source block")}.
>>
>> This (src_R{print("here")}) is not.
>> ===
>>
>> Regards,
>> Andreas
>
> I can confirm this behaviour and provide a patch to allow for inline
> source blocks to be preceded by punctuation, or, for instance, enclosed
> in parenthesis, as in Andreas' example. Patch is attached for
> consideration.
>
> Best, Martyn
This is an updated version of the previous patch, with debug noise
removed, and a couple of extra tests.
Best, Martyn
>From b46e7a496c30f683c50759013ad39a9d8c6ff42b Mon Sep 17 00:00:00 2001
From: Martyn Jago
Date: Thu, 26 Jan 2012 19:48:35 +
Subject: [PATCH] Fix for where inline source block is not preceded by whitespace but by
punctuation (reported by Andreas Leha).
* lisp/ob.el: Fix for where inline source block is not preceded by
whitespace but by punctuation.
* testing/lisp/test-ob.el: Regression tests.
---
lisp/ob.el | 30 ++--
testing/lisp/test-ob.el | 69 +++
2 files changed, 84 insertions(+), 15 deletions(-)
diff --git a/lisp/ob.el b/lisp/ob.el
index 70c258f..fd6a897 100644
--- a/lisp/ob.el
+++ b/lisp/ob.el
@@ -170,24 +170,24 @@ not match KEY should be returned."
(defun org-babel-get-inline-src-block-matches()
"Set match data if within body of an inline source block.
Returns non-nil if match-data set"
- (let ((src-at-0-p (save-excursion
+ (let* ((src-at-0-p (save-excursion
(beginning-of-line 1)
(string= "src" (thing-at-point 'word
(first-line-p (= 1 (line-number-at-pos)))
- (orig (point)))
-(let ((search-for (cond ((and src-at-0-p first-line-p "src_"))
- (first-line-p "[ \t]src_")
- (t "[ \f\t\n\r\v]src_")))
- (lower-limit (if first-line-p
- nil
- (- (point-at-bol) 1
- (save-excursion
- (when (or (and src-at-0-p (bobp))
- (and (re-search-forward "}" (point-at-eol) t)
- (re-search-backward search-for lower-limit t)
- (> orig (point
- (when (looking-at org-babel-inline-src-block-regexp)
- t ))
+ (orig (point))
+ (search-for (cond ((and src-at-0-p first-line-p "src_"))
+ (first-line-p "[ \t[:punct:]]src_")
+ (t "[ \f\t\n\r\v[:punct:]]src_")))
+ (lower-limit (if first-line-p
+ nil
+ (- (point-at-bol) 1
+(save-excursion
+ (when (or (and src-at-0-p (bobp))
+ (and (re-search-forward "}" (point-at-eol) t)
+ (re-search-backward search-for lower-limit t)
+ (> orig (point
+ (when (looking-at org-babel-inline-src-block-regexp)
+ t )
(defvar org-babel-inline-lob-one-liner-regexp)
(defun org-babel-get-lob-one-liner-matches()
diff --git a/testing/lisp/test-ob.el b/testing/lisp/test-ob.el
index 7dccd22..f4363f6 100644
--- a/testing/lisp/test-ob.el
+++ b/testing/lisp/test-ob.el
@@ -430,6 +430,75 @@ this is simple"
(buffer-substring-no-properties
(point-min) (point-max)))
+(ert-deftest test-org-babel/inline-src_blk-preceded-punct ()
+ "Test inline source block where preceded by punctuation"
+
+ ;; inline-src-blk preceded by point
+ (let ((test-line ".src_emacs-lisp[ :results verbatim ]{ \"x\" }"))
+(org-test-with-temp-text
+ test-line
+ (forward-char 1)
+ (org-ctrl-c-ctrl-c)
+ (should (string= (concat test-line " =\"x\"=")
+ (buffer-substring-no-properties
+ (point-min) (point-max))
+
+ ;; inline-src-blk preceded by equality
+ (let ((test-line "=src_emacs-lisp[ :results verbatim ]{ \"x\" }"))
+(org-test-with-temp-text
+ test-line
+ (forward-char 1)
+ (org-ctrl-c-ctrl-c)
+ (should (string= (concat test-line " =\"x\"=")
+ (buffer-substring-no-properties
+ (point-min) (point-max))
+
+ ;; inline-src-blk enclosed within parenthesis
+ (let ((test-line "(src_emacs-lisp[ :results verbatim ]{ \"x\" }"))
+(org-test-with-temp-text
+ (concat test-line ")")
+ (forward-char 1)
+ (org-ctrl-c-ctrl-c)
+ (should (string= (concat test-line " =\"x\"=)" )
+ (buffer-substring-no-properties
+ (point-min) (point-max))
+
+ ;; inline-src-blk enclosed within parenthesis
+ (let ((test-line "{src_emacs-lisp[ :results verbatim ]{ \"x\" }"))
+(org-test-with-temp-text
+ (concat test-line "}")
+ (forward-char 1)
+ (org-ctrl-c-ctrl-c)
+ (should (string= (concat test-line " =\"x\"=}")
+ (buffer-substring-no-properties
+ (point-min) (point-max)))
+
+(ert-deftest test-org-babel/inline-src_blk-preceded-by-letter ()
+ "Test inline source block invalid where preceded by letter"
+
+ ;; inline-src-blk preceded by letter
+ (org-test-with-temp-text
+ "asrc_emacs-lisp[ :results verbatim ]{ \"x\" }"
+(forward-char 1)
+
Re: [O] [ANN] ASCII back-end for new export engine
Nicolas Goaziou writes: > t...@tsdye.com (Thomas S. Dye) writes: > >> Nicolas Goaziou writes: >> >>> t...@tsdye.com (Thomas S. Dye) writes: > A way to set individual headings as numbered or unnumbered would be deluxe. Perhaps this is possible, but I haven't found it? >>> >>> It would require to modify Org's syntax (how to tell which headline has >>> to be numbered and which has not?). It is not possible at the moment. >> >> Could this be achieved without a syntax change by adding a new LaTeX >> attribute, similar to inparaenum and friends? >> >> #+attr_latex: * >> * An Unnumbered Heading > > No. Headlines, along with items, keywords and sections, can't have > affiliated keywords. Though, they have properties. It may be done with: > > :PROPERTIES: > :NUMBERING: nil > :END: > > But it's still new syntax. It could also be narrowed > to :LATEX_NUMBERING: nil, but I think that this feature, if implemented, > should be available for every major back-end, much like "num:1". A properties drawer makes a lot of sense to me in this situation. It would be great if Org Mode had its own mechanisms to specify 1) the level to which sections are numbered and 2) which headlines do not appear in the table of contents. The back-ends could respond to these in an appropriate way or not at all. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
[O] Marking specific elements for folding?
Hello! I was wondering, if there is a way to mark specific elements for staying folded unless explicitly shown. Reading the manual I only found possibilities to control the global folding of sections and blocks in general. However, what I want to do is: - Embed a table of numerical data in my org-mode file. - Perform calculations on the data, using the spread sheet capabilities. - Plot the data, preferably using a (probably lengthy) gnuplot script. - Export only the result graph. However, the calculations are usually not wanted to be seen, when looking at the file, so I'd like to specify, that this specific table and this specific gnuplot code block are to be folded by default. Is there some way to achieve this?
Re: [O] Marking specific elements for folding?
Yu writes: > However, the calculations are usually not wanted to be seen, when > looking at the file, so I'd like to specify, that this specific table > and this specific gnuplot code block are to be folded by default. > > Is there some way to achieve this? You can put them in a drawer. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
[O] how do scientists use org mode?
Hi this is my first post here and although I am evaluating org mode with great interest, I am also asking myself in which way other scientists are making use of org mode. It will take a while to get my head around how to accomplish certain things in org mode but for the moment I am intrigued by *why* one would want to approach the problem of organizing one's research with org mode and in which way. Are you putting exclusively your todos in, well, your todo file and perhaps keep project-related things, such as data and progress, notes, ideas etc. somewhere else? Or do you embed your notes and todos within their original context, i.e. is org mode your one-stop solution for data management? Do you maintain a separate file for every major project you are responsible for or involved in or throw everything into one or few humungous files and differentiate using hierarchies and tags? In the past I have hit some road blocks not so much with other softwares but rather concepts such as GTD, which I think is tailored to the needs of people outside science, so I would deeply appreciate your views and experience. If this list is geared towards the proximate aspects of development and less towards philosophy of usage, I apologize Christoph
Re: [O] how do scientists use org mode?
Aloha Christoph, Welcome to Org Mode. I'm an archaeologist who has found Org mode to be a great help in my scientific work. I use it as a laboratory notebook, a project planner, a platform for carrying out statistical analyses, and a tool for putting together compendia for reproducible research projects. I prefer to put everything for one project in a project-specific Org mode file, with a structure something like this: * Introduction * Results * Conclusions * Laboratory notebook :noexport * Project plan :noexport * Statistical analysis :noexport In this hypothetical example, the first three headlines hold the publication, which will be exported to LaTeX. The last three headlines are not exported, but set up spaces to accomplish different kinds of work. In one case, I use the publication facility of Org mode to create a web site that tracks a long running data entry project. Blocks of R code summarize the data entry with tables and graphs. I update this periodically so that the members of the team can see where we're at and spot data entry errors. I don't make anywhere near full use of Org Mode's capabilities, but find that I am (by my own standards, at least) insanely productive in this environment. It is flexible enough that I feel free to add information, knowing I can reorganize later without difficulty. It is structured enough that I don't waste time looking for things. Even at the early stages of a project, when the best organization hasn't crystallized yet, it is easy enough to identify bits and pieces so they can be easily found later. hth, Tom GMX Christoph 13 writes: > Hi > this is my first post here and although I am evaluating org mode with great > interest, I am also asking myself in which way other scientists are making > use of org mode. It will take a while to get my head around how to accomplish > certain things in org mode but for the moment I am intrigued by *why* one > would want to approach the problem of organizing one's research with org mode > and in which way. > Are you putting exclusively your todos in, well, your todo file and perhaps > keep project-related things, such as data and progress, notes, ideas etc. > somewhere else? Or do you embed your notes and todos within their original > context, i.e. is org mode your one-stop solution for data management? Do you > maintain a separate file for every major project you are responsible for or > involved in or throw everything into one or few humungous files and > differentiate using hierarchies and tags? > In the past I have hit some road blocks not so much with other softwares but > rather concepts such as GTD, which I think is tailored to the needs of people > outside science, so I would deeply appreciate your views and experience. > > If this list is geared towards the proximate aspects of development and less > towards philosophy of usage, I apologize > > Christoph > -- Thomas S. Dye http://www.tsdye.com
Re: [O] export-as-hmtl fail
Hi Martyn, thank you, this helped to track down the problem. Seems to be a conflict with flymake so have disabled that for now. aaron. On 25 January 2012 00:02, Martyn Jago wrote: > Hi Aaron > > aaron barclay writes: > > > Hello, > > > > When I use a python code block in a document any export-as-html results > in > > the error "Invalid file-name". Without a code block the export goes > without > > a hitch. Other exports work no probs such as export-as-ascii. The code > > block within the document acts as expected, it is only the export that > > fails. I was on org7.5 but updated to 7.8.03 but have the same result. > > > > Also, it is only the python code blocks that fail, others work. > > > > My babel setup is > > > > (org-babel-do-load-languages > > 'org-babel-load-languages > > '( (dot . t) > > (sh . t) > > (python . t) > > (emacs-lisp . t) > >)) > > > > (setq org-babel-python-command "python2.6") > > > > My code block is > > > > #+begin_src python :results output > > print "hi" > > > > #+end_src > > > > #+results: > > : hi > > > > Does anyone have any tips on what I might do to troubleshoot this. Could > it > > be something else in my setup or system? Any else ever experienced this? > > > > cheers, > > aaron. > > I can't replicate this error (see my versions below). Even breaking > `org-babel-python-command' does not break your code for me in the way > you describe. > > For diagnostic purposes, you may run the command: > - `M-x toggle-debug-on-error' > ...prior to exporting as html. This should give you a useful backtrace. > > Note also that if you are wishing to export the python results as > opposed to the python code, you will also need :exports results since > the default is `:exports code' . > > HTH > > Best, Martyn > > --- > Org-mode version 7.8.03 (release_7.8.03.192.ga38b.dirty) > GNU Emacs 24.0.92.1 (x86_64-apple-darwin, NS apple-appkit-1038.36) > of 2011-12-02 on bob.porkrind.org > > > > > >
[O] Export without code blocks
Hi, I am having trouble finding the correct way to export a document without the code blocks included. Should I be using #+EXPORT_EXCLUDE_TAGS? I can't seem to get it to work, anyone have the correct syntax? cheers, aaron.
Re: [O] Export without code blocks
Hi Aaron aaron barclay writes: > Hi, > > I am having trouble finding the correct way to export a document without > the code blocks included. Should I be using #+EXPORT_EXCLUDE_TAGS? I can't > seem to get it to work, anyone have the correct syntax? > > cheers, > aaron. #+EXPORT_EXCLUDE_TAGS is for defining tags (such as NO_EXPORT) to prevent headings or sub-headings (branches) being exported. As in: ** don't export me :NO_EXPORT: stuff Possibly what you need is :exports none or :exports results : begin_src python :exports results print "result" end_src What format are you exporting too? Best, Martyn
Re: [O] Export without code blocks
Martyn Jago writes: > Hi Aaron > > aaron barclay writes: > >> Hi, >> >> I am having trouble finding the correct way to export a document without >> the code blocks included. Should I be using #+EXPORT_EXCLUDE_TAGS? I can't >> seem to get it to work, anyone have the correct syntax? >> >> cheers, >> aaron. > > #+EXPORT_EXCLUDE_TAGS is for defining tags (such as NO_EXPORT) to > prevent headings or sub-headings (branches) being exported. As in: > > ** don't export me :NO_EXPORT: > stuff > > Possibly what you need is :exports none or :exports results : > > begin_src python :exports results > print "result" > end_src Of course this won't work in python since it will 'print' result, but not return it. so you also need :results output which makes, the `result' that which is printed to STDOUT (standard out). > What format are you exporting too? > > Best, Martyn
Re: [O] [TABLE-OF-CONTENTS] with ODT exporter?
> this means that [TABLE-OF-CONTENTS] isn't supported in the ODT > exporter. Fixed. Please pull again. --
