unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thanos Apollo <public@thanosapollo.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: "Philip Kaludercic" <philipk@posteo.net>,
	"Daniel Martín" <mardani29@yahoo.es>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: [External] : Re: [NonGNU ELPA] Package suggestion: yeetube
Date: Wed, 04 Oct 2023 19:26:54 +0300	[thread overview]
Message-ID: <87wmw2xs97.fsf@thanosapollo.com> (raw)
In-Reply-To: <SJ0PR10MB54881427A6FF6EE4BE868542F3CBA@SJ0PR10MB5488.namprd10.prod.outlook.com>


Drew Adams <drew.adams@oracle.com> writes:

> How old?  Emacs 20?  What minimal version
> does that package itself require?  Does
> it, itself, need some compat support...?

Philip will give you a more concrete answer, but according to the 
documentation:

```
Requires: ((emacs "24.4") (compat "29.1.4.2"))

   There is no need to depend on ‘emacs 24.4’ specifically.  One 
   can
choose any newer version, if features not provided by Compat 
necessitate
it, for example bug fixes or UI improvements.

   In any file where compatibility forms are used, a

     (require 'compat)

   should be added early on.  In packages which are part of Emacs 
   itself
and which want to take advantage of Compat, the ‘noerror’ flag 
should be
specified: ‘(require 'compat nil 'noerror)’.  In the future a 
minimal
version of Compat may be added to the Emacs core, such that the
‘noerror’ flag will not be necessary anymore.
```

Not sure, but maybe something like this is a valid use case?

``` emacs-lisp
(compat-call defvar-keymap yeetube-mode-map
	     :doc "Keymap for yeetube commands"
	     "RET" #'yeetube-play
             ...
```             


-- 
Thanos Apollo
https://thanosapollo.com



  reply	other threads:[~2023-10-04 16:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04  7:24 [NonGNU ELPA] Package suggestion: yeetube Thanos Apollo
2023-10-04  8:39 ` Stefan Kangas
2023-10-04  8:48   ` Thanos Apollo
2023-10-04 12:50     ` Stefan Kangas
2023-10-04 13:37       ` Thanos Apollo
2023-10-05 10:24   ` Richard Stallman
2023-10-05 10:44     ` Thanos Apollo
2023-10-05 11:07     ` Ihor Radchenko
2024-02-11  7:43   ` Using tor & url Thanos Apollo
2023-10-04 13:14 ` [NonGNU ELPA] Package suggestion: yeetube Daniel Martín
2023-10-04 13:33   ` Thanos Apollo
2023-10-04 15:22     ` Philip Kaludercic
2023-10-04 15:35       ` [External] : " Drew Adams
2023-10-04 16:26         ` Thanos Apollo [this message]
2023-10-06  8:59           ` Philip Kaludercic
2023-10-04 15:37       ` Thanos Apollo
2023-10-04 13:27 ` Emanuel Berg
2023-10-05  2:15   ` Thanos Apollo

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=87wmw2xs97.fsf@thanosapollo.com \
    --to=public@thanosapollo.com \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=mardani29@yahoo.es \
    --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).