From: Serghei Iakovlev <sadhooklay@gmail.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Emacs developers <emacs-devel@gnu.org>,
Drew Adams <drew.adams@oracle.com>,
John Yates <john@yates-sheets.org>
Subject: Re: [ELPA] New package: bnf-mode
Date: Mon, 06 May 2019 21:57:06 +0300 [thread overview]
Message-ID: <87o94f5s3h.fsf@gmail.com> (raw)
In-Reply-To: <jwv8svjydo3.fsf-monnier+emacsdiffs@gnu.org> (Stefan Monnier's message of "Mon, 06 May 2019 08:31:39 -0400")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>> No, Emacs Wiki has a wrong mode. For more see my comments here:
>> https://www.reddit.com/r/emacs/comments/b1lyyf/gnu_emacs_major_mode_for_editing_bnf_grammars/
>> <https://www.reddit.com/r/emacs/comments/b1lyyf/gnu_emacs_major_mode_for_editing_bnf_grammars/?utm_source=share&utm_medium=ios_app>
>>
>> And no guys, ebnf2ps does not provide syntax locking for BNF grammar
>
> ebnf2ps doesn't provide a mode at all. The mention of ebnf wasn't meant
> as "an alternative" to your mode, but rather I think as a suggestion
> for why your mode might be useful (i.e. as a complement to ebnf2ps).
>
> While looking at adding it to GNU ELPA I saw that you apparently haven't
> yet signed the corresponding paperwork. IOW the next step is to fill
> the form below and email it to the FSF as instructed so they can send
> you the relevant paperwork to sign.
>
>
> Stefan "still wondering what you use your mode for"
I use this mode for various experiments with languages. In particular,
I do research in the field of creating a programming language called
Zephir. I needed to get a formal description of the language and
this is exactly where I used the BNF. This description (I prefer
"specification" word) used during systems analysis and requirements
analysis.
>
> Please email the following information to assign@gnu.org, and we
> will send you the assignment form for your past and future changes.
>
> Please use your full legal name (in ASCII characters) as the subject
> line of the message.
> ----------------------------------------------------------------------
> REQUEST: SEND FORM FOR PAST AND FUTURE CHANGES
>
> [What is the name of the program or package you're contributing to?]
> Emacs
>
> [Did you copy any files or text written by someone else in these changes?
> Even if that material is free software, we need to know about it.]
>
>
> [Do you have an employer who might have a basis to claim to own
> your changes? Do you attend a school which might make such a claim?]
>
>
> [For the copyright registration, what country are you a citizen of?]
>
>
> [What year were you born?]
>
>
> [Please write your email address here.]
>
>
> [Please write your postal address here.]
>
>
>
>
>
> [Which files have you changed so far, and which new files have you written
> so far?]
I'll do this ASAP.
Thank you,
Serghei
next prev parent reply other threads:[~2019-05-06 18:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-04 15:51 [ELPA] New package: bnf-mode Serghei
2019-05-04 18:35 ` Stefan Monnier
[not found] ` <87h8a93qqu.fsf@gmail.com>
2019-05-05 14:49 ` Fwd: " Serghei Iakovlev
2019-05-05 14:56 ` Serghei Iakovlev
2019-05-05 16:07 ` Stefan Monnier
2019-05-05 22:31 ` John Yates
2019-05-06 0:47 ` Drew Adams
2019-05-06 0:48 ` Drew Adams
2019-05-06 5:54 ` Serghei Iakovlev
2019-05-06 12:31 ` Stefan Monnier
2019-05-06 18:57 ` Serghei Iakovlev [this message]
2019-05-07 0:59 ` Stefan Monnier
2019-05-07 17:36 ` Serghei Iakovlev
2019-05-07 17:58 ` Stefan Monnier
2019-05-07 18:54 ` Serghei Iakovlev
2019-05-07 19:01 ` Stefan Monnier
2019-05-09 4:06 ` Serghei Iakovlev
2019-05-05 15:01 ` Serghei Iakovlev
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=87o94f5s3h.fsf@gmail.com \
--to=sadhooklay@gmail.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=john@yates-sheets.org \
--cc=monnier@IRO.UMontreal.CA \
/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).