emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Austin Frank <austin.frank@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: another (different) template request
Date: Sat, 20 Jan 2007 01:08:10 +0100	[thread overview]
Message-ID: <87bqksc5e4.fsf@tallis.ens.fr> (raw)
In-Reply-To: <m03b67ok37.fsf@gmail.com> (Austin Frank's message of "Thu\, 18 Jan 2007 20\:56\:28 -0500")

Austin Frank <austin.frank@gmail.com> writes:

> I haven't yet investigated the templating options mentioned here
> (though dmacro sounds like it's got potential).  Still, I wonder if a)
> the feature already exists, or b) other people would be interested in
> seeing it included in a future version of Org.

I think templates are too much based on the way one works.  I can't
imagine one template turning out to be the default template for Org,
since the "default template" is just a scratch buffer.

For example, i've been using the one-project-per-file setup you've
described for a while.  It first matches my taste for playing with
options that made each file aware of the context in which i was using
it.  But after some time i (somewhat sadly) discovered my taste didn't
match my actual needs and switch back to the one-single-big-file
setup, since it does constrain a very sober (and hopefully more
efficient) use of metadata and options.  But of course this is my
story, and everyone uses Org for different needs, with different
tastes.

I can see one constructive way of providing templates for org-mode: to
post them on a dedicated page of the emacswiki, along with discussions
on how/why to use them, or how a template matches a specific use.  And
maybe the further step would be to provide a package with all the
templates.

Best,

-- 
Bastien

      reply	other threads:[~2007-01-21 23:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-19  1:56 another (different) template request Austin Frank
2007-01-20  0:08 ` Bastien [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=87bqksc5e4.fsf@tallis.ens.fr \
    --to=bzg@altern.org \
    --cc=austin.frank@gmail.com \
    --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).