From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: org-agenda-custom-commands have a serious bug!? Date: Thu, 9 Jun 2011 15:48:15 +0200 Message-ID: <64F5E327-C7BE-46DC-A226-F4EA158390CF@gmail.com> References: <201106091347207812494@163.com> <87r573dx75.fsf@mean.albasani.net> Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([140.186.70.92]:58426) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QUfb1-00034b-0s for emacs-orgmode@gnu.org; Thu, 09 Jun 2011 09:48:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QUfay-0000SH-B2 for emacs-orgmode@gnu.org; Thu, 09 Jun 2011 09:48:26 -0400 Received: from mail-ew0-f41.google.com ([209.85.215.41]:54191) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QUfax-0000Qo-CA for emacs-orgmode@gnu.org; Thu, 09 Jun 2011 09:48:24 -0400 Received: by ewy9 with SMTP id 9so642030ewy.0 for ; Thu, 09 Jun 2011 06:48:22 -0700 (PDT) In-Reply-To: <87r573dx75.fsf@mean.albasani.net> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Memnon Anon Cc: emacs-orgmode@gnu.org On 9.6.2011, at 14:15, Memnon Anon wrote: > "zw963" writes: > >> i have use org-agenda-custom-commands manage my thought and idea. when >> open my agenda custom view, I often require modified some heading >> content. when I use org-agenda-switch-to (shortcut key "enter") open >> and make changes, save and kill this buffer return to >> org-agenda-command window, move point to other heading, but it have a >> error tips."wrong type argument: stringp,nil" if i try to open other >> heading use "enter",I open a unpredictable org buffer. what a >> horrible..... This is to be expected. The agenda links back to the buffers using markers. Killing the buffers invalidates all the markers. So: don't kill the buffer! >> >> only I quit org-agenda-commands buffer, and reenter,i can work file. A cheaper way to fix this is to rebuild the agenda buffer with "g". - Carsten > > Ui, this sounds serious... > It would help tremendously if you could provide a minimal example > so that others can easily reproduce your setup and the problem. > > Memnon > >