From: Mark Barton <mbarton98@gmail.com>
To: Michael Maurer <maurer.michael@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: C-c . no longer inserts org-time-stamp (after upgrade to 9.5)
Date: Tue, 2 Nov 2021 09:39:26 -0700 [thread overview]
Message-ID: <64948F06-17B1-4E66-AA8F-F73044EE3940@gmail.com> (raw)
In-Reply-To: <CAH-0+bCfMbkLmXZ0wX0+38ToQDVq8GfZHhaMP6_ixf966KtRTg@mail.gmail.com>
It looks like follow-mode-prefix is a variable you can customize. It defaults to "C-c .” which is why the org-time-stamp does not run with "C-c .”
To see the follow-mode-map use "M-x describe-keymap follow-mode-map”
> On Nov 2, 2021, at 8:23 AM, Michael Maurer <maurer.michael@gmail.com> wrote:
>
> On Tue, 2 Nov 2021 at 09:41, Colin Baxter 😺 <m43cap@yandex.com> wrote:
>>
>>>>>>> Michael Maurer <maurer.michael@gmail.com> writes:
>>
>>> Subject line says it all, I upgraded to 9.5 two days ago and
>>> everything seemed to work, but today I fire up the PC and C-c . no
>>> longer is bound to anything. I guess I could custom-bind it in my
>>> config, but I'm more interested in why it's happening. The last
>>> package I installed after the upgrade was undo-fu and
>>> undo-fu-sessions, but I dont' think they are involved.
>>
>> They could be. I don't have those packages and C-c . works for me and I
>> am running the latest git pull from org-mode. You might also have
>> multiple org files present.
>>
>> Best wishes.
>
> I figured it out. It's follow-mode. As soon as you enable it in a
> buffer, C-c . stops working. I'm not sure if this incompatibility got
> introduced with 9.5, since it's been years since I last used
> follow-mode.
>
prev parent reply other threads:[~2021-11-02 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 8:18 C-c . no longer inserts org-time-stamp (after upgrade to 9.5) Michael Maurer
2021-11-02 8:36 ` Michael Maurer
2021-11-02 8:39 ` Michael Maurer
2021-11-02 8:41 ` Colin Baxter 😺
2021-11-02 15:23 ` Michael Maurer
2021-11-02 16:39 ` Mark Barton [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=64948F06-17B1-4E66-AA8F-F73044EE3940@gmail.com \
--to=mbarton98@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=maurer.michael@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).