* emacs-lilypond-mode should we?
@ 2022-07-11 7:10 jgart
2022-07-11 13:29 ` Efraim Flashner
0 siblings, 1 reply; 3+ messages in thread
From: jgart @ 2022-07-11 7:10 UTC (permalink / raw)
To: Guix Devel
Hi,
Should we package this mode separately from lilypond as emacs-lilypond-mode?
https://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=tree;f=elisp;h=dc4d450a9f98433d04ac87057571ab58f98497c5;hb=HEAD
all best,
jgart
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: emacs-lilypond-mode should we?
2022-07-11 7:10 emacs-lilypond-mode should we? jgart
@ 2022-07-11 13:29 ` Efraim Flashner
2022-07-12 17:54 ` Tobias Platen
0 siblings, 1 reply; 3+ messages in thread
From: Efraim Flashner @ 2022-07-11 13:29 UTC (permalink / raw)
To: jgart; +Cc: Guix Devel
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]
On Mon, Jul 11, 2022 at 02:10:36AM -0500, jgart wrote:
> Hi,
>
> Should we package this mode separately from lilypond as emacs-lilypond-mode?
>
> https://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=tree;f=elisp;h=dc4d450a9f98433d04ac87057571ab58f98497c5;hb=HEAD
>
> all best,
>
> jgart
I think it would be best to package it separately, and I'm pretty sure
that's already what is suggested. The two packages I have installed that
happen to have .el files installed also don't have them compiled to .elc
files. Best to keep it separate so it's done with all the automation of
the emacs-build-system.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: emacs-lilypond-mode should we?
2022-07-11 13:29 ` Efraim Flashner
@ 2022-07-12 17:54 ` Tobias Platen
0 siblings, 0 replies; 3+ messages in thread
From: Tobias Platen @ 2022-07-12 17:54 UTC (permalink / raw)
To: guix-devel
On Mon, 2022-07-11 at 16:29 +0300, Efraim Flashner wrote:
> On Mon, Jul 11, 2022 at 02:10:36AM -0500, jgart wrote:
> > Hi,
> >
> > Should we package this mode separately from lilypond as emacs-
> > lilypond-mode?
> >
> > https://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=tree;f=elisp;h=dc4d450a9f98433d04ac87057571ab58f98497c5;hb=HEAD
> >
> > all best,
> >
> > jgart
>
> I think it would be best to package it separately, and I'm pretty
> sure
> that's already what is suggested. The two packages I have installed
> that
> happen to have .el files installed also don't have them compiled to
> .elc
> files. Best to keep it separate so it's done with all the automation
> of
> the emacs-build-system.
>
I agree, soon I will use that one when I compose vocasynth songs using
lilypond, since I use emacs and a lilypond addon for festival, which I
have replaced with a more modern sinsy. Soon I will package that one
too.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-07-12 17:54 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-07-11 7:10 emacs-lilypond-mode should we? jgart
2022-07-11 13:29 ` Efraim Flashner
2022-07-12 17:54 ` Tobias Platen
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.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).