all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: mardani29@yahoo.es, 55788@debbugs.gnu.org, juri@linkov.net
Subject: bug#55788: [PATCH] Improve documentation of the raise-sexp command
Date: Mon, 06 Jun 2022 16:05:45 +0300	[thread overview]
Message-ID: <83a6aq7xhy.fsf@gnu.org> (raw)
In-Reply-To: <8735gix83b.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon,  06 Jun 2022 14:57:44 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Juri Linkov <juri@linkov.net>,  55788@debbugs.gnu.org,  mardani29@yahoo.es
> Date: Mon, 06 Jun 2022 14:57:44 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > 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.
> 
> Much better.  But perhaps ARG should be renamed to NUM or something to
> make things clearer.

Like this?

  (defun raise-sexp (&optional n)
    "Raise N sexps one level higher up the tree.

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

  Interactively, N is the numeric prefix argument, and defaults to 1.

  For instance, if you have:

    (let ((foo 2))
      (progn
	(setq foo 3)
	(zot)
	(+ foo 2)))

  and point is before (zot), \\[raise-sexp] will give you

    (let ((foo 2))
      (zot))"





  reply	other threads:[~2022-06-06 13:05 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
2022-06-06 12:57         ` Lars Ingebrigtsen
2022-06-06 13:05           ` Eli Zaretskii [this message]
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

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

  git send-email \
    --in-reply-to=83a6aq7xhy.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 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.