mirror of
https://git.savannah.gnu.org/git/emacs/org-mode.git
synced 2024-11-27 07:37:25 +00:00
acfcb14c82
Anupam Sengupta writes: > I routinely use time ranges (and occasionally time-stamp ranges) > in my org files to document the scheduled block of time for a > meeting or activity. As an example, I will mark meetings as: > > * A Meeting > <2009-03-12 Thu 10:00-11:00> > > As often happens with meetings, rescheduling needs to be done and > I use S-<up> or S-<down> on the time-stamp to make the > modifications. While this works fine, it usually leads to a > duplication when the *time* part of the time-stamp needs to be > changed. > > For the same example above, if the time-block has now changed to > 11:00-12:00, then I need to do S-<up> on both the "10:00" and the > "11:00" string. I.e, > > > * A Meeting > <2009-03-12 Thu 11:00-11:00> > ^ > +---------------- After the first S-<up> > > * A Meeting > <2009-03-12 Thu 11:00-12:00> > ^ > +---------------- After the second S-<up> > > Can we have a feature (with a toggle option perhaps) which would > *move* the block (i.e., both time entries) by the same amount > when either one is moved in the same direction. I.e., the > proposal is to have: > > * A Meeting > <2009-03-12 Thu 11:00-12:00> > ^ ^ > | | > | +---------- Automatically shifted > +---------------- After the S-<up> This is in fact how changing time works in many applications, and it does make sense here as well. The commits implements this change. It also implements a way to change the start time of an entry from the agenda. The date is normally changed with S-right/left. Now, if you add a C-u prefix, the hour will be changed. If you immediately press S-right/left again, hours will continue to be changed. A double prefix will do the same for minutes. |
||
|---|---|---|
| .. | ||
| .aspell.org.conf | ||
| .nosearch | ||
| ChangeLog | ||
| dir | ||
| Documentation_Standards.org | ||
| org.texi | ||
| orgcard.tex | ||
| orgcard.txt | ||
| texinfo.tex | ||