Hi,

Recently, but I cannot say for how long, I have found that dates
entered, for instance using "j" in the standard agenda view, no longer
choose a time/day in the future but seem to default to the current
year.  For instance, today, typing "j 2 feb RET" (with a real space
between 2 and feb) jumps me to 2010 February 2, not 2011.


#+begin_src emacs-lisp :results 
(describe-variable 'org-read-date-prefer-future)
#+end_src

#+results:
#+begin_example
org-read-date-prefer-future is a variable defined in `org.el'.
Its value is time

Documentation:
Non-nil means assume future for incomplete date input from user.
This affects the following situations:
1. The user gives a month but not a year.
For example, if it is April and you enter "feb 2", this will be read
as Feb 2, *next* year.  "May 5", however, will be this year.
2. The user gives a day, but no month.
For example, if today is the 15th, and you enter "3", Org-mode will
read this as the third of *next* month.  However, if you enter "17",
it will be considered as *this* month.

If you set this variable to the symbol `time', then also the following
will work:

3. If the user gives a time, but no day.  If the time is before now,
to will be interpreted as tomorrow.

Currently none of this works for ISO week specifications.

When this option is nil, the current day, month and year will always be
used as defaults.

You can customize this variable.
#+end_example

so according to the documentation should work as I expect but
doesn't...  Have I misunderstood something?

Thanks,
eric


#+begin_src emacs-lisp :results 
(format "%s\n%s\n" (org-version) (emacs-version))
#+end_src

#+results:
: Org-mode version 7.01trans (release_7.01h.645.g09015)
: GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0)
:  of 2010-08-14 on raven, modified by Debian