From mboxrd@z Thu Jan 1 00:00:00 1970 From: mega@retes.hu (=?utf-8?Q?G=C3=A1bor?= Melis) 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: Fri, 18 Feb 2011 15:46:15 +0100 Message-ID: <87sjvl9z9k.fsf@retes.hu> 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> <878vxdctma.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from [140.186.70.92] (port=41075 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PqRbC-0001HC-OT for emacs-orgmode@gnu.org; Fri, 18 Feb 2011 09:46:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PqRbB-0003mD-FG for emacs-orgmode@gnu.org; Fri, 18 Feb 2011 09:46:22 -0500 Received: from mail-bw0-f41.google.com ([209.85.214.41]:50322) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PqRbB-0003m2-Aa for emacs-orgmode@gnu.org; Fri, 18 Feb 2011 09:46:21 -0500 Received: by bwz16 with SMTP id 16so3698195bwz.0 for ; Fri, 18 Feb 2011 06:46:19 -0800 (PST) In-Reply-To: <878vxdctma.fsf@gnu.org> (Bastien's message of "Fri, 18 Feb 2011 15:19:57 +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: Bastien Cc: Julien Danjou , Org Mode List , Carsten Dominik Bastien writes: > Hi Carsten and all, > > 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've finally push a fix for this problem. > > The issue appeared when trying to redo a block agenda command, > where previous restrictions were not taking into account. > > I tested the fix on various agenda custom views, with the tests > provided by Michael (thanks!) and it looks fine. > > Please report any problem, this issue is pretty essential. > > Special thanks to Matt and Michael for their reports! I confirm that it's working as expected.