emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: katepano <katepano@gmail.com>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org
Subject: Re: what happened to the #+OPTIONS: \n:t ?
Date: Tue, 05 Apr 2011 10:07:23 +0300	[thread overview]
Message-ID: <4D9ABFAB.6070701@gmail.com> (raw)
In-Reply-To: <4782.1301939082@alphaville.usa.hp.com>

Thanks all for your responses, let me clarify a bit . . .

First of all I need <#+OPTIONS: \n:t>  because when I export an org file 
which has song lyrics in it I want to preserve the lines but accept css 
for nice printing (and singing afterwards).

Regarding, the other question, that of exporting, I need it because some 
software like blosxom can use a date stamp in the filename to present in 
a "timely" hierarchical manner the content (due to plugin 
http://www.enilnomi.net/download.html#permtimez ). If it could be done, 
a whole blog site (based on blosxom or derivatives) could be written as 
source org files and published automatically. I know probably blosxom is 
not good for bloging publicly but for personal use in ones PC is 
excellent (I use it for journal, tips and hacks database, study notes, 
book notes, songs database etc etc)

But do not bother, if it can't be done, ok. Actually I tried to do 
something myself, either through the org-publish.el or 
org-export-generic.el without much success :(

Well, thanks again

Katepano

On 04/04/2011 08:44 PM, Nick Dokos wrote:
> katepano<katepano@gmail.com>  wrote:
>
>> what happen to the #+OPTIONS: \n:t ? we need it back please!!!
> Why? what's the use case?
>
>> why it
>> does not work????
>>
>> By the way nobody responded to my message!!!
>>
>> http://www.mail-archive.com/emacs-orgmode@gnu.org/msg40104.html
>>
>> why? is it a stupid question or it can't be implemented?
>>
> [the question in that message is about exporting to a file with a different
> file name than the default, in particular consisting partly of a datestamp]
>
> Neither - but it is not the way it works currently. Again, if you can
> present a compelling use case, maybe somebody will implement it (but
> maybe not). You are always free to implement it yourself.
>
> Nick
>
>

  reply	other threads:[~2011-04-05  7:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04 14:42 what happened to the #+OPTIONS: \n:t ? katepano
2011-04-04 17:44 ` Nick Dokos
2011-04-05  7:07   ` katepano [this message]
2011-04-05  7:18     ` Jambunathan K
2011-04-05  7:31       ` katepano
2011-04-05  7:52         ` Christian Moe
2011-04-05  7:56           ` katepano
2011-04-05  8:09             ` Carsten Dominik
2011-04-04 17:47 ` Bernt Hansen
2011-04-04 17:57   ` Nick Dokos
2011-04-04 18:44     ` Carsten Dominik
2011-04-04 18:02   ` Bernt Hansen
2011-04-04 23:28 ` Bastien
2011-04-05  8:04 ` Carsten Dominik
2011-04-05  8:15   ` katepano
2011-04-05  8:26     ` Carsten Dominik

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=4D9ABFAB.6070701@gmail.com \
    --to=katepano@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.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 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).