From: Thomas S. Dye <tsd@tsdye.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org, Oleh Krehel <ohwoeowho@gmail.com>,
Oleh Krehel <oleh@oremacs.com>
Subject: Re: Is it possible to keep /all/ the heading properties in one place?
Date: Mon, 29 Feb 2016 03:42:10 -1000 [thread overview]
Message-ID: <m28u23pr9p.fsf@tsdye.com> (raw)
In-Reply-To: <87egbvesqm.fsf@nicolasgoaziou.fr>
Nicolas Goaziou writes:
> However, I still think it would be nice to have the document somewhere
> in the Org tree, perhaps in contrib/ as a start, then possibly one day
> in doc/.
Would it serve a purpose?
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2016-02-29 13:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 10:59 Is it possible to keep /all/ the heading properties in one place? Oleh Krehel
2016-02-25 13:37 ` Nicolas Goaziou
2016-02-25 13:46 ` Oleh Krehel
2016-02-25 14:03 ` Nicolas Goaziou
2016-02-25 14:26 ` Oleh Krehel
2016-02-25 16:52 ` Nicolas Goaziou
2016-02-25 18:21 ` Eric S Fraga
2016-02-26 16:35 ` Rasmus
2016-02-28 9:35 ` Eric S Fraga
2016-02-28 11:32 ` Rasmus
2016-02-28 12:44 ` Eric S Fraga
2016-02-28 16:46 ` Rasmus
2016-02-28 17:05 ` Eric S Fraga
2016-02-25 19:17 ` Oleh Krehel
2016-02-25 20:16 ` Nicolas Goaziou
2016-02-26 8:18 ` Oleh Krehel
2016-02-28 8:59 ` Nicolas Goaziou
2016-02-28 12:17 ` Oleh Krehel
2016-02-28 16:34 ` Thomas S. Dye
2016-02-29 10:05 ` Nicolas Goaziou
2016-02-29 13:42 ` Thomas S. Dye [this message]
2016-02-29 15:00 ` Nicolas Goaziou
2016-02-29 13:53 ` Marcin Borkowski
2016-02-29 15:05 ` Nicolas Goaziou
2016-02-29 17:57 ` Revisiting moving manual to Org (was: Is it possible to keep /all/ the heading properties in one place?) Kyle Meyer
2016-02-29 17:17 ` Is it possible to keep /all/ the heading properties in one place? Achim Gratz
2016-02-29 18:01 ` Thomas S. Dye
2016-02-29 18:47 ` Nicolas Goaziou
2016-02-25 17:47 ` Michael Brand
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=m28u23pr9p.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=ohwoeowho@gmail.com \
--cc=oleh@oremacs.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.