DST and appointments in other timezones
Hello world, I have appointments that are scheduled on timezones other than my computer's. Does org-mode support setting that? It looks like timestamps don't support adding a timezone, so I'm wondering whether there's a reasonable way to use s-expressions in timestamps for this? Well, ideally org-mode could be adapted to support timestamps in arbitrary timezones, but I guess there are reasons why that's not supported? Cheers, and huge thanks to all the devs and people who answer questions like these! Leo
org-capture fails to insert link even on :immediate-finish templates
Hello, I have an org-capture template with :immediate-finish t. In notmuch-mode, it looks like org-capture support is not implemented yet for the search interfaces, and so when capturing on these interfaces (without noticing), I get a capture without the link. Is it possible to make org-capture fail loudly when capturing a =:immediate-finish t= template for which all the substitutions didn't succeed, instead of just having empty strings at the substitution locations? Thank you! Leo
Re: [O] org-clock: Custom shortcuts for C-u C-c C-x C-i
Hi Michaël, Michaël Cadilhac writes: > This is not possible out of the box; can you say a bit more about how > you expect to indicate which tasks are to be always present? I would be thinking of something like defining a list of key -> link to a task (that may be generated with org-id's task ID, [[*foobar]] links or whatever) in my `init.el`. > A quick-and-dirty way to implement something along these lines is to > modify org-clock-history-push to always keep a selected set of markers > in org-clock-history. Hmm… That sounds like it'd work, but would have a pretty terrible UX. I guess I'll go with just using custom shortcuts for now, then, if there's no easy way to integrate it with C-ucxi. (I don't feel like I'm ready to dive into too intricate elisp yet) Thank you for your feedback! Cheers, Leo
[O] org-clock: Custom shortcuts for C-u C-c C-x C-i
Hello, When I run C-u C-c C-x C-i I get a choice between the interrupted task, the current task, the default task and recent tasks. I however wonder whether it's possible to add in custom shortcuts to fixed tasks? This would help me easily clock into my “IRC”, “Mails” etc. tasks, to and from which I frequently switch. Do you have any idea how to accomplish that? I haven't been able to find anything in the manual [1]. [1] https://orgmode.org/org.html#Clocking-commands Cheers, and thank you once again for this great piece of software! Leo
Re: [O] Closing a task yesterday (or changing the day cutoff to 4am)
Uwe Koloska writes: > Maybe the variable 'org-extend-today-until' can help. Indeed, thank you!
Re: [O] Closing a task yesterday (or changing the day cutoff to 4am)
Marcin Borkowski writes: > You do realize you are not the first one to have that problem, don't > you? Have you seen `org-agenda-todo-yesterday'? Thank you! Sounds like it'll combo nicely with `org-extend-today-until` pointed out by Uwe, to slowly make checking tasks the day before less and less convenient and push the sleep schedule the right way. >> Anyway, thank you for org-mode, that allows me to be mildly annoyed at >> things I wouldn't even have considered might become an issue someday >> with programs I used before! > > Not sure whether this is a compliment, but I like it:-). It's definitely meant to be! :)
[O] Closing a task yesterday (or changing the day cutoff to 4am)
Hello! I have a few tasks marked as `:STYLE: habit`. And I relatively often finish one of those daily habits after midnight. Yet, I'd like to count it as having been finished the day before, so that day switch time happens while I sleep. I do understand that the best fix to this problem would be to fix my sleep schedule and to go to sleep before midnight, but, assuming I can't fix this up, do you know if there is a workaround to either: * Make org-mode consider the day to switch at something like 4am * Automatically close a task as though it was the day before, 23:59 Currently my workaround is to close the task then manually fixup the `SCHEDULED`, `:LAST_REPEAT:` and `:LOGBOOK:` lines to set them to the day before, 23:59, but it's being… quite painful. Anyway, thank you for org-mode, that allows me to be mildly annoyed at things I wouldn't even have considered might become an issue someday with programs I used before! Cheers, Leo
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?
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…
[O] Making an agenda that includes scheduled-for-later tasks?
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] “Fuzzy” times (“evening”, “morning”, “night”…)
Hi Richard, Richard Lawrence writes: > What about just adding a tag (:evening:, :morning:, etc.) to represent a > fuzzy time, with a plain date stamp, like <2018-12-04>? > > That would allow you to easily create a custom agenda view containing > just entries with fuzzy times (if they have a timestamp with just a > date, you can even filter for those that are coming up in the next > couple of days). Then when it's convenient, you can look at this agenda > view and schedule things that are still fuzzy more precisely. This sounds like a good idea, thanks! Especially combined with Ken Mankoff's, so that the event still is shown in the overall agenda at an approximately correct hour so I don't schedule two things at the same (fuzzy) time :) With your two ideas it should make a quite good workaround, thank you! Cheers, Leo
Re: [O] “Fuzzy” times (“evening”, “morning”, “night”…)
Ken Mankoff writes: > On 2018-12-08 at 09:47 -0800, Leo Gaspard wrote: >> However, I think it may be a good idea to allow eg. this kind of >> timestamps: >> <2018-02-04 Tue evening> That would be handled as though it >> was eg. <2018-02-04 Tue 18:00-22:00> (which would be configurable), so >> that it would be both semantically correct (the time is still fuzzy) >> and correctly displayed (eg. on an agenda) >> [...] >> What do you think about this idea? Is there a better way to do what >> I'm trying to do with current tools? > > > I think this would be a neat feature. But as a first pass which can work > immediately, what about using one of the multiple text expansion packages > that are Org-agnostic to achieve this: Yasnippets or abbrev mode, for example? > > This doesn't maintain the "semantics (time still fuzzy)", but does let you > define and enter time ranges in a simpler way. Hmm… I guess some abbreviation or command could add the fuzzy time and add a comment to indicate that the time is fuzzy should work as a temporary workaround indeed, thank you for the idea :)
[O] “Fuzzy” times (“evening”, “morning”, “night”…)
Hello, In the process of migrating all my self-organization to org-mode, I noticed there is something that cannot currently be encoded in timestamps: fuzzy times, where an appointment is made for “Dec 4, Tue, evening” but with the hours not yet fixed. Currently my way of handling this has been to mark the tasks with time spans approx. correct and add a comment to fix them. However, I think it may be a good idea to allow eg. this kind of timestamps: <2018-02-04 Tue evening> That would be handled as though it was eg. <2018-02-04 Tue 18:00-22:00> (which would be configurable), so that it would be both semantically correct (the time is still fuzzy) and correctly displayed (eg. on an agenda) To be perfectly honest, my ulterior motive here is to auto-generate tasks “Decide of an exact time for [task]” a few days before the timestamp. However, I haven't investigated yet whether that'd actually be doable and I'm still pretty new to the lisp/emacs/org-mode ecosystems, so this may be completely impossible. What do you think about this idea? Is there a better way to do what I'm trying to do with current tools? Cheers, Leo
Re: [O] Setting timestamp from end time and an interval
Does anyone else find interest in this, or am I the only one having this want? Does anyone have a better idea of syntax to do this “negative interval”? `11am+-00:30` looks kind of weird, but `-` is already taken. Also, I often find myself inputting minutes in those intervals. Do you think a syntax like `11am+15'` would make sense, instead of `11am+00:15`, which is less nice to type? Cheers, Leo Leo Gaspard writes: > Hello, > > I find myself often working intervals “backwards”, eg. when planning > transportation: I need to be there at XX:YY, thus need to depart 35min > before. > > Org-mode has this great feature that when typing `11:12+00:35` it > automatically computes the interval 11:12-11:47. > > What I'm wondering is, whether there'd be interest in having > eg. `11:47+-00:35`, that'd create the same interval but from an *end* > time and interval duration. > > What do you think about this? Is there already a way of doing this I > don't know of? > > Cheers, > Leo
[O] Setting timestamp from end time and an interval
Hello, I find myself often working intervals “backwards”, eg. when planning transportation: I need to be there at XX:YY, thus need to depart 35min before. Org-mode has this great feature that when typing `11:12+00:35` it automatically computes the interval 11:12-11:47. What I'm wondering is, whether there'd be interest in having eg. `11:47+-00:35`, that'd create the same interval but from an *end* time and interval duration. What do you think about this? Is there already a way of doing this I don't know of? Cheers, Leo
Re: [O] [feature] Handle recurrence in <> and [] dates
Nicolas Goaziou writes: > Org didn't handle repeaters in inactive time stamps. This is now fixed > (in master). Thank you. Great, thank you!
Re: [O] Tasks performed on a certain day
Ken Mankoff writes: > What about passive date stamps? > > TODO Thing > > > ? That's exactly what I was looking for! I hadn't seen an example with TODO coupled with <> dates, and didn't think it'd have a special behavior. Thank you and Marcin for this solution! Cheers, Leo
Re: [O] Tasks performed on a certain day
Eric S Fraga writes: > On Tuesday, 6 Nov 2018 at 22:59, Leo Gaspard wrote: >> It is a task, so I want to be able to mark it as done and not see it for >> the rest of the day. But at the same time I can't SCHEDULE <> it, >> because otherwise if I don't do it the right day then it still bothers >> me the day after, at which I can't do it any longer any way. > > what if you add a, for instance, MISSED task indicator, equivalent to > DONE so that you can record that you didn't do the task and then move > on to the next scheduled time? I was hoping for something that would automatically mark the task as missed (well, I don't care about the task being marked as missed actually, just about it no longer appearing on my agenda), but I guess if it's not possible then this can do. Thank you :)
Re: [O] [feature] Handle recurrence in <> and [] dates
Hi Julius, Julius Dittmar writes: > if you want a task to re-open at a later date upon closing, add a line of > :REPEAT_TO_STATE: TODO > to the PROPERTIES drawer of that task. Well, I guess I stated my problem poorly, sorry :) Here is a translated example task from my .org file: *** TODO Check bank report SCHEDULED: <2000-02-10 Thu +1m> Dated [2000-01-01 Sat +1m] The point of this “Dated” field being to tell me to which report I should be looking, given I sometimes am a month late or so in checking my reports, and just put them in the (physical) drawer as I receive them. This “Dated” field is exactly what I would like to see updated when I mark the task as done (like the SCHEDULED date), but it looks like it doesn't move. Is there a trick to do this? Cheers, Leo
[O] Tasks performed on a certain day
Hello world, I am trying to figure out a way to represent, in org-mode, tasks that should be performed exactly on one day of the week. For instance, taking out the garbage. It is a task, so I want to be able to mark it as done and not see it for the rest of the day. But at the same time I can't SCHEDULE <> it, because otherwise if I don't do it the right day then it still bothers me the day after, at which I can't do it any longer any way. Does anyone have a trick to handle this kind of “on-this-date task” with org-mode? Cheers, Leo
Re: [O] [feature] Handle recurrence in <> and [] dates
Hello all! It's been ~2 weeks so I hope you'll forgive me bumping my post :) Do you have an opinion about this idea? Cheers, Leo Leo Gaspard writes: > Hello all! > > I have been using org-mode for a few days (switching over from > todo.txt [1]), and for the time being my experience has been great! > > There is a single thing I found weird up to now: it seems that > recurrence tags in <> and [] “tags” don't get bumped when a task is > completed and has a recurrence set in its SCHEDULED or DEADLINE date. > > The reason I'd like this is because I have monthly bank statements, > which come in the next month, and I'd like to store the bank statement's > date in a [] “tag” so that I can easily know which statement I'm > supposed to handle, even though this date is neither a SCHEDULED (as I > don't have the statement yet at the date it's produced) nor a DEADLINE > (for the same reason). > > What do you think about this? > > Anyway, thanks a lot for the great work! > > Cheers, > Leo > > > [1] http://todotxt.org/
Re: [O] Full-width characters break column display
Nicolas Goaziou writes: > The problem is that > > (string-width "何か") > > equals > > (string-width "") > > i.e, 4 characters, but both strings do not have the same length > visually. > > As long as the two sexps above disagree, it seems difficult to support > this. Oh. OK, so now I feel stupid: I was convinced full-width chars were twice the width of half-width chars… and it turns out the names are treacherous, and they are actually not. I guess this is a font / display issue then, and not an org-mode issue. Sorry for having bothered you and thank you! Leo
Re: [O] Full-width characters break column display
Nicolas Goaziou writes: >> Small issue I've been having with org-mode: full-width characters >> (eg. 何か) appear to be breaking column display. > > Org tables assume a fixed-width font. You need to use one, if such > thing exists for these characters. Well, it is fixed-width, but twice the width of spaces and vertical characters. Using it with regular English ｍａｋｅｓ ｉｔ ｌｏｏｋ ｌｉｋｅ ｔｈ ｉｓ, which I guess you'll grant me is not really usable :) I wonder if it'd be possible to support full-width chars for CJK script?
[O] Full-width characters break column display
Hello, Small issue I've been having with org-mode: full-width characters (eg. 何か) appear to be breaking column display. Does anyone know of a workaround for this? Cheers, and thank you for making org-mode as great as I'm currently discovering it is! Leo
[O] [feature] Handle recurrence in <> and [] dates
Hello all! I have been using org-mode for a few days (switching over from todo.txt [1]), and for the time being my experience has been great! There is a single thing I found weird up to now: it seems that recurrence tags in <> and [] “tags” don't get bumped when a task is completed and has a recurrence set in its SCHEDULED or DEADLINE date. The reason I'd like this is because I have monthly bank statements, which come in the next month, and I'd like to store the bank statement's date in a [] “tag” so that I can easily know which statement I'm supposed to handle, even though this date is neither a SCHEDULED (as I don't have the statement yet at the date it's produced) nor a DEADLINE (for the same reason). What do you think about this? Anyway, thanks a lot for the great work! Cheers, Leo [1] http://todotxt.org/
