Re: [Orgmode][babel] How to add results to text inline?
Hi Torsten,
Have a look at the 'src_{}' construct as described here:
http://orgmode.org/org.html#Structure-of-code-blocks
Hth,
Andreas
Am 23.02.2011 06:55, schrieb Torsten Wagner:
> Hi,
>
> guess this is a FAQ or at least a stupid question.
> However, I read along worg and wasn't able to find a solution.
>
> I would like to add the result of a source code block in some text
> paragraph.
>
> ---start--mini-example
>
> #+source:my_formula(my_parameter='1')
> #+begin_src python :results value :exports code
> y = 2
> f = my_parameter * y
> return f
> #+end_src
>
> In my long long paragraph after that I want to say that
> my result is #+call: my_formula(my_parameter='5') for x=5 but it is
> #+call: my_formula() for x=1
>
> ---end--mini-example
>
> Well I would replace the calls by the result of the source code block
> I read about no-web but this seems to work only within code blocks. I
> read about inline source code blocks, however, more complex functions
> would make it difficult to read.
>
> Thanks for pointing me to obvious solutions ;)
>
> Torsten
>
> CC. How about some C-like format string for number results like
> #+call: my_formula(my_parameter='5') :exports results :format %i5
> results in integer 5 digits
> 00010
> and #+call: my_formula(my_parameter='5') :exports results :format %s.3
> could result in scientific notation with 3 digits after the comma
> 1.000*10^1
>
> This would allow to format the result to the needs just in place.
>
> ___
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
smime.p7s
Description: S/MIME Cryptographic Signature
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode][babel] How to add results to text inline?
Hi, guess this is a FAQ or at least a stupid question. However, I read along worg and wasn't able to find a solution. I would like to add the result of a source code block in some text paragraph. ---start--mini-example #+source:my_formula(my_parameter='1') #+begin_src python :results value :exports code y = 2 f = my_parameter * y return f #+end_src In my long long paragraph after that I want to say that my result is #+call: my_formula(my_parameter='5') for x=5 but it is #+call: my_formula() for x=1 ---end--mini-example Well I would replace the calls by the result of the source code block I read about no-web but this seems to work only within code blocks. I read about inline source code blocks, however, more complex functions would make it difficult to read. Thanks for pointing me to obvious solutions ;) Torsten CC. How about some C-like format string for number results like #+call: my_formula(my_parameter='5') :exports results :format %i5 results in integer 5 digits 00010 and #+call: my_formula(my_parameter='5') :exports results :format %s.3 could result in scientific notation with 3 digits after the comma 1.000*10^1 This would allow to format the result to the needs just in place. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] How-to access org-mode data
Nevermind, I just found 'hacking' on worg might have some infos I could start with Torsten On 02/22/2011 09:40 PM, Torsten Wagner wrote: Hi, I try to extract certain information which are processed by org-mode. As an example the compiled agenda-list. Basically, I want to have certain parts of the agenda in a variable (or an array) instead of a buffer. I tried to follow org-agenda.el but this seems to be hard of a elisp beginner. At the moment I'm unsure what would be the best way to get those infos. I could run e.g., (org-agenda list nil nil 1) however, this always end up in a buffer, which I could start parsing and closing afterwards, but maybe there is a more smart way? I don't want to break any code and try to get this on top of the original org-mode code. To keep it simple for an example: Create org-agenda get the very next thing which need to be done as a string into a variable call result Any feedback is welcome Thanks Torsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Possible Calc support for Org-Babel?
Christopher Allan Webber writes: > (failed to wide-reply initially) > > I just had use for this for some quick calculations I wanted to add to > one of my files, but... > > Any idea why variables inside of parentheses don't work, but variables > outside of them do? > > #+BEGIN_SRC calc :var testvar=9000 > testvar - 200 > #+END_SRC > > #+results: > : 8800 > > > #+BEGIN_SRC calc :var testvar=9000 > (testvar - 200) 800 > #+END_SRC > > #+results: > : 800 testvar - 16 > Hi Christopher, Sorry about the LONG delay in replying to this email. I've just pushed up a fix for this problem. Thanks for reporting. Best -- Eric ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: [babel][patch] C++ inconsistencies
[...] > > Hi Eric > > Apologies, I'm still familiarising myself with Gnus but hopefully this > will work. > Worked perfectly, this is now applied thanks. > > Also thanks for Babel, I think its got a great future! > With engaged users sending in patches and improvements I'm sure it will. Thanks! -- Eric > > Regards > > Martyn > ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Nice python listings colors, or solution to beamer + minted brokenness?
Hi Chris
Just for completeness - and because I had little previous experience with
using =org-babel= stuff - I attempted to write a small =sh= source block
that parses the current =org-mode= file and builds an appropriate "emph"
entry in the listings =lstset=:
==
#+startup:
beamer
#+LaTeX_CLASS:
beamer
#+BEAMER_HEADER_EXTRA:
\usetheme{Madrid}\usecolortheme{default}
#+source: parse-classes
#+begin_src sh :var fileName=(buffer-file-name) :exports none :results
output latex
for class in `sed -n 's/.*class \([a-zA-Z0-9_]*\)(.*):/\1/p' $fileName`;
do
str="$str,$class"
done
cat
< wrote:
> Dan, all this information is super helpful. Thanks! My presentation is
> going to look great now, I think!
>
> I really appreciate your help!
> - cwebb
>
> --
> 𝓒𝓱𝓻𝓲𝓼𝓽𝓸𝓹𝓱𝓮𝓻 𝓐𝓵𝓵𝓪𝓷 𝓦𝓮𝓫𝓫𝓮𝓻
>
> ___
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: [babel][patch] C++ inconsistencies
Bastien writes: > Hi Martyn, > > Martyn Jago writes: > >> The FSF process is in progress - I'm currently waiting for the agreement >> to sign. I'll tidy up the YAML export. > > I confirm the assignment/disclaimer process with the FSF is complete. > > I added you to the list of contributors on Worg: > > http://orgmode.org/worg/org-contribute.html#contributors_with_fsf_papers > > (We need to wait a bit before the Worg repo is published on the > website.) > > Thanks for contributing! Hi Bastien I hope to help with Org mode where I can, although I have much to learn. In a way I see Org mode as the evolution of Emacs (which I've been using for several years to program Embedded C and Ruby) but that's another story. Thank you! Martyn ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: [babel][patch] C++ inconsistencies
"Eric Schulte" writes:
> Martyn Jago writes:
>
>> "Eric Schulte" writes:
>>
>> [...]
>>
> Hi Martyn,
>
> That's great news. A just had trouble trying to apply your earlier
> patch, could you reproduce the patch with
>
> git diff > cpp.patch
>
> then re-send the resulting patch as an attachment?
>
> Thanks -- Eric
>
>>
Hi Eric
Apologies, I'm still familiarising myself with Gnus but hopefully this
will work.
Also thanks for Babel, I think its got a great future!
Regards
Martyn
diff --git a/lisp/ob-C.el b/lisp/ob-C.el
index da0e768..5aa750c 100644
--- a/lisp/ob-C.el
+++ b/lisp/ob-C.el
@@ -38,7 +38,7 @@
(declare-function org-entry-get "org"
(pom property &optional inherit literal-nil))
-(add-to-list 'org-babel-tangle-lang-exts '("c++" . "cpp"))
+(add-to-list 'org-babel-tangle-lang-exts '("C++" . "cpp"))
(defvar org-babel-default-header-args:C '())
@@ -46,8 +46,8 @@
"Command used to compile a C source code file into an
executable.")
-(defvar org-babel-c++-compiler "g++"
- "Command used to compile a c++ source code file into an
+(defvar org-babel-C++-compiler "g++"
+ "Command used to compile a C++ source code file into an
executable.")
(defvar org-babel-c-variant nil
@@ -56,15 +56,15 @@ is currently being evaluated.")
(defun org-babel-execute:cpp (body params)
"Execute BODY according to PARAMS. This function calls
-`org-babel-execute:C'."
- (org-babel-execute:C body params))
+`org-babel-execute:C++'."
+ (org-babel-execute:C++ body params))
-(defun org-babel-execute:c++ (body params)
+(defun org-babel-execute:C++ (body params)
"Execute a block of C++ code with org-babel. This function is
called by `org-babel-execute-src-block'."
(let ((org-babel-c-variant 'cpp)) (org-babel-C-execute body params)))
-(defun org-babel-expand-body:c++ (body params)
+(defun org-babel-expand-body:C++ (body params)
"Expand a block of C++ code with org-babel according to it's
header arguments (calls `org-babel-C-expand')."
(let ((org-babel-c-variant 'cpp)) (org-babel-C-expand body params)))
@@ -81,7 +81,7 @@ header arguments (calls `org-babel-C-expand')."
(defun org-babel-C-execute (body params)
"This function should only be called by `org-babel-execute:C'
-or `org-babel-execute:c++'."
+or `org-babel-execute:C++'."
(let* ((tmp-src-file (org-babel-temp-file
"C-src-"
(cond
@@ -98,7 +98,7 @@ or `org-babel-execute:c++'."
(format "%s -o %s %s %s"
(cond
((equal org-babel-c-variant 'c) org-babel-C-compiler)
- ((equal org-babel-c-variant 'cpp) org-babel-c++-compiler))
+ ((equal org-babel-c-variant 'cpp) org-babel-C++-compiler))
(org-babel-process-file-name tmp-bin-file)
(mapconcat 'identity
(if (listp flags) flags (list flags)) " ")
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] [PATCH] Allow inclusion of author's email in LaTeX export
Hi, I noticed that special characters in the email, such as an underscore, are not escaped. This causes LaTeX errors. To reproduce, put this line at the top of an org file and try to export to PDF via LaTeX: #+EMAIL: first_l...@example.com Thanks, Hsiu-Khuern. On Mon, Jan 17, 2011 at 11:21 AM, Bastien wrote: > Hi Lawrence, > > Lawrence Mitchell writes: > >> * org-latex.el (org-export-latex-make-header): Export email in >> author line if `org-export-email-info' is non-nil. > > Thanks a lot - I just applied a slightly modified version of your > patch. > > The trick is to use (plist-get opt-plist :email-info) instead of > `org-export-email-info' so that in-buffer options are taken into > account. > > Thanks for submitting this! > > -- > Bastien > > ___ > Emacs-orgmode mailing list > Please use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode > ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Deriving mode from org-mode
On 02/22/2011 10:34 AM, Carsten Dominik wrote: Sorry for following up on my own mail. I want to add a pointer to the documentation for org-wikinodes.el: http://orgmode.org/worg/org-contrib/org-wikinodes.html Thanks. I've already seen that - I'm not very interesed in camelcase links. However I was planning to look at the implementation to get hints on how to implement good links. I currently (ab)use radio targets, every top level heading is in the format "* <<>>", which seems to work quite well, but doesnt feel very elegant. My main focus this far has been to get narrowing (I really don't want to risk seeing anything that may distract me) and a back function so that I can go back to previous page. anders ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] 2nd clone of Org-mode for Vim
Hi, I guess it all started with the FLOSS podcast done by Carsten Dominik. Thanks for that. It was the first time I heard about Org-mode. Herbert Sitz announced a first implementation last year (http://permalink.gmane.org/gmane.emacs.orgmode/33226). As far as I can tell a lot of people got attracted and are following the development at github. Around the same time I started implementing Org-mode for vim as well, without knowing about Herbert's implementation. In essence, it's aiming at the same goal. A bigger difference though is the implementation language - it's Python, not VimL and I built it to be easily extendable. Apart from that, vim-orgmode integrates well with other Vim plugins like taglist and repeat. If you are interested, you can access the code at https://github.com/jceb/vim-orgmode or send an e-mail if you have any further questions. Greetings, Jan Christoph -- Jan Christoph Ebersbach But by the grace of God I am what I am. 1. Cor 15,10 signature.asc Description: Digital signature ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Bytecompiler is unhappy...
On Feb 22, 2011, at 9:15 PM, Nicolas wrote: Hello, I've taken care of: In org-fill-paragraph: org.el:19105:27:Warning: assignment to free variable `struct' org.el:19110:33:Warning: reference to free variable `struct' In end of data: org-list.el:3007:1:Warning: the function `outline-flag-region' is not known to be defined. But I'm not sure what's the best way to handle this: In end of data: org.el:19993:1:Warning: the following functions are not known to be defined: org-inlinetask-at-task-p, org-inlinetask-toggle-visibility, org-inlinetask-outline-regexp (require 'org-inlinetask) within eval-when-compile, NO. Declare the functions an use (defvar name) for the variables. or declare the functions? I leave it to the enlightened ones. Regards, -- Nicolas ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] org-contacts.el
Hi Martin, Martin Butz wrote: Hi to all, I'm using org-mode since a year or so. Its a great peace of software and I could not imagine using another organizer and notes tool anymore! Thanks a lot for all this work! I tried to use org-contacts.el using the current version from git://git.naquadah.org/org-contacts.git My org-mode version is 7.4. I keep getting the initialization warning: Symbol's value as variable is void: org-property-set-functions-alist on emacs startup. Can anybody give a hint, what I'm doing wrong? Martin you'll have to use the git version of org-mode. org-contacts.el needs some patches integrated only after the 7.4 release. Best regards Robert ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Bytecompiler is unhappy...
Hello, I've taken care of: > In org-fill-paragraph: > org.el:19105:27:Warning: assignment to free variable `struct' > org.el:19110:33:Warning: reference to free variable `struct' > In end of data: > org-list.el:3007:1:Warning: the function `outline-flag-region' is not known to > be defined. But I'm not sure what's the best way to handle this: > In end of data: > org.el:19993:1:Warning: the following functions are not known to be defined: > org-inlinetask-at-task-p, org-inlinetask-toggle-visibility, > org-inlinetask-outline-regexp (require 'org-inlinetask) within eval-when-compile, or declare the functions? I leave it to the enlightened ones. Regards, -- Nicolas ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] org-contacts.el
Hi to all, I'm using org-mode since a year or so. Its a great peace of software and I could not imagine using another organizer and notes tool anymore! Thanks a lot for all this work! I tried to use org-contacts.el using the current version from git://git.naquadah.org/org-contacts.git My org-mode version is 7.4. I keep getting the initialization warning: Symbol's value as variable is void: org-property-set-functions-alist on emacs startup. Can anybody give a hint, what I'm doing wrong? Martin -- ~ sym.net || butz & siefer gbr || 50670 koeln || hansaring 78 phone +49(0)221/3762591 - twitter.com/symnet - mail b...@sym.net ~~ www.sym.net | www.moodalis.de ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: custom agenda view with tags-todo not work
Bastien writes:
> Hi Osiris,
>
> OSiRiS writes:
>
>> I tried to set the custom view in the calendar, but does not work.
>>
>> #+BEGIN_SRC elisp
>>
>> (setq org-agenda-custom-commands
>> '(
>> ("f" "FIXED" tags-todo
>> "+bug+TODO=\"DONE\"+STATUS=\"FIXED\"+CLOSED>=\"\"")
>> )
>> )
>>
>> #+END_SRC
>>
>> No error occurs when run:
>
> Looks good so far...
>
>> Can someone tell me where is the error? thanks!
>
> I don't understand what is the error. Can you be more specific?
> Also, don't forget to tell us what version of Org and Emacs you
> are using.
The problem is tags-todo will not match closed states. I ran into the
same problem trying to make an agenda view for tasks to archive. My
solution was to change to a tags match not a tags-todo match.
HTH,
Bernt
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Sending TODO items automatically to a specified email address
Thanks, Bastien By the way I use Mac mail, hopefully this shouldn't be a problem Cheers M Sent from my iPhone On Feb 22, 2011, at 10:30 AM, Bastien wrote: > Hi Marvin, > > Marvin Doyley writes: > >> Does anybody know how to send TODO as email attachment. What would be >> nice is if the TODO item is in the message and the text below it is >> an attachment. Basically, this is how I remind myself of things that >> I need to get done. > > The first step is to export selected entries to text files: > > #+begin_src emacs-lisp > (defun org-export-headings-to-ascii (&optional match scope) > "Export headings from the current buffer to ascii files." > (interactive) > (org-map-entries > (lambda () > (org-mark-subtree) > (let ((head (org-get-heading)) > (beg (point)) > (end (org-end-of-subtree))) > (org-export-region-as-ascii beg end t (get-buffer-create head)) > (with-current-buffer > (get-buffer-create head) > (write-file > (concat (replace-regexp-in-string " " "_" head) ".txt") > ;; see org-map-entries docstring > match scope)) > #+end_src > > Then to attach the files, which depends on what MUA you use. > > HTH, > > -- > Bastien ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] [PATCH] Re: [BUG] htmlp and latexp
Bastien writes:
> Hi Dan,
>
> Dan Davison writes:
>
>> I was thinking that if it were defvard in org.el, say as
>>
>> (defvar org-export-current-backend nil)
>>
>> then any code could use (null org-export-current-backend) to test
>> whether org is currently exporting or not. Otherwise, the code has to be
>> certain that it has been called during export if it is going to access
>> the variable.
>
> I agree this would be a good idea. If you have time, please send a
> patch. Otherwise, I just put it [somewhere] in my own todo list...
Here's a patch. I note that Eric S pointed out in a separate thread that
org-current-export-file can be used for a similar purpose.
Incidentally, I would suggest that org-current-export-file and
org-current-export-dir are renamed so that they are within the
org-export-* namespace. There are other areas of Org where I think the
naming should be standardised, notably in org-src.el: the distinction
between org-src-* and org-edit-src-* is unclear IMO. I think this is
kind of important, because in learning emacs one does makes use of these
namespace conventions, e.g. C-h v TAB. How much change
would there be if we demanded that *all* variables defined in org-foo.el
are named within the org-foo-* namespace?
Dan
commit ac9baa44c7c0baeb8ed3133ed79bc22c4eb6acc7
Author: Dan Davison
Date: Sun Feb 20 08:55:39 2011 -0800
New variable storing current export backend symbol, or nil.
* lisp/org-exp.el (org-export-current-backend): Variable to
hold current export backend symbol when export is in progress.
(org-export-preprocess-string): Bind `org-export-current-backend' to
backend symbols during export.
* lisp/org-exp-blocks.el (org-export-blocks-format-ditaa): Dynamically
scoped variable `backend' renamed as `org-export-current-backend'
(org-export-blocks-format-dot): Dynamically scoped variable `backend'
renamed as `org-export-current-backend'
(org-export-blocks-format-comment): Dynamically scoped variable
`backend' renamed as `org-export-current-backend'
* lisp/org-exp.el (org-export-convert-protected-spaces): Dynamically
scoped variable `backend' renamed as `org-export-current-backend'
* lisp/org-publish.el (org-publish-project-alist): Dynamically scoped
variable `backend' renamed as `org-export-current-backend'
(org-export-current-backend): Dynamically scoped variable `backend'
renamed as `org-export-current-backend'
(org-publish-aux-preprocess): Dynamically scoped variable `backend'
renamed as `org-export-current-backend'
* lisp/org-special-blocks.el (org-export-current-backend): Dynamically
scoped variable `backend' renamed as `org-export-current-backend'
(org-special-blocks-make-special-cookies): Dynamically scoped variable
`backend' renamed as `org-export-current-backend'
diff --git a/lisp/org-exp-blocks.el b/lisp/org-exp-blocks.el
index 1fac3bf..15549b8 100644
--- a/lisp/org-exp-blocks.el
+++ b/lisp/org-exp-blocks.el
@@ -242,7 +242,7 @@ passed to the ditaa utility as command line arguments."
"\n")))
(prog1
(cond
- ((member backend '(html latex docbook))
+ ((member org-export-current-backend '(html latex docbook))
(unless (file-exists-p out-file)
(mapc ;; remove old hashed versions of this file
(lambda (file)
@@ -301,7 +301,7 @@ digraph data_relationships {
(out-file (concat (car out-file-parts) "_" hash "." (cdr
out-file-parts
(prog1
(cond
- ((member backend '(html latex docbook))
+ ((member org-export-current-backend '(html latex docbook))
(unless (file-exists-p out-file)
(mapc ;; remove old hashed versions of this file
(lambda (file)
@@ -333,7 +333,7 @@ other backends, it converts the comment into an EXAMPLE
segment."
(let ((owner (if headers (car headers)))
(title (if (cdr headers) (mapconcat 'identity (cdr headers) " "
(cond
- ((eq backend 'html) ;; We are exporting to HTML
+ ((eq org-export-current-backend 'html) ;; We are exporting to HTML
(concat "#+BEGIN_HTML\n"
" (match-end 1) (match-beginning 1)))
(setq entry (match-string 1))
- (when (eq backend 'latex)
+ (when (eq org-export-current-backend 'latex)
(replace-match (format "\\index{%s}" entry) t t))
(save-excursion
(ignore-errors (org-back-to-heading t))
diff --git a/lisp/org-special-blocks.el b/lisp/org-special-blocks.el
index 54fb6cb..f253787 100644
--- a/lisp/org-special-blocks.el
+++ b/lisp/org-special-blocks.el
@@ -45,11 +45,12 @@
by org-special-blocks. These blocks will presumably be
interpreted by other mechanisms.")
-(defvar backend) ; dynamically scoped
+(defvar org-export-current-backend) ; dynamically scoped
(defun org-special-blocks-make-special-cookies ()
"Adds special cookies when #+begin_foo and #+end_foo tokens are
seen. This is run after a few special cases
RE: [Orgmode] using (id "Name") target in org-capture-templates
It would be quite useful if I could use currentfile in place of "path/to/file"
in the various Target patterns. That is, it would be nice to write something
like:
(setq org-capture-templates
'(("j" "Journal" entry (file+headline currentfile "Journal") "* %a\n\n%i"))
("t" "To Do" entry (file+headline currentfile "Tasks") "* TODO %? %i\n")))
Thanks.
-- Greg
--
Greg Sullivan gregory.sulli...@baesystems.com
(781)262-4553 (office) (978)430-3461 (cell)
-Original Message-
From: Bastien Guerry [mailto:bastiengue...@googlemail.com] On Behalf Of Bastien
Sent: Friday, February 11, 2011 5:22 AM
To: Sullivan, Gregory (US SSA)
Cc: Giovanni Ridolfi; Emacs-orgmode@gnu.org
Subject: Re: [Orgmode] using (id "Name") target in org-capture-templates
Hi Gregory,
"Sullivan, Gregory (US SSA)" writes:
> Thanks for the note. I did indeed mean to use headings.
>
> I think it would be nice to be able to have the file dynamic but the
> heading static in capture templates. In my case, I always want to
> find a particular heading in the buffer that the capture originated
> from. So I had to put the whole target spec in a function, as in:
I like the idea of being able to tell capture to use the current file.
This patch against latest Org allows you to use (currentfile) like this:
,
| (setq org-capture-templates
| '(("j" "Journal" entry (currentfile) "* %a\n\n%i")))
`
Let me know if you find this useful.
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Two questions about using a =#+begin_src emacs-lisp= block
"Eric Schulte" writes: > if you are worried that you don't have the correct version of Org-mode > installed you can check the output of the `org-version' function. Mine > reads > > "Org-mode version 7.4 (release_7.4.510.g1e35)" Note: the SHA1 for the git commit is only shown if Orgmode is installed into a subdirectory of the git working tree. I remember that this puzzled me at the beginning... After a few tries I've now set up as follows: - I'm tracking two branches local-maint->origin/maint (latest release) local->origin/master (developer version) with rebase and just add a single commit on top with customizations to the Makefile to get the install for each branch to the correct location - the latest release version is installed into .../site-lisp/orgmode/ and is the version that gets used when I "just" start emacs - in the git working tree I'm installing the latest developer snapshot into a subdirectory dev-lisp; always compile via make clean install && make clean otherwise emacs might pick up byte-compiled files even though you've changed the sources (by checking out another branch or doing a git pull or just editing something) - keep a file handy with: --8<---cut here---start->8--- ;; -*- lisp-interaction -*- (setq load-path (cons (expand-file-name "~/org-mode/lisp") load-path)) (setq load-path (cons (expand-file-name "~/org-mode/dev-lisp") load-path)) (setq load-path (cdr load-path)) --8<---cut here---end--->8--- load this into emacs and do C-j on one of the first two lines to switch to using either the compiled or uncompiled developer version. The last lines strips the load-path of the first element, which switches back to the "standard" load-path provided you didn't do any other additions to load-path inbetween. This is obviously customizable in several respects, but it works for me and lets me track several stages of orgmode development with minimal effort. 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 ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: convert orgmode to docx
Hi Bastien, thanks for the info! Do you have a hint, how I could do the export in batchmode from the console in Linux? Best Regards! Fabian On 02/22/2011 12:32 PM, Bastien wrote: Hi Fabian, Fabian Braennstroem writes: Oh, one question... does this mean, it would be easier to use the orgmode-version for everything or can I just add your odt-implementation to my existing orgmode installation!? for now you would have to use two repositories: one with current Org's functionalities, another one with odt export plus and old Org version. Jambunathan and I are working on integrating this, but it's not as straightforward as it might look. We'll keep you posted, thanks! ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: Re: [Orgmode] Two questions about using a =#+begin_src emacs-lisp= block
On Feb 22, 2011 1:06pm, Eric Schulte wrote: Chris Malone chris.m.mal...@gmail.com> writes: > Ok, this is still perplexing me, as I have a new version from git and I > still get the error. The following is complete list (sorry for the long > email!) of what I have done: > > * Get a fresh copy of =org-mode= from git and byte-compile: > > #+begin_src: sh > cd ~/install/org-mode > mkdir new_git_clone > cd new_git_clone > git clone git://orgmode.org/org-mode.git > cd org-mode; make &> make.out > ln -s ~/install/org-mode/new_git_clone/org-mode ~/install/org-mode/current > #+end_src > if you are worried that you don't have the correct version of Org-mode installed you can check the output of the `org-version' function. Mine reads "Org-mode version 7.4 (release_7.4.510.g1e35)" RIght - I was worried that I had possibly changed a lisp file that could be causing the error, so I wanted a fresh copy. > > During the =make= process, I noticed quite a few warnings. An example is > below (for a complete copy of =make.out=, see > http://astro.sunysb.edu/cmalone/nolink/make.out [...] > Are such warnings normal? > yes, these are normal compiler warnings which are generally cleaned up before releases but shouldn't have any negative impact on the behavior of Org-mode Ok, good to know. > > * Make sure my =.emacs= file is pointing to the correct location > Here is a copy of the =org-mode=-relevant sections of my =.emacs= file: > [...] > > * Attempt an export of the =org-mode= file found here: > http://astro.sunysb.edu/cmalone/nolink/python_class_lstings.org > One thing to note here, is that for your emacs-lisp block to work on export, you need to change this #+begin_src emacs-lisp :exports both (buffer-file-name) #+end_src to this #+begin_src emacs-lisp :var file-name=(buffer-file-name) :exports both file-name #+end_src because only header arguments are guaranteed to be evaluated in the original org-mode buffer during export. Again, thanks for pointing this out earlier. I hadn't changed it for the example, because the error was not associated with whether or not the actual =emacs-lisp= code returned anything meaningful. That said I was able to export your example file (without the change above) to html. When exporting to latex I ran into an issue, the problem here is that the LaTeX exporter *requires* at least one headline. It explicitly export the pre-first-headline and post-first-headline portions of the Org-mode buffer separately. When there is no headline, and the buffer contains code blocks, then they are exported *twice*, which causes the error you mentioned, because after the first pass of the code-block export, the results in the file are not valid for another pass of the exporter. If you place a "* " before the "Let's start this..." line, then the errors should disappear. Hope this helps. Best -- Eric That fixed it! Sorry for the trouble for something that seems so minor! Thanks again. Chris ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Bytecompiler is unhappy...
The orgmode git has picked up quite a bit of dirt during the last three months or so (no wonder with all the development going on)... I can start tracking down the commits, but I guess most of these should be pretty obvious to whoever edited the file in the first place. :-) Most of these are probably just missing defvars or something of this ilk, but a few might be genuine typos or oversights. In case there's some version dependence, I'm compiling on 23.1.1, Org-mode version 7.4 (release_7.4.521.g93a8fc9). In org-fill-paragraph: org.el:19105:27:Warning: assignment to free variable `struct' org.el:19110:33:Warning: reference to free variable `struct' In end of data: org.el:19993:1:Warning: the following functions are not known to be defined: org-inlinetask-at-task-p, org-inlinetask-toggle-visibility, org-inlinetask-outline-regexp In org-run-agenda-series: org-agenda.el:2476:15:Warning: reference to free variable `org-agenda-overriding-arguments' org-agenda.el:2513:46:Warning: reference to free variable `org-agenda-last-arguments' In org-get-entries-from-diary: org-agenda.el:4346:62:Warning: reference to free variable `diary-time-regexp' In org-agenda-get-timestamps: org-agenda.el:4712:54:Warning: assignment to free variable `show-all' org-agenda.el:4712:31:Warning: reference to free variable `show-all' In org-agenda-get-scheduled: org-agenda.el:5067:45:Warning: assignment to free variable `show-all' org-agenda.el:5067:40:Warning: reference to free variable `show-all' In org-archive-subtree: org-archive.el:305:25:Warning: assignment to free variable `infile-p' org-archive.el:304:69:Warning: reference to free variable `infile-p' In org-capture-insert-template-here: org-capture.el:1057:32:Warning: reference to free variable `txt' In end of data: org-capture.el:1411:1:Warning: the function `org-eval' is not known to be defined. Loading cl-extra... In org-export-blocks-format-ditaa: org-exp-blocks.el:245:15:Warning: reference to free variable `backend' In org-export-blocks-format-dot: org-exp-blocks.el:304:15:Warning: reference to free variable `backend' In org-export-blocks-format-comment: org-exp-blocks.el:336:11:Warning: reference to free variable `backend' In org-export-latex-tables: org-latex.el:1926:41:Warning: assignment to free variable `width' org-latex.el:1926:62:Warning: reference to free variable `width' In end of data: org-list.el:3007:1:Warning: the function `outline-flag-region' is not known to be defined. In end of data: org-special-blocks.el:97:1:Warning: the function `org-string-match-p' is not known to be defined. In orgtbl-ctrl-c-ctrl-c: org-table.el:3751:57:Warning: assignment to free variable `const-str' org-table.el:3751:40:Warning: reference to free variable `const-str' In org-babel-execute-src-block: ob.el:401:57:Warning: reference to free variable `org-src-lang-modes' In org-babel-expand-noweb-references: ob.el:1827:36:Warning: reference to free variable `org-babel-library-of-babel' In end of data: ob.el:2078:1:Warning: the following functions are not known to be defined: org-at-item-p, org-babel-tangle-comment-links In org-babel-exp-inline-src-blocks: ob-exp.el:147:4:Warning: value returned from (buffer-substring (match-beginning 0) (match-end 0)) is unused In end of data: ob-calc.el:98:1:Warning: the following functions are not known to be defined: calc-store-into, calc-recall, math-evaluate-expr In org-babel-python-initiate-session-by-key: ob-python.el:150:27:Warning: reference to free variable `py-default-interpreter' Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf Blofeld V1.15B11: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Two questions about using a =#+begin_src emacs-lisp= block
Chris Malone writes: > Ok, this is still perplexing me, as I have a new version from git and I > still get the error. The following is complete list (sorry for the long > email!) of what I have done: > > * Get a fresh copy of =org-mode= from git and byte-compile: > > #+begin_src: sh > cd ~/install/org-mode > mkdir new_git_clone > cd new_git_clone > git clone git://orgmode.org/org-mode.git > cd org-mode; make &> make.out > ln -s ~/install/org-mode/new_git_clone/org-mode ~/install/org-mode/current > #+end_src > if you are worried that you don't have the correct version of Org-mode installed you can check the output of the `org-version' function. Mine reads "Org-mode version 7.4 (release_7.4.510.g1e35)" > > During the =make= process, I noticed quite a few warnings. An example is > below (for a complete copy of =make.out=, see > http://astro.sunysb.edu/cmalone/nolink/make.out [...] > Are such warnings normal? > yes, these are normal compiler warnings which are generally cleaned up before releases but shouldn't have any negative impact on the behavior of Org-mode > > * Make sure my =.emacs= file is pointing to the correct location > Here is a copy of the =org-mode=-relevant sections of my =.emacs= file: > [...] > > * Attempt an export of the =org-mode= file found here: > http://astro.sunysb.edu/cmalone/nolink/python_class_lstings.org > One thing to note here, is that for your emacs-lisp block to work on export, you need to change this #+begin_src emacs-lisp :exports both (buffer-file-name) #+end_src to this #+begin_src emacs-lisp :var file-name=(buffer-file-name) :exports both file-name #+end_src because only header arguments are guaranteed to be evaluated in the original org-mode buffer during export. That said I was able to export your example file (without the change above) to html. When exporting to latex I ran into an issue, the problem here is that the LaTeX exporter *requires* at least one headline. It explicitly export the pre-first-headline and post-first-headline portions of the Org-mode buffer separately. When there is no headline, and the buffer contains code blocks, then they are exported *twice*, which causes the error you mentioned, because after the first pass of the code-block export, the results in the file are not valid for another pass of the exporter. If you place a "* " before the "Let's start this..." line, then the errors should disappear. Hope this helps. Best -- Eric ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Two questions about using a =#+begin_src emacs-lisp= block
Ok, this is still perplexing me, as I have a new version from git and I
still get the error. The following is complete list (sorry for the long
email!) of what I have done:
* Get a fresh copy of =org-mode= from git and byte-compile:
#+begin_src: sh
cd ~/install/org-mode
mkdir new_git_clone
cd new_git_clone
git clone git://orgmode.org/org-mode.git
cd org-mode; make &> make.out
ln -s ~/install/org-mode/new_git_clone/org-mode ~/install/org-mode/current
#+end_src
During the =make= process, I noticed quite a few warnings. An example is
below (for a complete copy of =make.out=, see
http://astro.sunysb.edu/cmalone/nolink/make.out
org.el:19993:1:Warning: the function `parse-time-string' might not be
defined
at
runtime.
org.el:19993:1:Warning: the following functions are not known to be
defined:
table--at-cell-p, org-clock-update-mode-line,
org-default-export-plist,
org-infile-export-plist,
org-inlinetask-at-task-p,
org-inlinetask-toggle-visibility,
org-clock-save-markers-for-cut-and-paste,
org-agenda-save-markers-for-cut-and-paste,
org-id-get-create,
dired-get-filename, org-id-store-link,
iswitchb-read-buffer,
org-agenda-copy-local-variable,
org-attach-reveal,
org-inlinetask-remove-END-maybe, org-agenda-skip,
org-format-agenda-item,
org-agenda-new-marker,
org-agenda-change-all-lines,
org-columns-number-to-string,
org-columns-get-format-and-top-level,
org-columns-compute,
calendar-absolute-from-iso,
calendar-iso-from-absolute, org-id-locations-save,
org-id-locations-load,
cdlatex-tab, org-export-latex-fix-inputenc,
orgtbl-send-table,
org-inlinetask-in-task-p,
org-inlinetask-goto-beginning,
org-inlinetask-goto-end,
org-inlinetask-outline-regexp,
fill-forward-paragraph,
beginning-of-visual-line,
org-agenda-set-restriction-lock,
speedbar-line-directory,
org-agenda-maybe-redo
Wrote /home/cmalone/install/org-mode/new_git_clone/org-mode/lisp/org.elc
Are such warnings normal?
* Make sure my =.emacs= file is pointing to the correct location
Here is a copy of the =org-mode=-relevant sections of my =.emacs= file:
;;
;; org-mode
stuff
;;
(add-to-list 'load-path
"/home/cmalone/install/org-mode/current/lisp")
(require
'org-install)
(add-to-list 'auto-mode-alist '("\\.org\\'" .
org-mode))
(global-set-key "\C-cl"
'org-store-link)
(global-set-key "\C-ca"
'org-agenda)
(global-set-key "\C-cb"
'org-iswitchb)
(setq org-log-done t)
;; using the prop_just
class
(require
'org-latex)
(add-to-list
'org-export-latex-classes
'("prop_just"
"\\documentclass{prop_just}
[NO-DEFAULT-PACKAGES]
[PACKAGES]
[EXTRA]"
("\\section{%s}" .
"\\section*{%s}")
("\\subsection{%s}" .
"\\subsection*{%s}")
("\\subsubsection{%s}" .
"\\subsubsection*{%s}")
("\\paragraph{%s}" .
"\\paragraph*{%s}")
("\\subparagraph{%s}" .
"\\subparagraph*{%s}")))
(add-to-list
'org-export-latex-classes
'("letter"
"\\documentclass{letter}
[DEFAULT-PACKAGES]
[PACKAGES]
[EXTRA]"))
; org-babel
stuff
(org-babel-do-load-languages
'org-babel-load-languages
'((org .
t)
(emacs-lisp .
t)
(python .
t)
(latex .
t)
(perl .
t)
(sh .
t)
(C .
t)
(ditaa .
t)))
(setq org-confirm-babel-evaluate nil)
;;
;; for
YASnippet
;;
(add-to-list 'load-path
"~/.emacs.d/plugins/yasnippet-0.6.1c")
(require
'yasnippet)
(yas/initialize)
(yas/load-directory "~/.emacs.d/plugins/yasnippet-0.6.1c/snippets")
;; define backtab (essentially Shift-Tab) for
org-mode
(global-set-key (kbd "") 'org-shifttab)
;; Make TAB the yas trigger key in the org-mode-hook and enable flyspell
mode a\
nd
autofill
(add-hook
'org-mode-hook
(lambda
()
;;
yasnippet
(make-variable-buffer-local
'yas/trigger-key)
(org-set-local 'yas/trigger-key
[tab])
(define-key yas/keymap [tab]
'yas/next-field-group)
;; flyspell mode for spell checking
everywhere
(flyspell-mode
1)
;; auto-fill mode
on
(auto-fill-mode 1)))
* Attempt an export of the =org-mode= file found here:
http://astro.sunysb.edu/cmalone/nolink/python_class_lstings.org
Exporting this to PDF, HTML, or ASCII (I didn't try other forms) results in
the following error in the *Messages* buffer: 'Invalid read syntax: "#"'. I
turned on =debu-on-error= and the *Messages* and *Backtrace* buffers can be
found here:
http://astro.sunysb.edu/cmalone/nolink/messages.txt
http://astro.sunysb.edu/cmalone/nolink/backtrace.txt
PS: I had already written most of this before I just saw your email -
hopefully this helps...
Chris
On Tue, Feb 22, 2011 at 10:06 AM, Chris Malone wrote:
> Hi Eric,
>
> I r
[Orgmode] [PATCH] Optional caption argument
Aloha all,
The attached patches activate some dormant code that handles an
optional argument to #+CAPTION:. An example of use is also added to
org.texi.
With these patches, Org-mode now recognizes a caption of the form:
#+CAPTION: [Short caption for list of figures]{Long caption for table
(or link).}
and exports it properly to LaTeX.
All the best,
Tom
0001-lisp-org-latex.el-Enable-optional-argument-to-LaTeX-.patch
Description: Binary data
0002-lisp-org-exp.el-Set-shortn-nil-before-parsing-a-capt.patch
Description: Binary data
0003-doc-org.texi-Added-example-of-short-caption-use.patch
Description: Binary data
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Two questions about using a =#+begin_src emacs-lisp= block
Chris Malone writes: > Hi Eric, > > I removed all the compiled elisp files, and the problem still persists. > Next step will be a completely fresh install from git; my current version is > up to date, but maybe there was some conflict that git didn't complain > about... > Before doing that could you re-send a minimal example with instruction for how to reproduce the problem, and I'll give it another shot. Thanks -- Eric > > Chris > > On Mon, Feb 21, 2011 at 2:48 PM, Eric Schulte wrote: > >> Chris Malone writes: >> [...] >> > >> > I added =(setq org-confirm-babel-evaluate nil)= to my =.emacs= file, and >> indeed I am not asked about evaluating the code block, but I'm still getting >> the invalid >> > syntax error when =org-babel-exp= is called the second time on the >> =emacs-lisp= code block.? I should mention that this is somewhere in the >> byte-code, as the error >> > is: >> > >> > byte-code: Invalid read syntax: "#" >> > >> > in the *Messages* buffer.? I still don't fully understand why it should >> be evaluating that code block twice. >> > >> >> Hmm, it may be worth cleaning out all compiled .elc files from within >> Org-mode, the calling org-reload, and see if the problem persists. >> >> Best -- Eric >> >> > >> > Chris >> ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Insert ampersand in HTML export?
On Fri, 18 Feb 2011 10:04:52 +0100
Bastien wrote:
> Nick Dokos writes:
>
> > #+BIND: org-export-html-protect-char-alist (("&" . "&"))
>
> Yes, no quote needed. Thanks Nick for correcting me.
>
> --
> Bastien
Also I found a bug in that version of org-mode. How do I report it or
should I report it because it's a development version?
There seems to be a problem with the escape character @. Anytime the
preceding character is *NOT* a white space (including non-breaking
space), the export breaks.
This wasn't a problem before in 7.3.
In 7.3, this code exports fine:
point @A@
^
|
non-breaking space
It exports to:
point A
In the development version, that code snippet exports to:
point @A
not at all what's intended
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Insert ampersand in HTML export?
On Fri, 18 Feb 2011 10:04:52 +0100
Bastien wrote:
> Nick Dokos writes:
>
> > #+BIND: org-export-html-protect-char-alist (("&" . "&"))
>
> Yes, no quote needed. Thanks Nick for correcting me.
>
> --
> Bastien
OK, finally tried it out. Unfortunately, while the variable works, it doesn't
stay local---if you include the file in SETUPFILE, the variable also applies to
that file.
Is there a way to make sure that variable stays local?
Ex:
macro.org
#+BIND: org-export-html-protect-char-alist (("&" . "&"))
#+MACRO: test & should stay as is
macro-import.org
##+SETUPFILE: macro.org
* Hello World
This & should receive the amp treatment. But doesn't.
{{{test}}}
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: question about capture templates
Carsten Dominik writes: > I do love dynamic scoping, this give a lot of power in Emacs. > Org-mode internals use that power often. This is venturing a bit far afield, at least for this thread, but I'm curious if anyone knows: does the recent work on supporting Elisp in Guile mean that Elisp applications are eventually expected to be ported to Scheme? And if so, what does that mean for Org development? >> One gotcha: S-expressions in templates are apparently always evaluated >> as function calls -- you can't just directly access a string value, like >> %(foo). > > I guess you mean a variable value? Right, yes, a variable with a string value. I guess my point is more properly stated by saying there doesn't seem to be a way to evaluate an atomic S-expression in a template. But this seems like a fair trade for not having to write a second set of parentheses around every non-atomic expression. > The shortest form may be %(symbol-value foo) if you want to access the > value of a variable in a template. That's handy -- thanks! Richard ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] BUG? Exporting "missing level" to LaTeX fails
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/22/2011 02:24 PM, Bastien wrote: > Hi Rainer, > > Rainer M Krug writes: > >> If I export to htrml, the "missing level" is exported "properly", but in >> the LaTeX / pdf export, all levels below the "missing level" (FIRST, >> SECOND) are not exported. >> >> Am I right in considering this a bug? > > I'd call this a limitation of the current LaTeX exporter, which requires > the Org file to be propertly structured (i.e. with no missing levels.) Well - agreed on the "not properly structured" part, but that limitation cost me more then an hour work to figure out why my longish document does not export one heading. Would it be possible, to print a warning when that happens? Rainer > - -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Natural Sciences Building Office Suite 2039 Stellenbosch University Main Campus, Merriman Avenue Stellenbosch South Africa Tel:+33 - (0)9 53 10 27 44 Cell: +27 - (0)8 39 47 90 42 Fax (SA): +27 - (0)8 65 16 27 82 Fax (D) : +49 - (0)3 21 21 25 22 44 Fax (FR): +33 - (0)9 58 10 27 44 email: rai...@krugs.de Skype: RMkrug -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1j3HEACgkQoYgNqgF2egqr1gCcD92Aof1/dzpPpBJHr4fAwJ7d KHIAnjXAph/oHH/fp9pk6JFsrpZEHIAT =iKx4 -END PGP SIGNATURE- ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] [annoyance] Inserted headlines are immediately folded
Hi, I just experienced the latest day(s) a small annoyance when inserting (copying) one headline into an existing Org file: it is folded immediately upon insertion. For example, inserting: --8<---cut here---start->8--- ** RDV client ABC <2011-07-05 Tue 08:30-09:15> --8<---cut here---end--->8--- results into such a file: --8<---cut here---start->8--- * Appointments ** RDV medical <2011-02-23 Wed 08:45-09:00> ** RDV client ABC... ** Birthday Donja <2011-03-05 Sat 18:30> --8<---cut here---end--->8--- Before, when inserting such a node, it stayed expanded, which my preferred way of viewing the file. I don't (think I) have any customization that would explain this new behavior. Can you confirm it? Best regards, Seb -- Sébastien Vauban ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] BUG? Exporting "missing level" to LaTeX fails
Hi Rainer, Rainer M Krug writes: > If I export to htrml, the "missing level" is exported "properly", but in > the LaTeX / pdf export, all levels below the "missing level" (FIRST, > SECOND) are not exported. > > Am I right in considering this a bug? I'd call this a limitation of the current LaTeX exporter, which requires the Org file to be propertly structured (i.e. with no missing levels.) -- Bastien ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Clock summary doesn't work in some cases
Hi Robert, Robert Klein writes: > in the git version as of this morning > (1e35a5ea37194d686f432d384f4e264498ca6294) the clock summary doesn't > work right. Below is a clock summary with a version from February 11 > and below that a clock summary with the git version I downloaded just a > couple of hours ago. Fixed, thanks. -- Bastien ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Sending TODO items automatically to a specified email address
Hi Marvin, Marvin Doyley writes: > Does anybody know how to send TODO as email attachment. What would be > nice is if the TODO item is in the message and the text below it is > an attachment. Basically, this is how I remind myself of things that > I need to get done. The first step is to export selected entries to text files: #+begin_src emacs-lisp (defun org-export-headings-to-ascii (&optional match scope) "Export headings from the current buffer to ascii files." (interactive) (org-map-entries (lambda () (org-mark-subtree) (let ((head (org-get-heading)) (beg (point)) (end (org-end-of-subtree))) (org-export-region-as-ascii beg end t (get-buffer-create head)) (with-current-buffer (get-buffer-create head) (write-file (concat (replace-regexp-in-string " " "_" head) ".txt") ;; see org-map-entries docstring match scope)) #+end_src Then to attach the files, which depends on what MUA you use. HTH, -- Bastien ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Fwd: [Orgmode] Go to today in Calendar
>> I just found that you can press "." in the Calendar to jump to today's >> date. > > Nice one, I didn't know that! > > Thanks for the tip, No prob. If anyone else has short/simple tips cool things that they find in org-mode please post them -- I enjoy reading the "Cool! I found XXX feature" e-mails. --Nate ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: how to filter CATEGORY entries in org-agenda-custom command (agenda)?
Hi Rainer, Rainer Stengele wrote: > I am in the middle of my org file, having a > > #+CATEGORY: TEST > > in line 1 of the file. Putting the code > > (org-entry-get (point) "CATEGORY") > > in the middle of my file under any headline and evaluating it gives me "nil". > Shouldn't the code give me "TEST"? That usage of CATEGORY is deprecated, or not actively supported at least. The advised way is to put the category as a real property, inside the PROPERTIES drawer. Best regards, Seb -- Sébastien Vauban ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Two questions about using a =#+begin_src emacs-lisp= block
Hi Eric, I removed all the compiled elisp files, and the problem still persists. Next step will be a completely fresh install from git; my current version is up to date, but maybe there was some conflict that git didn't complain about... Chris On Mon, Feb 21, 2011 at 2:48 PM, Eric Schulte wrote: > Chris Malone writes: > [...] > > > > I added =(setq org-confirm-babel-evaluate nil)= to my =.emacs= file, and > indeed I am not asked about evaluating the code block, but I'm still getting > the invalid > > syntax error when =org-babel-exp= is called the second time on the > =emacs-lisp= code block.? I should mention that this is somewhere in the > byte-code, as the error > > is: > > > > byte-code: Invalid read syntax: "#" > > > > in the *Messages* buffer.? I still don't fully understand why it should > be evaluating that code block twice. > > > > Hmm, it may be worth cleaning out all compiled .elc files from within > Org-mode, the calling org-reload, and see if the problem persists. > > Best -- Eric > > > > > Chris > ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] how to filter CATEGORY entries in org-agenda-custom command (agenda)?
Am 11.02.2011 11:32, schrieb Bastien: > Hi Rainer, > > Rainer Stengele writes: > >> how to filter CATEGORY entries in org-agenda-custom command (agenda)? > You can do this by setting `org-agenda-skip-function' to a function > that matches CATEGORY. You can find a subtree's category through > > (org-entry-get (point) "CATEGORY") > > HTH, > Hi Bastien, I am in the middle of my org file, having a #+CATEGORY: TEST in line 1 of the file. Putting the code (org-entry-get (point) "CATEGORY") in the middle of my file under any headline and evaluating it gives me "nil". Shouldn't the code give me "TEST"? - Rainer ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] (no subject)
From: Vincent-Xavier JUMEL
To: emacs-orgmode@gnu.org
Subject: Bug: Bug in agenda on DEADLINE/SCHEDULE with -3d [7.4]
Date: Mon, 21 Feb 2011 23:13:32 +0100
Message-ID:
<87d3mlyr1v.fsf@tauceticentral.i-did-not-set--mail-host-address--so-tickle-me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
An entry with a SCHEDULE or a DEADLINE using the doesn't
produce the documented behavior. Anyone does have the same issue ?
Emacs : GNU Emacs 23.2.1 (i686-pc-linux-gnu, GTK+ Version 2.21.6)
of 2010-09-01 on rhenium, modified by Debian
Package: Org-mode version 7.4
current state:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
(setq
org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars)
org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
org-agenda-files '("~/org/parinux.org")
org-blocker-hook '(org-block-todo-from-checkboxes)
org-metaup-hook '(org-babel-load-in-session-maybe)
org-capture-templates '(("a" "Ajoute un atelier" entry
(file+headline "~/org/parinux.org"
"Premier Samedi")
(file
"~/.emacs.d/org/templates/atelier_parinux.tpl")
)
("c" "Ajoute une conf=C3=A9rence" entry
(file+headline "~/org/parinux.org"
"Conf=C3=A9rences")
(file
"~/.emacs.d/org/templates/conference_parinux.tpl=
")
)
("v" "Ajoute un vote" entry
(file+headline "~/org/parinux.org"
"Votes")
(file
"~/.emacs.d/org/templates/vote_parinux_ca_2011.t=
pl")
)
)
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-startup-folded 'content
org-export-blocks-postblock-hook '(org-exp-res/src-name-cleanup)
org-export-latex-format-toc-function 'org-export-latex-format-toc-default
org-tab-first-hook '(org-hide-block-toggle-maybe
org-src-native-tab-command-maybe
org-babel-hide-result-toggle-maybe)
org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
org-confirm-shell-link-function 'yes-or-no-p
org-export-first-hook '(org-beamer-initialize-open-trackers)
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-default-notes-file "~/org/notes"
org-babel-pre-tangle-hook '(save-buffer)
org-cycle-hook '(org-cycle-hide-archived-subtrees
org-cycle-hide-drawers org-cycle-show-empty-lines
org-optimize-window-after-visibility-change)
org-export-preprocess-before-normalizing-links-hook '(org-remove-file-link=
-modifiers)
org-mode-hook '(#[nil "\300\301\302\303\304$\207"
[org-add-hook change-major-mode-hook
org-show-block-all append local]
5]
#[nil "\300\301\302\303\304$\207"
[org-add-hook change-major-mode-hook
org-babel-show-result-all append local]
5]
org-babel-result-hide-spec
org-babel-hide-all-hashes)
org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point
org-babel-execute-safely-maybe)
org-confirm-elisp-link-function 'yes-or-no-p
org-export-interblocks '((lob org-babel-exp-lob-one-liners)
(src org-babel-exp-inline-src-blocks))
org-occur-hook '(org-first-headline-recenter)
org-export-preprocess-before-selecting-backend-code-hook '(org-beamer-sele=
ct-beamer-code)
org-export-latex-final-hook '(org-beamer-amend-header
org-beamer-fix-toc
org-beamer-auto-fragile-frames
org-beamer-place-default-actions-for-lists)
org-enforce-todo-checkbox-dependencies t
org-metadown-hook '(org-babel-pop-to-session-maybe)
org-export-blocks '((src org-babel-exp-src-blocks nil)
(comment org-export-blocks-format-comment t)
(ditaa org-export-blocks-format-ditaa nil)
(dot org-export-blocks-format-dot nil))
)
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: [BUG] - error when compiling org sources from git
Carsten Dominik gmail.com> writes: > Me bad, this is fixed now. > Thanks, you are more than quick! :) Seweryn ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] [BUG] - error when compiling org sources from git
Seweryn Kokot writes: > I have just pulled orgmode sources from git and get the following > running 'make': > > In org-capture-expand-file: > org-capture.el:734:33:Warning: malformed cond form: `t' > org-capture.el:734:33:Warning: malformed cond form: `file' > org-capture.el:743:41:Error: Wrong type argument: listp, t > make: *** [lisp/org-capture.elc] Error 1 Carsten just fixed this. Thanks for reporting! -- Bastien ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] How-to access org-mode data
Hi, I try to extract certain information which are processed by org-mode. As an example the compiled agenda-list. Basically, I want to have certain parts of the agenda in a variable (or an array) instead of a buffer. I tried to follow org-agenda.el but this seems to be hard of a elisp beginner. At the moment I'm unsure what would be the best way to get those infos. I could run e.g., (org-agenda list nil nil 1) however, this always end up in a buffer, which I could start parsing and closing afterwards, but maybe there is a more smart way? I don't want to break any code and try to get this on top of the original org-mode code. To keep it simple for an example: Create org-agenda get the very next thing which need to be done as a string into a variable call result Any feedback is welcome Thanks Torsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] [BUG] - error when compiling org sources from git
On Feb 22, 2011, at 1:33 PM, Seweryn Kokot wrote: > I have just pulled orgmode sources from git and get the following > running 'make': > > In org-capture-expand-file: > org-capture.el:734:33:Warning: malformed cond form: `t' > org-capture.el:734:33:Warning: malformed cond form: `file' > org-capture.el:743:41:Error: Wrong type argument: listp, t > make: *** [lisp/org-capture.elc] Error 1 Me bad, this is fixed now. > > Regards, > Seweryn > > > ___ > Emacs-orgmode mailing list > Please use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] [BUG] - error when compiling org sources from git
I have just pulled orgmode sources from git and get the following running 'make': In org-capture-expand-file: org-capture.el:734:33:Warning: malformed cond form: `t' org-capture.el:734:33:Warning: malformed cond form: `file' org-capture.el:743:41:Error: Wrong type argument: listp, t make: *** [lisp/org-capture.elc] Error 1 Regards, Seweryn ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Poll for the next OrgCamp in Paris
Hello, A poll is open for the next OrgCamp in Paris : http://papillon.peacefrogs.net/poll/HIWAJM1298126080/ "OrgCamps are informal events where people gather IRL to contribute to Org by discussing how they use it and by doing contributions to the code, the manuals and the online tutorials." Nearly 20 people attended the first OrgCamp in Paris. Fred. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] BUG? Exporting "missing level" to LaTeX fails
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Considering the following file: * first * second * third *** FIRST *** SECOND * fourth If I export to htrml, the "missing level" is exported "properly", but in the LaTeX / pdf export, all levels below the "missing level" (FIRST, SECOND) are not exported. Am I right in considering this a bug? Cheers, Rainer - -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Natural Sciences Building Office Suite 2039 Stellenbosch University Main Campus, Merriman Avenue Stellenbosch South Africa Tel:+33 - (0)9 53 10 27 44 Cell: +27 - (0)8 39 47 90 42 Fax (SA): +27 - (0)8 65 16 27 82 Fax (D) : +49 - (0)3 21 21 25 22 44 Fax (FR): +33 - (0)9 58 10 27 44 email: rai...@krugs.de Skype: RMkrug -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1jpmIACgkQoYgNqgF2egq7qACdFRBf4yhCycRN8T+SYE1BlLzD i9IAnjNhKCx5zEVqr5K5IDpMsUmpBDLt =jASZ -END PGP SIGNATURE- ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Worg publishing broken?
Sébastien Vauban writes: > What I can say is that this feature is scheduled (well, not really) on my > private task list for Org. Not only languages, but as well highlight of all > other keywords such as `:vars', `:exports' and the like. Great, let us know how it goes and if you need help. Best, -- Bastien ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Bug: org-meta-return and collapsed sections [6.33x]
Hi Dave, Dave Abrahams writes: > When I am at the end of a line on a collapsed item and I hit `M-RET', I > expect it to insert a heading before the next *visible* line, i.e. after > this item. Instead, it injects the new heading before this item's > content. This has been fixed long ago, Org 6.33 is quite old now. I suggest you upgrade to a more recent version, if that's possible to you. Thanks, -- Bastien ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Deriving mode from org-mode
Hi Anders, Anders Waldenborg writes: > It is a "personal wiki" mode. It automatically narrows to current top level > heading, adds some extra navigation functions and allows creating links to > new "pages" (= top level heading) in a simple way. Hopefully I can clean it > up a little bit soon and publish it. That'd be great, thanks! -- Bastien ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: question about capture templates
Hi Carsten,
Carsten Dominik writes:
> I have just implemented that whenever you mean a file name
> in capture templates, you can instead give a function, a
> variable, or a lisp form. So your original attempt
>
>>> ("m" "Message" entry (file+datetree (buffer-file-name
>>> (buffer-base-buffer))) "* MSG @ %U %?\n %a")
>
> should now work.
Neat, thanks!
--
Bastien
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: convert orgmode to docx
Hi Fabian, Fabian Braennstroem writes: > Oh, one question... does this mean, it would be easier to use the > orgmode-version for everything or can I just add your odt-implementation to > my existing orgmode installation!? for now you would have to use two repositories: one with current Org's functionalities, another one with odt export plus and old Org version. Jambunathan and I are working on integrating this, but it's not as straightforward as it might look. We'll keep you posted, thanks! -- Bastien ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Context-sensitive word count in org mode (elisp)
Hi Paul, Paul Sexton writes: > The process of contributing to Worg is too complicated for me. You can clone the Worg.git repository with $ git clone git://repo.or.cz/Worg.git Then make some edit on Worg. Then commit your changes with $ git commit -a -m "Your message" Then create a patch with $ git format-patch master Then send the patch. > If someone else wants to add it somewhere on my behalf that is fine > with me. I added a section "Count words in an Org buffer" with your code in Worg/org-hacks.org. Thanks. > Have you thought of making Worg a wiki? > Wikis hosted on github can be written in org-mode format. Yes, but this format is limited. I think it's good to have all Org's functionalities in Worg, not only the one needed for publication. In particular, org-issues.org contains lots of information that we want to handle locally, not just for publishing. Best, -- Bastien ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: [babel][patch] C++ inconsistencies
Hi Martyn, Martyn Jago writes: > The FSF process is in progress - I'm currently waiting for the agreement > to sign. I'll tidy up the YAML export. I confirm the assignment/disclaimer process with the FSF is complete. I added you to the list of contributors on Worg: http://orgmode.org/worg/org-contribute.html#contributors_with_fsf_papers (We need to wait a bit before the Worg repo is published on the website.) Thanks for contributing! -- Bastien ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] IMPORTANT Modified link escaping in Org mode
Hi David, David Maus writes: >> Could you add the dmaus-org-check-percent-escapes.el function somewhere >> in Worg/org-hacks.org? This will allow us to link to it when releasing >> the next Org version. > > Done and done. Gave it the custom link 'check-old-link-escapes'. Thanks for this. -- Bastien ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] multiple agenda buffers
Hi Suvayu, Suvayu Ali writes: > This is exactly how I was expecting things to work when I proposed the > idea! Wonderful work, lots and lots of thank yous. :) Well, this command turned out to be trivial -- so thanks to the design of org-agenda.el ;) -- Bastien ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] need help with lisp for export function regarding timestamps
Hi Arun, Arun Persaud writes: > thanks for the answer. Played around with it and got it working now. > Will post it in Worg under google sync after I cleaned it up a bit. Thanks! -- Bastien ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Clock summary doesn't work in some cases
Hi, in the git version as of this morning (1e35a5ea37194d686f432d384f4e264498ca6294) the clock summary doesn't work right. Below is a clock summary with a version from February 11 and below that a clock summary with the git version I downloaded just a couple of hours ago. Somewhere in between all the headline information got lost. I guess this is caused by the introduction of org-clock-clocktable-language-setup on February 13. Is there a chance of defaulting the language to en if no language or a language without translation is set? Thanks a lot, Robert #+BEGIN: clocktable :maxlevel 2 :scope file-with-archives :emphasize nil :tstart "<2011-02-09 Mi 00:00>" :tend "<2011-02-15 Di 23:59>" Clock summary at [2011-02-21 Mo 14:23] | Headline |Time | | |+-+--| | ALL *Total time* | *17:30* | | |+-+--| | *File time*| *17:30* | | | task 1.1 |2:30 | | | task 1.2 misc |3:00 | | | TODO task 1.3 | 10:00 | | | task 1.4 |2:00 | | | \__ subtask 1.4.1 | | 2:00 | |+-+--| | *File time*| *0:00* | | #+END ** 21.2.2010 - 22.2.2010 #+BEGIN: clocktable :maxlevel 2 :scope file-with-archives :emphasize nil :tstart "<2011-02-16 Mi 00:00>" :tend "<2011-02-22 Di 23:59>" Clock summary at [2011-02-22 Di 11:23] | | | |--+-| | ** | *19:40* | |--+-| | ** | *19:40* | | task 2.1 | 5:25| | TODO task 2.2| 14:15 | |--+-| | ** | *0:00* | #+END ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Unable to select source code blocks
Il giorno 21/feb/2011, alle ore 12.51, Eric S Fraga ha scritto: > Giorgio Valoti writes: > >> Hi, > >> I don’t know if I’m missing something but I can’t get the >> org-babel-goto-named-src-block to work. When I invoke it on the sample >> file below the autocompletion shows nil and nothing else and if insert >> the source code block name I get a no match. I’m using org 7.4 with >> Emacs 23.2. >> >> * Source code navigation test >> #+srcname: test >> #+begin_src sh >>echo 'hello world' >> #+end_src >> >> #+results: test >> : hello world >> * Another item, another source code block >> #+srcname: test2 >> #+begin_src sh >>echo 'ciao mondo' >> #+end_src >> >> #+results: test2 >> : ciao mondo >> * and so on >> >> Thank you in advance >> -- >> Giorgio Valoti > > Giorgio, > > this works just fine for me; I don't know what you mean by > autocompletion but I use ido-everywhere and both test and test2 appear > in the prompt for =org-babel-goto-named-src-block=. Hi Eric, I don’t use ido-mode (maybe I should? Seems cool!). By autocomplete I meant tab completion. -- Giorgio Valoti ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Deriving mode from org-mode
On Feb 22, 2011, at 10:21 AM, Carsten Dominik wrote: > > On Feb 22, 2011, at 10:17 AM, Anders Waldenborg wrote: > >> On 02/15/2011 05:11 AM, Bastien wrote: >>> (org-mode-p) does the advertized job: checking whether we are in >>> org-mode major mode. It would be confusing to also check against >>> org derived modes, at least with that function's name. >> >> Agreed. Just hope it isn't used like that in other places. >> >> [] >> >>> Fixed, I corrected this directly in `org-edit-src-code', allow source >>> code to be edited from org-mode derived modes. >> >> Thanks! >> >>> Can you share what kind of derived mode you're writing? What for? >> >> It is a "personal wiki" mode. It automatically narrows to current top level >> heading, adds some extra navigation functions and allows creating links to >> new "pages" (= top level heading) in a simple way. Hopefully I can clean it >> up a little bit soon and publish it. > > You might also want to take a look at org-wikinodes.el in > the contrib directory. Sorry for following up on my own mail. I want to add a pointer to the documentation for org-wikinodes.el: http://orgmode.org/worg/org-contrib/org-wikinodes.html - Carsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Deriving mode from org-mode
On Feb 22, 2011, at 10:17 AM, Anders Waldenborg wrote: > On 02/15/2011 05:11 AM, Bastien wrote: >> (org-mode-p) does the advertized job: checking whether we are in >> org-mode major mode. It would be confusing to also check against >> org derived modes, at least with that function's name. > > Agreed. Just hope it isn't used like that in other places. > > [] > >> Fixed, I corrected this directly in `org-edit-src-code', allow source >> code to be edited from org-mode derived modes. > > Thanks! > >> Can you share what kind of derived mode you're writing? What for? > > It is a "personal wiki" mode. It automatically narrows to current top level > heading, adds some extra navigation functions and allows creating links to > new "pages" (= top level heading) in a simple way. Hopefully I can clean it > up a little bit soon and publish it. You might also want to take a look at org-wikinodes.el in the contrib directory. - Carsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Bug: org-meta-return and collapsed sections [6.33x]
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.
When I am at the end of a line on a collapsed item and I hit `M-RET', I
expect it to insert a heading before the next *visible* line, i.e. after
this item. Instead, it injects the new heading before this item's
content.
It's arguable that `M-RET' should *always* insert a new item after the
current one, whether or not the current one is collapsed. I'm certain I
would appreciate that behavior, because it's the 99% case (how often do
you really want to separate a heading from its content?). I can always
hit `RET * * * SPC' (or whatever) in the < 1% of cases where I need a
different behavior.
Emacs : GNU Emacs 23.2.1 (x86_64-apple-darwin, NS apple-appkit-1038.29)
of 2010-05-08 on black.local
Package: Org-mode version 6.33x
current state:
==
(setq
org-agenda-deadline-leaders '("D: " "D%d: ")
org-clock-in-switch-to-state "STARTED"
org-agenda-skip-scheduled-if-deadline-is-shown t
org-todo-keyword-faces '(("TODO" :foreground "medium blue" :weight bold)
("APPT" :foreground "medium blue" :weight bold)
("NOTE" :foreground "brown" :weight bold)
("STARTED" :foreground "dark orange" :weight bold)
("WAITING" :foreground "red" :weight bold)
("DELEGATED" :foreground "dark violet" :weight bold)
("DEFERRED" :foreground "dark blue" :weight bold)
("SOMEDAY" :foreground "dark blue" :weight bold)
("PROJECT" :height 1.5 :weight bold :foreground
"black"))
org-agenda-custom-commands '(("E" "Errands (next 3 days)" tags
"Errand&TODO<>\"DONE\"&TODO<>\"CANCELLED\"&STYLE<>\"habit\"&SCHEDULED<\"<+3d>\""
((org-agenda-overriding-header "Errands (next 3
days)")
)
)
("A" "Priority #A tasks" agenda ""
((org-agenda-ndays 1)
(org-agenda-overriding-header "Today's priority
#A tasks: ")
(org-agenda-skip-function
(quote (org-agenda-skip-entry-if (quote
notregexp) "\\=.*\\[#A\\]")))
)
)
("B" "Priority #A and #B tasks" agenda ""
((org-agenda-ndays 1)
(org-agenda-overriding-header "Today's priority
#A and #B tasks: ")
(org-agenda-skip-function
(quote (org-agenda-skip-entry-if (quote
regexp) "\\=.*\\[#C\\]")))
)
)
("w" "Waiting/delegated tasks" tags
"TODO=\"WAITING\"|TODO=\"DELEGATED\""
((org-agenda-overriding-header
"Waiting/delegated tasks:")
(org-agenda-sorting-strategy
(quote (todo-state-up priority-down
category-up)))
)
)
("u" "Unscheduled tasks" tags
"TODO<>\"\"&TODO<>\"DONE\"&TODO<>\"CANCELLED\"&TODO<>\"NOTE\"&CATEGORY<>{CEG\\|ABC\\|Bizcard\\|Adagio\\|EVAprint\\|\\}"
((org-agenda-overriding-header "Unscheduled
tasks: ")
(org-agenda-skip-function
(quote
Re: [Orgmode] Re: question about capture templates
On Feb 22, 2011, at 5:59 AM, Richard Lawrence wrote: > "Filippo A. Salustri" writes: > >> org-capture clearly has the original buffer handy (for %a >> stuff) yet I can't get it out of there without hacking the org code, which I >> am loathe to do. > > I too was in a situation just today where I was calling org-capture > programatically, and needed access to stuff in the calling environment. > My solution (which may not be very good, and may not work for you) is to > dynamically scope the calling environment stuff that I need into the > org-capture call, like so: > > #+begin_src emacs-lisp > ; in the calling code, I scope some val I need into `foo...' > (let ((foo some-val-I-need)) > (org-capture nil "tm")) > #+end_src > > Then, in the template identified by "tm", I have S-expression expansion > that operates on foo, even though it wasn't explicitly passed as a > parameter, e.g.: > > * My capture template > The car of foo is %(car foo). > The cdr of foo is %(cdr foo). > %a > etc. ... > > This works well enough for me, though it may feel kind of icky, since > from the template writer's perspective, `foo' looks like a global > variable whose value could be coming from anywhere. I do love dynamic scoping, this give a lot of power in Emacs. Org-mode internals use that power often. > Accordingly, then, > this solution is mostly useful if you know that you're going to be using > the template via custom Elisp calls to org-capture, and not via the > usual capture interface, so that you can guarantee that `foo' has a > useful value when the template is expanded. > > One gotcha: S-expressions in templates are apparently always evaluated > as function calls -- you can't just directly access a string value, like > %(foo). I guess you mean a variable value? The shortest form may be %(symbol-value foo) if you want to access the value of a variable in a template. Kind regards - Carsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Deriving mode from org-mode
On 02/15/2011 05:11 AM, Bastien wrote: (org-mode-p) does the advertized job: checking whether we are in org-mode major mode. It would be confusing to also check against org derived modes, at least with that function's name. Agreed. Just hope it isn't used like that in other places. [] Fixed, I corrected this directly in `org-edit-src-code', allow source code to be edited from org-mode derived modes. Thanks! Can you share what kind of derived mode you're writing? What for? It is a "personal wiki" mode. It automatically narrows to current top level heading, adds some extra navigation functions and allows creating links to new "pages" (= top level heading) in a simple way. Hopefully I can clean it up a little bit soon and publish it. anders ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: question about capture templates
On Feb 22, 2011, at 1:39 AM, Filippo A. Salustri wrote:
> Thanks to everyone for the varied and thoughtful responses. I didn't think
> of backquotes, but I know about them from Scheme, and no, they shouldn't work
> in this case.
>
> Very frustrating. org-capture clearly has the original buffer handy (for %a
> stuff) yet I can't get it out of there without hacking the org code, which I
> am loathe to do. Hmmm. I'll think some more. If I come up with anything;
> I'll report it.
I have just implemented that whenever you mean a file name
in capture templates, you can instead give a function, a
variable, or a lisp form. So your original attempt
>> ("m" "Message" entry (file+datetree (buffer-file-name
>> (buffer-base-buffer))) "* MSG @ %U %?\n %a")
should now work.
Hope this helps
- Carsten
>
> Cheers.
> Fil
>
> 2011/2/21 Sébastien Vauban
> Hi Richard,
>
> Richard Lawrence wrote:
> > Sébastien Vauban writes:
> >> "Filippo A. Salustri" wrote:
> >>> I would really like to be able to vary the file into which a captured item
> >>> goes. Specifically, I'd like to insert the item into whatever file I was
> >>> visiting when I started the capture.
> >
> >> You have to use backquotes so that expressions are considered as code to
> >> execute, instead of data. See Emacs manual.
> >
> > I'm not sure that backquotes will do what the OP wants. Backquotes will
> > allow the OP to compute the value of a target file at the time the (setq
> > org-capture templates ...) form is evaluated. The OP needs a way to
> > determine the target file at the time of capture (right?), not at the time
> > the variable is set.
>
> You're definitely right. I missed the distinction "at Org launch time" vs "at
> execution time"... Pull my answer off the records ;-)
>
> Best regards,
> Seb
>
> --
> Sébastien Vauban
>
>
> ___
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>
>
> --
> Filippo A. Salustri, Ph.D., P.Eng.
> Mechanical and Industrial Engineering
> Ryerson University
> 350 Victoria St, Toronto, ON
> M5B 2K3, Canada
> Tel: 416/979-5000 ext 7749
> Fax: 416/979-5265
> Email: salus...@ryerson.ca
> http://deseng.ryerson.ca/~fil/
> ___
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
- Carsten
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
