unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: thierry.volpiatto@gmail.com
To: help-gnu-emacs@gnu.org
Subject: Re: yasnippet and friends: usefull ?
Date: Wed, 29 Apr 2009 17:00:50 +0200	[thread overview]
Message-ID: <87tz47sdwd.fsf@tux.homenetwork> (raw)
In-Reply-To: gt9cfv$uc2$1@news.eternal-september.org

Richard Riley <rileyrgdev@googlemail.com> writes:

> thierry.volpiatto@gmail.com writes:
>
>> Hi,
>> NOTE:
>> Instead of yasnippet, you can use also else-mode:
>>
>> http://www.emacswiki.org/emacs/ElseMode
>>
>> It's very well documented.
>>
>> I prefer it than yasnippet.
>
> Just as an aside noticing it's not hosted on the wiki (it would be nice
> if it was), Andy Stewart wrote a great utility suite for accessing
> emacs wiki code : see 
>
> http://www.emacswiki.org/emacs/AutoInstall
>
> ,----
> |    1. Find the Elisp file. Locate it on the web, either from a private site, or from a code repository such as the EmacsWiki ElispArea or gist.
> |    2. Asynchronous parallel download the file.
> |    3. Batch install files Some extension (such as Icicles) have many packages need install, and install those packages one by one is painful.
> |    4. View differences with the old version. Sometimes, you’ll want to view the differences between the new and old versions before you update.
> |    5. Save the Elisp file. You might keep your elisp files organized by categories, but this causes its own problems: if you download a new elisp file, you need to make sure you’re deleting the old one, a hassle if the file is located deep in a storage directory.
> |    6. Install the Elisp file.
> |    7. Keep the Elisp file updated.
> `----
>
> It has saved me a lot of time - especially with the "update" feature.

Yes it's nice, i use it also.

> (also, the instructions for "else" talk about installing help files into
> ~/info which is wrong for most of us).

For me it's in ~/elisp/info (but it can be anywhere else), 
you have just to write this line

,----
| * ELSE: (else).      Emacs Language Sensitive Editor mode.
`----

in your dir file.

and also in .emacs:

(add-to-list 'Info-default-directory-list "/home/you/elisp/info")

>>
>> Xavier Maillard <xma@gnu.org> writes:
>>
>>>    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 ;)
>>>
>>> regards
>>>
>>> 	Xavier

-- 
A + Thierry Volpiatto
Location: Saint-Cyr-Sur-Mer - France





  reply	other threads:[~2009-04-29 15:00 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 [this message]
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
  -- 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=87tz47sdwd.fsf@tux.homenetwork \
    --to=thierry.volpiatto@gmail.com \
    --cc=help-gnu-emacs@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).