@ Giovanni: the manual says \n:nil does not work. I played around with it anyway but was unsuccessful. Bummer as it seemed like it would have been perfect...
@ TIm, I am aware of this option and it's what I was referencing in the original note with:
> I could resort to explicit html every time I post (requiring <br \>
> for every line break) but this would also require fixing all
> pre-existing posts which is pretty much not an option.
But what about my point that currently all my posts do not use this? When I experimented with this option yesterday it turned old posts into huge run-on paragraphs with no structure, hence I don't really think it's an option unless I re-edit every post. Going forward, it'd be easier to somehow get rid of line breaks... though maybe I should just write my own template or something. I don't really use <p> in my posts anyway but prefer the single line space created by just on <br \>.
I dunno -- any thoughts? Should I re-do like 30 posts for this? Is there any other way?
Thanks for the help, all.
John
On Wed, Jul 28, 2010 at 5:30 AM, Tim Burt
<tcburt@rochester.rr.com> wrote:
> I use org for exporting to html and then pasting into blogger
I use this process also for Blogger
> ... but every time I do I need to delete line breaks.
... but I do not need to delete line breaks. See
http://naturallogofx.rketburt.org/2010/07/linebreaks-blogger-and-org-mode.html
for an article that describes what I do. The fix for me was in the
Blogger settings, not anything in emacs.
> Is there a way to get org to just publish the blob without breaking
> lines every time?
I do not know how to prevent line breaks in the export, but nor have I
needed to do that.
> I'm guessing it has to do with my minor fill mode as the line breaks
> tend to be the same as they are in org.
>
> In typical export, everything is surrounded by <html> tags but in blogger on
> doesn't have these and thus line breaks are line breaks.
The article reference above indicates how to stop Blogger from
presenting an input linebreak (e.g. newline character) as an output
linebreak.
> I could resort to explicit html every time I post (requiring <br \>
> for every line break) but this would also require fixing all
> pre-existing posts which is pretty much not an option.
>
> Any idea what I could do?
Let me know if the article reference does not help solve the issue.
Tim
>
>
> Thanks,
> John