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 19:56:02 +0100 [thread overview]
Message-ID: <trinity-3a4c8ec3-6837-4fcc-a76f-4a2543a299c8-1605034562125@3c-app-mailcom-bs15> (raw)
In-Reply-To: <87361hhwtd.fsf@web.de>
Still getting the keyseq as undefined.
> Sent: Tuesday, November 10, 2020 at 7:49 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:
>
> > The update is still giving me trouble though. Could be a problem with passing the arguments
> > to rec-field-nwltok
> >
> > I have the following
> >
> > (defun rec-field-nwltok (beg end nwltok)
> > (interactive
> > (list (region-beginning)
> > (region-end)
> > (read-string "rec-field-nwltok: " nil nil ";; + ")))
> > (replace-regexp "^" nwltok nil beg end) )
> >
> > (add-hook 'emacs-lisp-mode-hook
> > (defun myrec-field-nwltok ()
> > (define-key emacs-lisp-mode-map (kbd "H-z") #'rec-field-nwltok)))
>
> That works well for me. Of what kind is that trouble?
>
> Michael.
>
>
>
next prev parent reply other threads:[~2020-11-10 18:56 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
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 [this message]
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-3a4c8ec3-6837-4fcc-a76f-4a2543a299c8-1605034562125@3c-app-mailcom-bs15 \
--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).