[O] How do you use `pre-scheduled' deadline skipping with repeaters?
I really like to use `pre-scheduled' as the value of `org-agenda-skip-deadline-prewarning-if-scheduled'. Quoting the manual, "this can be used in a workflow where the first showing of the deadline will trigger you to schedule it, and then you don't want to be reminded of it because you will take care of it on the day when scheduled." I started applying this to tasks with repeating deadlines. So, for instance, I have the following in my agenda right now: ** REPEAT oil change :drive: SCHEDULED: <2014-12-23 Tue 09:00> DEADLINE: <2014-12-31 Wed .+6m> When I mark this done, the deadline repeater updates as I expect. But the scheduling information stays there and I have to manually unschedule the task to get it out of my agenda. I started looking into writing a function to unschedule after a repeat, but I'm having difficulty figuring out where to hook into `org-todo'. Or do I want to hook into `org-auto-repeat-maybe'? So, yeah. Do others use this `pre-scheduled' workflow for repeating deadlines? If so, is there an obvious solution to this little nuisance that I'm not seeing? -- Trevor Murphy, ASA, MAAA GnuPG Key: 0x83881C0A
[O] sql can't export an empty table, gives error
If you try to export this document: #+BEGIN_SRC sql :exports both select 1 limit 0; #+END_SRC It fails to export with an error in *Messages*: user-error: Empty table - created default table It also stops processing the document at that point. (That SQL code produces no output but is not a SQL error.) I'd prefer if it would just leave that empty (missing) table out, and keep going. Is there any way to do that? -- Gary
Re: [O] How to prevent [] is interpreted as footnote in table?
Enzo Chi writes:
> How to prevent [] is interpreted as footnote in table?
I think [N] is hardcoded as footnote-reference cf. org-footnote-re. You
example doesn't even work when footnotes are turned off.
#+OPTIONS: f:nil
| d[1] |
If you think this is an issue you could open a bug report.
You could use snippets, but it's a bit inconvenient:
| d@@latex:[1]@@ |
You could make macro that inserts a snippet for whichever backend is the
current one
#+MACRO: num (eval (format "@@%s:[%d]@@" org-export-current-backend $1))
| d{{{num(1)}}} |
(Only tested with latex).
Hope it helps,
Rasmus
--
Sådan en god dansk lagereddike kan man slet ikke bruge mere
Re: [O] SCHEDULED in a comment line is not ignored by sparse-tree
Hello, James Harkins writes: > This appears to be buggy behavior, but I'm asking here first in case it might > already have been fixed. > > A couple of months ago, I was trying to create a repeating timestamp for two > different days of the week. First I tried a diary-sexp, but that wasn't > compatible with habits, so I gave that up. But I didn't want to throw away > the string completely, because it took some digging to figure it out. So I > put "# " at the beginning of the SCHEDULED line and thought that would be the > end of it. (In the source block, "#" has two spaces before it. These come > from C-c ' editing. In my original file, the "#" for the comment is flush > left.) > > #+BEGIN_SRC org > ,** TODO Update lesson grades 2 > :Comp: > SCHEDULED: <2014-12-06 Sat 23:59 .+1w> > :PROPERTIES: > :STYLE:habit > :LOGGING: TODO MAYBE INPROG MTG | DONE(!) POSTPONED CANCELED > :END: > # SCHEDULED: <%%(memq (calendar-day-of-week date) '(3 6))> > #+END_SRC > > Just now, I tried to open a sparse-tree view with a scheduled date range -- > C-c / c c D (set range) -- and got the message: > > byte-code: Bad timestamp `%%(memq (calendar-day-of-week date) '(3 6))' > Error was: (Not a standard Org-mode time string: %%(memq > (calendar-day-of-week date) '(3 6))) This should be fixed. Thank you for reporting it. Regards, -- Nicolas Goaziou
Re: [O] How to make appear the "note taken" in the calendar?
Rasmus wrote: > jenia.iv...@gmail.com (jenia.ivlev) writes: > >> How do I make appear the "note taken" in the agenda? >> Like for example, if in a org-file, I press C-c C-z under a node, this >> command will create a new note for that node. How do I make such notes >> appear in the calendar? > > Do you use both the Emacs calendar and the Org-Agenda? > >> In contrast, "state changes" of an org-node, like going from TODO to >> DONE, appears in the calendar if you press "C-u l". >> >> So again, how do you make appear, in the calendar, the notes-taken in an >> org file? > > I'm probably misunderstanding, but how about just adding a time stamp on a > note in one of your agenda files? E.g.: > > ** My Trip Home > <2014-12-24 07:12-14:55> I think the OP wants to see a more granular view of notes taken during clocking for example. --8<---cut here---start->8--- ** Meeting with Bob :LOGBOOK: CLOCK: [2011-08-11 Thu 09:42]--[2011-08-11 Thu 10:00] => 0:18 - Prepare my slides. CLOCK: [2011-08-11 Thu 10:02]--[2011-08-11 Thu 18:09] => 8:07 - Go on site, and deliver my presentation. :END: --8<---cut here---end--->8--- That is (or was) possible with the "org-timeline" view -- which is soon to be obsoleted? Best regards, Seb -- Sebastien Vauban
[O] How to prevent [] is interpreted as footnote in table?
How to prevent [] is interpreted as footnote in table? In table, something like "d[4]" would be interpreted as footnote. Tried to use "=d[4]=", it will be exported with different font to other cells in the table.
Re: [O] iswitchb is deprecated
Hi Stephen, Thanks for your comment. Stephen Eglen writes: > Since Emacs 24.4, iswitchb is marked as obsolete: > > -- > This function is obsolete since 24.4; > use `icomplete-mode' or `ido-mode' instead. > -- > > Do people use `org-iswitchb' much? If so, it might be time to get it to > default to ido or icomplete. First, there's already the variable org-completion-use-ido which also affects org-switchb. Second, I don't know if there's a point in /removing/ the support for org-completion-use-iswitchb. E.g. Debian still has an old version of Emacs. What you could do is make ido the default backend, especially if icomplete-mode is obsolete. E.g. in org-switchb you would edit this statement to default to ido, preferably only if icomplete is obsolete: (unless (or org-completion-use-ido org-completion-use-iswitchb) (setq org-completion-use-iswitchb t)) You could also update the docstring of `org-completion-use-iswitchb'. See http://orgmode.org/worg/org-contribute.html for the details. Cheers, Rasmus -- However beautiful the theory, you should occasionally look at the evidence
Re: [O] How to make appear the "note taken" in the calendar?
Hi, jenia.iv...@gmail.com (jenia.ivlev) writes: > How do I make appear the "note taken" in the agenda? > Like for example, if in a org-file, I press C-c C-z under a node, this > command will create a new note for that node. How do I make such notes > appear in the calendar? Do you use both the Emacs calendar and the Org-Agenda? > In contrast, "state changes" of an org-node, like going from TODO to > DONE, appears in the calendar if you press "C-u l". > > So again, how do you make appear, in the calendar, the notes-taken in an > org file? I'm probably misunderstanding, but how about just adding a time stamp on a note in one of your agenda files? E.g.: ** My Trip Home <2014-12-24 07:12-14:55> Hope it helps, Rasmus -- If you can mix business and politics wonderful things can happen!
Re: [O] Fwd: demoting a heading inserts spaces in column-0 text
Hello, Sebastien Vauban writes: > Regarding CLOCK lines, I guess we all agree it's not user-input, but > data managed by Org, right? Right. But the problem, which I explained already, is different here. > - user-inputted text > - Org-managed stuff (such as clock line, timestamps or property drawers) > > Note that I wrote timestamps instead of planning info because I also > would find it clearer to get: > >>> Some text >>> [2014-12-14 Sun 18:55] > > than > >>> Some text >>> [2014-12-14 Sun 18:55] > > (when one wants to insert the timestamp in a captured note or task) This is not possible in the general case since timestamps can be located almost anywhere. I suggest to live with it. >> Again, I suggest to sync indentation of planning info and all adjacent >> drawers. Nothing smarter. > > Including the LOGBOOK, then? That would already fulfill several above > cases IIUC As long as LOGBOOK is located at the top of the section, right after planning info or some drawers, it should be fine. If it is located elsewhere, it will not be indented automatically. > not the timestamp one, though. See above. Regards, -- Nicolas Goaziou
[O] iswitchb is deprecated
Since Emacs 24.4, iswitchb is marked as obsolete: -- This function is obsolete since 24.4; use `icomplete-mode' or `ido-mode' instead. -- Do people use `org-iswitchb' much? If so, it might be time to get it to default to ido or icomplete. Stephen
