From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Re: [Accepted] Re: Bug: Jumping to a date in the agenda changes view back to 'day' [7.4 (release_7.4.80.g0e5e5)] Date: Thu, 17 Feb 2011 15:43:23 +0100 Message-ID: <87vd0i4t84.fsf@gnu.org> References: <20110201115210.6AD9A8783@myhost.localdomain> <87wrlfl1jx.fsf@fastmail.fm> <87sjvzaezr.fsf@keller.adm.naquadah.org> <871v3hjhac.fsf@gnu.org> <8AA3F93A-FFEC-4D8B-941C-22DBD8D05082@gmail.com> <87oc6kupqf.fsf@keller.adm.naquadah.org> <87y65ow14i.fsf@keller.adm.naquadah.org> <8739nwrm7m.fsf@gnu.org> <097F3E2B-6A1A-433D-B02C-218E26BA1440@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from [140.186.70.92] (port=38459 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Pq54j-00072v-61 for emacs-orgmode@gnu.org; Thu, 17 Feb 2011 09:43:22 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Pq54h-0002bE-QT for emacs-orgmode@gnu.org; Thu, 17 Feb 2011 09:43:21 -0500 Received: from mail-bw0-f41.google.com ([209.85.214.41]:55714) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Pq54h-0002b1-GU for emacs-orgmode@gnu.org; Thu, 17 Feb 2011 09:43:19 -0500 Received: by bwz16 with SMTP id 16so2620321bwz.0 for ; Thu, 17 Feb 2011 06:43:18 -0800 (PST) In-Reply-To: <097F3E2B-6A1A-433D-B02C-218E26BA1440@gmail.com> (Carsten Dominik's message of "Thu, 17 Feb 2011 14:57:23 +0100") 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: Carsten Dominik Cc: Julien Danjou , =?iso-8859-1?Q?G=E1bor?= Melis , Org Mode List Hi Carsten, Carsten Dominik writes: > For what it is worth, and for the record, I still do not > believe that this is the correct solution to the problem. > I believe it causes the issue reported in > > http://thread.gmane.org/gmane.emacs.orgmode/37673 > > But unfortunately I have not had time to study the issue > in more detail. I hope to do this before the next release. thanks for the heads up -- this is on top of my priority list, hopefully I'll fix this soon. Best, -- Bastien