From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Danil Orlov Newsgroups: gmane.emacs.devel Subject: Re: Including Yasnippet to Emacs Date: Mon, 17 Mar 2014 23:12:54 +0200 Message-ID: <20140317211254.GC28011@debian> References: <20140317041012.GA24472@debian> <20140317174244.GA28011@debian> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1395090778 315 80.91.229.3 (17 Mar 2014 21:12:58 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 17 Mar 2014 21:12:58 +0000 (UTC) Cc: emacs-devel@gnu.org To: =?iso-8859-1?Q?Jo=E3o_T=E1vora?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Mar 17 22:13:08 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WPeqI-00029J-WD for ged-emacs-devel@m.gmane.org; Mon, 17 Mar 2014 22:13:07 +0100 Original-Received: from localhost ([::1]:60235 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPeqI-0004Uy-D5 for ged-emacs-devel@m.gmane.org; Mon, 17 Mar 2014 17:13:06 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39942) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPeqE-0004UW-QD for emacs-devel@gnu.org; Mon, 17 Mar 2014 17:13:03 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WPeqD-00068z-DT for emacs-devel@gnu.org; Mon, 17 Mar 2014 17:13:02 -0400 Original-Received: from mail-ee0-x232.google.com ([2a00:1450:4013:c00::232]:56584) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPeqD-00068v-5e for emacs-devel@gnu.org; Mon, 17 Mar 2014 17:13:01 -0400 Original-Received: by mail-ee0-f50.google.com with SMTP id c13so4701636eek.9 for ; Mon, 17 Mar 2014 14:13:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=2MvFdpB4WOukemDX5AjobM0bVmneJA8b9p+M3jvjgV4=; b=Iu3q1jxyMatNxGMlogVxlgFEgIZEQCQ5xyVUxmbL2ZdKO/o/rgxMegUywVnlhXk+KV RTDWJzJ8Tp0M1IAYJYlRTFYN0TCxpe9seJwZlPZDqenITW4kh6v55lyWokMlxTd93wqZ 9WOlu2X13JcKdZFl08SIc7FK6NKivFSGZmQFkhRsQ9VJdgKDLQY22EZcIFDMotpCstbi aYj4on2RWQcm5VJc91shCVV+X0E86TistyfiHMAdmjywlxyhCyOMuBaLz+cGgt+7vwAH MkABNYzQF7Lply/C1W/gWJ+g/PvHvA//g+yD7DMYe3ZO0q8G6t9igKoLeDvXWXowublz 5NWg== X-Received: by 10.15.93.201 with SMTP id w49mr10493943eez.69.1395090780243; Mon, 17 Mar 2014 14:13:00 -0700 (PDT) Original-Received: from debian ([2001:5c0:1400:a::af]) by mx.google.com with ESMTPSA id i47sm42150362eeg.6.2014.03.17.14.12.57 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Mon, 17 Mar 2014 14:12:59 -0700 (PDT) Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4013:c00::232 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:170462 Archived-At: Can you explain me about snippet.el ? I've found this one: http://www.emacswiki.org/emacs/SnippetMode But as far as I understand you, you working over some backend engine for yasnippet? On Mon, Mar 17, 2014 at 08:23:58PM +0000, João Távora wrote: > Stefan writes: > > > 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). > > Actually, you can compile these umpteen little files into one file per > mode. See `yas-compile-directory'. Few use it AFAIK, but it's there and > it should work (at least the tests show it does). > > And that's because yasnippet already has an elisp interface to defining > snippets, `yas-define-snippets'. There is definitely some suckage to it, > otherwise I wouldn't be writing snippet.el, but users or distribtors > aren't forced to deal with those million files. > > > [ 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. ] > > Indeed, I've answered many bugs from those who don't understand why > snippets don't work as intended, and I don't blame them. > > > 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. > > Danil, snippet.el is in its core just as powerful as yasnippet. Just a > few bits are missing like in-snippet expansions and snippet revival > after undo, but I plan to (re)implement them all. > > >> 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 I intend to keep the familiar yasnippet keying mechanism in > yasnippet.el. In general yasnippet will keep most backward > compatibility. > > > more docs we could provide. For snippet.el, it's still in flux and > > there are indeed no docs yet, IIRC. > > `define-snippet's docstring contains the gist of what that main entry > point will be. It's quite heavy at 60 lines, so maybe parts of it belong > to the manual, but it should give you an idea of what the defined > snippets can do. Did you read this docstring, Danil? > >