From: Eric Schulte <schulte.eric@gmail.com>
To: Josh Berry <taeric@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Running Node.js and exporting css.
Date: Sat, 23 Aug 2014 23:51:28 -0400 [thread overview]
Message-ID: <8738cmczpb.fsf@gmail.com> (raw)
In-Reply-To: <CAG9v9N=eoYW76+-2O-NKdTpdAn5qNxsF6bFLCHGTR9zzHFCP8g@mail.gmail.com> (Josh Berry's message of "Fri, 22 Aug 2014 10:54:21 -0400")
Josh Berry <taeric@gmail.com> writes:
> 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.
>
Thanks for the report Josh, I just pushed up an improved regexp for the
parsing of multi-line js results.
Best -- Eric
>
> 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
>
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D (see https://u.fsf.org/yw)
prev parent reply other threads:[~2014-08-24 3:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 14:54 Running Node.js and exporting css Josh Berry
2014-08-24 3:51 ` Eric Schulte [this message]
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=8738cmczpb.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=taeric@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 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.