From: Ian Eure <ian@digg.com>
To: Xavier Maillard <xma@gnu.org>
Cc: help-gnu-emacs@gnu.org, Leo <sdl.web@gmail.com>
Subject: Re: yasnippet and friends: usefull ?
Date: Wed, 29 Apr 2009 15:13:57 -0700 [thread overview]
Message-ID: <3173E455-E1A5-42EF-806C-D7FD210EE8C5@digg.com> (raw)
In-Reply-To: <200904282225.n3SMP36j017386@zogzog.maillard.mobi>
On Apr 28, 2009, at 3:25 PM, Xavier Maillard wrote:
>
> On 2009-04-28 07:34 +0100, Xavier Maillard wrote:
>> Hi,
>>
>> I was revamping my $TMP directory and found on old archive of
>> yasnippet.
>>
>> Does anybody is really using it ? I mean do you find easy to TAB
>> everytime you are typing code ? How do you use it in real life ?
>> Don't you think abbrev-* is easier and less intrusive ?
>
> I use a modified snippet.el that integrates into abbrev
> seamlessly. I
> like it better than yasnippet.
>
> Why ? Is it available somewhere ? How do you practically use it ?
> Along my previous post, I decided to try yasnippet. It is nice
> but you have to remember what is the "combo trigger" to use in
> order to have it does something ;)
>
(setq yas/trigger-key (kbd "SPC"))
The other I prefer about yasnippet is that it will expand snippets
containing non-word-constituent characters, which abbrev can't. So I
can't have "@p" expand to "@param" with abbrev, but I can with
yasnippet.
- Ian
next prev parent reply other threads:[~2009-04-29 22:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 22:25 yasnippet and friends: usefull ? Xavier Maillard
2009-04-29 0:49 ` Leo
2009-04-29 5:57 ` thierry.volpiatto
[not found] ` <mailman.6228.1240985098.31690.help-gnu-emacs@gnu.org>
2009-04-29 11:08 ` Richard Riley
2009-04-29 15:00 ` thierry.volpiatto
2009-05-02 6:18 ` thierry.volpiatto
[not found] ` <mailman.6255.1241017689.31690.help-gnu-emacs@gnu.org>
2009-04-29 16:23 ` Richard Riley
2009-04-29 22:13 ` Ian Eure [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-29 22:25 Xavier Maillard
2009-04-29 22:25 Xavier Maillard
2009-04-28 6:34 Xavier Maillard
2009-04-28 8:05 ` Leo
2009-04-28 17:37 ` Ian Eure
2009-04-29 18:07 ` Alberto Luaces
2009-04-29 17:33 ` Nikolaj Schumacher
2009-05-04 9:07 ` Mike Mattie
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=3173E455-E1A5-42EF-806C-D7FD210EE8C5@digg.com \
--to=ian@digg.com \
--cc=help-gnu-emacs@gnu.org \
--cc=sdl.web@gmail.com \
--cc=xma@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.
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).