[O] adding a new org-element?
Suppose one wanted to add a new org-element/syntax to org-mode. Where would one start? I am interested in something like the following syntax: $(arbitrary stuff inside the sexp)$ with a mechanism to call an export function to transcode it. Any pointers to getting started? -- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu
Re: [O] scheme SRC blocks
> In addition to requiring 'geiser-install you have to set the > geiser-active-implementations variable, e.g.: Customizing the geiser-active-implementations variable works for me. Thank you. > alternatively there is a :scheme header argument for src blocks: > > #begin_src scheme :scheme guile Unfortunately, this doesn't work for me. Is this header argument documented somewhere in the manual? This approach seems more self-contained to the org file, and it'll be good to have this, in case I want to send my org file to someone else, or if I decide to try out more scheme implementations. signature.asc Description: PGP signature
[O] Duplicating Capture Times
I use orgmode capturing to schedule events. The date ends up going in to three places: since my agenda file has things scheduled in a tree, it asks where in the tree to put it. Then it asks, what regular date to insert for the schedule; then it asks what date to use for the deadline. I use deadlines because of how they function in orgmode, and I use regular dates so they are exported properly for Google Calendar. But how can I cause two or even all three of these to use the answer from just one prompting of the date, so I don't have to specify so many times? Thanks, - Tory
[O] clock tables and archived trees
Hi, I've been using clock tables to track my work, and it works pretty well. I have a journal.org file, with a different heading for each month. Under that heading is a clocktable with the :block property set to that month, and :step day. This gives me a daily summary for the month. However, if I complete a task early in the month, and then archive its heading, any further updates to the clocktable will not reflect the time spent on that item - the effort is no longer included in the clock table. Is there a way to cope with this? Perhaps a setting to keep the times for archived items, or a different workflow that will allow for dynamic work time-tracking that is compatible with archiving completed tasks? Thanks for any suggestions, Tyler -- plantarum.ca
Re: [O] scheme SRC blocks
On Mon, 21. Mar 08:22, Robert Klein wrote: Hi, Arun Isaac wrote: I have an org file with scheme SRC blocks like so. #+BEGIN_SRC scheme (some-code-here) #+END_SRC Every time, I open the org file, I get prompted for the "Scheme implementation" and I need to choose an implementation (guile, in my case) before continuing. Similarly, I am also prompted for the same when publishing the org file, or opening up the SRC block using org-edit-special (C-c ') for editing. This happens because of the behaviour of the command "scheme-mode" which prompts for the required scheme implementation. Manually choosing the scheme implementation every time is tedious and annoying. Is there some way to circumvent this issue? In addition to requiring 'geiser-install you have to set the geiser-active-implementations variable, e.g.: #+begin_src emacs-lisp (require 'geiser-install) (setq geiser-active-implementations '(guile)) #+end_src See also http://www.nongnu.org/geiser/geiser_3.html#choosing_002dimpl in the Geiser manual. Best regards Robert Hi, alternatively there is a :scheme header argument for src blocks: #begin_src scheme :scheme guile Regards Bernhard
Re: [O] scheme SRC blocks
Hi, Arun Isaac wrote: > > I have an org file with scheme SRC blocks like so. > > #+BEGIN_SRC scheme > (some-code-here) > #+END_SRC > > Every time, I open the org file, I get prompted for the "Scheme > implementation" and I need to choose an implementation (guile, in my > case) before continuing. Similarly, I am also prompted for the same > when publishing the org file, or opening up the SRC block using > org-edit-special (C-c ') for editing. This happens because of the > behaviour of the command "scheme-mode" which prompts for the required > scheme implementation. > > Manually choosing the scheme implementation every time is tedious and > annoying. Is there some way to circumvent this issue? In addition to requiring 'geiser-install you have to set the geiser-active-implementations variable, e.g.: #+begin_src emacs-lisp (require 'geiser-install) (setq geiser-active-implementations '(guile)) #+end_src See also http://www.nongnu.org/geiser/geiser_3.html#choosing_002dimpl in the Geiser manual. Best regards Robert