From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Kaushal <kaushal.modi@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Export to html inserts strange unicode characters at line breaks because of fci-mode [8.2.7c (8.2.7c-64-g01f736-elpa @ /home/kmodi/.emacs.d/elpa/org-20140915/)]
Date: Fri, 26 Sep 2014 12:02:14 +0200 [thread overview]
Message-ID: <87ppeid7ix.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAFyQvY2kEAnVhJa3KmOFj7wpPbXcKcDzg4=cmqwYaoAytj=h8w@mail.gmail.com> (Kaushal's message of "Thu, 25 Sep 2014 15:50:59 -0400")
Hello,
Kaushal <kaushal.modi@gmail.com> writes:
> I have fci-mode installed and enabled for programming modes.
>
> When org exports to html, htmlize figures out the syntax highlighting of
> the code by calling =(funcall lang-mode)=.
>
> That activates =fci-mode=.
>
> =fci-mode= shows the fill column using a unicode character. The issue is
> that org export to html exports that character as well.
>
> Those characters show up in html as below!
> http://i.imgur.com/8WplTqw.png
>
> So the solution is to fix the =orx-html-fontify-code= function.
I don't think so. `fill-column-indicator' is not even in core Emacs. We
shouldn't provide a workaround for every package out there.
Can't you simply disable this minor mode before exporting buffer, in
a hook such as `org-export-before-parsing-hook'?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-09-26 10:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 19:50 Bug: Export to html inserts strange unicode characters at line breaks because of fci-mode [8.2.7c (8.2.7c-64-g01f736-elpa @ /home/kmodi/.emacs.d/elpa/org-20140915/)] Kaushal
2014-09-25 23:55 ` Grant Rettke
2014-09-25 23:58 ` Kaushal
2014-09-26 0:05 ` Grant Rettke
2014-09-26 0:50 ` Thorsten Jolitz
2014-09-26 10:02 ` Nicolas Goaziou [this message]
2014-09-26 10:19 ` Kaushal
2014-09-27 19:25 ` Aaron Ecay
2015-06-04 20:10 ` Kaushal
2015-06-05 7:02 ` Nicolas Goaziou
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=87ppeid7ix.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=kaushal.modi@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).