From: Christopher Dimech <dimech@gmx.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Adding String to Beginning of Lines
Date: Tue, 10 Nov 2020 14:40:08 +0100 [thread overview]
Message-ID: <trinity-287bf496-d149-44d7-aacc-7cf699dd7d0b-1605015608250@3c-app-mailcom-bs07> (raw)
In-Reply-To: <87o8k5csqj.fsf@web.de>
I now have got 'rec-cont', which lets me pass a string.
How can I add a dafault if I don't pass a regex in the
mini-buffer.
(defun rec-cont (beg end regex)
(interactive "r\ns rec-cont regex: ")
(replace-regexp "^" regex nil beg end))
;; (replace-regexp "^" ";; + " nil beg end))
> Sent: Tuesday, November 10, 2020 at 1:16 PM
> From: "Michael Heerdegen" <michael_heerdegen@web.de>
> To: help-gnu-emacs@gnu.org
> Subject: Re: Adding String to Beginning of Lines
>
> Christopher Dimech <dimech@gmx.com> writes:
>
> > Have used the following
> >
> > (defun compfx ()
> > (interactive "r")
> > (query-replace-regexp "^" ";; + "))
>
> (defun compfx (beg end)
> (interactive "r")
> (query-replace-regexp "^" ";; + " nil beg end))
>
> Do you want to be asked interactively whether to replace each "match"?
> If not, we want to use something non-interactive instead of
> `query-replace-regexp'.
>
>
> Michael.
>
>
>
next prev parent reply other threads:[~2020-11-10 13:40 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 10:43 Adding String to Beginning of Lines Christopher Dimech
2020-11-10 11:10 ` tomas
2020-11-10 11:19 ` Christopher Dimech
2020-11-10 11:29 ` Christopher Dimech
2020-11-10 11:54 ` Michael Heerdegen
2020-11-10 11:58 ` Christopher Dimech
2020-11-10 12:07 ` Michael Heerdegen
2020-11-10 12:03 ` Christopher Dimech
2020-11-10 12:16 ` Michael Heerdegen
2020-11-10 13:40 ` Christopher Dimech [this message]
2020-11-10 14:06 ` Jean Louis
2020-11-10 14:29 ` Michael Heerdegen
2020-11-10 19:12 ` Jean Louis
2020-11-10 19:42 ` Michael Heerdegen
2020-11-10 21:22 ` Jean Louis
2020-11-11 10:59 ` Michael Heerdegen
2020-11-17 16:06 ` Jean Louis
2020-11-17 16:28 ` Michael Heerdegen
2020-11-10 22:31 ` Stefan Monnier
2020-11-10 23:00 ` Drew Adams
2020-11-11 21:37 ` Michael Heerdegen
2020-11-10 14:16 ` Michael Heerdegen
2020-11-10 14:38 ` Christopher Dimech
2020-11-10 14:49 ` Michael Heerdegen
2020-11-10 17:52 ` Christopher Dimech
2020-11-10 18:03 ` Michael Heerdegen
2020-11-10 18:25 ` Christopher Dimech
2020-11-10 18:49 ` Michael Heerdegen
2020-11-10 18:56 ` Christopher Dimech
2020-11-10 19:02 ` Michael Heerdegen
2020-11-10 19:29 ` Christopher Dimech
2020-11-10 20:07 ` Michael Heerdegen
2020-11-10 22:45 ` tomas
2020-11-11 11:16 ` Michael Heerdegen
2020-11-11 13:22 ` Christopher Dimech
2020-11-11 13:56 ` Michael Heerdegen
2020-11-11 14:07 ` tomas
2020-11-11 14:49 ` Christopher Dimech
2020-11-11 17:20 ` Christopher Dimech
2020-11-11 18:12 ` Michael Heerdegen
2020-11-11 18:25 ` Stefan Monnier
2020-11-11 18:35 ` Christopher Dimech
2020-11-10 14:03 ` Jean Louis
2020-11-10 11:42 ` Michael Heerdegen
2020-11-10 18:47 ` H. Dieter Wilhelm
2020-11-12 19:01 ` Dante Catalfamo
2020-11-14 22:09 ` Jamie Beardslee
2020-11-14 23:17 ` Stefan Monnier
2020-11-14 23:39 ` Jamie Beardslee
2020-11-15 9:12 ` tomas
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=trinity-287bf496-d149-44d7-aacc-7cf699dd7d0b-1605015608250@3c-app-mailcom-bs07 \
--to=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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.
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).