From: Stefan Kangas <stefan@marxist.se>
To: "Trent W. Buck" <trentbuck@gmail.com>
Cc: 36759@debbugs.gnu.org
Subject: bug#36759: 26.1; nftables major mode
Date: Sat, 5 Sep 2020 01:13:21 +0000 [thread overview]
Message-ID: <CADwFkm=RrFNUepty0Srg71RSO8f9idTv_Mq8o3X6p_1y1LRbDw@mail.gmail.com> (raw)
In-Reply-To: <20190812011632.GA935@goll.lan> (Trent W. Buck's message of "Mon, 12 Aug 2019 11:16:34 +1000")
"Trent W. Buck" <trentbuck@gmail.com> writes:
> Eli Zaretskii wrote:
>>> nftables is a Linux kernel firewall.
>>> I couldn't find a major mode for this, so I wrote a basic one.
>>> Could someone else adopt it into mainline Emacs?
>>
>> Would it be possible to rewrite this mode using define-generic-mode?
>> See generic-x.el for some example of using that macro.
>
> I didn't know about define-generic-mode!
>
> (My elisp-fu is Giraffe Book vintage, and I've been using
> e.g. conf-mode instead of ini-generic-mode, and third-party
> apache-mode instead of apache-conf-generic-mode.)
>
> I can have a go, but I don't know when I'll get around to it.
(That was one year ago.)
Are you still working on this mode? Have you made any progress, so far?
next prev parent reply other threads:[~2020-09-05 1:13 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
2019-08-12 1:16 ` Trent W. Buck
2020-09-05 1:13 ` Stefan Kangas [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkm=RrFNUepty0Srg71RSO8f9idTv_Mq8o3X6p_1y1LRbDw@mail.gmail.com' \
--to=stefan@marxist.se \
--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 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.