unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Kost <alezost@gmail.com>
To: Thorsten Wilms <t_w_@freenet.de>
Cc: 31069@debbugs.gnu.org
Subject: bug#31069: emacs-smartparens: sp-forward-barf-sexp broken
Date: Sat, 07 Apr 2018 18:19:58 +0300	[thread overview]
Message-ID: <87sh87xcv5.fsf@gmail.com> (raw)
In-Reply-To: <c5728883-472b-8f0c-c1b3-abdfa752c5cf@freenet.de> (Thorsten Wilms's message of "Fri, 6 Apr 2018 22:35:04 +0200")

Thorsten Wilms (2018-04-06 22:35 +0200) wrote:

> On 05.04.2018 21:25, Alex Kost wrote:
>
>> It probably wouldn't help but... all these commands work for me without
>> any error (I use smartparens 1.11 installed with Guix).
>>
>> I don't use "smartparens-mode", I use these commands directly (bound to
>> some keys).  This is the configuration for smartparens I have in my
>> emacs config file:
>>
>> (with-eval-after-load 'smartparens
>>    (require 'smartparens-config nil t)
>>    (setq
>>     sp-navigate-reindent-after-up nil
>>     sp-ignore-modes-list nil
>>     sp-wrap-entire-symbol 'globally))
>
> 1.11 here, too.
>
> That piece of configuration doesn't affect the issue; but now I can say
> that it doesn't matter if smartparens-mode or smartparens-strict-mode or
> neither is active, slurp works, barf doesn't.
>
> I'm back to paredit, but would still like to figure this out.

Sorry, I don't know what could cause your problem.  My only idea is
maybe you have some mixed (incompatible) packages both from Guix and
from (M)ELPA (for example, "dash.el" from Melpa and "smartparens" from
Guix).  Look at "M-x list-load-path-shadows".

-- 
Alex

  reply	other threads:[~2018-04-07 15:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05 10:12 bug#31069: emacs-smartparens: sp-forward-barf-sexp broken Thorsten Wilms
2018-04-05 19:25 ` Alex Kost
2018-04-06 20:35   ` Thorsten Wilms
2018-04-07 15:19     ` Alex Kost [this message]
2018-04-07 18:54       ` Thorsten Wilms
2018-04-18 23:34         ` Christopher Lemmer Webber
2018-04-07 19:09     ` Oleg Pykhalov
2018-04-08 18:21       ` Alex Kost

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sh87xcv5.fsf@gmail.com \
    --to=alezost@gmail.com \
    --cc=31069@debbugs.gnu.org \
    --cc=t_w_@freenet.de \
    /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/guix.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).