[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GNU ELPA] Pulsar version 1.0.1

From: ELPA update
Subject: [GNU ELPA] Pulsar version 1.0.1
Date: Tue, 15 Aug 2023 17:05:13 -0400

Version 1.0.1 of package Pulsar has just been released in GNU ELPA.
You can now find it in M-x list-packages RET.

Pulsar describes itself as:

  Pulse highlight on demand or after select functions

More at

## Summary:


                            Protesilaos Stavrou

  This manual, written by Protesilaos Stavrou, describes the customization
  options for `pulsar' (or `pulsar.el'), and provides every other piece of
  information pertinent to it.

  The documentation furnished herein corresponds to stable version 1.0.0,
  released on 2023-08-12.  Any reference to a newer feature which does not
  yet form part of the latest tagged commit, is explicitly marked as such.

  Current development target is 1.1.0-dev.

## Recent NEWS:

                        CHANGE LOG OF PULSAR.EL

The newest release is at the top.  For further details, please consult
the manual: <>.

Version 1.0.0 on 2023-08-12

  • The `next-buffer' and `previous-buffer' commands are added to the
    default value of the user option `pulsar-pulse-functions'.  They
    will now trigger a pulse effect after they are called (if
    `pulsar-mode' is enabled in the current buffer or
    `pulsar-global-mode' is in use).

  • The command `pulsar-recenter-middle' is now an alias for
    `pulsar-recenter-center', instead of being the original name.  Users
    do not need to change anything on their end: this is just an
    internal arrangement to use a name that corresponds to the one of
    the underlying "recenter" mechanism.

  • The Lisp macro that was used to derive the Pulsar "recenter"
    commands has been removed.  The commands are `pulsar-recenter-top'
    and `pulsar-recenter-center'.  I originally thought the macro would
    be useful in more places, but I ended up relying on it only twice.

    Thanks to Ryan Kaskel for pointing out an intermediate typo/error I
    made while redefining the macro and before I decided to remove it
    altogether.  This was done as a comment on the GitHub mirror:

  • The Lisp macro `pulsar-pulse-with-face' is renamed to
    `pulsar-define-pulse-with-face'.  Its definition is updated to
    simplify how a Pulsar function is defined with a given face.
    Examples of such functions are `pulsar-pulse-line-red',

  • Pulsar now retrieves the absolute beginning of the minibuffer
    prompt.  This means that a pulse in the minibuffer will cover the
    text of the prompt, as opposed to only affecting the input area.  As
    such, the pulse is visible even if the minibuffer is empty
    (e.g. what happens with the default completion setup when calling

  • The manual provides instructions on how to set up Pulsar to produce
    a pulse when the minibuffer is activated.  It cannot be done with
    the `pulsar-pulse-functions', though the setup is not too involved.
    In short:

    │ (add-hook 'minibuffer-setup-hook #'pulsar-pulse-line)
    │ ;; OR something like this, replacing "blue" with one among red,
    │ ;; green, yellow, magenta, cyan:
    │ (add-hook 'minibuffer-setup-hook #'pulsar-pulse-line-blue)

Version 0.5.0 on 2022-08-19

  ⁃ Added convenience functions/commands to pulse a line using one of
    the provided faces.  These can be used interactively or via Lisp
    (e.g. be assigned to a hook).  They are:

    • `pulsar-pulse-line-red'
    • `pulsar-pulse-line-green'
    • `pulsar-pulse-line-yellow'
    • `pulsar-pulse-line-blue'
    • `pulsar-pulse-line-magenta'
    • `pulsar-pulse-line-cyan'

  ⁃ Deprecated `pulsar-pulse-on-window-change' due to complications it
    created in some edge cases.  Part of this effort was to fix a bug
    that pertained to a duplicate pulse when the pulsar commands were
    invoked via `M-x'.  The duplication had the effect of potentially
    overriding the color of the pulse such as if, say,
    `pulsar-pulse-line-red' was invoked while the `pulsar-face' was

  ⁃ Restored several command symbols to the default value of
    `pulsar-pulse-functions'.  Those were disabled to support the use
    option `pulsar-pulse-on-window-change', but as that is now removed
    we revert to the old and more predictable way of handling things.

  ⁃ Introduced conditionality that checks for `real-this-command'.  This
    is necessary for commands that have to fudge `this-command' to
    provide their functionality.  Such is the case with the
    `evil-scroll-up' and `evil-scroll-down' commands which are
    internally reported as
  …  …

reply via email to

[Prev in Thread] Current Thread [Next in Thread]