From: david@adboyd.com (J. David Boyd)
To: emacs-orgmode@gnu.org
Subject: Re: Bug in Agenda mode?
Date: Thu, 29 Apr 2010 12:52:08 -0400 [thread overview]
Message-ID: <e8r633a42x3.fsf@FLM000025LVE9F.catmktg.com> (raw)
In-Reply-To: 9FF66EA7-41C4-4292-9185-83164F4E9270@gmail.com
Carsten Dominik <carsten.dominik@gmail.com> writes:
> On Apr 29, 2010, at 4:51 PM, J. David Boyd wrote:
>
>>
>> If I do a C-a a, I see my weekly agenda, starting 'today'.
>>
>> Then I can hit 'd', and see today laid out better. Back to 'w',
>> and I
>> see the weekly agenda again.
>>
>> I can scroll down to tomorrow, hit 'd', and see tomorrow. But when I
>> hit 'w', I'm back to the week view, but now it starts on tomorrow, and
>> not today.
>>
>> And if I scroll down two days, and hit 'd', then 'w' to come back to
>> the
>> week view, I'm misplaced forward 2 days.
>>
>> Is this a bug, or 'just the way it works'. I'd never noticed before,
>> but I don't think I had actually tried that.
>
> looks like you have set org-agenda-start-on-weekday to nil. The is
> works like you describe. If you set it to a number, the week will
> always start on that day.
>
> The problem is that, if you are still in the current week, it might
> make sense to have the week start at today when you switch back to
> week view. But when you are further away from today, the week view
> must be constructed in a way that the day which was last shown in day
> view is also shown. Since you have opted to have your week view start
> at whatever weekday is today, Org assumes now that you want a week
> starting on the last shown day.
>
> Hmmmm.
>
> I am not sure what would be best here.
>
> - Carsten
>
I can live with that. I only set the agenda to start from the current
day because I didn't really care about seeing days that had already gone
by.
I think what surprised me the most was that, once I went to a specific
day, and then back to week mode, and I started on a different day, was
that I couldn't reset it to what it had previously been without exiting
the agenda and starting over.
I don't consider it a problem, just 'the way it is'. Now that I know
that is how it works, I can deal with it.
No, sorry, that's not saying it correctly. I have no problems
what-so-ever with how it works, I just didn't understand it.
Thanks for a great program!
Dave in Largo, FL
next prev parent reply other threads:[~2010-04-29 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 14:51 Bug in Agenda mode? J. David Boyd
2010-04-29 15:33 ` Carsten Dominik
2010-04-29 16:52 ` J. David Boyd [this message]
2010-04-29 18:39 ` Bernt Hansen
2010-04-29 19:05 ` J. David Boyd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e8r633a42x3.fsf@FLM000025LVE9F.catmktg.com \
--to=david@adboyd.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.