From: Jesper Harder <harder@myrealbox.com>
Subject: Re: Using comment-region in function
Date: Thu, 13 May 2004 17:44:21 +0200 [thread overview]
Message-ID: <m3pt98xrfu.fsf@defun.localdomain> (raw)
In-Reply-To: ser7to9wic.fsf@pc020549.dhcp.germanlloyd.org
hoel@gl-group.com (Berthold Höllmann) writes:
> Jesper Harder <harder@myrealbox.com> writes:
>
>> Use `comment-region'?
>>
>> (comment-region
>> (point)
>> (progn
>> (insert "This is a comment")
>> (point)))
>
> This does not work for skeletons:
I don't know anything about skeletons, but ...
> (define-skeleton head
> "Insert a standard header for C files"
> ""
> (comment-region
> (point)
> (blurb-head)
> (point)))
is obviously wrong. You can't leave out the `progn' from my example.
--
Jesper Harder <http://purl.org/harder/>
next prev parent reply other threads:[~2004-05-13 15:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 11:45 Using comment-region in function Berthold Höllmann
2004-05-13 12:09 ` Jesper Harder
2004-05-13 15:28 ` Berthold Höllmann
2004-05-13 15:44 ` Jesper Harder [this message]
2004-05-13 19:01 ` Berthold Höllmann
2004-05-13 20:48 ` Stefan Monnier
2004-05-13 15:44 ` Kevin Rodgers
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=m3pt98xrfu.fsf@defun.localdomain \
--to=harder@myrealbox.com \
/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).