unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: larsi@gnus.org, 55788@debbugs.gnu.org, mardani29@yahoo.es
Subject: bug#55788: [PATCH] Improve documentation of the raise-sexp command
Date: Mon, 06 Jun 2022 13:44:17 +0300	[thread overview]
Message-ID: <83mteq841q.fsf@gnu.org> (raw)
In-Reply-To: <86h74ywae2.fsf@mail.linkov.net> (message from Juri Linkov on Mon, 06 Jun 2022 10:33:25 +0300)

> Cc: 55788@debbugs.gnu.org, Daniel Martín <mardani29@yahoo.es>
> From: Juri Linkov <juri@linkov.net>
> Date: Mon, 06 Jun 2022 10:33:25 +0300
> 
> >   "Raise ARG sexps higher up the tree.
> > This means that the ARGth enclosing form will be deleted and
> > replaced with the form that follows point.
> >
> > For instance, if you have:
> >
> >   (let ((foo 2))
> >     (progn
> >       (setq foo 3)
> >       (zot)
> >       (+ foo 2)))
> >
> > and point is before (zot), `M-x raise-sexp' will give you
> >
> >   (let ((foo 2))
> >     (zot))"
> 
> It seems that new docstring suggests that `M-2 M-x raise-sexp' will give
> 
>   (zot)
> 
> whereas really it will give
> 
>   (let ((foo 2))
>     (zot)
>     (+ foo 2))
> 
> since ARG is the number of sexps that follow point and that will be raised.

Right.  Is the below better?

    Raise ARG sexps one level higher up the tree.

  This function removes the sexp enclosing the form which follows
  point, and then re-inserts ARG sexps following point, thus raising
  them one level up.






  reply	other threads:[~2022-06-06 10:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m1y1ydnuj5.fsf.ref@yahoo.es>
2022-06-04  0:26 ` bug#55788: [PATCH] Improve documentation of the raise-sexp command Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-04 11:58   ` Lars Ingebrigtsen
2022-06-06  7:33     ` Juri Linkov
2022-06-06 10:44       ` Eli Zaretskii [this message]
2022-06-06 12:57         ` Lars Ingebrigtsen
2022-06-06 13:05           ` Eli Zaretskii
2022-06-06 13:13             ` Lars Ingebrigtsen
2022-06-06 14:11               ` Eli Zaretskii

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=83mteq841q.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=55788@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=larsi@gnus.org \
    --cc=mardani29@yahoo.es \
    /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).