Re: [O] Making an agenda that includes scheduled-for-later tasks?
Stig Brautaset writes:
> Does changing your "E" entry to this help at all?
>
> ,
> | ("E" "Effortless tasks"
> | todo '("TODO" "WAITING")
> | ((org-agenda-overriding-header "Effortless tasks")
> | (org-agenda-skip-function '(org-agenda-skip-entry-if 'regexp
> ":Effort:" 'todo '("APPT")))
> | (org-agenda-todo-ignore-scheduled nil)
> | (org-agenda-todo-ignore-deadlines nil)
> | (org-agenda-todo-ignore-timestamp nil)
> `
Thank you, it worked great! I wonder whether the documentation of
=org-agenda-custom-commands= could be expanded around the =settings=
parameter, so as to make it easier to find this solution by oneself? I
don't know myself the list of settings that could go there, though, so
couldn't really write it myself unfortunately :/
> By the way, the documentation for the `org-agenda-custom-commands'
> variable says that the third entry should be "a single keyword for TODO
> keyword searches", so the '("TODO" "WAITING") you have may be partly why
> things are not working how you expect? You may want to try a compound
> one like this:
> ,
> | ("E" "Effortless tasks"
> | ((todo "TODO")
> | (todo "WAITING"))
> | ((org-agenda-overriding-header "Effortless tasks")
> | (org-agenda-skip-function '(org-agenda-skip-entry-if 'regexp
> ":Effort:" 'todo '("APPT")))
> | (org-agenda-todo-ignore-scheduled nil)
> | (org-agenda-todo-ignore-deadlines nil)
> | (org-agenda-todo-ignore-timestamp nil)
> `
This works, however it splits the =TODO= and =WAITING= tasks in two
different sections in the display. I think Nick's solution is a bit
closer to what I tried to do here, as it mixes the two keywords in one.
Thank you!
Leo
Re: [O] Making an agenda that includes scheduled-for-later tasks?
Nick Dokos writes: >tags "TODO=\"TODO\"|TODO=\"WAITING\"" Thank you! This one worked great :)
Re: [O] Making an agenda that includes scheduled-for-later tasks?
Leo Gaspard writes:
> Hello all!
>
> Just trying to bump this question: How does one make an agenda view that
> includes tasks that are already scheduled for later?
>
> (more details in the quoted mail below)
>
> Cheers,
> Leo
>
> Leo Gaspard writes:
>
>> Hello all!
>>
>> I am trying to make an agenda view of all tasks that don't have the
>> :Effort: property set, including tasks that are scheduled for later.
>>
>> My init.el files includes the following lines (of interest is the "E"
>> agenda):
>> ```
>> (setq org-agenda-custom-commands
>> '(("U" "Unscheduled tasks"
>> todo '("TODO" "WAITING")
[General disclaimer: I can never remember what goes where in
org-agenda-custom-commands, and it's
all untested. Tread carefully.]
I don't think the "todo" type can do that. You might want to use the "tags"
type with a search
- see
(info "(org) Matching tags and properties")
It should be something like
tags "TODO=TODO|WAITING"
or maybe
tags "TODO=\"TODO|WAITING\""
or maybe
tags "TODO=\"TODO\"|TODO=\"WAITING\""
(or maybe something else :-) ).
>> ((org-agenda-overriding-header "Unscheduled tasks")
>>(org-agenda-skip-function '(org-agenda-skip-entry-if 'scheduled
>> ("E" "Effortless tasks"
>> todo '("TODO" "WAITING")
>> ((org-agenda-overriding-header "Effortless tasks")
>>(org-agenda-skip-function '(org-agenda-skip-entry-if 'regexp
>> ":Effort:" 'todo '("APPT")))
>> ```
>>
>> However, for some reason only tasks that are either not scheduled or
>> scheduled for some time in the past show up in this agenda. This makes
>> it useless, as the point is to remember to put in efforts for every
>> task *before* they are scheduled (and thus started)
>>
>> Do you have an idea what I could have missed?
Maybe (org-agenda-span 'month)?
>>
>> Thanking you in advance,
>> Leo
>>
>> PS: Also, I've noticed setting =todo '("TODO" "WAITING")= is apparently
>> not enough to get it to ignore the APPT-tagged items, so I've added the
>> filter to =org-agenda-skip-entry-if=. If you have an idea what I'm doing
>> wrong…
>
>
--
Nick
"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler
Re: [O] Making an agenda that includes scheduled-for-later tasks?
Leo Gaspard writes:
> Hello all!
>
> I am trying to make an agenda view of all tasks that don't have the
> :Effort: property set, including tasks that are scheduled for later.
>
> My init.el files includes the following lines (of interest is the "E"
> agenda):
> ```
> (setq org-agenda-custom-commands
> '(("U" "Unscheduled tasks"
>todo '("TODO" "WAITING")
>((org-agenda-overriding-header "Unscheduled tasks")
> (org-agenda-skip-function '(org-agenda-skip-entry-if 'scheduled
> ("E" "Effortless tasks"
>todo '("TODO" "WAITING")
>((org-agenda-overriding-header "Effortless tasks")
> (org-agenda-skip-function '(org-agenda-skip-entry-if 'regexp
> ":Effort:" 'todo '("APPT")))
> ```
>
> However, for some reason only tasks that are either not scheduled or
> scheduled for some time in the past show up in this agenda.
Does changing your "E" entry to this help at all?
,
| (setq org-agenda-custom-commands
| '(("U" "Unscheduled tasks"
|todo '("TODO" "WAITING")
|((org-agenda-overriding-header "Unscheduled tasks")
| (org-agenda-skip-function '(org-agenda-skip-entry-if 'scheduled
| ("E" "Effortless tasks"
|todo '("TODO" "WAITING")
|((org-agenda-overriding-header "Effortless tasks")
| (org-agenda-skip-function '(org-agenda-skip-entry-if 'regexp
":Effort:" 'todo '("APPT")))
| (org-agenda-todo-ignore-scheduled nil)
| (org-agenda-todo-ignore-deadlines nil)
| (org-agenda-todo-ignore-timestamp nil)
`
By the way, the documentation for the `org-agenda-custom-commands'
variable says that the third entry should be "a single keyword for TODO
keyword searches", so the '("TODO" "WAITING") you have may be partly why
things are not working how you expect? You may want to try a compound
one like this:
,
| (setq org-agenda-custom-commands
| '(("U" "Unscheduled tasks"
|todo '("TODO" "WAITING")
|((org-agenda-overriding-header "Unscheduled tasks")
| (org-agenda-skip-function '(org-agenda-skip-entry-if 'scheduled
| ("E" "Effortless tasks"
|((todo "TODO")
| (todo "WAITING"))
|((org-agenda-overriding-header "Effortless tasks")
| (org-agenda-skip-function '(org-agenda-skip-entry-if 'regexp
":Effort:" 'todo '("APPT")))
| (org-agenda-todo-ignore-scheduled nil)
| (org-agenda-todo-ignore-deadlines nil)
| (org-agenda-todo-ignore-timestamp nil)
`
Regards,
Stig
Re: [O] Making an agenda that includes scheduled-for-later tasks?
Hello all!
Just trying to bump this question: How does one make an agenda view that
includes tasks that are already scheduled for later?
(more details in the quoted mail below)
Cheers,
Leo
Leo Gaspard writes:
> Hello all!
>
> I am trying to make an agenda view of all tasks that don't have the
> :Effort: property set, including tasks that are scheduled for later.
>
> My init.el files includes the following lines (of interest is the "E"
> agenda):
> ```
> (setq org-agenda-custom-commands
> '(("U" "Unscheduled tasks"
>todo '("TODO" "WAITING")
>((org-agenda-overriding-header "Unscheduled tasks")
> (org-agenda-skip-function '(org-agenda-skip-entry-if 'scheduled
> ("E" "Effortless tasks"
>todo '("TODO" "WAITING")
>((org-agenda-overriding-header "Effortless tasks")
> (org-agenda-skip-function '(org-agenda-skip-entry-if 'regexp
> ":Effort:" 'todo '("APPT")))
> ```
>
> However, for some reason only tasks that are either not scheduled or
> scheduled for some time in the past show up in this agenda. This makes
> it useless, as the point is to remember to put in efforts for every
> task *before* they are scheduled (and thus started)
>
> Do you have an idea what I could have missed?
>
> Thanking you in advance,
> Leo
>
> PS: Also, I've noticed setting =todo '("TODO" "WAITING")= is apparently
> not enough to get it to ignore the APPT-tagged items, so I've added the
> filter to =org-agenda-skip-entry-if=. If you have an idea what I'm doing
> wrong…
Re: [O] org-tempo violating org-mode conventions since 9.2
Hello, Gabriele Lana writes: > following the conventions (https://orgmode.org/manual/Conventions.html) > "Keywords and blocks are written in uppercase to enhance their readability" > but since 9.2 all blocks inserted are lowercase, why? To make it clear, this convention is for the /manual/ only, not for Org syntax. Blocks are case insensitive. Regards, -- Nicolas Goaziou
Re: [O] org-tempo violating org-mode conventions since 9.2
On 2019-01-25 3:05 PM, Gabriele Lana wrote: > Hi, > > following the conventions (https://orgmode.org/manual/Conventions.html) > "Keywords and blocks are written in uppercase to enhance their readability" > but since 9.2 all blocks inserted are lowercase, why? > > Is there a clean way to put them back in uppercase? I mean alse the ~BEGIN~ > and ~END~ part of the blocks > Just to throw in my 2¢, I personally strongly prefer the less-obnoxious all-lowercase variant for all ‘#+’ keywords, though I do sometimes use uppercase for things like #+TITLE or #+AUTHOR every now and again. I think it would be nice to provide a defcusom to allow choosing between upper vs. lowercase. As of now, you should be able to get all uppercase by customizing the `org-tempo-keywords-alist' list and by redefining `org-tempo-add-block' (for the “begin” and “end” parts) in org-tempo.el. > > Thanks > > -- > Gabriele Lana > https://github.com/gabrielelana > https://twitter.com/gabrielelana Best, amin
[O] org-tempo violating org-mode conventions since 9.2
Hi, following the conventions (https://orgmode.org/manual/Conventions.html) "Keywords and blocks are written in uppercase to enhance their readability" but since 9.2 all blocks inserted are lowercase, why? Is there a clean way to put them back in uppercase? I mean alse the ~BEGIN~ and ~END~ part of the blocks Thanks -- Gabriele Lana https://github.com/gabrielelana https://twitter.com/gabrielelana
[O] [PATCH] Export overlay specification for beamer notes
Hi,
Sometime I find it useful to align Beamer notes with slide overlays, for
example, when stepping through a worked example (see attachment).
Beamer permits notes to have overlay specifications but presently these
are not exported by org.
--
Jamie Forth
>From 5faeaf613b3eb8f687ca2a2addfce974d588fafe Mon Sep 17 00:00:00 2001
From: Jamie Forth
Date: Mon, 21 Jan 2019 18:01:13 +
Subject: [PATCH] lisp/ox-beamer.el: Export overlay specification for notes
* ox-beamer.el (org-beamer-headline): Pass overlay specification to
beamer `\note{}' command.
This is useful for animating multiple slides within a single frame and
displaying only relevant note for each step.
TINYCHANGE
---
lisp/ox-beamer.el | 23 ---
1 file changed, 16 insertions(+), 7 deletions(-)
diff --git a/lisp/ox-beamer.el b/lisp/ox-beamer.el
index 05894ffab..7811dd6b5 100644
--- a/lisp/ox-beamer.el
+++ b/lisp/ox-beamer.el
@@ -645,13 +645,22 @@ as a communication channel."
contents))
;; Case 4: HEADLINE is a note.
((member environment '("note" "noteNH"))
- (format "\\note{%s}"
- (concat (and (equal environment "note")
- (concat
- (org-export-data
- (org-element-property :title headline) info)
- "\n"))
- (org-trim contents
+(concat "\\note"
+ ;; Overlay specification.
+ (let ((overlay (org-element-property :BEAMER_ACT headline)))
+ (when overlay
+ (org-beamer--normalize-argument
+ overlay
+ (if (string-match "\\`\\[.*\\]\\'" overlay)
+ 'defaction 'action
+ (format "{%s}"
+(concat (and (equal environment "note")
+ (concat
+ (org-export-data
+ (org-element-property :title headline)
+ info)
+ "\n"))
+(org-trim contents)
;; Case 5: HEADLINE is a frame.
((= level frame-level)
(org-beamer--format-frame headline contents info))
--
2.20.1
#+startup: beamer
#+beamer_theme: Singapore
#+beamer_header: \usepackage{pgfpages}
#+beamer_header: \setbeameroption{show notes on second screen=right}
#+options: toc:nil H:2
* Section 1
** Slide 1
*** Step 1:B_onlyenv:
:PROPERTIES:
:BEAMER_ACT: <+>
:BEAMER_env: onlyenv
:END:
Foo
- a
- b
Step 1 note :B_note:
:PROPERTIES:
:BEAMER_env: note
:BEAMER_ACT: <.>
:END:
- qux
*** Step 2:B_onlyenv:
:PROPERTIES:
:BEAMER_ACT: <+>
:BEAMER_env: onlyenv
:END:
Bar
- c
- d
Step 2 note :B_note:
:PROPERTIES:
:BEAMER_env: note
:BEAMER_ACT: <.>
:END:
- qux
# Local Variables:
# org-beamer-environments-extra: (("onlyenv" "O" "\\begin{onlyenv}%a" "\\end{onlyenv}"))
# End:
Re: [O] Table Columns
Hello, Scott Randby writes: > On 1/24/19 3:36 PM, Nicolas Goaziou wrote: >> Scott Randby writes: >> >>> I wonder this: Is there a way to tell Org to align and shrink all the >>> tables in an Org file after startup or does it have to be done on an >>> individual basis? >> >> It should be >> >>#+startup: align shrink > > This is what I had in my file originally, but when I opened the file, > there would be a lengthy delay before it actually opened. When > I removed the code from the file, it opened immediately. I don't know > what is going on. The code navigates to each table, align them, determine what columns should be shrunk, and actually shrink them. This is long if you have many tables. It is indeed better, in this case, to shrink them individually. Regards, -- Nicolas Goaziou
