emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Garjola Dindi <garjola@garjola.net>
To: emacs-orgmode@gnu.org
Subject: Agenda buffer name after following a time stamp
Date: Sat, 24 Oct 2020 18:45:58 +0200	[thread overview]
Message-ID: <87tuuj4lo9.fsf@pc-117-162.ovh.com> (raw)


Accidentally pressing <enter> or <C-c C-o> on an inactive time stamp in
an org mode buffer, I found myself in an agenda buffer with name "*Org
Agenda(a:2020-10-22)" corresponding to the agenda of the date of the
time stamp.

I understand that this is the expected behaviour (jumping to that date),
but I am puzzled by the buffer name. Most annoyingly, from this moment,
unless I restart emacs, most new agenda generations will create a buffer
with the same name, that is "*Org Agenda(a:2020-10-22)" in my example
independently of the date for which the agenda is generated.

Steps to reproduce:

1. Press <C-c C-o> on [2020-10-22 Thu]. This generates the agenda for
   that date in a buffer named "*Org Agenda(a:2020-10-22)"
2. Close the agenda with "q" or "x"
3. invoke the org-agenda dispatcher, choose t (or any other view except
   "a"). This generates a buffer named "*Org Agenda(a:2020-10-22)"
   instead of "*Org Agenda*".

Using the interactive commands org-todo-list has the same behaviour.

However, using "a" in the agenda dispatcher or calling org-agenda-list
generates a buffer correctly called  "*Org Agenda*".

I have tried with "emacs -q" and the behaviour is the same.

Is this an expected behaviour? I have not been able to find the
information in the manual.

Thank you.


             reply	other threads:[~2020-10-24 16:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-24 16:45 Garjola Dindi [this message]
2020-11-09  6:10 ` Agenda buffer name after following a time stamp Kyle Meyer

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:

  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=87tuuj4lo9.fsf@pc-117-162.ovh.com \
    --to=garjola@garjola.net \
    --cc=emacs-orgmode@gnu.org \


* 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


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).