From: Eric S Fraga <ucecesf@ucl.ac.uk>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: HTML export and blogging to blogger.com
Date: Wed, 17 Nov 2010 16:46:25 +0000 [thread overview]
Message-ID: <87hbff6gpq.fsf@ucl.ac.uk> (raw)
In-Reply-To: <AANLkTinZ3qWpSvMxda51DTRr1-9=aLrZ+GCspq-5AbV5@mail.gmail.com> (John Hendy's message of "Wed, 17 Nov 2010 10:36:57 -0600")
John Hendy <jw.hendy@gmail.com> writes:
> On Wed, Nov 17, 2010 at 3:09 AM, Eric S Fraga <ucecesf@ucl.ac.uk> wrote:
>
> John Hendy <jw.hendy@gmail.com> writes:
>
> [...]
>
> > There was also a reference in the original post below to
> > longlines-mode...
>
> I apologise for jumping into the middle of a conversation but your
> reference to longlines-mode brings to mind visual-line-mode which was
> introduced in Emacs 23 (I believe). This mode turns on =word-wrap= as
> well which makes the text look like it has been filled (i.e. soft
> returns in your parlance) without actually changing the underlying
> text.
>
> I saw that as well. Haven't tried it but the question will be whether
> Org exports the actual contents of the file or what it appears to be
> on the screen. Longlines mode seems to do something similar in that it
> is "wrapped" but the file actually contains no line breaks... however
> when exporting to html, Org seems to use what the buffer looks like,
> not what the actual file contains.
Very strange. I don't observe this behaviour at all. With
visual-line-mode enabled *and* truncate-lines disabled (so that the
lines are actually wrapped on the screen; note that org sets line
truncation to be on by default), the text in my display (for a short
example) appears as 5 or 6 lines (depends on the window width, of
course) but the exported HTML is a single line.
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 23.2.1
: using Org-mode version 7.3 (release_7.3.86.gb3d6f)
next prev parent reply other threads:[~2010-11-17 16:46 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 22:05 HTML export and blogging to blogger.com Samuel Wales
2010-11-11 22:50 ` Nick Dokos
2010-11-11 23:06 ` Samuel Wales
2010-11-12 3:45 ` Nick Dokos
2010-11-11 23:07 ` John Hendy
2010-11-11 23:18 ` Samuel Wales
2010-11-11 23:40 ` John Hendy
2010-11-12 2:25 ` Samuel Wales
2010-11-12 10:47 ` Eric S Fraga
2010-11-12 19:32 ` Samuel Wales
2010-11-14 1:25 ` Samuel Wales
2010-11-14 2:26 ` John Hendy
2010-11-14 2:54 ` Samuel Wales
2010-11-16 3:01 ` Samuel Wales
2010-11-16 9:50 ` Giovanni Ridolfi
2010-11-16 18:26 ` Samuel Wales
2010-11-16 23:17 ` Samuel Wales
2010-11-16 23:32 ` John Hendy
2010-11-17 0:13 ` Samuel Wales
2010-11-17 0:17 ` Samuel Wales
2010-11-17 4:34 ` John Hendy
2010-11-17 4:45 ` John Hendy
2010-11-17 9:09 ` Eric S Fraga
2010-11-17 16:36 ` John Hendy
2010-11-17 16:46 ` Eric S Fraga [this message]
2010-11-24 1:59 ` Samuel Wales
2010-11-24 9:09 ` Eric S Fraga
2010-11-24 2:03 ` Samuel Wales
2010-11-17 11:47 ` Christian Moe
2010-11-17 12:28 ` Add a hook with #+BIND? Christian Moe
2010-11-18 5:44 ` Re: HTML export and blogging to blogger.com John Hendy
2010-11-17 3:46 ` Nick Dokos
2010-11-17 4:18 ` John Hendy
2010-11-17 5:17 ` Nick Dokos
2010-11-17 5:52 ` Samuel Wales
2010-11-17 6:09 ` Nick Dokos
2010-11-24 2:00 ` Samuel Wales
2010-11-17 10:17 ` Tim Burt
2010-11-24 1:58 ` Samuel Wales
-- strict thread matches above, loose matches on Subject: below --
2012-05-29 17:24 Annoying behavior of RET after a timestamp Nick Dokos
2012-05-29 17:46 ` Nick Dokos
2012-05-29 17:54 ` Samuel Wales
2012-05-29 18:43 ` Nick Dokos
2012-05-29 18:57 ` Samuel Wales
2012-05-29 19:04 ` suvayu ali
2012-05-29 19:15 ` Nick Dokos
2012-05-29 19:21 ` Nick Dokos
2012-05-29 19:26 ` Nick Dokos
2012-05-29 20:05 ` Samuel Wales
2012-05-31 12:43 ` Matt Lundin
2012-06-01 13:57 ` Bastien
2012-06-01 13:55 ` Bastien
2012-06-01 15:41 ` Nick Dokos
2009-06-11 11:58 tea-time? henry atting
2009-06-11 12:34 ` tea-time? Sebastian Rose
2009-07-17 3:56 ` tea-time? Samuel Wales
2009-07-17 7:24 ` tea-time? Bastien
2009-07-25 19:49 ` tea-time? Samuel Wales
2009-07-25 22:20 ` tea-time? Bastien
2009-07-26 0:14 ` tea-time? Samuel Wales
2009-07-26 19:04 ` tea-time? Bastien
2009-07-29 17:30 ` tea-time? Samuel Wales
2009-07-29 17:31 ` tea-time? Samuel Wales
2009-07-29 17:41 ` tea-time? Bastien
2009-07-29 17:54 ` tea-time? Samuel Wales
2009-07-29 18:41 ` tea-time? Bastien
2009-07-29 19:06 ` tea-time? Bastien
2009-07-29 21:45 ` tea-time? Samuel Wales
2009-07-29 22:29 ` tea-time? Nick Dokos
2009-07-30 5:18 ` tea-time? Bastien
2009-07-30 10:56 ` tea-time? Eric S Fraga
2009-07-30 12:34 ` tea-time? Richard Riley
2009-07-30 5:48 ` tea-time? Bastien
[not found] ` <samologist@gmail.com>
2012-08-28 1:11 ` How to make kill-sexp work as in the rest of Emacs? Samuel Wales
2012-08-28 3:43 ` Nick Dokos
2012-08-28 4:08 ` Samuel Wales
2012-08-28 5:30 ` Nick Dokos
2012-08-28 5:33 ` Samuel Wales
2012-08-30 5:04 ` Bastien
2009-07-17 12:46 ` tea-time? Bernt Hansen
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=87hbff6gpq.fsf@ucl.ac.uk \
--to=ucecesf@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=jw.hendy@gmail.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).