unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Ricky Tigg <ricky.tigg@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: v. 29.1.1 | Missing syntax colouring option
Date: Thu, 10 Aug 2023 14:18:39 +0300	[thread overview]
Message-ID: <CAM_8-Cj75vcfY4qHoC2q8QeP8wwSpBgTDHf26rmfgTM+_1Jriw@mail.gmail.com> (raw)

Hello. As a regular Fedora GNU-Linux user I am used to gnome-editor. When I
have to switch to Windows' side, it is invariably by accident. Here for
instance to investigate some properties of the TPM 2.0 chip as reported in
PowerShell in order to compare them as those I obtained on Linux's side.

It appears that GNU Emacs strangely supports Windows. An opportunity to
have the GNU spirit everywhere is through something I could not miss so I
installed it, as v. 29.1.1. Nonetheless as per the content at
https://www.gnu.org/software/emacs/, "*Content-aware editing modes,
including syntax coloring, for many file types*." an option dedicated to
set the *coding language* is missing from the UI.

The extension of the file I work with is *ps1*. I doubt Emacs knows how to
determine that the expected code language is PowerShell as there is no
syntax coloring.

Also an observation that cannot be missed; the software lacks the option *Open
a recent file*. Having to repeatedly specify the same path is without doubt
not an option in modern software. It would be worth adding that option..
Regards.


             reply	other threads:[~2023-08-10 11:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10 11:18 Ricky Tigg [this message]
2023-08-10 15:44 ` v. 29.1.1 | Missing syntax colouring option Emanuel Berg
2023-08-10 16:08 ` [External] : " Drew Adams
2023-08-10 19:47   ` Emanuel Berg
2023-08-10 17:48 ` Eli Zaretskii
2023-08-10 18:09   ` Emanuel Berg
2023-08-10 19:49 ` Jens Schmidt via Users list for the GNU Emacs text editor
2023-08-10 20:24   ` Emanuel Berg
2023-08-10 19:56 ` Rudolf Schlatte
2023-08-10 20:27   ` Emanuel Berg

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAM_8-Cj75vcfY4qHoC2q8QeP8wwSpBgTDHf26rmfgTM+_1Jriw@mail.gmail.com \
    --to=ricky.tigg@gmail.com \
    --cc=help-gnu-emacs@gnu.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.
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).