emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Bastien <bzg@altern.org>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org, Rasmus <rasmus@gmx.us>
Subject: Re: [new exporter] adhere org-export-date-timestamp-format?
Date: Wed, 09 Jan 2013 19:30:48 +0100	[thread overview]
Message-ID: <87vcb6qkdj.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87k3rm2q03.fsf@gmail.com> (Nicolas Goaziou's message of "Wed, 09 Jan 2013 19:03:08 +0100")

Hi Nicolas,

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Before I start coding it, I wonder if functions related to timestamp
> objects, that is `org-export-timestamp-has-time-p',
> `org-export-format-timestamp', `org-export-split-timestamp-range' and
> `org-export-translate-timestamp' shouldn't be moved from org-export.el
> to org.el. After all, there are not only useful in an export context.
>
> What do you think about it?

I agree they are general and should be move out of org-export.el.

Note that one of my plan for 8.[01] is to put org.el on diet so that
it loads more quickly and for more basic stuff.  So maybe there will
be org-plan.el at some point for org-schedule, org-deadline and 
anything related to planning.  Ideally, Org would *just* be outline
reloaded (with orgtble and all editing facilities), while other
features would have their own library.  So maybe those functions
will end up outside of org.el one day... but I'd say it's okay
to have them in org.el for now.

Thanks,

-- 
 Bastien

next prev parent reply	other threads:[~2013-01-09 18:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-18 14:43 [new exporter] adhere org-export-date-timestamp-format? Rasmus
2012-12-24  1:50 ` Bastien
2013-01-06 10:00   ` Nicolas Goaziou
2013-01-06 11:45     ` Bastien
2013-01-09 15:29       ` Nicolas Goaziou
2013-01-09 17:15         ` Bastien
2013-01-09 18:03           ` Nicolas Goaziou
2013-01-09 18:30             ` Bastien [this message]
2013-01-12 11:30               ` Nicolas Goaziou
2013-01-12 14:45                 ` Bastien
2013-01-30 21:53                   ` Nicolas Goaziou
2013-01-30 23:54                     ` Rasmus

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=87vcb6qkdj.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    --cc=rasmus@gmx.us \
    /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

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).