From: "Alberto Simões" <albie@alfarrabio.di.uminho.pt>
Subject: Automatically closing braces/parenthesis, etc
Date: Sun, 17 Jul 2005 19:43:36 +0100 [thread overview]
Message-ID: <42DAA6D8.2030904@alfarrabio.di.uminho.pt> (raw)
Hi
I found in this list archive that if I add the following code to my
.emacs, I get automatically closing braces, etc
(setq skeleton-pair t)
(global-set-key "(" 'skeleton-pair-insert-maybe)
(global-set-key "[" 'skeleton-pair-insert-maybe)
(global-set-key "\"" 'skeleton-pair-insert-maybe)
(global-set-key "'" 'skeleton-pair-insert-maybe)
(global-set-key "{" 'skeleton-pair-insert-maybe)
And it is true. Unfortuantely, this does not work under CPerl mode.
Probably because CPerl redefines something. Is there any easy way to go
around it?
Thanks
Alberto
--
Alberto Simões - Departamento de Informática - Universidade do Minho
Campus de Gualtar - 4710-057 Braga - Portugal
next reply other threads:[~2005-07-17 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-17 18:43 Alberto Simões [this message]
[not found] <mailman.843.1121626467.20277.help-gnu-emacs@gnu.org>
2005-07-17 21:34 ` Automatically closing braces/parenthesis, etc Stefan Monnier
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=42DAA6D8.2030904@alfarrabio.di.uminho.pt \
--to=albie@alfarrabio.di.uminho.pt \
/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).