From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Proposing new function for basic editing
Date: Tue, 6 Feb 2024 08:05:33 +0100 [thread overview]
Message-ID: <CAO48Bk-KmVVhPF=MLTjpqLmmaM+=-3H8_boK+cA05t9aWPXCWQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1521 bytes --]
Hi,
I really don't know if this is useful for more people or it's just me. In
the elisp I write, I have ended up more than once wrapping the point or the
active region with two strings.
I normally use a yasnippet for this, so I really don't use elisp ;-)
But when I need this for a package, I end up replicating the following
function where I need it:
--- cut here ---
(defun surround-region-or-point (before after &optional put-after)
"Insert `before' before mark or region,
`after' after mark or region and
put mark after `after' if `put-after' is not nil"
(if (use-region-p)
(with-restriction (region-beginning) (region-end)
;; Insert `before' before region
(goto-char (point-min))
(insert before)
(goto-char (point-max))
;; Insert `after' after region
(if put-after
(insert after) ; put point after inserted string
(save-excursion (insert after)))) ; put point after region
(progn
(insert before)
(if put-after
(insert after) ; put point after both strings
(save-excursion (insert after)))))) ; put point between strings
--- cut here ---
I was wondering if it would make sense to have this in the emacs lisp
library once and for good.
Best, /PA
--
Fragen sind nicht da, um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet
[-- Attachment #2: Type: text/html, Size: 2139 bytes --]
next reply other threads:[~2024-02-06 7:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 7:05 Pedro Andres Aranda Gutierrez [this message]
2024-02-06 8:14 ` Proposing new function for basic editing Philip Kaludercic
2024-02-06 10:34 ` Pedro Andres Aranda Gutierrez
2024-02-06 8:25 ` Adam Porter
2024-02-06 9:16 ` Pedro Andres Aranda Gutierrez
2024-02-06 17:29 ` Juri Linkov
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='CAO48Bk-KmVVhPF=MLTjpqLmmaM+=-3H8_boK+cA05t9aWPXCWQ@mail.gmail.com' \
--to=paaguti@gmail.com \
--cc=emacs-devel@gnu.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).