all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: Gdobbins <gdobbins@protonmail.com>
Cc: 26187@debbugs.gnu.org
Subject: bug#26187: Bug in indent-sexp
Date: Mon, 20 Mar 2017 09:20:25 -0400	[thread overview]
Message-ID: <87inn43x0m.fsf@users.sourceforge.net> (raw)
In-Reply-To: <edMndW2R6yeReqnOzTcnnOjIXQP11nlOH5iS8FbaHpSHzsqYGXO9JRYjF6ZbSKEnNY0hg-xORHOReNQpi1pd6PrwwAYSLzeNY-bls1FHEcU=@protonmail.com> (gdobbins@protonmail.com's message of "Sun, 19 Mar 2017 21:18:09 -0400")

Gdobbins <gdobbins@protonmail.com> writes:

> The refactor of indent-sexp in commit 3ee3995d105ff02f0fac540757431d36cb45c6c7 broke the assumption
>
> ;; If ENDPOS is nil, it is safe not to scan before point
> ;; since every line we indent is more deeply nested than point is.
>
> thereby breaking functionality in paredit. The attached patch fixes
> this.

Could you post the scenario which is broken?  I have a another pending
change to indent-sexp for Bug#25122 [1] which actually removes the
rescanning completely, but I'm not sure if that would rebreak this
scenario or fix it...

[1]: https://debbugs.gnu.org/cgi/bugreport.cgi?att=1;bug=25122;msg=74;filename=v2-0001-Don-t-reparse-the-sexp-in-indent-sexp-Bug-25122.patch





  reply	other threads:[~2017-03-20 13:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20  1:18 bug#26187: Bug in indent-sexp Gdobbins
2017-03-20 13:20 ` npostavs [this message]
2017-03-20 20:00   ` Gdobbins
2017-03-21  3:22     ` npostavs
2017-03-21  4:24       ` Gdobbins
2017-03-22  0:49 ` npostavs

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

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

  git send-email \
    --in-reply-to=87inn43x0m.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=26187@debbugs.gnu.org \
    --cc=gdobbins@protonmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.