Re: [O] Sending commits to Org
Hi Jarmo, Jarmo Hurri writes: > Or, if you are a git newbie like me, and fail to read the relevant part > of the org page on contributing, and make your changes in the original > master, you can also create patches from the original master branch > using the HEAD identifier. You should try to always edit from a dedicated branch. If you commit something in master and want to discard this commit later on, you will end up in trouble. Git makes it really easy to deal with branch. I found this short and useful video: http://www.youtube.com/watch?v=RDGzF2M-zlo HTH, -- Bastien
Re: [O] Visibility cycling with inline tasks
Thanks Carsten and Bastien! On 22 September 2012 11:03, Carsten Dominik wrote: > GReat, thanks! > > - Carsten > > On 22.9.2012, at 11:02, Bastien wrote: > >> Hi Carsten, >> >> Carsten Dominik writes: >> >>> I agree that this would be a good default, but not with a hard-coded 6. >>> >>> (add-hook 'org-cycle-hook >>> (lambda (state) (when (eq state 'contents) >>> (and (boundp 'org-inlinetask-min-level) >>> org-inlinetask-min-level >>> (hide-sublevels (1- org-inlinetask-min-level)) >>> >>> >>> And it is probably better to wrap this into a function and add that function >>> to the default value of org-cycle-hook, after org-cucle-hide-drawers >> >> Done in master. Thanks! >> >> -- >> Bastien >
Re: [O] New LaTeX exporter, Invalid search bound
Hello, t...@tsdye.com (Thomas S. Dye) writes: > A document that exported nicely with the new LaTeX exporter on 9/18 now > fails with a more recent pull from git. I've included a portion of the > backtrace and the section of the org file that triggers the error. I have pushed a fix related to this on master branch. Would you try again and tell me if it's also correct on your side? Thank you. Regards, -- Nicolas Goaziou
Re: [O] question/suggestions about org-refile
Hi Arun, Arun Persaud writes: > I'm using org-capture together with org-refile to organize my > todo-items. I also have my notes distributed over several org-files, so > I have set org-refile-use-outline-path to file. There are two things > that I wished org-refile could do, but don't know how to achieve: > > a) Include local headers for level1 (instead of only file names) > > Using org-refile-use-outline-path=file the path for org refile always > has to start with the file name. It would be great, if in case I don't > give a file name, the current file name would be assumed and would > show org-file names and current top headings for the first level. This > would be helpful, since I mostly refile to the same file, but sometimes > move things to other files. Did you try this? (setq org-refile-use-outline-path t) > b) creating sublevels on the fly > > It would be nice, if I could create new a sublevel during the refiling > process. (setq org-refile-allow-creating-parent-nodes t) HTH, -- Bastien
Re: [O] org-metaup / org-metadown nerfed in 7.9.1
Hello, Trevor Vartanoff writes: > I suppose people who only write and handle text with Internet-style > line breaks between paragraphs won't notice any change. Those who > don't will either get "cannot" messages, or they will be quite > surprised when org scans down, down, down for the next line break and > ends up shifting 20 paragraphs as one element. Org has its own definition for a paragraph, which, apparently, doesn't match yours. A paragraph ends either at a blank line, at the end of the buffer, or at the start of another non-paragraph element. In particular, indentation is unrelated to paragraph boundaries. Hence, there is no such thing as "20 paragraphs as one element". A paragraph is always a single element. Regards, -- Nicolas Goaziou
Re: [O] org-metaup / org-metadown nerfed in 7.9.1
Hello, Bastien writes: > Hi Anthony, > > Anthony Lander writes: > >> I use the M-up/dn behaviour a lot to move property lines up and down. > > Maybe each property line could be a new element recognized as such by > org-element.el. This way org-metaup/down on a property line would move > it up/down. > > (Maybe there are some other benefits from having such an element, > but I'll trust Nicolas on this.) > > Nicolas, what do you think? I'm fine with this change. How would that new element be named? `headline-property'? `property'? Also, do we want this change in 7.9.3? In that case, it may be wise to delay its release by a couple of days. Regards, -- Nicolas Goaziou
Re: [O] Problem with org-entities-user
Hello, Carsten Dominik writes: > On 22.9.2012, at 10:52, Nicolas Goaziou wrote: >> If the LaTeX command doesn't require an argument, you can always add it >> to `org-entities-user'. > > Yes, even though this is not very clean by itself. This is debatable. Entities are perfectly integrated into Org and are, by essence, multiple-back-end friendly. >> Anyway this is a minor point. I guess it will be swept under the rug of >> historical reasons, after all. > > Maybe not. I can go along with your arguments for cleanness. Would you > object to keeping this feature in as an option, turned off be default, > so that it is at least easy to keep lengthy files working? I'd rather leave it as it is, then. This option would require to maintain two versions of the parser: one without LaTeX commands and another one with them. That would defeat the whole point of removing them. > The way I understand it, the new exporter will be default in 8.0, so > this is the time to make some incompatible changes. Indeed. I will preserve my quota of backward-incompatible changes for other things. Regards, -- Nicolas Goaziou
Re: [O] Bug: ob.R sets ess-ask-for-ess-directory to a wrong value [7.8.03 (release_7.9.1.301.g1fea5)]
Vitalie Spinu writes: > This is a custom variable in ESS and is by default t. If org is loaded > before ESS the variable is set to a wrong value. Thanks for the report, I've pushed up a fix. > Package: Org-mode version 7.8.03 (release_7.9.1.301.g1fea5) You really should at least create the autoload files… Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] org-metaup / org-metadown nerfed in 7.9.1
Hi Nicolas, Nicolas Goaziou writes: > How would that new element be named? `headline-property'? `property'? `property' is fine, unless it is semantically too close to other elements and/or objects. > Also, do we want this change in 7.9.3? In that case, it may be wise to > delay its release by a couple of days. Having this for Org 8.0 is okay, lets commit this in master. Thanks! Ps: the next minor release will be 7.9.2. -- Bastien
Re: [O] Problem with org-entities-user
On 23.9.2012, at 10:30, Nicolas Goaziou wrote: > Hello, > > Carsten Dominik writes: > >> On 22.9.2012, at 10:52, Nicolas Goaziou wrote: >>> If the LaTeX command doesn't require an argument, you can always add it >>> to `org-entities-user'. >> >> Yes, even though this is not very clean by itself. > > This is debatable. Entities are perfectly integrated into Org and are, > by essence, multiple-back-end friendly. I only mean in the sense that entities are made to insert symbols and characters, not to execute commands. It certainly can be used to that, but this is not the intention of this mechanism. > >>> Anyway this is a minor point. I guess it will be swept under the rug of >>> historical reasons, after all. >> >> Maybe not. I can go along with your arguments for cleanness. Would you >> object to keeping this feature in as an option, turned off be default, >> so that it is at least easy to keep lengthy files working? > > I'd rather leave it as it is, then. This option would require to > maintain two versions of the parser: one without LaTeX commands and > another one with them. That would defeat the whole point of removing > them. > >> The way I understand it, the new exporter will be default in 8.0, so >> this is the time to make some incompatible changes. > > Indeed. I will preserve my quota of backward-incompatible changes for > other things. OK. - Carsten > > > Regards, > > -- > Nicolas Goaziou
Re: [O] org-metaup / org-metadown nerfed in 7.9.1
On 23.9.2012, at 10:25, Nicolas Goaziou wrote: > Hello, > > Bastien writes: > >> Hi Anthony, >> >> Anthony Lander writes: >> >>> I use the M-up/dn behaviour a lot to move property lines up and down. >> >> Maybe each property line could be a new element recognized as such by >> org-element.el. This way org-metaup/down on a property line would move >> it up/down. >> >> (Maybe there are some other benefits from having such an element, >> but I'll trust Nicolas on this.) >> >> Nicolas, what do you think? > > I'm fine with this change. > > How would that new element be named? `headline-property'? `property'? node-property is another possibility. - Carsten > > Also, do we want this change in 7.9.3? In that case, it may be wise to > delay its release by a couple of days. > > > Regards, > > -- > Nicolas Goaziou >
Re: [O] org-url-hexify-p is not respected
Hi James, sorry to come back late on this. I understand what feels wrong: you store links normally (not using ids), then a library loads org-id.el behind your back, then suddenly storing links is based on ids, not on text, just because the default value for `org-link-to-org-use-id' is 'create-if-interactive-and-no-custom-id. I fixed this in this commit: http://orgmode.org/w/org-mode.git?p=org-mode.git;a=commit;h=0906e3 `org-link-to-org-use-id' has been moved to org-id.el, and its default value is now nil. I will advertize this change more widely in the next bugfix release. Thanks for your patience in struggling with this, -- Bastien
Re: [O] time-up/down in org-agenda-sorting-strategy seems to have no effect?
Hi Richard, this is now fixed, thanks! -- Bastien-more-than-one-year-later
Re: [O] org-capture target files
Hi Kalev, Kalev Takkis writes: > Is it possible to take a note in org-capture and to specify one or > several files to put the message into only after the note is written? You can refile a note from the capture buffer with C-c C-w. I added a command to /copy/ the note instead of refiling it: C-c M-w. Finding the copying location works the same way than for refile. So now you can copy the item from the capture buffer to several files. > The workflow I have in mind is first pressing C-c c to take a note; > selecting the type of note I'd like to take; typing the message, > pasting a link etc., finishing the note, with C-c C-c and then ending > up in a list of available *.org files (which could already be on > display in a window next to capture window) from which I can select > the file(s) where to send the note to. The available process is a bit different: capture, edit, refile or copy, then finalize the capture process. > After some ferocious googling > for the past two months it seems that this kind of system does not > exist (right?). Two months of googling! Phew. :) > But would it be possible to write something like that? After > consulting with the org-capture.el file I have some doubts, all > capture templates expect the destination file to be known beforehand, Yes -- hence the different process describe above. > and the filename is resolved early in the capture process. There is > a template where a function is supposed to find the target and which > is described as the most flexible way, but since the capture already > happens in the target file in an indirect buffer, I don't think it's > flexibility is enough. > > What do you think, is there a way to do this? Please try the new feature if you can (it is in the git master branch) and let me know if it helps. Best, -- Bastien
[O] Make errors from a fresh git clone
Greetings. I am getting a bunch of make errors (20 failed files) when trying to make the newest git version. This is from a clean git clone. The errors are all of the same form; two examples below: Compiling /home/jarmo/src/org/org-mode/lisp/org-ascii.el... In toplevel form: org-ascii.el:29:1:Error: Invalid read syntax: ")" Compiling /home/jarmo/src/org/org-mode/lisp/org-beamer.el... In toplevel form: org-beamer.el:32:1:Error: Invalid read syntax: ")" Any ideas of what might be going wrong? -- Jarmo
Re: [O] Make errors from a fresh git clone
Jarmo Hurri writes: > Any ideas of what might be going wrong? Bastien committed a merge conflict in org-agenda. I've pushed up a fix, but it should probably be reviewed again. For further reports, please say what branch and commit you're on. 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] Make errors from a fresh git clone
Achim Gratz writes: > Jarmo Hurri writes: >> Any ideas of what might be going wrong? > > Bastien committed a merge conflict in org-agenda. I've pushed up a > fix, but it should probably be reviewed again. Ok, it compiles now. Thanks! I thought the decription "fresh git clone" would specify where I was: master and latest revision. sh-4.2$ git status # On branch master nothing to commit (working directory clean) sh-4.2$ git describe release_7.9.1-314-g998e556 sh-4.2$ git log -2 commit 998e5565c4043702a5f583236b0db22bd526dcb4 Author: Achim Gratz Date: Sun Sep 23 16:27:25 2012 +0200 Fix merge conflict in org-agenda.el * lisp/org-agenda.el: Merge conflict due to additional parameters in both maint and master resolved. Needs review! commit ed991f49d7f5d27664ff09ae19e6b7e9690edbfb Merge: a14948c 5a29711 Author: Bastien Guerry Date: Sun Sep 23 12:01:05 2012 +0200 Merge branch 'maint' -- Jarmo
Re: [O] question/suggestions about org-refile
Hello
On 09/23/2012 01:08 AM, Bastien wrote:
> Hi Arun,
>
> Arun Persaud writes:
>
>> I'm using org-capture together with org-refile to organize my
>> todo-items. I also have my notes distributed over several org-files, so
>> I have set org-refile-use-outline-path to file. There are two things
>> that I wished org-refile could do, but don't know how to achieve:
>>
>> a) Include local headers for level1 (instead of only file names)
>>
>> Using org-refile-use-outline-path=file the path for org refile always
>> has to start with the file name. It would be great, if in case I don't
>> give a file name, the current file name would be assumed and would
>> show org-file names and current top headings for the first level. This
>> would be helpful, since I mostly refile to the same file, but sometimes
>> move things to other files.
>
> Did you try this?
>
> (setq org-refile-use-outline-path t)
I used to have this set to file, but then I _always_ had to add the file
name even for local headlines. I now switched to ido using:
(setq ido-everywhere t)
(setq ido-enable-flex-matching t)
(setq ido-max-directory-size 10)
(ido-mode (quote both))
(setq org-refile-use-outline-path nil)
(setq org-completion-use-ido t)
(setq org-outline-path-complete-in-steps nil)
(setq org-refile-targets '((org-agenda-files :maxlevel . 5)
(("~/org/all.org_done" "~/org/work.org_done") :maxlevel . 5) ))
(defun ap/verify-refile-target ()
"Exclude todo keywords with a done state from refile targets"
(or (not (member (nth 2 (org-heading-components)) org-done-keywords)))
(save-excursion (org-goto-first-child))
)
(setq org-refile-target-verify-function 'ap/verify-refile-target)
which works very well for me, especially once I added the
verify-refile-target.
>> b) creating sublevels on the fly
>>
>> It would be nice, if I could create new a sublevel during the refiling
>> process.
>
> (setq org-refile-allow-creating-parent-nodes t)
exactly what I wanted :)
Thanks
Arun
Re: [O] Make errors from a fresh git clone
Achim Gratz writes: > Jarmo Hurri writes: >> Any ideas of what might be going wrong? > > Bastien committed a merge conflict in org-agenda. I've pushed up a fix, > but it should probably be reviewed again. Sorry I overlooked this one and thanks for fixing it! -- Bastien
Re: [O] Make errors from a fresh git clone
Jarmo Hurri writes: > I thought the decription "fresh git clone" would specify Well, it's related to time, so not 100% always clear :) -- Bastien
[O] [PATCH] Lookup functions, take two
Greetings.
Modified the patch as requested: the ordering in the documentation is
now "Column formulas" before the new "Lookup functions".
Also made org-table.el (require 'cl) in general, not only compile time,
because there was a warning of it being required at runtime, but there
is still a warning at compile time. Seemed like a reasonable thing to
do, although given the discussion on possible namespace clashes on the
net makes me doubt the approach. It seems GNU does not like CL. I can
implement a new function corresponding to CL's "position" if you find it
necessary.
Have fun.
--
Jarmo
>From 238551583ecf381d576f42b718e16f1601a43e55 Mon Sep 17 00:00:00 2001
From: Jarmo Hurri
Date: Sun, 23 Sep 2012 18:16:01 +0300
Subject: [PATCH] Lookup functions for tables
* lisp/org-table.el: added functions org-lookup-first and
org-lookup-last
* doc/org.texi: documented the use of lookup functions
---
doc/org.texi | 89 +++-
lisp/org-table.el | 13 ++-
2 files changed, 98 insertions(+), 4 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index e740ca5..2eb8b58 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -378,6 +378,7 @@ The spreadsheet
* Durations and time values:: How to compute durations and time values
* Field and range formulas::Formula for specific (ranges of) fields
* Column formulas:: Formulas valid for an entire column
+* Lookup functions::Lookup functions for searching tables
* Editing and debugging formulas:: Fixing formulas
* Updating the table:: Recomputing all dependent fields
* Advanced features:: Field and column names, parameters and automatic recalc
@@ -2405,6 +2406,7 @@ formula, moving these references by arrow keys
* Durations and time values:: How to compute durations and time values
* Field and range formulas::Formula for specific (ranges of) fields
* Column formulas:: Formulas valid for an entire column
+* Lookup functions::Lookup functions for searching tables
* Editing and debugging formulas:: Fixing formulas
* Updating the table:: Recomputing all dependent fields
* Advanced features:: Field and column names, parameters and automatic recalc
@@ -2790,7 +2792,7 @@ can also be used to assign a formula to some but not all fields in a row.
Named field, see @ref{Advanced features}.
@end table
-@node Column formulas, Editing and debugging formulas, Field and range formulas, The spreadsheet
+@node Column formulas, Lookup functions, Field and range formulas, The spreadsheet
@subsection Column formulas
@cindex column formula
@cindex formula, for table column
@@ -2829,7 +2831,90 @@ stores it. With a numeric prefix argument(e.g.@: @kbd{C-5 C-c =}) the command
will apply it to that many consecutive fields in the current column.
@end table
-@node Editing and debugging formulas, Updating the table, Column formulas, The spreadsheet
+@node Lookup functions, Editing and debugging formulas, Column formulas, The spreadsheet
+@subsection Lookup functions
+@cindex lookup functions in tables
+@cindex table lookup functions
+
+Org has two predefined Emacs Lisp functions for lookups in tables.
+@table @code
+@item (org-lookup-first val search-list return-list &optional predicate)
+@findex org-lookup-first
+Searches for the first element @code{el} in list @code{search-list} for which
+@lisp
+(predicate val el)
+@end lisp
+is @code{t}; returns a value from the corresponding
+position in list @code{return-list}. The default @code{predicate} is
+@code{equal}.
+@item (org-lookup-last val search-list return-list &optional predicate)
+@findex org-lookup-last
+Similar as @code{org-lookup-first} above, but searches for the @i{last} element for which the predicate is
+@code{t}.
+@end table
+
+The examples below illustrate searches inside a single table. In real-world
+applications, the searched data is often in a different table and is accessed
+by remote references.
+
+The first example contains the searched data in the first and the second
+column. The lookup is performed in column 5, where the year corresponding to
+the percentage in column 4 is searched. Notice that an error is returned if
+the lookup is unsuccessful.
+@example
+@group
+ | year | percentage | | percentage | year |
+ |--++---++|
+ | 2009 | 12.2 | | 14.3 | 2010 |
+ | 2010 | 14.3 | | 19.4 | 2012 |
+ | 2011 | 14.3 | | 11.5 | #ERROR |
+ | 2012 | 19.4 | || #ERROR |
+ #+TBLFM: $5='(org-lookup-first $4 '(@@2$2..@@>$2) '(@@2$1..@@>$1));N
+@end group
+@end example
+
+The second example illustrates standard use of lookups for teachers. The
+first two columns contain a grading table. The fourth and the fifth column
+contain student names and their marks, and the last column contains the
+results of doing a lookup for the appropriate grade. Notice the use of
+@c
Re: [O] question/suggestions about org-refile
Hi Arun, Arun Persaud writes: > I used to have this set to file, but then I _always_ had to add the file > name even for local headlines. It does not require the file name here and now. Maybe an old behavior. > I now switched to ido using: > > [...] > > which works very well for me, especially once I added the > verify-refile-target. Nice. Maybe you could add this somewhere on Worg? Best, -- Bastien
Re: [O] question/suggestions about org-refile
On 09/23/2012 08:27 AM, Bastien wrote: > Hi Arun, > > Arun Persaud writes: > >> I used to have this set to file, but then I _always_ had to add the file >> name even for local headlines. > > It does not require the file name here and now. > Maybe an old behavior. > >> I now switched to ido using: >> >> [...] >> >> which works very well for me, especially once I added the >> verify-refile-target. > > Nice. Maybe you could add this somewhere on Worg? sure, should I create a new headline "refile" on the tutorial place or should it go somewhere else? Arun
Re: [O] New LaTeX exporter, Invalid search bound
Nicolas Goaziou writes: > Hello, > > t...@tsdye.com (Thomas S. Dye) writes: > >> A document that exported nicely with the new LaTeX exporter on 9/18 now >> fails with a more recent pull from git. I've included a portion of the >> backtrace and the section of the org file that triggers the error. > > I have pushed a fix related to this on master branch. Would you try > again and tell me if it's also correct on your side? > > Thank you. > > > Regards, Thanks Nicolas, my document exports as expected now. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
[O] No title in org-export-as-odt
Hi, Any hint to get rid of the title in a org-export-as-odt session? I've tried #+OPTIONS: title:nil author:nil timestamp:nil toc:nil #+LANGUAGE: es * HELLO and I get the filename as odt file title. If I try #+TITLE: #+OPTIONS: title:nil author:nil timestamp:nil toc:nil #+LANGUAGE: es * HELLO I get an empty line, OrgTitle-styled. Run out of ideas. TIA
Re: [O] org-capture target files
On Sun, Sep 23, 2012 at 1:11 PM, Bastien wrote: > Hi Kalev, > > Kalev Takkis writes: > > > Is it possible to take a note in org-capture and to specify one or > > several files to put the message into only after the note is written? > > You can refile a note from the capture buffer with C-c C-w. > > I added a command to /copy/ the note instead of refiling it: C-c M-w. > Finding the copying location works the same way than for refile. So > now you can copy the item from the capture buffer to several files. > > > The workflow I have in mind is first pressing C-c c to take a note; > > selecting the type of note I'd like to take; typing the message, > > pasting a link etc., finishing the note, with C-c C-c and then ending > > up in a list of available *.org files (which could already be on > > display in a window next to capture window) from which I can select > > the file(s) where to send the note to. > > The available process is a bit different: capture, edit, refile or copy, > then finalize the capture process. > > > After some ferocious googling > > for the past two months it seems that this kind of system does not > > exist (right?). > > Two months of googling! Phew. :) > > > But would it be possible to write something like that? After > > consulting with the org-capture.el file I have some doubts, all > > capture templates expect the destination file to be known beforehand, > > Yes -- hence the different process describe above. > > > and the filename is resolved early in the capture process. There is > > a template where a function is supposed to find the target and which > > is described as the most flexible way, but since the capture already > > happens in the target file in an indirect buffer, I don't think it's > > flexibility is enough. > > > > What do you think, is there a way to do this? > > Please try the new feature if you can (it is in the git master branch) > and let me know if it helps. > > Best, > > -- > Bastien > Thanks, I tried it out and it seems to work. Hopefully it will be useful for others too. Another thing I've been meaning to ask: org-capture-mode-hook seems to be triggered twice, why is that? It was also present in the previous version of org that I used, 7.8.02 and I can confirm now it's there in the latest git version also. If it's not a bug but a desired feature can I disable it from running twice? I'd like to attach some code to it and getting the results twice is slightly annoying. Regards, Kalev
Re: [O] Inline and executing the document
One more thought:
The :RESULTS: :END:
wrapper would allow to replace when inline code is run once again.
It would fit with my personal workflow to be able to check what will go into
the exported documents
while fiddling around in the source document.
If this does not fit with what the org designers think, thats OK.
I just wanted to note that the implementation replacement of results of inline
code
in this special case could probably done with ease.
Erich
On Sep 20, 2012, at 9:09 PM, Neuwirth Erich wrote:
> Thank you,
> this clarified things for me!
>
> I will look and suggest a place for mentioning this in the docs.
>
> Erich
>
>
> On Sep 20, 2012, at 4:23 PM, Neuwirth Erich
> wrote:
>
>> Sorry for not reading the docs carefully enough.
>> I had overlooked :results wrap
>> But even with this options things behave strangely.
>>
>> src_emacs-lisp[:results wrap]{(+ 2 3)} :RESULTS:
>> 5:END:
>> :RESULTS:
>> 5:END:
>> :RESULTS:
>> 5:END:
>> :RESULTS:
>> 5:END:
>> :RESULTS:
>> 5:END:
>>
>>
>> Running the code multiple times in the document produces multiple outputs.
>> I though the whole idea of wrapping was intended to mark results in a way
>> the are replaces
>> when the command is reexecuted.
>>
>> Furthermore, on exporting the keywords :RESULTS: and :END:
>> are written into the exported document (I tried LaTeX+pdf and HTML)
>>
>> Am I still misunderstanding something?
>>
>>
>>
>
>
[O] [org-e-beamer-export-to-pdf] Slide with two columns?
Hi, Can anyone make a two column slide yet? Like this example for the old exporter: http://orgmode.org/worg/sources/org-tutorials/org-beamer/presentation.org It looks as if it should be possible (by which I mean the appropriate properties are available), just wondering if it is something wrong with my setup. Thanks, Myles
Re: [O] org-metaup / org-metadown nerfed in 7.9.1
Hello, Carsten Dominik writes: > node-property is another possibility. There's now a new element type in master: node-property. Regards, -- Nicolas Goaziou
Re: [O] [org-e-beamer-export-to-pdf] Slide with two columns?
Hello,
Myles English writes:
> Can anyone make a two column slide yet? Like this example for the old
> exporter:
>
> http://orgmode.org/worg/sources/org-tutorials/org-beamer/presentation.org
>
> It looks as if it should be possible (by which I mean the appropriate
> properties are available), just wondering if it is something wrong with
> my setup.
You can have a look at the following example:
--8<---cut here---start->8---
#+TITLE: Two columns
#+LaTeX_CLASS: beamer
#+BEAMER_THEME: Rochester [height=20pt]
#+BEAMER_COLOR_THEME: spruce
* Frame title
Some text before
** Column without title
:BMCOL:
:PROPERTIES:
:BEAMER_col: 0.5
:END:
Some text
** Alert block in another column
:B_alertblock:BMCOL:
:PROPERTIES:
:BEAMER_env: alertblock
:BEAMER_col: 0.5
:END:
Alert !
** Quit column env with an ignoreheading
:B_ignoreheading:
:PROPERTIES:
:BEAMER_env: ignoreheading
:END:
You also quit column env with any other block type as long as there
is no BEAMER\under{}col property in the headline.
--8<---cut here---end--->8---
Regards,
--
Nicolas Goaziou
Re: [O] question/suggestions about org-refile
Arun Persaud writes: > sure, should I create a new headline "refile" on the tutorial place or > should it go somewhere else? As you want. I think worg/org-hacks.org could do. -- Bastien
Re: [O] org-metaup / org-metadown nerfed in 7.9.1
Nicolas Goaziou writes: > There's now a new element type in master: node-property. Fantastic, thanks! -- Bastien
Re: [O] No title in org-export-as-odt
Hi Miguel, Miguel Ruiz writes: > Any hint to get rid of the title in a org-export-as-odt session? I don't think you can > #+OPTIONS: title:nil author:nil timestamp:nil toc:nil ^ This option is not supported. -- Bastien
Re: [O] Inline and executing the document
Hi Erich,
Erich Neuwirth writes:
> One more thought:
> The :RESULTS: :END:
> wrapper would allow to replace when inline code is run once again.
> It would fit with my personal workflow to be able to check what will go into
> the exported documents
> while fiddling around in the source document.
>
> If this does not fit with what the org designers think, thats OK.
It would not be a "drawer" anymore.
> I just wanted to note that the implementation replacement of results of
> inline code
> in this special case could probably done with ease.
FWIW you can use src_{} for inline code.
Best,
--
Bastien
Re: [O] Problem with org-entities-user
Carsten Dominik writes: > On 23.9.2012, at 10:30, Nicolas Goaziou wrote: > >> Hello, >> >> Carsten Dominik writes: >> >>> On 22.9.2012, at 10:52, Nicolas Goaziou wrote: If the LaTeX command doesn't require an argument, you can always add it to `org-entities-user'. >>> >>> Yes, even though this is not very clean by itself. >> >> This is debatable. Entities are perfectly integrated into Org and are, >> by essence, multiple-back-end friendly. > > I only mean in the sense that entities are made to insert symbols and > characters, not to execute commands. It certainly can be used to that, > but this is not the intention of this mechanism. > Yes, this is the essence of the mismatch. The mechanism is designed to work with entities, but the regular expression catches all LaTeX commands, whose names don't distinguish entities from other constructs AFAIK. >> Anyway this is a minor point. I guess it will be swept under the rug of historical reasons, after all. >>> >>> Maybe not. I can go along with your arguments for cleanness. Would you >>> object to keeping this feature in as an option, turned off be default, >>> so that it is at least easy to keep lengthy files working? >> >> I'd rather leave it as it is, then. This option would require to >> maintain two versions of the parser: one without LaTeX commands and >> another one with them. That would defeat the whole point of removing >> them. >> >>> The way I understand it, the new exporter will be default in 8.0, so >>> this is the time to make some incompatible changes. >> >> Indeed. I will preserve my quota of backward-incompatible changes for >> other things. > > > OK. > Two versions of the parser! Yikes, that doesn't sound good. Links still provide a path to handle arbitrary LaTeX commands and have them send sensible output to the different backends. They don't look so great in the Org buffer, but that is an aesthetic issue, not functional. Thanks, Nicolas, for the new LaTeX exporter. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] Org table html export problem
Hi Jai, Jai writes: > I'm getting couple of html export errors. Please find org files and > corresponding backtraces attached. I can't reproduce this error. Maybe someone else can. Otherwise, if you can, please test latest code from git. Thanks! -- Bastien
[O] new exporter: exporting subtree as beamer
Hi all,
I am having trouble to export a subtree as beamer document with the new
exporter. (Org-mode version 7.9.1 (release_7.9.1-316-g66fe32)
Here is a simple org-document, that was prepared for beamer export using
org-e-beamer-insert-options-template:
[ test_beamer.org ]
* Test Beamer
:PROPERTIES:
:EXPORT_LaTeX_CLASS: beamer
:EXPORT_LaTeX_CLASS_OPTIONS: [presentation]
:EXPORT_FILE_NAME: presentation.pdf
:COLUMNS: %45ITEM %10BEAMER_env(Env) %10BEAMER_act(Act) %4BEAMER_col(Col)
%8BEAMER_opt(Opt)
:BEAMER_col_ALL: 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 0.0 :ETC
:END:
** First Slide :B_frame:
:PROPERTIES:
:BEAMER_env: frame
:END:
- first bullet
And this is what I get when I export the subtree "Test Beamer" as
beamer:
[ TeX export ]
% Created 2012-09-23 So 21:07
\usetheme{default}
\author{Andreas Leha}
\date{\today}
\title{Test Beamer}
\hypersetup{
pdfkeywords={},
pdfsubject={},
pdfcreator={Generated by Org mode 7.9.1 in Emacs 24.2.50.1.}}
\begin{document}
\maketitle
\begin{frame}{Outline}
\tableofcontents
\end{frame}
\begin{frame}[label=sec-1]{First Slide}
\begin{itemize}
\item first bullet
\end{itemize}
\end{frame}
% Generated by Org mode 7.9.1 in Emacs 24.2.50.1.
\end{document}
What am I missing here?
Regards,
Andreas
Re: [O] new exporter: exporting subtree as beamer
Hello, Andreas Leha writes: > I am having trouble to export a subtree as beamer document with the new > exporter. (Org-mode version 7.9.1 (release_7.9.1-316-g66fe32) > > Here is a simple org-document, that was prepared for beamer export using > org-e-beamer-insert-options-template: > > > [ test_beamer.org ] > * Test Beamer >:PROPERTIES: >:EXPORT_LaTeX_CLASS: beamer >:EXPORT_LaTeX_CLASS_OPTIONS: [presentation] >:EXPORT_FILE_NAME: presentation.pdf >:COLUMNS: %45ITEM %10BEAMER_env(Env) %10BEAMER_act(Act) %4BEAMER_col(Col) > %8BEAMER_opt(Opt) >:BEAMER_col_ALL: 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 0.0 :ETC >:END: > > ** First Slide > :B_frame: > :PROPERTIES: > :BEAMER_env: frame > :END: > - first bullet > > > > > And this is what I get when I export the subtree "Test Beamer" as > beamer: The code produced looks correct. What did you expect? Regards, -- Nicolas Goaziou
Re: [O] new exporter: exporting subtree as beamer
Hi Nicolas,
> Hello,
>
> Andreas Leha writes:
>
>> I am having trouble to export a subtree as beamer document with the new
>> exporter. (Org-mode version 7.9.1 (release_7.9.1-316-g66fe32)
>>
>> Here is a simple org-document, that was prepared for beamer export using
>> org-e-beamer-insert-options-template:
>>
>>
>> [ test_beamer.org ]
>> * Test Beamer
>>:PROPERTIES:
>>:EXPORT_LaTeX_CLASS: beamer
>>:EXPORT_LaTeX_CLASS_OPTIONS: [presentation]
>>:EXPORT_FILE_NAME: presentation.pdf
>>:COLUMNS: %45ITEM %10BEAMER_env(Env) %10BEAMER_act(Act)
>> %4BEAMER_col(Col) %8BEAMER_opt(Opt)
>>:BEAMER_col_ALL: 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 0.0 :ETC
>>:END:
>>
>> ** First Slide
>> :B_frame:
>> :PROPERTIES:
>> :BEAMER_env: frame
>> :END:
>> - first bullet
>>
>>
>>
>>
>> And this is what I get when I export the subtree "Test Beamer" as
>> beamer:
>
> The code produced looks correct. What did you expect?
>
>
> Regards,
thanks for looking into this. Sorry for not being clear.
I was expecting a compilable Beamer document. Especially, I am missing
a document class in the exported TeX:
[ TeX export ]
% Created 2012-09-23 So 21:07
\usetheme{default}
\author{Andreas Leha}
\date{\today}
\title{Test Beamer}
\hypersetup{
pdfkeywords={},
pdfsubject={},
pdfcreator={Generated by Org mode 7.9.1 in Emacs 24.2.50.1.}}
\begin{document}
\maketitle
\begin{frame}{Outline}
\tableofcontents
\end{frame}
\begin{frame}[label=sec-1]{First Slide}
\begin{itemize}
\item first bullet
\end{itemize}
\end{frame}
% Generated by Org mode 7.9.1 in Emacs 24.2.50.1.
\end{document}
Best,
Andreas
[O] [Bug] org-capture datetree+prompt: wrong time (range) information in timestamp (%T escape sequence)
Dear org-mode users and developers,
* what I want to do
I want to use org-capture instead of Emacs diary (+calendar)
[fn:1] in order to record all kinds of events and appointments.
* how I try to achieve this
I try to use org-capture. I want to be prompted for the date of
the event or the date and time / time range of the appointment.
I want the event/appointment to be recorded in a date tree under
it's respective date, not under today. I want a timestamp in the
resulting heading in order to see the date/appointment in the
agenda view and I want to see the respective time (range)
information if there is any.
I tried to achieve this with an file+datetree+prompt template as
such:
(setq org-capture-templates (quote (
("d" "diary the Org way" entry (file+datetree+prompt
"~/org/diary.org") "* %? %T
noted: %U"
* how it works
If using this template I'm prompted for a date and this date is
used as target in the date tree. That's fine. The same date is
also used in the timestamp of the captured items heading which is
produced via expansion of the %T exscape. That#s fine too. If I
also enter at the same prompt a time for the appointment as
e.g. 19:00 this time information is reused in the time stamp in
the heading. That's fine too. This way I'm able to enter
appointments.
* when it does not work
But there are two problems with the time information, which I
consider to be bugs:
1) If I enter a time *range* at the prompt, the %T expands to the
time when I invoked the capture ("now") while the date is
still the entered day, not today. This is a mixture of the
events date / recording time which I consider to be a bug.
Instead I expect to see the date and time range of the
appointment.
2) If I do not enter a time at all, since for instance the date
is not bound to a time (e.g. holiday, birthday) the %T also
expands to the time when I invoked the capture ("now") while
the date is still the entered day, not today.
Here instead I expect to see no time information at all, since
I did not enter one.
At least I also consider the mixture of the events date /
recording time information a bug.
* how to reproduce the bug
This is with
- Emacs GNU Emacs 24.2.50.1 (i486-pc-linux-gnu, X
toolkit, Xaw scroll bars) of 2012-09-19 on dex, modified by
Debian (Emacs-snapshot)
- Org-mode version 7.9.1 (release_7.9.1-316-g66fe32 @
/home/grfz/src/org-mode/lisp/)
I tested this with Emacs -Q and this minimal setup:
(add-to-list 'load-path (expand-file-name "~/src/org-mode/lisp"))
(setq load-path (cons "~/src/org-mode/contrib/lisp/" load-path))
(setq load-path (cons "~/.Emacs.d/elisp" load-path))
(require 'org-install)
(global-set-key "\C-cc" 'org-capture)
(setq org-capture-templates (quote (
("d" "diary the Org way" entry (file+datetree+prompt
"~/org/diary.org") "* %? %T"
* how grateful I am
Thanks for your attention and for org-mode, Gregor
--
-... --- .-. . -.. ..--.. ...-.-
Footnotes:
[fn:1] Mostly for performance reasons: Building the Agenda is
slow due to my large diary file. It's much faster if
appointment data is stored in org files.
Re: [O] org-metaup / org-metadown nerfed in 7.9.1
Hi Bastien, On 12-Sep-22, at 5:24 AM, Bastien wrote: > Hi Anthony, > > Anthony Lander writes: > >> I use the M-up/dn behaviour a lot to move property lines up and down. > > Maybe each property line could be a new element recognized as such by > org-element.el. This way org-metaup/down on a property line would move > it up/down. That would be wonderful - and I see that it will be in 8.0! Thank you & Nicolas for that. -Anthony
Re: [O] new exporter: exporting subtree as beamer
Andreas Leha writes:
> I was expecting a compilable Beamer document. Especially, I am missing
> a document class in the exported TeX:
>
> [ TeX export ]
> % Created 2012-09-23 So 21:07
> \usetheme{default}
> \author{Andreas Leha}
> \date{\today}
> \title{Test Beamer}
> \hypersetup{
>pdfkeywords={},
>pdfsubject={},
>pdfcreator={Generated by Org mode 7.9.1 in Emacs 24.2.50.1.}}
> \begin{document}
>
> \maketitle
> \begin{frame}{Outline}
> \tableofcontents
> \end{frame}
>
>
> \begin{frame}[label=sec-1]{First Slide}
> \begin{itemize}
> \item first bullet
> \end{itemize}
> \end{frame}
> % Generated by Org mode 7.9.1 in Emacs 24.2.50.1.
> \end{document}
>
You need a "beamer" entry in `org-e-latex-classes' (note: "beamer" name
isnt't mandatory, but it has to match the LaTeX class requested).
I use the following:
#+begin_src emacs-lisp
(add-to-list 'org-e-latex-classes
'("beamer"
"\\documentclass[presentation]{beamer}
\[DEFAULT-PACKAGES]
\[PACKAGES]
\[EXTRA]"
("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
("\\subsubsection{%s}" . "\\subsubsection*{%s}")))
#+end_src
Regards,
Re: [O] new exporter: exporting subtree as beamer
Hi Nicolas,
> Andreas Leha writes:
>
>> I was expecting a compilable Beamer document. Especially, I am missing
>> a document class in the exported TeX:
>>
>
> You need a "beamer" entry in `org-e-latex-classes' (note: "beamer" name
> isnt't mandatory, but it has to match the LaTeX class requested).
>
> I use the following:
>
> #+begin_src emacs-lisp
> (add-to-list 'org-e-latex-classes
> '("beamer"
>"\\documentclass[presentation]{beamer}
> \[DEFAULT-PACKAGES]
> \[PACKAGES]
> \[EXTRA]"
>("\\section{%s}" . "\\section*{%s}")
>("\\subsection{%s}" . "\\subsection*{%s}")
>("\\subsubsection{%s}" . "\\subsubsection*{%s}")))
> #+end_src
Thanks a lot. That was the missing piece.
Regards,
Andreas
Re: [O] new exporter: exporting subtree as beamer
Hi Nicolas, >> [ test_beamer.org ] >> * Test Beamer >>:PROPERTIES: >>:EXPORT_LaTeX_CLASS: beamer >>:EXPORT_LaTeX_CLASS_OPTIONS: [presentation] >>:EXPORT_FILE_NAME: presentation.pdf >>:COLUMNS: %45ITEM %10BEAMER_env(Env) %10BEAMER_act(Act) >> %4BEAMER_col(Col) %8BEAMER_opt(Opt) >>:BEAMER_col_ALL: 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 0.0 :ETC >>:END: >> >> ** First Slide >> :B_frame: >> :PROPERTIES: >> :BEAMER_env: frame >> :END: >> - first bullet >> One more thing, though. The "EXPORT_FILE_NAME" is ignored at my side. Regards, Andreas
Re: [O] Org table html export problem
Thank you Bastien. My apoligies, my incorrect settings to "org-export-html-table-tag" variable were the cause of the problem. Now it works. Thank you, Jai
Re: [O] org-e-groff-export-to-groff produces empty output file
Nicolas Goaziou writes: > `e-html' back-end turns them into images (with, i.e. dvipng). Would that > be applicable to Groff as well? Hi: I did a test with the dvipng output and the issue is converting it to EPS after they have been generated. The better solution is to add support for dvips to get an EPS directly from DVI. I'll play with org.el and see if I get it going. Luis -- Luis Anaya papo anaya aroba hot mail punto com "Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo
Re: [O] dnd-protocol-alist and org
*bump* Does anyone else think that'd be a nice feature? I'm having a hard time making dnd-protocol-alist work on OSX though, any hints appreciated :) On Wed, Sep 5, 2012 at 8:35 PM, Marcelo de Moraes Serpa wrote: > In addition to that: An even more awesome feature would be to hook into > the pasting process in emacs, get that data, save that to a pre-defined > location, and link it in the org buffer. Imagine copying an image from > anywhere and being able to insert it in the org buffer with just a paste > command! :) > > > On Wed, Sep 5, 2012 at 8:31 PM, Marcelo de Moraes Serpa < > celose...@gmail.com> wrote: > >> Hi list, >> >> I've been trying to get dnd-protocol-alist to work on Emacs 23, OSX (GNU >> Emacs 23.4.1 (x86_64-apple-darwin, NS apple-appkit-1038.36) of 2012-01-29 >> on bob.porkrind.org) but couldn't so far. Has anyone got it to work with >> Cocoa Emacs? >> >> I think this could be used to implement some real cool features, such as >> dragging-and-dropping->auto-archiving of images and other file types. This >> way, one could, for example, drag an image into an org buffer, and it would >> be copied to a pre-configured location and displayed auto-magically. What >> do you think? >> >> Cheers, >> >> Marcelo. >> >> >> >> >
Re: [O] org-capture target files
Hi Kalev, Kalev Takkis writes: > Another thing I've been meaning to ask: org-capture-mode-hook seems > to be triggered twice, why is that? This was a bug, fixed. Thanks for reporting it, -- Bastien
Re: [O] dnd-protocol-alist and org
Hi Marcelo, Marcelo de Moraes Serpa writes: > *bump* Does anyone else think that'd be a nice feature? I'm having a > hard time making dnd-protocol-alist work on OSX though, any hints > appreciated :) AFAIU this is a general Emacs question, maybe you'll have more chance on emacs-devel. -- Bastien
Re: [O] indenting in todo list agendas
Hi, Wiskey 5 Alpha writes: > I use org-tags-match-list-sublevels 'indented to create an indented > list when using tags-todo. How can I do the same if I want to make a > todo agenda view ? in the git master branch, you can use the %l specifier for `org-agenda-prefix-format'. This will insert as many spaces as the level of the TODO entry. Please read the docstring for details. HTH, -- Bastien
Re: [O] No title in org-export-as-odt
Hi,
> Miguel Ruiz
> writes:
>
> > Any hint to get rid of the title in a org-export-as-odt
> session?
>
> I don't think you can
org-odt-format-preamble function says:
...
(when title
(concat
(org-odt-format-stylized-paragraph
'title (org-odt-format-tags
'("" . "") title))
;; separator
""))
...
So I only need to find a way to assign nil to title variable inside the
document.
Also I might define a new option with org-export-inbuffer-options-extra, but
the elaboration of the function is beyond my knowledge.
I would appreciate any idea.
>
> > #+OPTIONS: title:nil author:nil timestamp:nil
> toc:nil
>
> ^
>
> This option is not supported.
>
> --
> Bastien
>
>
Thanks.
Re: [O] No title in org-export-as-odt
Miguel Ruiz wrote:
> Hi,
>
>
> > Miguel Ruiz
> > writes:
> >
> > > Any hint to get rid of the title in a org-export-as-odt
> > session?
> >
> > I don't think you can
>
>
> org-odt-format-preamble function says:
>
> ...
> (when title
> (concat
> (org-odt-format-stylized-paragraph
> 'title (org-odt-format-tags
> '("" . "") title))
> ;; separator
> ""))
> ...
>
> So I only need to find a way to assign nil to title variable inside the
> document.
>
I don't think you can unless you change the code. The title is set in
org-lparse.el::org-do-lparse
like this:
,
| ...
|(title (org-xml-encode-org-text-skip-links
| (or (and subtree-p (org-export-get-title-from-subtree))
| (plist-get opt-plist :title)
| (and (not body-only)
| (not
|(plist-get opt-plist :skip-before-1st-heading))
| (org-export-grab-title-from-buffer))
| (and buffer-file-name
| (file-name-sans-extension
|(file-name-nondirectory buffer-file-name)))
| "UNTITLED")))
| ...
`
so even if you arrange for the opt-plist to set :title to nil,
the buffer-file-name will override it.
Nick
> Also I might define a new option with org-export-inbuffer-options-extra, but
> the elaboration of the function is beyond my knowledge.
>
> I would appreciate any idea.
>
>
> >
> > > #+OPTIONS: title:nil author:nil timestamp:nil
> > toc:nil
> >
> > ^
> >
> > This option is not supported.
> >
> > --
> > Bastien
> >
> >
>
> Thanks.
>
>
