From: Roland Kaufmann <roland.kaufmann@gmail.com>
To: Hrvoje Niksic <hniksic@xemacs.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Markup on same line as text
Date: Wed, 16 Feb 2011 22:53:53 +0100 [thread overview]
Message-ID: <4D5C4771.7030600@gmail.com> (raw)
In-Reply-To: <87zkpvkape.fsf@xemacs.org>
> Your patch may work in this particular case, but the idea behind
> htmlize is to describe the state of the buffer. If a property ends
> after the newline, it is intended that the generated HTML reflect
The philosophical question is then: Is the newline character part of the
syntax construct that is being fontified, or rather a "formatting code"
that should be kept separate?
Being whitespace it (mostly) doesn't matter visually, which makes it an
easy choice to include in tokens to preserve formatting continuity
between lines.
However, any further line processing by other modules is complicated
significantly if the terminator is put inside the markup.
> I am not familiar with org-mode, so I will need a description of
> exactly how to reproduce this bug. Specifically I don't know how to
> put a reference on the next line.
This Elisp will create/overwrite a buffer called foo.org in the /tmp
directory containing problematic code and export it to foo.html:
(let ((filename (expand-file-name "foo.org" temporary-file-directory)))
(switch-to-buffer (find-file-noselect filename))
(erase-buffer)
(insert "*
#+BEGIN_SRC emacs-lisp
(let ((x 42)) ; meaning of l.u.e.
(print x)) ; (ref:2)
#+END_SRC")
(save-buffer)
(org-mode)
(org-export-as-html nil))
--
Roland.
next prev parent reply other threads:[~2011-02-16 21:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 22:12 [PATCH] Markup on same line as text Roland Kaufmann
2011-02-16 20:04 ` Hrvoje Niksic
2011-02-16 21:53 ` Roland Kaufmann [this message]
2011-02-17 21:58 ` Hrvoje Niksic
2011-02-19 14:26 ` Roland Kaufmann
2011-02-19 23:49 ` Hrvoje Niksic
2011-02-26 9:39 ` Bastien
2011-02-27 21:09 ` Roland Kaufmann
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=4D5C4771.7030600@gmail.com \
--to=roland.kaufmann@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=hniksic@xemacs.org \
/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).