From: Matt <matt@excalamus.com>
To: "Ihor Radchenko" <yantar92@posteo.net>
Cc: "Derek Chen-Becker" <derek@chen-becker.org>,
"Emacs-orgmode" <Emacs-orgmode@gnu.org>
Subject: Re: [BUG] No font lock in src blocks for shells in org-babel-shell-names (was Re: Font lock for org-babel shell scripts?)
Date: Sat, 01 Apr 2023 19:21:57 -0400 [thread overview]
Message-ID: <1873f20a792.fcfc6bcd54095.5358297633673942037@excalamus.com> (raw)
In-Reply-To: <87jzyyehwr.fsf@localhost>
---- On Thu, 30 Mar 2023 04:55:32 -0400 Ihor Radchenko wrote ---
> Matt matt@excalamus.com> writes:
>
> > I think this approach will work fine. I tried examples for each shell type and keywords like if/then/else and function names are highlighted.
>
> Even for posh (powershell)?
Yes. It's not great since sh-mode looks for Korn-based keywords. It does string highlighting and common keywords like 'if', 'exit', and 'param'.
next prev parent reply other threads:[~2023-04-01 23:23 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 ` [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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1873f20a792.fcfc6bcd54095.5358297633673942037@excalamus.com \
--to=matt@excalamus.com \
--cc=Emacs-orgmode@gnu.org \
--cc=derek@chen-becker.org \
--cc=yantar92@posteo.net \
/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.