emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: David O'Toole <dto@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Adapting org-mode to my needs
Date: Fri, 21 Apr 2006 10:04:16 +0200	[thread overview]
Message-ID: <e4362df4e0734a65be36407194a9be51@gmail.com> (raw)
In-Reply-To: <m3vet31wwz.fsf@gnu.org>

Hi David,

this looks exactly right, I agree on all accounts.  A few comments:

>
> ;; I would like to contribute this and more, as I think of stuff. I'd
> ;; be happy to do the required paperwork with the FSF.

Great.  Likely not for Emacs 22.1, but later, yes, I want to integrate 
this.  And if we integrate it, the FSF will need the paperwork done.

> 	    ; allow user to turn off the printout of author, email,
> 	    ; date at the top of pages. I really want this.
> 	
> 	    :auto-preamble nil

I actually would like to move author and date into a standard postamble 
because this is more the HTML way of doing things.  Then we will also 
need

	    :auto-postamble nil


>
> 	    ; the following are inserted into the right places in the
> 	    ; real html header by org-publish-as-html
>
> 	    :style "my-css-string"
> 	    :language "en"
> 	    :author user-full-name
> 	    :email user-mail-address
>
> 	    ; other options that should over-ride global variables
> 	    ; when publishing (of course, options set per orgfile
> 	    ; should override everything.im
>
> 	    :headline-levels 3
> 	    :toc nil
>
> 	    ; can you think of more?

I guess for consistency we should support almost all options in 
#+OPTIONS, plus
whatever I have customization options for.

One problem:  I think it is not easy to distinguish a nil property from 
an unspecified property....  Ah, I see there is also `plist-member' for 
this.  Great.

> (file-name-sans-extension (buffer-name))
>
> ;; instead of just
>
> (buffer-name)

Agreed.

Maybe we take the technical details off the mailing list and cc to 
emacs-orgmode only if the mail contains issues of broader interest?  
Anyone on this list who would like to listen to the technical chatter?

- Carsten

  reply	other threads:[~2006-04-21  8:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-18 15:06 Adapting org-mode to my needs David O'Toole
2006-04-19  6:10 ` Carsten Dominik
2006-04-19 12:22   ` Carsten Dominik
2006-04-19 13:53   ` David O'Toole
2006-04-21  2:31   ` David O'Toole
2006-04-21  8:04     ` Carsten Dominik [this message]
2006-04-21  8:16       ` David Emery
2006-04-21 14:11       ` Carsten Dominik
2006-04-21 14:33         ` David O'Toole
2006-04-26 20:16   ` Interaction of org-mode and Muse (was: Adapting org-mode to my needs) Michael Olson
2006-04-27  7:31     ` Carsten Dominik
2006-04-27 12:56       ` [Emacs-orgmode] Interaction of org-mode and Muse Michael Olson
  -- strict thread matches above, loose matches on Subject: below --
2006-04-18 19:15 Adapting org-mode to my needs David O'Toole

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=e4362df4e0734a65be36407194a9be51@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=dto@gnu.org \
    --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).