emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: "Sławomir Grochowski" <slawomir.grochowski@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] `org-agenda-write' (error "No buffer named *Org Agenda*")
Date: Sun, 28 Jul 2024 18:54:29 +0000	[thread overview]
Message-ID: <875xspmjoa.fsf@localhost> (raw)
In-Reply-To: <87ed7dwygq.fsf@gmail.com>

Sławomir Grochowski <slawomir.grochowski@gmail.com> writes:

> I am encountering an error when running the `org-agenda-write' command on
> any 'Agenda Views'. The error message is:
> (error "No buffer named *Org Agenda*"). 
>
> Despite this error, the file is created successfully. The part of the
> code from `org-agenda-write' that triggers this error is:
>
> (set-buffer (or agenda-bufname
> 		    ;; FIXME: I'm pretty sure called-interactively-p
>                     ;; doesn't do what we want here!
> 		    (and (called-interactively-p 'any) (buffer-name))
> 		    org-agenda-buffer-name))
>
> I commented out this code, and everything seems to work fine. However, I
> am unsure of the purpose of this code and whether commenting it out is
> the right solution.

I agree that the code you commented is redundant and also harmful when
used with sticky agendas (despite multiple previous attempted fixes).
Fixed, on main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=433fbdbc63

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


      reply	other threads:[~2024-07-28 18:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-28 11:24 [BUG] `org-agenda-write' (error "No buffer named *Org Agenda*") Sławomir Grochowski
2024-07-28 18:54 ` Ihor Radchenko [this message]

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=875xspmjoa.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=slawomir.grochowski@gmail.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).