Re: [O] orgmode for many continuous tasks?
On Wednesday, 27 Sep 2017 at 13:24, Bob Newell wrote: [...] > To further the concept: If TODOs had due dates/time estimates/time spent > as perhaps additional properties, and there was a better way to express > dependencies (I think there is already an org-mode adjunct for this), > some coding could turn this into a Task Juggler input file. There is ox-taskjuggler in org-contrib... -- : Eric S Fraga via Emacs 27.0.50, Org release_9.1.1-78-gfbf47c signature.asc Description: PGP signature
[O] Tangling org file with nested org source block
Hi list, I am trying to tangle the following org file: , | #+PROPERTY: header-args :tangle output.org | | #+BEGIN_SRC org | | ,* Test | | ,#+BEGIN_SRC org | ,,#+BEGIN_SRC emacs-lisp | '(1 2 3) | ,,#+END_SRC | ,#+END_SRC | | #+END_SRC ` (note the double commas at the beginning of the inner-most block). I am working on master (Org mode version 9.1.1 (release_9.1.1-79-g731e1c.dirty @ .../org-mode/lisp/)), and I get the following: , output.org | * Test | | #+BEGIN_SRC org | #+BEGIN_SRC emacs-lisp | '(1 2 3) | #+END_SRC | #+END_SRC ` The inner block does not get escaped which causes issues when exporting. Trying to investigate this, I ended up in the ~org-babel-tangle-single-block~ function in =ob-tangle.el=. The second comma is removed by a call to ~org-unescape-code-in-string~ (l. 497). Since the incoming string has already been cleaned-up (i.e. the first comma removed) at that point I wonder why this call is necessary. When I remove that call to ~org-unescape-code-in-string~, tangling produces the output I expect: , output.org | * Test | | #+BEGIN_SRC org | ,#+BEGIN_SRC emacs-lisp | '(1 2 3) | ,#+END_SRC | #+END_SRC ` where the inner source block is properly escaped. So, is the call to ~org-unescape-code-in-string~ required? Does anyone know if there is a way to get the desired output? Thanks in advance, thibault
Re: [O] orgmode for many continuous tasks?
Mycroft Jones writes: > I'm wondering if org-mode can do this: > > I have many tasks. Some are one off. But many are tasks that will take a > period of time, days, weeks, months. I need to schedule a bit of time every > day. Over time I can complete the tasks by plugging away. But I have so > many. > Half hour chunks work for some tasks, 1 or 2 or 3 hour chunks work best for > others. Aloha, This sort of thing is really a project management issue. While I know you're asking for an org-mode solution, something like Task Juggler will do the kind of scheduling you want. But it would be a fair amount of work entering progress and updating scenarios every night. What is really needed is a good org-mode/Task Juggler interface. (There is an Emacs interface but it's meant for creating and running Task Juggler scenarios directly.) I'm not necessarily volunteering to write one, but it could be done. However this doesn't help you in the near term. To further the concept: If TODOs had due dates/time estimates/time spent as perhaps additional properties, and there was a better way to express dependencies (I think there is already an org-mode adjunct for this), some coding could turn this into a Task Juggler input file. There is already a project management adjunct for Emacs, but it doesn't do scheduling. -- Bob Newell Honolulu, Hawai`i * Via Gnus/BBDB/Org/Emacs/Linux *
Re: [O] orgmode for many continuous tasks?
On Wed, 27 Sep 2017 13:02:26 -0400, Mycroft Jones wrote: On Wed, Sep 27, 2017 at 07:14:25PM +0300, Melleus wrote: That's true. But the clipboard can't beep when you might have forgotten about some important appointment when shearing a sheep, driving a tractor or doing other interesting things... If you don't neeed the reminder functionality then the clipboard is the winner I should agree. If you had a days advance warning, the appointment should be in the printout on the clipboard. If it is an appointment that suddenly came up, you should write it on the clipboard. If you have an urgent appointment scheduled, you shouldn't be up on the roof or driving the tractor. :) Mycroft When I am driving the tractor I cannot hear anything beep. Maybe I should do a Hackaday project that would notify me. Air-raid sirens or eclipsing the sun might get my notice. When shearing sheep I don't want anything on me that is any more high tech than the shears. The electric shears have a high-tech motor. The low-tech, which are actually safer for the sheep, have not changed in design for hundreds of years or more. Burgon & Ball have made them since 1730. https://www.burgonandball.com/shop/scripts/prodList.asp?idcategory=80 I have some nice aluminum clipboards that also have a compartment. Portable writing desk, if you will. I'm going to try incorporating them into a better method for keeping track of things. No beeping, though.
Re: [O] orgmode for many continuous tasks?
On Wed, Sep 27, 2017 at 07:14:25PM +0300, Melleus wrote: That's true. But the clipboard can't beep when you might have forgotten about some important appointment when shearing a sheep, driving a tractor or doing other interesting things... If you don't neeed the reminder functionality then the clipboard is the winner I should agree. If you had a days advance warning, the appointment should be in the printout on the clipboard. If it is an appointment that suddenly came up, you should write it on the clipboard. If you have an urgent appointment scheduled, you shouldn't be up on the roof or driving the tractor. :) Mycroft
Re: [O] orgmode for many continuous tasks?
Mycroft Jones writes: >>Maybe it's a bit overhead, but anyway. You can use org-caldav-sync to sync the >>todos with local owncloud (or other caldav) server and use some phone/tablet's >>calendar to sync with owncloud to have your tasklist with you on the run and >>you can use it for capturing todos also, as the two-way sync is no problem for >>org-caldav-sync. > > When you're up on a roof, or driving a tractor, or shearing a sheep, a cell > phone can be destroyed very quickly. Last thing you need is it dropped into > the mud and stepped on by a heavy ungulate. Clipboard is cheap, and you can > always print out your list again. Getting in the habit of being away from the > computer is good. Getting in the habit of reviewing the days events at the > end > of it is also good. That's true. But the clipboard can't beep when you might have forgotten about some important appointment when shearing a sheep, driving a tractor or doing other interesting things... If you don't neeed the reminder functionality then the clipboard is the winner I should agree.
Re: [O] How to suppress latex exporting as a list if a name that begins with a single letter
On Wednesday, 27 Sep 2017 at 08:02, Charles Millar wrote: [...] > I read the documentation and I suppose that there is no way to set > that variable on a per file basis. Correct? You could use emacs file variables for this, along the lines of # -*- org-set-list-allow-alphabetical: nil; -*- at the top of the file or a local variables list at the end (see Emacs info manual for more information). -- : Eric S Fraga via Emacs 26.0.50, Org release_9.1-64-g657302 signature.asc Description: PGP signature
Re: [O] export of formatted date macro fails
Hi, On Wed, 27 Sep 2017 13:21:14 + Kaushal Modi wrote: > On Wed, Sep 27, 2017, 8:52 AM Robert Klein wrote: > > > > > and later the macro > > > > {{{date(%A, %B %e, %Y)}} > > > > The exported document only has the "Sunday" (%A) part of the date. > > > > Same for {{{date(%A,%B%e,%Y)}}. > > > > , is used as Org macro arguments separator. So that needs to be > escaped with a backslash. > > Try: > > {{{date(%A\, %B %e\, %Y)}} > you're so right. IIRC I use it in some files, too. *Banging my head on the wall* Thank you very much!! Best regards Robert
Re: [O] export of formatted date macro fails
On Wed, Sep 27, 2017, 8:52 AM Robert Klein wrote: > > and later the macro > > {{{date(%A, %B %e, %Y)}} > > The exported document only has the "Sunday" (%A) part of the date. > > Same for {{{date(%A,%B%e,%Y)}}. > , is used as Org macro arguments separator. So that needs to be escaped with a backslash. Try: {{{date(%A\, %B %e\, %Y)}} > -- Kaushal Modi
[O] export of formatted date macro fails
Hi, when I export a formatted date via the {{{date}}} macro _and_ use e.g. commas and/or spaces, I only get the first component in the exported file (tested for HTML and PDF export). E.g. in my document I have a date: #+DATE: [2008-11-09 Sun 11:00] and later the macro {{{date(%A, %B %e, %Y)}} The exported document only has the "Sunday" (%A) part of the date. Same for {{{date(%A,%B%e,%Y)}}. So far I see (org-timestamp-format timestamp "%A, %B %e, %Y") works for a timestamp created by (org-element-timestamp-parser). I don't understand the macro code at all (e.g.. org-macro-replace-all). Versions are: Org mode version 9.1.1 (release_9.1.1-7-g226d2f @ /home/roklein/.emacs.d/org-mode/lisp/) GNU Emacs 25.3.1 (x86_64-unknown-openbsd, GTK+ Version 2.24.31) of 2017-09-26 Any help is greatly appreciated. Thank you very much. Best regards Robert
Re: [O] Beamer_act property is misnamed in org-mode Ubuntu package
On September 27, 2017 14:03:06 Eric S Fraga wrote: On Wednesday, 27 Sep 2017 at 11:53, James Harkins wrote: Hi, There seems to be a mistake in the org-mode Ubuntu 16.02 packages. For beamer, if I C-c C-x p to add a property, one of the predefined options is: :BEAMER_act(Act): 1 I think (could be wrong on this) that org includes any properties you already have as pre-defined options available to you. Maybe you have this property already in your file? No, I have never used this (incorrect) property. This occurs in a brand new org file too. Oh, just did a search: ox-beamer.el, line 81, defines columns for beamer properties, including the incantation "%10BEAMER_act(Act)" -- which, except for the %10, matches the behavior precisely. It appears that C-c C-x p is treating this as the true name of the property, when it's really something for display. Anyway, the string inserted by C-c C-x p just doesn't work. hjh Sent with AquaMail for Android http://www.aqua-mail.com
Re: [O] How to suppress latex exporting as a list if a name that begins with a single letter
On 09/27/2017 02:27, Michael Strey wrote: Hi Charlie, On Di, 2017-09-26 at 19:22, Charles Millar wrote: A. Persons Name is exported as 1. Persons Name not A. Persons Name. What about marking as verbatim? =A. Person= Best regards Michael Strey I will give this a try later on. For the moment, as Eric suggested, I have reset org-list-allow-alphabetical to nil. Thanks. Charlie Millar
Re: [O] How to suppress latex exporting as a list if a name that begins with a single letter
On 09/27/2017 02:00, Eric S Fraga wrote: On Tuesday, 26 Sep 2017 at 19:22, Charles Millar wrote: For example A. Persons Name is exported as 1. Persons Name You must have set org-list-allow-alphabetical to non-nil... maybe turn this off? You are correct. I did that s.. long ago I forgot. I read the documentation and I suppose that there is no way to set that variable on a per file basis. Correct? Could a header argument be implemented to override this? Charlie Millar
[O] Disable fontification when exporting tables
#+OPTIONS: latex:t toc:nil H:3 Hi, How can I disable fontifications when exporting this: | QueryID | SQL Text | Query Time (Seconds) | Query Time Hot (Seconds) | |-+-+--+--| | Q0 | SELECT avg(c1) from (select Year, Month, count(*) as c1 from ontime group by Year, Month); | 1.27 | 0.13 | | Q1 | SELECT DayOfWeek, count(*) AS c FROM ontime WHERE Year >= 2000 AND Year <= 2008 GROUP BY DayOfWeek ORDER BY c DESC; | 1.23 | 0.21 | regards, -- Amos Bird amosb...@gmail.com