all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Lic. Federico G. Stilman" <fstilman@gmail.com>
To: emacs-devel@gnu.org
Subject: Best (or common) pratices on package development workflow
Date: Thu, 1 Jun 2023 20:11:13 -0300	[thread overview]
Message-ID: <CAL4zx3O+_WGh5vWUzwUKWGoK1088TCVYamUERKt4J4M9xVuC0A@mail.gmail.com> (raw)

Hi all,

First things first. I started development with Emacs Lisp a few weeks
ago after using for more than 20 years Emacs for my daily work. So I
am a newbie on the Emacs Lisp development side.

I am currently writing a simple Emacs package consisting of one .el file.

I have a couple of defcustom declarations that initialize some
variables with a default value. And this is the source of my question.

Every time I make a change to the init value of the defcustom
declaration, I have to unload the feature provided by the package,
with something like:

  (unload-feature 'my-package)

and after that, reload the library with something like

  (load-library "my-package")

If not, the customization framework doesn't account for the change on
the default value of the custom variables.

My question is: which is the workflow you use when developing a
package for Emacs, for easily "reloading" the package for any kind of
changes by taken into account?

Re-evaluating the entire, or loading the file, works for reloading
functions. But - as far as I know - does not work for reloading
defcustom initialization values.

My package is for now something very simple consisting of one .el
file. I wonder how do you manage this when a package consists of many
.el files.

Thank you all,

Federico



             reply	other threads:[~2023-06-01 23:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-01 23:11 Lic. Federico G. Stilman [this message]
2023-06-01 23:51 ` Best (or common) pratices on package development workflow Ruijie Yu via Emacs development discussions.
2023-06-02  1:08   ` Lic. Federico G. Stilman
2023-06-01 23:56 ` Michael Heerdegen
2023-06-02  1:09   ` Lic. Federico G. Stilman

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=CAL4zx3O+_WGh5vWUzwUKWGoK1088TCVYamUERKt4J4M9xVuC0A@mail.gmail.com \
    --to=fstilman@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 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.