emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Colin Baxter <m43cap@yandex.com>
To: emacs-orgmode@gnu.org
Subject: Re: Invalid-read-syntax
Date: Wed, 20 Apr 2016 18:46:38 +0100	[thread overview]
Message-ID: <87potk896p.fsf@yandex.com> (raw)
In-Reply-To: 87potks349.fsf@gmail.com

On Wed, Apr 20 2016, Nick Dokos wrote:

> Colin Baxter <m43cap@yandex.com> writes:
>
>> The file /lisp/ox-html.el of org-mode release_8.3.4-743-g516bbf has
>> binary content at line 1952, whereas the same file of org-mode
>> release_8.3.4-721-g16ad80 has not. Perhaps this is significant.
>>
>
> Perhaps I'm missing something but I don't see anything like that.I also
> don't see any changes to ox-html.el between 16ad80 and 516bbf. I
> checked out 516bbf and lines 1950+ of ox_html.el look like this:
>
>        (when title
> 	 (format
> 	  (if html5-fancy
> 	      "<header>\n<h1 class=\"title\">%s</h1>\n%s</header>"
> 	    "<h1 class=\"title\">%s%s</h1>\n")
> 	  (org-export-data title info)
>
> Maybe your local copy is corrupted somehow? What happens if you
>
>  git checkout -- .../lisp/ox-html.el
>
> ?
>
> --
> Nick

git checkout /path/to/ox-html.el worked and removed the binary stuff. I
guess it must have been corrupted during the git pull. Thank you.

Best wishes,

Colin.

  reply	other threads:[~2016-04-20 17:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19  6:01 Invalid-read-syntax Colin Baxter
2016-04-19 19:23 ` Invalid-read-syntax Nicolas Goaziou
2016-04-20  5:59   ` Invalid-read-syntax Colin Baxter
2016-04-20  6:39     ` Invalid-read-syntax Alan Schmitt
2016-04-20  8:13       ` Invalid-read-syntax Colin Baxter
2016-04-20 15:37         ` Invalid-read-syntax Nick Dokos
2016-04-20 17:46           ` Colin Baxter [this message]
2016-04-21  5:35             ` Invalid-read-syntax Colin Baxter

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=87potk896p.fsf@yandex.com \
    --to=m43cap@yandex.com \
    --cc=emacs-orgmode@gnu.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).