unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Yates <john@yates-sheets.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Bozhidar Batsov <bozhidar@batsov.dev>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Packages quality
Date: Fri, 7 Jan 2022 10:52:50 -0500	[thread overview]
Message-ID: <CAJnXXoh2Mp=oEq-eLhECCm6wH=2r0LGfQ20aGwc9HnTMK7Qs8w@mail.gmail.com> (raw)
In-Reply-To: <CADwFkm=TWUoG+pKUihefJpJmVvLzWSr-8m=4Rx7+hz3vmbpEsg@mail.gmail.com>

Stefan, you did indeed write 'package.el' which I then  misread
as 'use-package.el'.  My apologies.

I agree that finding a way to integrate straight-like capabilities
into emac's core package management is much to be desired.

/john

On Fri, Jan 7, 2022 at 7:16 AM Stefan Kangas <stefankangas@gmail.com> wrote:
>
> John Yates <john@yates-sheets.org> writes:
>
> > On Fri, Jan 7, 2022 at 2:56 AM Stefan Kangas <stefankangas@gmail.com> wrote:
> >>
> >> I don't know if this is what you mean, but one example that comes to
> >> mind is how straight.el is not at all integrated with package.el (which
> >> in your opinion, IIRC, could be rectified).
> >
> > As a very happy user of straight I feel that Radon Rosborough,
> > straight's author, is  being unfairly maligned.
>
> I don't understand.  How is it maligning, unfairly or otherwise, the
> author of some package to say that it could be integrated with another
> package?
>
> > He has integrated straight exactly as John Wiegley intended.  From
> > use-package's README.md:
>
> I believe the discussion was about package.el, not use-package.el.



-- 
John Yates
505 Tremont St, #803
Boston, MA 02116



  reply	other threads:[~2022-01-07 15:52 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <164145738158.2838.5769558384331859964@vcs2.savannah.gnu.org>
     [not found] ` <20220106082302.0A19CC0DA1E@vcs2.savannah.gnu.org>
2022-01-06 10:02   ` [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package Philip Kaludercic
2022-01-06 12:00     ` Stefan Kangas
2022-01-06 13:35       ` Philip Kaludercic
2022-01-06 14:30         ` Packages quality (was: [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package) Stefan Monnier
2022-01-06 15:03           ` Bozhidar Batsov
2022-01-06 17:07             ` Packages quality Stefan Monnier
2022-01-06 19:50               ` Tim Cross
2022-01-07  7:54               ` Stefan Kangas
2022-01-07 11:45                 ` John Yates
2022-01-07 12:16                   ` Stefan Kangas
2022-01-07 15:52                     ` John Yates [this message]
2022-01-07  7:55             ` Packages quality (was: [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package) Stefan Kangas
2022-01-07 10:22               ` Bozhidar Batsov
2022-01-07 10:54                 ` Stefan Kangas
2022-01-06 17:28           ` Packages quality Philip Kaludercic
2022-01-06 19:55         ` [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package Juri Linkov
2022-01-07  7:55         ` Stefan Kangas
2022-01-16 17:49           ` Philip Kaludercic
2022-01-16 22:19             ` Stefan Monnier
2022-01-19  8:57               ` Philip Kaludercic
2022-01-19 15:19                 ` Stefan Monnier
2022-01-16 22:32             ` Stefan Kangas
2022-01-16 23:16               ` Ergus
2022-01-19  9:05                 ` Philip Kaludercic
2022-01-16 23:47               ` Stefan Monnier
2022-01-19  9:03               ` Philip Kaludercic
2022-01-17  7:37             ` Jean Louis
2022-01-19  9:10               ` Philip Kaludercic
2022-01-07 10:02         ` Stefan Kangas
2022-01-10  1:18           ` Stefan Monnier
2022-01-07  9:38     ` Augusto Stoffel

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='CAJnXXoh2Mp=oEq-eLhECCm6wH=2r0LGfQ20aGwc9HnTMK7Qs8w@mail.gmail.com' \
    --to=john@yates-sheets.org \
    --cc=bozhidar@batsov.dev \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=stefankangas@gmail.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 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).