From: Juri Linkov <juri@jurta.org>
To: Eli Barzilay <eli@barzilay.org>
Cc: 4136@emacsbugs.donarmstrong.com
Subject: bug#4136: 23.1; delete-pair
Date: Fri, 14 Aug 2009 02:28:21 +0300 [thread overview]
Message-ID: <87eirfs56q.fsf@mail.jurta.org> (raw)
In-Reply-To: <19075.45378.67131.491453@winooski.ccs.neu.edu> (Eli Barzilay's message of "Thu, 13 Aug 2009 02:22:58 -0400")
> `delete-pair' is deleting what it documents -- instead of removing the
> open paren of the following sexp, it deletes the current one. So, if
> the cursor is on some whitespace that precedes an expression, the
> whitespace is deleted, and the open paren is left intact.
This should be fixed with the following patch:
Index: lisp/emacs-lisp/lisp.el
===================================================================
RCS file: /sources/emacs/emacs/lisp/emacs-lisp/lisp.el,v
retrieving revision 1.102
diff -u -r1.102 lisp.el
--- lisp/emacs-lisp/lisp.el 22 Jul 2009 02:45:37 -0000 1.102
+++ lisp/emacs-lisp/lisp.el 13 Aug 2009 23:27:42 -0000
@@ -530,8 +530,12 @@
(defun delete-pair ()
"Delete a pair of characters enclosing the sexp that follows point."
(interactive)
- (save-excursion (forward-sexp 1) (delete-char -1))
- (delete-char 1))
+ (save-excursion
+ (forward-sexp 1)
+ (save-excursion
+ (backward-sexp 1)
+ (delete-char 1))
+ (delete-char -1)))
(defun raise-sexp (&optional arg)
"Raise ARG sexps higher up the tree."
--
Juri Linkov
http://www.jurta.org/emacs/
prev parent reply other threads:[~2009-08-13 23:28 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 6:22 bug#4136: 23.1; delete-pair Eli Barzilay
2009-08-13 9:53 ` martin rudalics
2009-08-13 23:29 ` Juri Linkov
2009-08-14 1:18 ` Eli Barzilay
2009-08-14 15:50 ` Stefan Monnier
2009-08-14 22:45 ` Juri Linkov
2009-08-15 1:46 ` Eli Barzilay
2009-08-15 23:06 ` Juri Linkov
2009-08-16 0:00 ` Eli Barzilay
2009-08-17 0:46 ` Juri Linkov
2009-08-17 3:13 ` Eli Barzilay
2009-08-17 21:17 ` Juri Linkov
2009-08-18 7:13 ` martin rudalics
2009-08-19 0:48 ` Juri Linkov
2020-09-14 14:08 ` Lars Ingebrigtsen
2020-09-14 19:12 ` Juri Linkov
2020-09-15 12:27 ` Lars Ingebrigtsen
2020-09-15 18:07 ` Juri Linkov
2020-09-17 14:45 ` Lars Ingebrigtsen
2020-09-18 8:35 ` Juri Linkov
2020-09-18 10:59 ` Lars Ingebrigtsen
2020-09-21 19:12 ` Juri Linkov
2020-09-22 14:45 ` Lars Ingebrigtsen
2020-09-22 18:18 ` Juri Linkov
2020-09-23 13:15 ` Lars Ingebrigtsen
2020-11-12 20:21 ` Juri Linkov
2020-11-12 21:16 ` Basil L. Contovounesios
2020-11-13 8:29 ` Juri Linkov
2020-11-16 20:55 ` Juri Linkov
2020-11-16 21:37 ` Drew Adams
2009-08-16 10:27 ` martin rudalics
2009-08-18 3:10 ` Stefan Monnier
2009-08-19 0:47 ` Juri Linkov
2009-08-15 10:11 ` martin rudalics
2009-08-14 7:17 ` martin rudalics
2009-08-14 22:45 ` Juri Linkov
2009-08-15 10:11 ` martin rudalics
2009-08-15 23:03 ` Juri Linkov
2009-08-16 10:27 ` martin rudalics
2009-08-13 23:28 ` Juri Linkov [this message]
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eirfs56q.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=4136@emacsbugs.donarmstrong.com \
--cc=eli@barzilay.org \
/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/emacs.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).