all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Josh Berry <taeric@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Running Node.js and exporting css.
Date: Fri, 22 Aug 2014 10:54:21 -0400	[thread overview]
Message-ID: <CAG9v9N=eoYW76+-2O-NKdTpdAn5qNxsF6bFLCHGTR9zzHFCP8g@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]

Couple of weeks ago, I accidentally spammed the message board with several
attempts to send up a couple of patches for some problems I was seeing.
 So, firstly, apologies for the spam.

The two problems I was seeing were related to executing js using node.js,
and exporting css with vendor properties.

The node.js problem is that it will start putting in newlines if a
structure is past some size.  I think this may be "fixable" by changing
some settings in node.js, but it was also easy enough to change the regex
to look past newlines in org.  An example of the problem can be seen by
running the following

  #+BEGIN_SRC js
    return [[1, 2],[1, 2],[1, 2],[1, 2],[1, 2],[1, 2],[1,2]]
  #+END_SRC

If you remove just one of the inner arrays, it will work as desired.

The other problem is just as short.  Simply export the following when you
have org-src-fontify-natively set.

  #+BEGIN_SRC css
    foo {
      -webkit-appearance: none;
    }
  #+END_SRC

I cobbled a small change that seemed to fix that.

At any rate, again apologies for the previous spam.  I didn't want to just
respam immediately with an apology.

Thanks!

--
josh

[-- Attachment #2: Type: text/html, Size: 1552 bytes --]

             reply	other threads:[~2014-08-22 14:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22 14:54 Josh Berry [this message]
2014-08-24  3:51 ` Running Node.js and exporting css Eric Schulte

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAG9v9N=eoYW76+-2O-NKdTpdAn5qNxsF6bFLCHGTR9zzHFCP8g@mail.gmail.com' \
    --to=taeric@gmail.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.