From: "Kjartan Óli Águstsson" <kjartanoli@outlook.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [ELPA] New package: calibre.el
Date: Thu, 20 Apr 2023 19:46:58 +0000 [thread overview]
Message-ID: <GV1P193MB2310AC3578548C8AD730C05EDF639@GV1P193MB2310.EURP193.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <87h6ta2yvx.fsf@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 566 bytes --]
Philip Kaludercic <philipk@posteo.net> writes:
>> As for the usage of eieio, is there a reason not to use it?
>
> If you just need a structure then cl-defstruct should be a less-heavy
> solution.
Noted, I'm hoping to add the ability to edit metadata in the future, and
from the small experiments I've done eieio-customize-object looks
useful, since it means I don't have to write the UI for that editing. So
I'll probably stick with EIEIO for now.
--
Kjartan Oli Agustsson
GPG Key fingerprint: 4801 0D71 49C0 1DD6 E5FD 6AC9 D757 2FE3 605E E6B0
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 691 bytes --]
next prev parent reply other threads:[~2023-04-20 19:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 23:23 [ELPA] New package: calibre.el Kjartan Óli Águstsson
2023-04-18 6:05 ` Philip Kaludercic
2023-04-18 8:19 ` Kjartan Óli Águstsson
2023-04-20 13:37 ` dalanicolai
2023-04-20 19:28 ` Kjartan Óli Águstsson
2023-04-20 18:26 ` Philip Kaludercic
2023-04-20 19:46 ` Kjartan Óli Águstsson [this message]
2023-05-09 12:50 ` Kjartan Óli Águstsson
2023-05-10 6:36 ` Philip Kaludercic
2023-05-10 11:24 ` Eli Zaretskii
2023-05-10 12:34 ` Kjartan Óli Águstsson
2023-05-16 19:38 ` Philip Kaludercic
2023-05-17 15:01 ` Kjartan Óli Águstsson
2023-05-18 13:01 ` Philip Kaludercic
2023-05-18 16:23 ` Kjartan Óli Águstsson
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=GV1P193MB2310AC3578548C8AD730C05EDF639@GV1P193MB2310.EURP193.PROD.OUTLOOK.COM \
--to=kjartanoli@outlook.com \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
/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).