[O] org-jira.el
Hi, all I have implemented org-jira.el, bringing org-mode and Jira system together. Wrote a Wiki page for it on emacswiki: http://www.emacswiki.org/emacs/OrgJiraMode Hope somebody find it useful, if he/she is also using Jira and loves org-mode.
Re: [O] Problem with noweb-ref property
Tomas Grigera tgrig...@gmail.com writes: Hi Eric, Thanks a lot for your quick reply and fix. Getting the git repo version scares me a bit, but I guess I'll just have to take the plunge! Here we go :) Thanks again, Tomas On Thu, Dec 29, 2011 at 16:51, Eric Schulte eric.schu...@gmx.com wrote: Tomas Grigera tgrig...@gmail.com writes: Hi list, This is my first post, so just let me say first that I have been using org-mode for 10 months or so and I love it. It's an exceptional package, and before I ask my question I would just like to thank Carsten, Bastien, and the community for the great work and for sharing. Now my question: I am trying to extract code from a .org file by tangling with noweb-style references. As I understand from the manual, if I write foo in a code block, the line will be expanded with the code block named foo. This name I can set with #+NAME: or with the :noweb-ref header argument. Both ways work for me, except that I cannont set the :noweb-ref argument through a property. The following example is almost verbatim from the manual: #+BEGIN_SRC sh :tangle yes :noweb yes :shebang #!/bin/sh fullest-disk #+END_SRC * the mount point of the fullest disk ** query all mounted disks #+HEADER: :noweb-ref fullest-disk #+BEGIN_SRC sh df \ #+END_SRC ** strip the header row :PROPERTIES: :noweb-ref: fullest-disk :END: #+BEGIN_SRC sh :noweb yes |sed '1d' \ #+END_SRC If I understand correctly, tangling should produce a file which is a concatenation of the two code blocks. However, when I do org-babel-tangle, only the first block is inserted. Am I doing something wrong? I'm with emacs 23.2.1 and org-mode 7.8.02 Thanks in advance, Tomas Hi Tomas, You are correct the behavior described above is a bug introduced by a fairly recent commit of mine which switched to using regular expressions when resolving noweb references in an attempt to decrease the time required to tangle code blocks (which can be significant in large code blocks). However correct performance is more important than fast performance. I've just pushed up a patch which fixes the bug you've described, and hopefully doesn't slow down the tangling process too significantly. Cheers, -- Eric Schulte http://cs.unm.edu/~eschulte/ Hi Eric, unfortunately, for me it does result in a considerably slow down. (Well, I did not bisect this time but still suspect the commit you mention in this thread.) As a test case you can still use http://pastebin.com/c42jS1Be from my last post on this matter and expand the first source block. Sorry to ask again: Would it be possible to speed things up again or to make the :noweb-ref feature optional? Regards, Andreas
Re: [O] [babel] Is there a way to use edebug on emacs-lisp code blocks ?
Am 01.01.2012 23:40, schrieb Nicolas Goaziou: Marc-Oliver Ihmmarc-oliver@online.de writes: So, if I have something like: #+call: foo(1,2) I cannot see a way to get a buffer with all the code, that foo might expand into, INCLUDING the assignments for the arguments 1 and 2. (If babel would give me such a buffer, than it would be easy to use edebug on it, I agree.) So, to be more precise: Is there any command that would expand a full #+call: line like above with all its arguments into pure elisp ? AFAIK, there is no such command. Regards, Okay, thanx ! Than I will simply define an elisp-function and use edebug in that. That's definitely fair enough for my case ! (but I will keep explicit edebug-support on my wishlist :-) with kind regards, Marc-Oliver Ihm
Re: [O] Location of OpenDocument style files should be configurable
Ulrich
So, could the build system please be changed, such that the datadir
value at _compile_ time is taken, not at _install_ time?
I.e., something like the patch included below.
BTW, maybe one could think about supporting DESTDIR? That should be
trivial to implement, simply prepend $(DESTDIR) to all destination
paths in the install-* make targets. I can prepare a patch if this is
wanted.
http://www.gnu.org/prep/standards/html_node/DESTDIR.html
It would be wonderful if you could provide a patch (and a usage note).
ps: Makefiles are beyond my jurisdiction. I will let Bastien act on your
patch(es).
Jambunathan K.
Cheers,
Ulrich
From f6eb5150418bfd5de35b8f4f9ca39f4cbff1d40b Mon Sep 17 00:00:00 2001
From: Ulrich Mueller u...@gentoo.org
Date: Sun, 1 Jan 2012 21:39:21 +0100
Subject: [PATCH] Don't re-compile org-odt.el at install time.
---
Makefile |6 +-
1 files changed, 1 insertions(+), 5 deletions(-)
diff --git a/Makefile b/Makefile
index 520b0fd..642b21f 100644
--- a/Makefile
+++ b/Makefile
@@ -247,14 +247,10 @@ p:
g:
${MAKE} pdf open doc/orgguide.pdf
-# Always force re-compilation of org-odt
-lisp/org-odt.elc: org-odt-data-dir
-org-odt-data-dir:
-
# Sleight of hand to hard code the value of $(datadir) in
# org-odt.el. See variables `org-odt-styles-dir-list' and
# `org-odt-schema-dir-list'.
-install-lisp: BATCH_EXTRA = -eval (setq org-odt-data-dir (expand-file-name
\$(datadir)\))
+lisp/org-odt.elc: BATCH_EXTRA = -eval (setq org-odt-data-dir
(expand-file-name \$(datadir)\))
install-lisp: $(LISPFILES) $(ELCFILES)
if [ ! -d $(lispdir) ]; then $(MKDIR) $(lispdir); else true; fi ;
Re: [O] [PATCH] Org manual on :noweb-ref property
Hi Tomas, Tomas Grigera tgrig...@gmail.com writes: After Eric's fix a couple of days ago, setting :noweb-ref through a property now works as explained in the manual. However, the example given will only work if one turns on property inheritance. I think it is worthwhile noting this in the manual. The patch here adds that comment. Thanks for the patch -- I've committed a slightly different version, using a footnote. First time I send a patch, sorry if I screwd up. You did right, thanks! -- Bastien
Re: [O] Feature suggestion
Hi York, York Zhao gtdplatf...@gmail.com writes: May I suggest a feature that when the point is inside a TeX source block and C-c C-c is pressed, instead of showing the error No org-babel-execute function for tex!, can we process the current tex block to output the dvi or pdf file? I'd rather define a org-babel-execute:tex function for that. Maybe look at org-babel-execute:* functions and suggest one? Thanks! -- Bastien
Re: [O] Feature suggestion
York Zhao gtdplatf...@gmail.com writes: May I suggest a feature that when the point is inside a TeX source block and C-c C-c is pressed, instead of showing the error No org-babel-execute function for tex!, can we process the current tex block to output the dvi or pdf file? I'd rather define a org-babel-execute:tex function for that. Maybe look at org-babel-execute:* functions and suggest one? Thanks! Hi Bastien, I think this is a good idea. By `org-babel-execute:tex' do you mean `org-babel-execute-tex'? York
[O] [babel][bug]
There is a bug running babel on Emacs 22.1.1 with a minimal init file. The following code works: --8---cut here---start-8--- * Test passes #+begin_src emacs-lisp hello there #+end_src #+results: : hello there --8---cut here---end---8--- The following fails: --8---cut here---start-8--- * Test fails #+begin_src emacs-lisp :results silent hello there #+end_src --8---cut here---end---8--- The problem appears to be associated with the :results parsing. The backtrace is as follows: --8---cut here---start-8--- Debugger entered--Lisp error: (wrong-type-argument listp 58) matches(114 58) matched(114 58) #[(ch)
Re: [O] Feature suggestion
Hi York, York Zhao gtdplatf...@gmail.com writes: I think this is a good idea. By `org-babel-execute:tex' do you mean `org-babel-execute-tex'? No, I mean org-babel-execute:tex. There is a whole family of Babel functions that let C-c C-c act upon a source block, with respect to the langage used. Do `C-h f org-babel-execute: TAB' to see the list of available function for your configuration. Then you can pick up a langage you are familiar with in this list, jump to the Emacs lisp function and start getting familiar with the code to write your own org-babel-execute:tex function. But wait, there is already org-babel-execute:latex, so I think part of the problem is already solved. Good exploration, -- Bastien
Re: [O] About the use of PROPERTY meta lines...
Sebastien Vauban wxhgmqzgw...@spammotel.com writes: #+TITLE: Properties #+AUTHOR:Seb Vauban #+PROPERTY: var foo=1 #+PROPERTY: var+ bar=2 * Abstract IIUC, properties are set in this way: - on a file basis, before any heading, through the =PROPERTY= keyword, - on a subtree basis, through the =PROPERTIES= block. My comprehension is that the =PROPERTY= keyword may not be used inside trees, and should be ignored if that would happen. While it is not normal usage, I think that it is legal for #+PROPERTY: lines (or #+Option: lines etc...) to appear inside of subtrees. Best -- Eric The following example shows that either: - I'm wrong to think so, - there is a bug. What is the right assumption here? * Subtree Being located in a subtree, the following lines are ill-placed IMHO: #+PROPERTY: var foo=Hello #+PROPERTY: var+ world Though, they're well taken into account: #+begin_src emacs-lisp foo #+end_src #+results: : Hello world These lines have even wiped the definition of =bar= (because of the use of =var= without any =+=): #+begin_src emacs-lisp (+ foo bar) #+end_src returns the error Symbol's value as variable is void: bar. Best regards, Seb -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] inline src_R also in latex src block
Michael Bach pha...@gmail.com writes:
Hello,
I am using org-mode version 7.8.02
I can successfully do inline `src_R' e.g. via
\begin{equation}
src_R{4 + 4}
\end{equation}
where `8' is put into the equation environment on export. Sadly, there
is no LaTeX font lock in the org file this way. But when I do it inside
a latex src block providing font lock, e.g.
#+name: test
#+begin_src latex
\begin{equation}
src_R{4 + 4}
\end{equation}
#+end_src
the `src_R' is put in literally on latex export.
Is there a way of preprocessing this latex src block with babel for R
prior to exporting?
I don't know of a way to evaluate inline code blocks which are already
inside of regular code blocks. You could try direct begin_latex code
blocks, but in-buffer font lock support may simply not be possible in
this situation.
Best,
Thanks in advance,
Michael
--
Eric Schulte
http://cs.unm.edu/~eschulte/
Re: [O] [babel] noweb with ob-screen??
Torsten Wagner torsten.wag...@gmail.com writes: Hi this is a follow up on a early post. I try to get noweb working with ob-screen. I wrote several code blocks and named them. I finished with a code block which calls all other blocks using noweb notation adding to its header :noweb yes. I execute this block by C-c C-c but the noweb reference get not resolved. In my understanding they should isn't it? Or do I mix tangling and execution? In my understanding noweb should work for both cases isn't it? The expansion should occur as part of executing the code block. For example notice the expansion of the sh code blocks in this example... #+begin_src sh :noweb yes :results output first second #+end_src #+results: : first : second #+name: first #+begin_src sh echo first #+end_src #+name: second #+begin_src sh echo second #+end_src I looked in the source code of ob-screen and try to get an idea why it doesn't work. However compare to other babel modes I could not find that it is missing anything related to noweb. It seems to me that noweb is a babel mode independent functionality and hence should work with all babel languages. This is certainly the case, noweb expansion occurs *before* the language specific code is invoked. In fact I can confirm that an expanded body is passed to the screen execution function. Are you sure that it is only screen code blocks for which you are having trouble with noweb references? Could you ensure that the attached example above expands for sh code blocks, and then try to translate it to screen code blocks? If I'm wrong could someone please point me to an example in the source code how to implement noweb functionality. The above example should serve, the manual is also a good resource, and finally there any many small examples located at http://eschulte.github.com/org-scraps/ Best -- Eric Thanks a lot Torsten Cc. Sorry all this is written down from memory on my smartphone and hence no code examples and maybe wrong syntax. -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] Problem with noweb-ref property
Andreas Leha andreas.l...@med.uni-goettingen.de writes: Tomas Grigera tgrig...@gmail.com writes: Hi Eric, Thanks a lot for your quick reply and fix. Getting the git repo version scares me a bit, but I guess I'll just have to take the plunge! Here we go :) Thanks again, Tomas On Thu, Dec 29, 2011 at 16:51, Eric Schulte eric.schu...@gmx.com wrote: Tomas Grigera tgrig...@gmail.com writes: Hi list, This is my first post, so just let me say first that I have been using org-mode for 10 months or so and I love it. It's an exceptional package, and before I ask my question I would just like to thank Carsten, Bastien, and the community for the great work and for sharing. Now my question: I am trying to extract code from a .org file by tangling with noweb-style references. As I understand from the manual, if I write foo in a code block, the line will be expanded with the code block named foo. This name I can set with #+NAME: or with the :noweb-ref header argument. Both ways work for me, except that I cannont set the :noweb-ref argument through a property. The following example is almost verbatim from the manual: #+BEGIN_SRC sh :tangle yes :noweb yes :shebang #!/bin/sh fullest-disk #+END_SRC * the mount point of the fullest disk ** query all mounted disks #+HEADER: :noweb-ref fullest-disk #+BEGIN_SRC sh df \ #+END_SRC ** strip the header row :PROPERTIES: :noweb-ref: fullest-disk :END: #+BEGIN_SRC sh :noweb yes |sed '1d' \ #+END_SRC If I understand correctly, tangling should produce a file which is a concatenation of the two code blocks. However, when I do org-babel-tangle, only the first block is inserted. Am I doing something wrong? I'm with emacs 23.2.1 and org-mode 7.8.02 Thanks in advance, Tomas Hi Tomas, You are correct the behavior described above is a bug introduced by a fairly recent commit of mine which switched to using regular expressions when resolving noweb references in an attempt to decrease the time required to tangle code blocks (which can be significant in large code blocks). However correct performance is more important than fast performance. I've just pushed up a patch which fixes the bug you've described, and hopefully doesn't slow down the tangling process too significantly. Cheers, -- Eric Schulte http://cs.unm.edu/~eschulte/ Hi Eric, unfortunately, for me it does result in a considerably slow down. (Well, I did not bisect this time but still suspect the commit you mention in this thread.) As a test case you can still use http://pastebin.com/c42jS1Be from my last post on this matter and expand the first source block. Sorry to ask again: Would it be possible to speed things up again or to make the :noweb-ref feature optional? Hi Andreas, I've just pushed up a new variable to the git repository. To enable the faster regexp-based method of noweb expansion (which is not able to resolve noweb-ref header arguments inherited from sub-tree or file-wide properties) put the following in your config. (setq *org-babel-use-quick-and-dirty-noweb-expansion* t) Best, Regards, Andreas -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] Unable to unfold a folded block having point directly after the folded block
Hi Rainer, Rainer Stengele rainer.steng...@online.de writes: Having *** Headline :LOGBOOK: - point is at the end of the headline - moving one line down I am at the end of the LOGBOOK line There I cannot open the folded LOGBOOK block with TAB. I have to move point one character back in order to unfold it with TAB. After that I can no more reach the end of this line like before, where I could not unfold with TAB. Is this intended? No. This is fixed now. Thanks, -- Bastien
Re: [O] Filter the agenda by category
Awesome, thanks! Cheers, Viktor Bastien wrote: Hi Vicktor, Viktor Rosenfeld listuse...@googlemail.com writes: is it possible to quickly limit what the agenda is showing to one category? Yes -- you can now use `' to filter the agenda through the category from the current line. Another press to `' will remove the filter. This filter can be combined with tag filters -- Also check the new option `org-agenda-category-filter-preset'. Best, -- Bastien
Re: [O] Color agenda items
Hi Max, Maximilian Matthe maxi.mat...@googlemail.com writes: I've imported school holidays from .ics into my org-mode setup. They do show up in the agenda. I would like to have a special color for all holiday entries in the agenda. Maybe I can add this in the PROPERTIES-Drawer? I don't think so. How are you adding your .ics data into your Agenda? And another related question: Is it possible to give the start and end of a date (e.g. holidays) a different color than the intermediate days? Nope, sorry. -- Bastien
Re: [O] org-column face
Hi Michael, Michael Brand michael.ch.br...@gmail.com writes: What is the right way for the setup to get all this working? The default face for the column view is DeJa Sans Mono for me, working fine. Are things okay by just setting the face with M-x customize-face RET org-column RET then picking up the font family of your choice? -- Bastien
[O] org-contacts: match name without formatting
I use radio headers in my contacts data base, like: * Alice * Bob (Alice's brother) org-contacts was presenting the names with before, so you needed to type to match them. I attach a patch to remove this particular formatting before presenting the completions; in this way you can match them by Al or B Removing bold/italic/underline/pre is harder. If there is any better function to remove formatting, please use it. -- Daniel -- diff --git a/contrib/lisp/org-contacts.el b/contrib/lisp/org-contacts.el index 74d68dc..156fa66 100644 --- a/contrib/lisp/org-contacts.el +++ b/contrib/lisp/org-contacts.el @@ -375,12 +375,18 @@ This function should be called from `gnus-article-prepare-hook'. (org-completing-read prompt (org-contacts-filter) predicate t initial-input hist def inherit-input-method)) +(defun org-contacts-format-name (name) + Remove some formatting marks from contact name + (replace-regexp-in-string org-radio-target-regexp \\1 name) + ; TODO also remove emphasis (org-emphasis-alist) +) + (defun org-contacts-format-email (name email) Format a mail address. (unless email (error `email' cannot be nul)) (if name - (concat name email ) + (concat (org-contacts-format-name name) email ) email)) (defun org-contacts-check-mail-address (mail)
Re: [O] Please test the new Makefile
I've implemented a few improvements in my fork that should take care of most issues raised in recent discussions: - default target is now all instead of help - make does not complain when not inside a Git tree - all installations prefixed with $(DESTDIR) to allow for staged installation - introduced $(datadir) as replacement for $(etcdir) and moved into default.mk; $(datadir) is recorded as a defconst into org-install.el - more robust shell code - removed maint.mk and maint-targets.mk, these will have to be rolled into local.mk (or included from there) on the server I'm uncertain about the integration of the ODT exporter (although it works on my machine): it seems that the schema files should reside in etc/schema (and ETCDIR should include schema on install)? Why are the schema files only in contrib? Also there is some compile-time evaluation of org-odt-data-dir that seems unnecessary to me (I don't set this variable at compile-time, anyhow)? Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ DIY Stuff: http://Synth.Stromeko.net/DIY.html
Re: [O] Location of OpenDocument style files should be configurable
Jambunathan K kjambunat...@gmail.com writes: I have pushed a fix so that make install will do the right thing. Package maintainers have to modify just the $(lispdir) and $(datadir) vars in the Makefile. (Hopefully) They don't have to do anything special at all. You may also want to read the comments under DATAFILES to have an idea of what is available for packaging. I've implemented it somewhat differently in my Makefile fork, please see the thread here: http://thread.gmane.org/gmane.emacs.orgmode/50366/focus=50378 (org-odt-styles-dir-list, org-odt-schema-dir-list): New variables. Pay specific attention to (eval-when-compile ...) form through which Makefile's $(datadir) - contained in `org-odt-data-dir' - gets compiled in as a hard coded constant. I don't understand the need for compile-time evaluation. In any case it would be nice to avoid it. I see why the schema directory doesn't become part of GNU Emacs, but why should org-mode git not distribute and install the files? For my Makefile fork it would simply need adding schema to ETCDIRS and moving the files from contrib to etc. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
[O] org-diary-class doesn't skip weeks
Could somebody help me, please? I had org 7.5 before and the following sexp worked fine: %%(org-diary-class 8 11 2011 6 2 2012 1 47 51 52 14) StudentName 4:45pm-5:15pm After upgrading to org 7.7 the skipping weeks part stopped working, meaning I still have a student appearing in Agenda at 4:45pm during the 52nd week, even though I excluded him. I also upgraded to org 7.8.2 both on my mac and in Ubuntu, and both stopped working (don't skip weeks) I found a post that the command org-diary-class has been deprecated? Does it mean that the skipping-week feature is implemented somehow differently, or maybe the syntax is wrong? Thank you in advance, Evgeniy
Re: [O] org-column face
Hi Bastien Setting org-column-face did not solve my issues (and in my opinion should be avoided if possible) but helped me to find out that the problem is either set-frame-font too late in my large setup or the use of default-frame-alist even when at the first place. This minimal setup works for all use cases mentioned earlier: (set-frame-font DejaVu Sans Mono-12) (add-to-list 'load-path /f/git/org-mode/lisp/) (require 'org-install) (require 'org) Now I am a bit confused why the above works but not (add-to-list 'default-frame-alist '(font . DejaVu Sans Mono-12)) (add-to-list 'load-path /f/git/org-mode/lisp/) (require 'org-install) (require 'org) because the Emacs info manual mentions default-frame-alist but not set-frame-font. Michael On Mon, Jan 2, 2012 at 20:08, Bastien b...@altern.org wrote: Michael Brand michael.ch.br...@gmail.com writes: What is the right way for the setup to get all this working? The default face for the column view is DeJa Sans Mono for me, working fine. Are things okay by just setting the face with M-x customize-face RET org-column RET then picking up the font family of your choice?
Re: [O] About the use of PROPERTY meta lines...
Hi Eric and all, Eric Schulte wrote: Sebastien Vauban wxhgmqzgw...@spammotel.com writes: #+TITLE: Properties #+AUTHOR:Seb Vauban #+PROPERTY: var foo=1 #+PROPERTY: var+ bar=2 * Abstract IIUC, properties are set in this way: - on a file basis, before any heading, through the =PROPERTY= keyword, - on a subtree basis, through the =PROPERTIES= block. My comprehension is that the =PROPERTY= keyword may not be used inside trees, and should be ignored if that would happen. While it is not normal usage, I think that it is legal for #+PROPERTY: lines (or #+Option: lines etc...) to appear inside of subtrees. I realize this is not especially a Babel question, but more a Org core question... Thanks for your answer -- which generates a new one, though: what is then the expected *semantics* of such a construct? There are at least 3 different views on such a construct: putting a PROPERTY line inside a subtree... - ... resets some values from that point up to the end of the subtree - ... resets some values from that point up to the end of the buffer - ... defines some values which can have already been by the subtree Best regards, Seb The following example shows that either: - I'm wrong to think so, - there is a bug. What is the right assumption here? * Subtree Being located in a subtree, the following lines are ill-placed IMHO: #+PROPERTY: var foo=Hello #+PROPERTY: var+ world Though, they're well taken into account: #+begin_src emacs-lisp foo #+end_src #+results: : Hello world These lines have even wiped the definition of =bar= (because of the use of =var= without any =+=): #+begin_src emacs-lisp (+ foo bar) #+end_src returns the error Symbol's value as variable is void: bar. -- Sebastien Vauban
