emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Charles Millar <millarc@verizon.net>
To: emacs-orgmode@gnu.org
Subject: Re: add blocks to org-structure-template-alist
Date: Fri, 27 Apr 2018 20:43:51 -0400	[thread overview]
Message-ID: <4a10e297-beee-13b6-06bd-9127fbbc5d7a@verizon.net> (raw)
In-Reply-To: <87muxop7pi.fsf@gnu.org>

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

Hi, again,

On 04/27/2018 07:09 PM, Bastien wrote:
> Hi Charles,
>
> Charles Millar <millarc@verizon.net> writes:
>
>> Is this correct of has the format changed?
> The format slightly changed, please check this option's docstring.
>
> Also see ORG-NEWS here, which I just updated:
>
> https://code.orgmode.org/bzg/org-mode/src/master/etc/ORG-NEWS#L65
>
> Let me know if you think this is informative enough for other
> users.
Prior to posting I did read the docstring for 
org-structure-template-alist in version 9.1.12 and I found nothing 
concerning "roll your own" templates. I have also read your org-news 
entry as well as the other replies.

It is not clear to me - is it possible to write my own, fairly simple 
template with a few modifications that are a result of some recent 
changes or, for example, are elements such as those in 
tempo-define-template now required?

Thanks.

Charlie Millar

[-- Attachment #2: Type: text/html, Size: 1593 bytes --]

  reply	other threads:[~2018-04-28  0:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-27 22:24 add blocks to org-structure-template-alist Charles Millar
2018-04-27 23:00 ` Nicolas Goaziou
2018-04-27 23:12   ` Bastien
2018-04-27 23:22     ` Nicolas Goaziou
2018-04-28  6:16       ` Bastien
2018-04-28  0:12     ` Eric Abrahamsen
2018-04-29 20:34     ` Rasmus
2018-04-27 23:09 ` Bastien
2018-04-28  0:43   ` Charles Millar [this message]
2018-04-28  6:22     ` Bastien
2018-04-28 13:02       ` Charles Millar

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=4a10e297-beee-13b6-06bd-9127fbbc5d7a@verizon.net \
    --to=millarc@verizon.net \
    --cc=emacs-orgmode@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.
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).