emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: CRSHCMDR <typkrft@gmail.com>
To: Tim Cross <theophilusx@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: JS2 Syntax Highlighting for Source Blocks
Date: Sat, 12 Sep 2020 22:01:26 -0400	[thread overview]
Message-ID: <ea762937-f3a5-4736-ba8e-b395e533dc9f@Spark> (raw)
In-Reply-To: <87v9gipi19.fsf@gmail.com>

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

If I use js2 I lose all syntax highlighting, if I use js or javascript I get the same syntax highlighting.

Also sorry for the duplicate emails, that was not intentional.

Thanks,
Brandon
On Sep 12, 2020, 9:44 PM -0400, Tim Cross <theophilusx@gmail.com>, wrote:
>
> CRSHCMDR <typkrft@gmail.com> writes:
>
> > Is it possible to use js2-mode instead of js-mode for the syntax highlighting of code blocks in org-mode? The reason that I ask is that the current js-mode syntax highlighting leaves something to be desired, and is from my perspective broken. For instance after declaring a variable, the usage of that variable is no longer highlighted. You can see the difference here https://imgur.com/a/4b2LyhE.
> >
> > I have tried using the ‘org-src-lang-modes, but I’m either not setting it correctly, or I’m barking up the wrong tree.
> >
>
> What happens if you just use 'js2' as the language in the source block
> header instead of javascript?
>
>
> --
> Tim Cross

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

      reply	other threads:[~2020-09-13  2:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4a4f6286-0600-4e6a-90b9-174257e19a48@Spark>
2020-09-12 19:04 ` JS2 Syntax Highlighting for Source Blocks CRSHCMDR
2020-09-13  1:44   ` Tim Cross
2020-09-13  2:01     ` CRSHCMDR [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

  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=ea762937-f3a5-4736-ba8e-b395e533dc9f@Spark \
    --to=typkrft@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=theophilusx@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).