From: Hugo Thunnissen <devel@hugot.nl>
To: emacs-devel@gnu.org
Cc: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: [ELPA] New Package: phpinspect.el
Date: Mon, 7 Aug 2023 22:22:53 +0200 [thread overview]
Message-ID: <25249bd1-bd1b-5888-b67f-718ffd0ad6ff@hugot.nl> (raw)
Hi all,
I would like to propose my package, phpinspect.el, to be added to GNU Elpa.
PHPInspect is a minor mode that provides code intelligence for PHP in
Emacs. At its core is a PHP parser implemented in Emacs Lisp. PHPInspect
comes with backends for |completion-at-point|, |company-mode| and
|eldoc|. A backend for |xref| is planned to be implemented at a later
date. The main documentation can be found in the docstring of
phpinspect-mode and in README.md in the source repository.
I have done my best to bring much of the package's code under test with
ert and "fieldtest" the package by using it myself. There are some parts
of the code though that I think need to be tested in more environments
than mine to see how they hold up. For example: the package makes heavy
use of collaborative threads to parse and index code while emacs is
otherwise idling. I have done my best to make this as non-intrusive as
possible, but I'm not sure how the default behavior of the threads will
hold up for users on different (maybe less performant) systems from mine.
I have signed my copyright papers a year back, so I think the paperwork
is in order.
The elpa contribution process is all new to me and my code has mostly
only been read and written by me, so pointers and feedback on both
topics are very welcome :)
source repository: https://github.com/hugot/phpinspect.el.git
Kind regards,
Hugo
next reply other threads:[~2023-08-07 20:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 20:22 Hugo Thunnissen [this message]
2023-08-12 4:56 ` [ELPA] New Package: phpinspect.el Stefan Monnier
2023-08-12 5:04 ` Stefan Monnier
2023-08-15 17:45 ` Hugo Thunnissen
2023-08-15 20:28 ` Philip Kaludercic
2023-08-15 21:33 ` Hugo Thunnissen
2023-08-15 21:56 ` Philip Kaludercic
2023-08-15 22:03 ` Stefan Monnier
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=25249bd1-bd1b-5888-b67f-718ffd0ad6ff@hugot.nl \
--to=devel@hugot.nl \
--cc=emacs-devel@gnu.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).