From: Eli Zaretskii <eliz@gnu.org>
To: trentbuck@gmail.com (Trent W. Buck)
Cc: 36759@debbugs.gnu.org
Subject: bug#36759: 26.1; nftables major mode
Date: Sat, 10 Aug 2019 11:07:12 +0300 [thread overview]
Message-ID: <834l2pa1fz.fsf@gnu.org> (raw)
In-Reply-To: <87d0i2ecma.fsf@goll.lan> (trentbuck@gmail.com)
> From: trentbuck@gmail.com (Trent W. Buck)
> Date: Mon, 22 Jul 2019 17:45:33 +1000
>
> nftables is a Linux kernel firewall.
>
> Its configuration uses a complex BNF where many keywords are repeated;
> they mean different things in different places.
>
> I want syntax highlighting and smart indentation for such files,
> because they're very hard to read in just conf-mode,
> even with some conf-space-keywords.
>
> I couldn't find a major mode for this, so I wrote a basic one.
> This is working well enough for today, but I don't have the time or
> interest to maintain it properly.
>
> If someone else is prepared to adopt it and get it into mainline Emacs,
> that would be FANTASTIC.
Sorry for the delay in responding.
Would it be possible to rewrite this mode using define-generic-mode?
See generic-x.el for some example of using that macro.
If using generic.el is somehow impossible or impractical, then could
you please format your code as a separate Lisp file according to our
conventions (see any of the *.el files in the Emacs tree for an
example), add a NEWS entry, and submit that in the "git format-patch"
form? Bonus points for adding tests based on your example file.
Thanks.
next prev parent reply other threads:[~2019-08-10 8:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 7:45 bug#36759: 26.1; nftables major mode Trent W. Buck
2019-08-10 8:07 ` Eli Zaretskii [this message]
2019-08-12 1:16 ` Trent W. Buck
2020-09-05 1:13 ` Stefan Kangas
2020-09-05 4:34 ` Trent W. Buck
2021-09-22 21:16 ` Lars Ingebrigtsen
2021-09-23 2:22 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-24 2:49 ` Trent W. Buck
2022-05-02 8:40 ` Lars Ingebrigtsen
2022-05-02 12:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-23 0:38 ` Trent W. Buck
2022-05-23 12:21 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=834l2pa1fz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36759@debbugs.gnu.org \
--cc=trentbuck@gmail.com \
/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.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).