From: Jean Louis <bugs@gnu.support>
To: Christopher Dimech <dimech@gmx.com>
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: Re: Inserting Schedule in Org-Mode requires calendar buffer
Date: Wed, 18 Nov 2020 02:32:41 +0300 [thread overview]
Message-ID: <X7RdmYv74oVzm5GJ@protected.rcdrun.com> (raw)
In-Reply-To: <trinity-85c3783f-f422-4a18-978d-dd0609bef09c-1605653937915@3c-app-mailcom-bs06>
* Christopher Dimech <dimech@gmx.com> [2020-11-18 01:59]:
SCHEDULED: <2020-11-18 Wed>
> > Sent: Tuesday, November 17, 2020 at 11:13 PM
> > From: "Jean Louis" <bugs@gnu.support>
> > To: "Christopher Dimech" <dimech@gmx.com>
> > Cc: "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
> > Subject: Re: Inserting Schedule in Org-Mode requires calendar buffer
> >
> > * Christopher Dimech <dimech@gmx.com> [2020-11-18 01:07]:
> > > > Sent: Tuesday, November 17, 2020 at 11:02 PM
> > > > From: "Jean Louis" <bugs@gnu.support>
> > > > To: "Christopher Dimech" <dimech@gmx.com>
> > > > Cc: "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
> > > > Subject: Re: Inserting Schedule in Org-Mode requires calendar buffer
> > > >
> > > > * Christopher Dimech <dimech@gmx.com> [2020-11-18 00:56]:
> > > > > When I want to insert a schedule in Org-Mode, I need to have the
> > > > > calendar buffer in emacs to work. Is there some customary way
> > > > > that people include in their init file for emacs.
> > > >
> > > > When inserting schedule item with C-c C-s the calendar buffer is
> > > > opening automatically. Do you see it opening automatically?
> > >
> > > The problem occurs when hitting 'C-c <'.
> >
> > On my side it just inserts in the buffer: <2020-11-18 Wed> but does
> > not ask me automatically for calendar to be chosen. The documentation says:
> >
> > ‘C-c <’ (‘org-date-from-calendar’)
> > Insert a timestamp corresponding to point date in the calendar.
>
> Suppose I load Emacs and hit 'C-c <'
>
> Emacs tells me "No buffer named *Calendar*"
Now I get it, I can also see that.
I can also observe when I first enter schedule with C-c C-s then
calendar buffer disappears and right after I could use C-c <
That means you need to open at least one time calendar as function C-c
< must somehow get where the cursor is in calendar buffer or where the
cursor was in calendar buffer.
Namely when I insert schedule with C-c C-s and insert date, the
calendar buffer is not killed or removed, it is still activated rather
buried that I do not see it. That is why the function C-c < works as
it looks into calendar buffer that is there but not visible in front
of me.
I do not think that is any bug.
Open calendar buffer and then invoke the function.
prev parent reply other threads:[~2020-11-17 23:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 21:54 Inserting Schedule in Org-Mode requires calendar buffer Christopher Dimech
2020-11-17 22:02 ` Jean Louis
2020-11-17 22:06 ` Christopher Dimech
2020-11-17 22:13 ` Jean Louis
2020-11-17 22:58 ` Christopher Dimech
2020-11-17 23:32 ` Jean Louis [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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=X7RdmYv74oVzm5GJ@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
/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.
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).