all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Tim Hawes <trhawes@gmail.com>
Cc: 41364@debbugs.gnu.org
Subject: bug#41364: 27.0.91; org-self-insert-command does not work
Date: Sun, 17 May 2020 19:41:09 +0200	[thread overview]
Message-ID: <87zha6e9xm.fsf@gmail.com> (raw)
In-Reply-To: <87lflqdca8.fsf@gmail.com> (Tim Hawes's message of "Sun, 17 May 2020 07:35:43 -0400")

Tim Hawes <trhawes@gmail.com> writes:

> Start emacs with emacs -Q
> Start or open an org-mode document
> type <s and tab, nothing happens
> describe-key looks correct.

Does the following snippet from ORG-NEWS's "incompatible changes"
section[1] look relevant?

> *** Change in the structure template expansion
> 
> Org 9.2 comes with a new template expansion mechanism, combining
> ~org-insert-structure-template~ bound to ~C-c C-,~.
> 
> If you customized the ~org-structure-template-alist~ option manually,
> you probably need to update it, see the docstring for accepted values.
> 
> If you prefer using previous patterns, e.g. =<s=, you can activate
> them again by requiring Org Tempo library:
> 
> : (require 'org-tempo)
> 
> or add it to ~org-modules~.
> 
> If you need complex templates, look at the ~tempo-define-template~
> function or at solutions like Yasnippet.


[1] M-: (find-file (concat data-directory "ORG-NEWS"))
    (I'm sure there's an easier way to visit this file without popping
    up a web browser, I just can't seem to find it.)





  reply	other threads:[~2020-05-17 17:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-17 11:35 bug#41364: 27.0.91; org-self-insert-command does not work Tim Hawes
2020-05-17 17:41 ` Kévin Le Gouguec [this message]
2020-05-22 11:46   ` Bastien via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-05-22 11:46     ` Bastien via General discussions about Org-mode.

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zha6e9xm.fsf@gmail.com \
    --to=kevin.legouguec@gmail.com \
    --cc=41364@debbugs.gnu.org \
    --cc=trhawes@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.