Re: [O] what happened to the #+OPTIONS: \n:t ?

[katepano]

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<address@hidden>  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/address@hidden/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