emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt <matt@excalamus.com>
To: "Derek Chen-Becker" <derek@chen-becker.org>
Cc: "Emacs-orgmode" <Emacs-orgmode@gnu.org>
Subject: Re: Font lock for org-babel shell scripts?
Date: Tue, 28 Mar 2023 17:07:00 -0400	[thread overview]
Message-ID: <1872a0ba9d3.ecc1ea6b412263.1693292189426769869@excalamus.com> (raw)
In-Reply-To: <CAMbmz5kyiXN5zeWE9f3RmfktONpyc7jL846MM1vXeEfAwOSAPA@mail.gmail.com>


 ---- On Tue, 28 Mar 2023 13:24:39 -0400  Derek Chen-Becker  wrote --- 

 > I'm trying to figure out whether there's a bug or just a misconfiguration on my end with font lock for org-babel shell source blocks. If I run emacs 28.2 (with -q) and open the following org file, I can evaluate both source blocks but only the "bash" block has syntax highlighting. I've confirmed that opening a zsh script (e.g. with a zsh shebang) highlights correctly. If this list isn't the right place to ask about this issue, does someone know where I could look for help?

This is the right place to ask.  And thanks for asking!

I'm able to reproduce it.

I'm not familiar with how Org handles the font lock.  However, I notice that calling C-c ' (`org-edit-special') results in the error:  No such language mode: zsh-mode

I suspect that without a language mode, Org has no way to know how to color the block.

As a quick work around, you can define zsh-mode as shell-script-mode to get coloring:

(defalias 'zsh-mode 'shell-script-mode)


  reply	other threads:[~2023-03-28 21:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28 17:24 Font lock for org-babel shell scripts? Derek Chen-Becker
2023-03-28 21:07 ` Matt [this message]
2023-03-28 21:53 ` [BUG] No font lock in src blocks for shells in org-babel-shell-names (was Re: Font lock for org-babel shell scripts?) Matt
2023-03-29  9:35   ` Ihor Radchenko
2023-03-29 17:04     ` Derek Chen-Becker
2023-03-29 20:17       ` Matt
2023-03-30  8:56         ` Ihor Radchenko
2023-03-30 23:10           ` Derek Chen-Becker
2023-03-31 13:08             ` Ihor Radchenko
2023-03-31 17:04               ` Derek Chen-Becker
2023-03-31 17:46                 ` Ihor Radchenko
2023-04-01 23:21           ` Matt
2023-04-03 17:42             ` Derek Chen-Becker
2023-04-04 12:32               ` Ihor Radchenko
2023-04-04 14:49                 ` Derek Chen-Becker
2023-04-07 15:29                 ` Matt
2023-04-07 15:32                   ` Derek Chen-Becker
2023-04-17 15:12                   ` Matt
2023-04-17 15:21                     ` Ihor Radchenko
2023-04-20 14:42                       ` Max Nikulin

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=1872a0ba9d3.ecc1ea6b412263.1693292189426769869@excalamus.com \
    --to=matt@excalamus.com \
    --cc=Emacs-orgmode@gnu.org \
    --cc=derek@chen-becker.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).