all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Morgan Smith <Morgan.J.Smith@outlook.com>
Cc: 52439@debbugs.gnu.org
Subject: [bug#52439] [PATCH 1/2] gnu: Add emacs-rec-mode.
Date: Sun, 12 Dec 2021 01:39:55 +0100	[thread overview]
Message-ID: <1d60848f3732844757e25a29db1d155dd7d885b3.camel@gmail.com> (raw)
In-Reply-To: <BYAPR05MB4023ADC56881243600380063C5739@BYAPR05MB4023.namprd05.prod.outlook.com>

Hi,

Am Samstag, den 11.12.2021, 19:09 -0500 schrieb Morgan Smith:
> Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
> > Rather than a new package, I think we can very well edit the
> > existing package in-place, so that we don't need to add a
> > meaningless deprecation.  For all intents and purposes, this still
> > is emacs-recutils -- it's still hosted alongside recutils even
> > though it's no longer bundled with it.
> 
> I have no clue if this is the intention or not but I always find that
> the emacs package names are in the format: emacs-FEATURE.  As in I
> can just do (load "FEATURE") to load the package and start
> exploring.  I was very confused when I first downloaded the package
> as (load "recutils") did nothing and I had to do (load "rec-
> mode").  I realize this convention isn't written down anywhere but I
> think maybe it should be because it's very helpful to me personally.
For the record, the convention is usually to use the upstream name, but
that's not always reasonable.  In this particular case, I'd argue that
emacs-recutils is equally good as it's still close enough to upstream,
plus the package does not solely contain rec-mode and ob-rec could
equally be seen as entry point.

As for loading FEATURE, that again only works for single-feature
libraries.  In addition, you shouldn't typically rely on (load
"FEATURE") or (require 'FEATURE) outside of other libraries anyway. 
Autoloads exist and Guix handles them.

Cheers





  reply	other threads:[~2021-12-12  0:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-11 19:39 [bug#52439] [PATCH 1/2] gnu: Add emacs-rec-mode Morgan.J.Smith
2021-12-11 19:46 ` [bug#52439] [PATCH 2/2] gnu: emacs-recutils: Deprecate in favor of emacs-rec-mode Morgan.J.Smith
2021-12-11 22:35 ` [bug#52439] [PATCH 1/2] gnu: Add emacs-rec-mode Liliana Marie Prikler
2021-12-12  0:09   ` Morgan Smith
2021-12-12  0:39     ` Liliana Marie Prikler [this message]
2021-12-12  1:15       ` Morgan Smith
2021-12-13 19:39         ` Liliana Marie Prikler
2021-12-14  0:54 ` [bug#52439] [PATCH] gnu: emacs-recutils: Update to 1.8.2-0.058dbe4 Morgan.J.Smith
2021-12-14 19:36   ` Liliana Marie Prikler
2021-12-14 20:34     ` bug#52439: " Liliana Marie Prikler

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=1d60848f3732844757e25a29db1d155dd7d885b3.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=52439@debbugs.gnu.org \
    --cc=Morgan.J.Smith@outlook.com \
    /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/guix.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.