Pierre Rouleau issues

Results 34 issues of


Pierre Rouleau

Fix byte compiler warning about functions obsolete since Emacs 26.1

Coding issue: code transformation commands should use the '*' in the interactive spec stating they do not modify read-only buffers.

## Expected code behavior The interactive functions that transform code, such as `sp-add-to-previous-sexp` should use the **"*"** character in the interactive form to prevent operation inside a read-only buffer. So...

waiting-for-reporter

Question: how can a post-handler modify position of point?

I'm new to smartparens and have read the manual/wiki trying to find a way to solve problems the transformation commands (such as `sp-forward-sexp`) leave when applied to Erlang code. -...

bug

waiting-for-reporter

Make sp-forward-symbol and sp-backward-symbol skip comments.

The change diff seems bigger that it really is. The change include: - A new function: `sp-inside-comment` that returns non-nil when point is inside comment - Modification of the sp-forward-symbol`:...

(sp-add-to-previous-sexp 2) lead to unbalanced block in Erlang.

## Expected behavior Starting with following Erlang code:, with point being `|` ``` erlang AList = [0, 1, [2, 3], |4, 5]. ``` I would expect that executing `(sp-backward-slurp-sexp 2)`...

sp-backward-symbol does not skip over comment in Erlang code.

## Expected behavior With located at position marked by ∎ in following Erlang code in erlang-mode buffer: ``` erlang start_app(App) -> % first clause ∎start_app(App, temporary). ``` Executing `M-x sp-backward-symbol`...

Bug? lispy-unbind-variable does not replace the unbound variable with its value as described in docs

- Lispy version: lispy-20210121.926 - Tested on Emacs 26.3 and 27.1 - Wanted behavior description: [lispy-unbind-variable doc](http://oremacs.com/lispy/#lispy-unbind-variable) - Observed behavior: Start with the following code and placing the cursor at...

Pierre Rouleau