Re: [Orgmode] no line break after subheading?

2010-10-27 Thread Christian Moe
Hi, Matt, Here's a dirty CSS workaround (I seem to be posting a lot of those lately) that should actually make this look more or less as you want it in HTML. #+TITLE: Test #+STYLE: .timeline div * {display: inline;} * Timeline :PROPERTIES: :HTML_CONTAINER_CLASS: timeline :END: ** Sep

Re: [Orgmode] no line break after subheading?

2010-10-27 Thread Bastien
Matt Price writes: > should be rendered (written in html for convenience, since i don't speak > latex): > > Timeline > Semtember 2011: Research team assembles initial documents > > Do folks think this is something I can do from org somehow Maybe you can use descriptive lists? -- Bastien __

Re: [Orgmode] no line break after subheading?

2010-10-26 Thread Jeff Horn
As a workaround, you could use description lists, such that your source code becomes: ** Timeline - September 2011 :: Research team assembles initial documents Though this will be less useful in HTML export since the exporter adds a line break after 2011. It should render how you want using th

Re: [Orgmode] no line break after subheading?

2010-10-26 Thread Thomas S. Dye
Hi Matt, In LaTeX with the standard article class, I believe that \paragraph{} and \subparagraph{} are the sections that set the heading on the same line as the text. How you get that in the LaTeX output depends on how you've set org-export-latex-classes. All the best, Tom On Oct 26, 20

Re: [Orgmode] no line break after subheading?

2010-10-26 Thread Sebastian Rose
Matt Price writes: > Hi eveyrone, > > I'm coming up on this with some frequency now -- I often need to write > documents in a pretty compact format, in which subheadings really need to be > on the same line as their component text. so for instance here: > > ** Timeline > *** September 2011 > Rese

[Orgmode] no line break after subheading?

2010-10-26 Thread Matt Price
Hi eveyrone, I'm coming up on this with some frequency now -- I often need to write documents in a pretty compact format, in which subheadings really need to be on the same line as their component text. so for instance here: ** Timeline *** September 2011 Research team assembles initial document