emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Memnon Anon <gegendosenfleisch@googlemail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-agenda-custom-commands  have a serious bug!?
Date: Thu, 9 Jun 2011 15:48:15 +0200	[thread overview]
Message-ID: <64F5E327-C7BE-46DC-A226-F4EA158390CF@gmail.com> (raw)
In-Reply-To: <87r573dx75.fsf@mean.albasani.net>


On 9.6.2011, at 14:15, Memnon Anon wrote:

> "zw963" <zw963@163.com> 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
> 
> 

  reply	other threads:[~2011-06-09 13:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09  5:47 zw963
2011-06-09 12:15 ` Memnon Anon
2011-06-09 13:48   ` Carsten Dominik [this message]
2011-06-09 14:18 ` Nick Dokos
2011-06-11  5:54   ` zw963
2011-06-11  8:48   ` Bug: org-agenda-custom-commands bugs [7.5] zw963
2011-06-30 16:05     ` Bastien

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=64F5E327-C7BE-46DC-A226-F4EA158390CF@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=gegendosenfleisch@googlemail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).