Version 0.4.0 of package Pulsar has just been released in GNU ELPA.
You can now find it in M-x package-list RET.
Pulsar describes itself as:
Pulse highlight on demand or after select functions
More at https://elpa.gnu.org/packages/pulsar.html
Recent NEWS:
━━━━━━━━━━━━━━━━━━━━━━━━━
CHANGE LOG OF PULSAR.EL
━━━━━━━━━━━━━━━━━━━━━━━━━
The newest release is at the top. For further details, please consult
the manual: <https://protesilaos.com/emacs/pulsar>.
Version 0.4.0 on 2022-07-19
═══════════════════════════
⁃ Added the user option `pulsar-pulse-on-window-change'. This covers
all commands or functions that affect the current window, so there
is no need to include them individually in the
`pulsar-pulse-functions'. Users who prefer to trigger a pulse only
after select functions (e.g. only after `other-window') are advised
to set this user option to nil and update the
`pulsar-pulse-functions' accordingly. Thanks to Ivan Popovych for
the patch (commit `b1a78dd').
⁃ Changed the default value of `pulsar-pulse-functions' to omit all
those commands which are already covered by the aforementioned. In
the interest of continuity, the old value is kept in the source
code, with the relevant symbols commented out.
⁃ Named the mailing list email address as the `Maintainer:' of Pulsar.
The package headers help the user find our primary sources and/or
communication channels. This change conforms with work being done
upstream in package.el by Philip Kaludercic. I was informed about
it here:
<https://lists.sr.ht/~protesilaos/general-issues/%3C875ykl84yi.fsf%40posteo.net%3E>.
⁃ Updated the documentation, where necessary and made other minor
tweaks to the code.
Version 0.3.0 on 2022-04-08
═══════════════════════════
⁃ Changed the source repository from GitLab to SourceHut:
<https://git.sr.ht/~protesilaos/pulsar>. Use the mailing list to
start a discussion, report a bug, send a patch, etc.:
<https://lists.sr.ht/~protesilaos/pulsar>. The GitLab URL will
serve as a mirror from now on (a GitHub mirror is still available
and will remain that way).
⁃ Refined how Pulsar behaves in the case of the last line. Basically,
when the last line cannot be highlighted we want to pulse the one
right above. Thanks to JD Smith for fine-tuning this behaviour in
merge request 1 over at the GitLab mirror:
<https://gitlab.com/protesilaos/pulsar/-/merge_requests/1> (exempt
from the requirement to assign copyright to the Free Software
Foundation as it is below the threshold).
⁃ Ensured that the Pulsar effect are limited to the current window
when the buffer is displayed in multiple windows. This avoids the
common problem of simultaneous highlights in multiple locations,
which confuse rather than inform the user of where the point is.
Thanks to Aymeric Agon-Rambosson for the contribution in merge
request 2 over at the GitLab mirror:
<https://gitlab.com/protesilaos/pulsar/-/merge_requests/2>. Aymeric
has assigned copyright to the Free Software Foundation.
⁃ Wrote a buffer-local and a global minor mode that sets up Pulsar.
This supersedes the old design which had a built-in assumption that
the "pulse line" effect should always be global. Now the user has
more flexibility. They may also disable Pulsar on demand. Note
that pulsar still only triggers its effect for entries in the user
option `pulsar-pulse-functions'. Thanks to Rudolf Adamkovič for the
feedback in issue 9 over at the GitLab mirror:
<https://gitlab.com/protesilaos/pulsar/-/issues/9>.
⁃ Implement the `pulsar-highlight-dwim' command. It is like the
`pulsar-highlight-line' except it also understands regions, be they
regular or rectangular. Thanks to Mark Barton for the feedback in
issue 13 over at the GitLab mirror:
<https://gitlab.com/protesilaos/pulsar/-/issues/13>.
⁃ Clarified some technical points in various doc strings and the
manual, such as what is the `pulsar-delay' and the
`pulsar-iterations'. Thanks to Rudolf Adamkovič for the feedback in
issue 12 over at the GitLab mirror:
<https://gitlab.com/protesilaos/pulsar/-/issues/12>.
Version 0.2.0 on 2022-03-16
═══════════════════════════
⁃ Fixed an inconsistency that was present when Emacs was running in a
… …