From: Philip Kaludercic <philipk@posteo.net>
To: Ackerley Tng <ackerleytng@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: How do you develop emacs core packages?
Date: Mon, 21 Nov 2022 09:12:41 +0000 [thread overview]
Message-ID: <87h6ysbrhy.fsf@posteo.net> (raw)
In-Reply-To: <CANZnma58N31YzQ4Oj8nmoNrr0+OjX=PwyGBPqr-f6+=JU91t5Q@mail.gmail.com> (Ackerley Tng's message of "Sun, 20 Nov 2022 10:18:52 -0800")
Ackerley Tng <ackerleytng@gmail.com> writes:
> Hi Emacs Developers!
>
> Would like to learn your workflow while developing core packages.
>
> I use the package manager's version of emacs, so I have a lot of
> .el.gz files in some system directory.
>
> If I want to develop on one of those, I usually make a copy of the
> entire file, and then iterate by evaluating the function in emacs to
> override existing definitions, but sometimes when global variables
> initialized on emacs startup need to be adjusted, I find it hard to
> undo those steps, which the default package sets up.
>
> What's your workflow for developing core packages, do you have any
> tricks to share?
The main thing would be to build Emacs from source, then you always have
the newest versions of any file you wish to work on (which will prevent
issues when applying patches), and if you clone the emacs.git
repository, you'll be able to prepare git patches and see the version
history.
This might be of use: https://git.savannah.gnu.org/cgit/emacs.git/tree/CONTRIBUTE
prev parent reply other threads:[~2022-11-21 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 18:18 How do you develop emacs core packages? Ackerley Tng
2022-11-21 9:12 ` Philip Kaludercic [this message]
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=87h6ysbrhy.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=ackerleytng@gmail.com \
--cc=emacs-devel@gnu.org \
/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).