unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Danil Orlov <zargener@gmail.com>
To: Stefan <monnier@iro.umontreal.ca>
Cc: "João Távora" <joaotavora@gmail.com>, emacs-devel@gnu.org
Subject: Re: Including Yasnippet to Emacs
Date: Mon, 17 Mar 2014 23:09:42 +0200	[thread overview]
Message-ID: <20140317210942.GB28011@debian> (raw)
In-Reply-To: <jwv38ig4ofd.fsf-monnier+emacs@gnu.org>

Okay, I've got your point.

On Mon, Mar 17, 2014 at 03:36:42PM -0400, Stefan wrote:
> > I've checked those ones you noted, even snippet.el. They all are not so
> > powerful and user-friendly as yasnippet.
> 
> snippet.el is not designed to be user-friendly, but to be easy to
> integrate in a major-mode instead (yasnippet rather sucks in this
> regard, you end up needing to distribute umpteen little files instead).
> 
> [ BTW, part of the intention behind snippet.el is to make Edebug work
>   with them.  Si in some cases they may turn out to be more
>   user-friendly, rather than less so.  ]
> 
> As for "not so powerful", I'm not sure what you mean: they should be
> pretty much as powerful as yasnippet's since yasnippet will be written
> on top of them.  And of course, they can run any Lisp code you like.
> 
> > And they are all not manage keybindings.
> 
> This layer is not provided yet, indeed.  E.g. I want to link snippet.el with
> abbrevs, so the "table of snippets" will be an abbrev table.
> 
> > And probably not support expansion depending on context in simple way.
> 
> Not sure what "in a simple way" means.
> 
> > And docs are really stingy.
> 
> For skeleton.el, the system is trivial enough that I don't know what
> more docs we could provide.  For snippet.el, it's still in flux and
> there are indeed no docs yet, IIRC.
> 
> > And snippet language is not so powerful and readable, as in yasnippet.
> 
> "Readable" here is in the eye of the beholder.  But the whole idea
> behind snippet.el is to get rid of this dichotomy: you can write your
> snippets using the Lispish snippet.el syntax (i.e. a syntax that
> makes sense to me) or you can write them in the yasnippet syntax if
> you prefer $ over parentheses.
> 
> 
>         Stefan



      parent reply	other threads:[~2014-03-17 21:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-17  4:10 Including Yasnippet to Emacs Danil Orlov
2014-03-17 14:45 ` Stefan
2014-03-17 14:53   ` joakim
2014-03-17 17:15   ` João Távora
2014-03-17 17:42   ` Danil Orlov
2014-03-17 19:36     ` Stefan
2014-03-17 20:23       ` João Távora
2014-03-17 21:12         ` Danil Orlov
2014-03-17 21:09       ` Danil Orlov [this message]

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=20140317210942.GB28011@debian \
    --to=zargener@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).