From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Newsgroups: gmane.emacs.devel Subject: Re: Including Yasnippet to Emacs Date: Mon, 17 Mar 2014 15:36:42 -0400 Message-ID: References: <20140317041012.GA24472@debian> <20140317174244.GA28011@debian> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1395085016 28528 80.91.229.3 (17 Mar 2014 19:36:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 17 Mar 2014 19:36:56 +0000 (UTC) Cc: =?windows-1252?B?Sm/jbyBU4XZvcmE=?= , emacs-devel@gnu.org To: Danil Orlov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Mar 17 20:37:04 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 1WPdLM-0004kx-0B for ged-emacs-devel@m.gmane.org; Mon, 17 Mar 2014 20:37:04 +0100 Original-Received: from localhost ([::1]:59905 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPdLL-0005u8-Ir for ged-emacs-devel@m.gmane.org; Mon, 17 Mar 2014 15:37:03 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49626) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPdL9-0005dX-Sf for emacs-devel@gnu.org; Mon, 17 Mar 2014 15:36:59 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WPdL2-0002X6-Cc for emacs-devel@gnu.org; Mon, 17 Mar 2014 15:36:51 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:28134) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPdL2-0002X2-8z for emacs-devel@gnu.org; Mon, 17 Mar 2014 15:36:44 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EABK/CFHO+KKg/2dsb2JhbABEvw4Xc4IeAQEEAVYjBQsLDiYSFBgNJIgeBsEtkQoDjhiWYoFegxM X-IPAS-Result: Av4EABK/CFHO+KKg/2dsb2JhbABEvw4Xc4IeAQEEAVYjBQsLDiYSFBgNJIgeBsEtkQoDjhiWYoFegxM X-IronPort-AV: E=Sophos;i="4.84,565,1355115600"; d="scan'208";a="52382463" Original-Received: from 206-248-162-160.dsl.teksavvy.com (HELO pastel.home) ([206.248.162.160]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 17 Mar 2014 15:36:43 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 0A38D6028B; Mon, 17 Mar 2014 15:36:43 -0400 (EDT) In-Reply-To: <20140317174244.GA28011@debian> (Danil Orlov's message of "Mon, 17 Mar 2014 19:42:44 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.181 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:170457 Archived-At: > 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