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: [BUG] No font lock in src blocks for shells in org-babel-shell-names (was Re: Font lock for org-babel shell scripts?)
Date: Tue, 28 Mar 2023 17:53:10 -0400	[thread overview]
Message-ID: <1872a35eeec.dcff8bea422796.5356383202108217532@excalamus.com> (raw)
In-Reply-To: <CAMbmz5kyiXN5zeWE9f3RmfktONpyc7jL846MM1vXeEfAwOSAPA@mail.gmail.com>

Of the shells given in `org-babel-shell-names' (that is, "sh" "bash" "zsh" "fish" "csh" "ash" "dash" "ksh" "mksh" "posh"), only "sh" and "bash" have font locking in source blocks.

For example,

#+begin_src sh
  if [ -z $TEST ]; then
      echo Fontified
  fi
#+end_src

#+begin_src bash
  if [ -z $TEST ]; then
      echo Fontified
  fi
#+end_src

#+begin_src zsh
  if [ -z $TEST ]; then
      echo No fontification
  fi
#+end_src

#+begin_src fish
  if [ -z $TEST ]; then
     echo No fontification
  fi
#+end_src

#+begin_src csh
  if [ -z $TEST ]; then
      echo No fontification
  fi
#+end_src

#+begin_src ash
  if [ -z $TEST ]; then
      echo No fontification
  fi
#+end_src

#+begin_src dash
  if [ -z $TEST ]; then
      echo No fontification
  fi
#+end_src

#+begin_src ksh
  if [ -z $TEST ]; then
      echo No fontification
  fi
#+end_src

#+begin_src mksh
  if [ -z $TEST ]; then
      echo No fontification
  fi
#+end_src

#+begin_src posh
  if [ -z $TEST ]; then
      echo No fontification
  fi
#+end_src

 Does anyone know which function is responsible for re-fontifing source blocks?


  parent reply	other threads:[~2023-03-28 21:54 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
2023-03-28 21:53 ` Matt [this message]
2023-03-29  9:35   ` [BUG] No font lock in src blocks for shells in org-babel-shell-names (was Re: Font lock for org-babel shell scripts?) 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=1872a35eeec.dcff8bea422796.5356383202108217532@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).