emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tomas@tuxteam.de
To: Marco Wahl <marcowahlsoft@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Calendar vs. org-agenda exit
Date: Wed, 23 Jun 2021 17:28:36 +0200	[thread overview]
Message-ID: <20210623152836.GA18563@tuxteam.de> (raw)
In-Reply-To: <87k0mkwqzh.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1759 bytes --]

On Wed, Jun 23, 2021 at 05:16:50PM +0200, Marco Wahl wrote:
> Hi.
> 
> > is org mode rebinding keys in the calendar?
> 
> Yes.  "c" calls the Org agenda.
> 
> "i" in the calendar calls org-agenda-diary-entry when
> org-agenda-diary-file has been configured.  (See function
> org--setup-calendar-bindings.)

Thanks! This must be it, I'll have a look and report back.

> > I ask, because I've been using traditional calendar+diary; now,
> > when I try to insert an entry (i-d in calendar), I get
> >
> >   "Wrong type argument: commandp, org-agenda-diary-entry"
> 
> > The following experiment points in Org's general direction:
> >
> >   - emacs -Q
> >   - M-x calendar
> >   - with point on some date, i-d
> >   - diary buffer is open, with a new line primed with date
> >   - M-x load-library <RET> "org"
> >   - again, in calendar, i-d
> >   - the above error results.
> >
> > I'm not sure yet whether I fat-fingered something, so I'd like
> > some hints in investigating before declaring this to be a bug.
> 
> Thanks for providing a detailed path to the error.  But I can't
> reproduce this error; I get
> 
> - diary buffer is open, with a new line primed with date
> 
> instead of the error.

I must have mis-communicated. The above (i.e. diary buffer opens with
no error) happens after the -Q. Note that it is the non-org diary.

> Since you start with -Q and command org-agenda-diary-entry is a command
> in org-agenda this looks suspicious AFAICT.
> 
> Does the
> 
> - M-x load-library <RET> "org"
> 
> mix in some weird Org version and/or setting?  And btw why load Org a
> second time?

No, it is the first load of org. I'll look into org-agenda diary file,
as you suggest above.

Cheers
 - t

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2021-06-23 15:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22 10:39 org-edit-src-exit randomizes / mixes up code in source-buffer on exit mcg
2021-06-22 13:33 ` Sébastien Miquel
2021-06-22 14:57   ` mcg
2021-06-23  9:15 ` Calendar vs. org-agenda exit tomas
2021-06-23 15:16   ` Marco Wahl
2021-06-23 15:28     ` tomas [this message]
2021-06-23 16:16       ` [SOLVED] (kinda) " tomas
2021-06-24 10:13         ` Stephen Berman
2021-06-24 12:09           ` tomas
2021-06-24 12:44             ` Stephen Berman
2021-06-24 15:04               ` Nicolas Goaziou
2021-06-24 17:28                 ` tomas
2021-06-24 20:54               ` Tim Cross
2021-06-24 21:07                 ` tomas

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=20210623152836.GA18563@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=marcowahlsoft@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).