From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: Bug: Jumping to a date in the agenda changes view back to 'day' [7.4 (release_7.4.80.g0e5e5)] Date: Tue, 18 Jan 2011 10:43:23 +0100 Message-ID: <320B5333-BD2A-40B2-8FE7-972BFC72C32F@gmail.com> References: <87ei9a30tx.fsf@norang.ca> <87k4j2e1bb.fsf@noorul.maa.corp.collab.net> <87y67i0z5c.fsf@norang.ca> <87zkr3h3qv.fsf@norang.ca> <257A79BB-86AC-43E5-AE9D-132168283FFB@gmail.com> <87k4i7gz5a.fsf@norang.ca> <8739ord2r4.fsf@norang.ca> <97009C4F-F6B7-4C54-BF3C-B3DE5EF15547@gmail.com> <10856187-1F13-4E34-90AE-B25B2C6EFC83@gmail.com> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from [140.186.70.92] (port=58551 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Pf864-0001Us-1c for emacs-orgmode@gnu.org; Tue, 18 Jan 2011 04:43:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Pf863-0005At-1P for emacs-orgmode@gnu.org; Tue, 18 Jan 2011 04:43:27 -0500 Received: from mail-fx0-f41.google.com ([209.85.161.41]:48557) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Pf862-0005Aj-S5 for emacs-orgmode@gnu.org; Tue, 18 Jan 2011 04:43:26 -0500 Received: by fxm12 with SMTP id 12so6909102fxm.0 for ; Tue, 18 Jan 2011 01:43:25 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Julien Danjou Cc: Bernt Hansen , Org Mode , Noorul Islam K M On Jan 17, 2011, at 5:46 PM, Julien Danjou wrote: > On Mon, Jan 17 2011, Carsten Dominik wrote: > >> This should not be done with a key, but automatically in a clever >> way. It >> used to work. > > Well, it used to work very bad, that's why I rewrote that thing > initially. It was resetting too often to the default without any > reason. I am not sure if I understand this part of the issue. The old code was certainly bad in the sense that it changed custom variables. However, it generally did not reset to a default value (in fact, the default value was lost due to the explicit changes org org-agenda- ndays). Otherwise, if would continue to use whatever value you set with your latest view change and keep this until you change it again. So what was your issue with this part? > So agenda-ndays you define the "clever way" to me? :-) I guess I misformulated here. In fact, the current code does behave cleverly already. You implementation does in fact switch back to the default number of days whenever I issue a new agenda command. For example if I set org-agenda-span to 3,` C-c a a' gives me three days. Then I use a custom command which does the agenda with 2 days, and that sticks through `f' and `b' and `g' commands, as it should. But when I do `C-c a a' again, I get back to the default span of 3 days. I like that. So there you have your command to go back to the default span. If you think we do need an extra command for this, you could do that under the "v" dispatcher in the agenda. Maybe "v SPACE"? - Carsten