unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Protesilaos Stavrou <info@protesilaos.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [ELPA] Add 'pulsar' package
Date: Sun, 20 Mar 2022 08:43:19 +0200	[thread overview]
Message-ID: <87o821f7js.fsf@protesilaos.com> (raw)
In-Reply-To: <87h77x51d6.fsf@posteo.net>

On 2022-03-16, 16:05 +0000, Philip Kaludercic <philipk@posteo.net> wrote:

>>> I have no real opinion on this, I just wanted to bring it up in case you
>>> hadn't considered it before (and also because in this case, at least from
>>> what I understand the package does, it should be rather easy).
>>
>> I think a standalone package and a patch for 'master' are not mutually
>> exclusive.  As I wrote before, we can deprecate pulsar when Emacs 29 is
>> the new stable and has this functionality built-in.
>>
>> As for whether such a patch would be easy, I admit that I do not know
>> how best to implement it.  If you or anyone else can write such a patch,
>> please do it.
>
> I guess it might depend on how many features you want to re-implement in
> the core. Please don't misinterpret this, but I think that the core
> functionality, pulsing a line after certain commands, could be done by
> providing a single user option, with a custom setter.

As I wrote before, I do not know how best to do this in core.  This is
not me faking ignorance to support a different opinion: I genuinely do
not know how to do this with a single option.  Please do it if you
can---it will also help me learn something new.

At any rate, this is not what this thread is about.  I think pulsar
belongs in the archive.  I post on emacs-devel to give others a chance
to point out any obvious flaws with the package.  If there are none, the
patch must be installed in elpa.git (I have write access and can do that
myself, if needed).

There are people who are already using pulsar and I believe there is no
technical reason why it should not be in GNU ELPA.

To your point though about patching the core, I repeat what I already
stated in unequivocal terms: I will deprecate pulsar when the Emacs
version that includes its functionality becomes the stable version of
Emacs.  Until then, the package has a good reason to exist and be
readily available.

-- 
Protesilaos Stavrou
https://protesilaos.com



  reply	other threads:[~2022-03-20  6:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14  7:39 [ELPA] Add 'pulsar' package Protesilaos Stavrou
2022-03-14  8:24 ` Philip Kaludercic
2022-03-14  8:38   ` Protesilaos Stavrou
2022-03-14 16:41     ` Philip Kaludercic
2022-03-16 12:14       ` Protesilaos Stavrou
2022-03-16 16:05         ` Philip Kaludercic
2022-03-20  6:43           ` Protesilaos Stavrou [this message]
2022-03-20 11:29             ` Philip Kaludercic
2022-03-22 10:37               ` Protesilaos Stavrou
2022-03-23  9:03                 ` Philip Kaludercic

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=87o821f7js.fsf@protesilaos.com \
    --to=info@protesilaos.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).