ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: seyal.zavira@gmail.com
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: context-lmtx-mode – Emacs package for editing .ctx files in ConTeXt LMTX
Date: Mon, 22 Sep 2025 06:09:21 -0000	[thread overview]
Message-ID: <175852136108.2540.17915294865500943598@cgl.ntg.nl> (raw)
In-Reply-To: <175721906299.2482.18333600504184088551@cgl.ntg.nl>

Hi everyone,

My apologies for the very delayed reply. My focus was recently captured by
another project I was excited to finish, the CONTEXT-STARTERKIT, which I
shared in a separate thread. Thank you all for your patience and for the
incredibly positive and encouraging feedback on the context-lmtx-mode
package. It's fantastic to see this level of interest.

A special thank you to Hraban for adding the project to the ConTeXt
Garden wiki! I truly appreciate that; it’s a huge honor and will help
more users discover it.

Joaquín and Riviera, I was thrilled to read your enthusiastic comments.
I hope the package proves useful, and I look forward to any feedback or
ideas you might have whenever you get a chance.

Jim asked a very important question about how this package compares to
AUCTeX's context mode. It's a great point, and I'll do my best to
clarify my goals, though I must be transparent about my own experience.

To be honest, as I am relatively new to the world of TeX and ConTeXt, I
haven't used AUCTeX extensively myself. Therefore, I can't offer a
detailed user-experience comparison based on deep, long-term usage.
Instead, I can explain the philosophy and technical goals that drove me
to create context-lmtx-mode as an alternative:

My primary motivation was to build a modern editing experience from the
ground up, designed *exclusively* for ConTeXt LMTX, with these
principles in mind:

1. Simplicity and "Just Works" Philosophy:
   I aimed for a lightweight package that requires minimal configuration.
   The goal is for it to work seamlessly out of the box, especially for
   things like compiler detection, which can sometimes be a hurdle.

2. Superior Multi-Language Highlighting (via Polymode):
   This is the core technical advantage. context-lmtx-mode uses
   polymode to correctly handle and highlight different languages
   embedded within a .ctx file. This means if you have Lua code inside
   \startluacode, Metapost code inside \startMPcode, or XML blocks,
   each snippet gets its own proper syntax highlighting and indentation.
   This is a common pain point in other editors, and I wanted to solve
   it properly.

3. Strict Focus on LMTX:
   The package is intentionally built only for modern ConTeXt LMTX.
   This focus allows for more accurate syntax and tooling, without the
   legacy burden of supporting older MkII/MkIV versions.

4. Non-Intrusive and Safe Design:
   The package is self-contained. Any optional utilities are isolated
   and won't alter your global Emacs settings, making it safe to try
   out without disrupting your existing configuration.

So, rather than seeing it as a direct competitor to a mature suite like
AUCTeX, I see context-lmtx-mode as a focused tool that excels at the
*core editing task*, particularly for users who write modern,
multi-language ConTeXt documents and value simplicity.

I hope this gives a clearer picture of the vision. I welcome everyone to
give it a try and share their thoughts, open issues on GitHub, or
suggest features. Your feedback is what will shape its future.

Best regards,

Seyal
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2025-09-22  6:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-07  4:24 [NTG-context] " seyal.zavira
2025-09-07  5:52 ` [NTG-context] " Joaquín Ataz López
2025-09-07 14:18   ` Jim
2025-09-07  8:53 ` Henning Hraban Ramm
2025-09-07 11:09 ` Jim
2025-09-07 13:02 ` Riviera Taylor via ntg-context
2025-09-22  6:09 ` seyal.zavira [this message]
2025-09-22  7:03   ` juh+ntg-context--- via ntg-context
2025-09-22  7:11   ` Hans Hagen via ntg-context
2025-09-22 15:51     ` seyal.zavira
2025-09-22 17:52       ` juh+ntg-context--- via ntg-context
2025-09-23  0:07   ` Jim
2025-09-09 23:55 Lizardo Reyna via ntg-context

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=175852136108.2540.17915294865500943598@cgl.ntg.nl \
    --to=seyal.zavira@gmail.com \
    --cc=ntg-context@ntg.nl \
    /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 NNTP newsgroup(s).