From: Rusi <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Guide for package use?(was A package in a league of its own: Helm)
Date: Thu, 28 Aug 2014 22:49:40 -0700 (PDT) [thread overview]
Message-ID: <dcd41753-0892-4948-8c31-e7726d419e97@googlegroups.com> (raw)
In-Reply-To: <787f8d86-dede-4627-b4e5-3658a1833455@googlegroups.com>
On Friday, August 29, 2014 9:48:33 AM UTC+5:30, solidi...@gmail.com wrote:
> I wrote a guide for Helm here: http://tuhdo.github.io/helm-intro.html
>
>
> Hope it help with your Helm usage if you are new to Helm.
Hey Solidius you seem to be doing good work!
There are some oldtimers (like myself) who need an intro to the
new-n-shiny packaging system. How about a tutorial on that?
I started reading up on that then found on the org-mode list (org is
one of my biggest uses of emacs) that org is too large to fit
neatly into the packaging framework. At that point I decided to postpone switching and wait...
next prev parent reply other threads:[~2014-08-29 5:49 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 4:18 A package in a league of its own: Helm solidius4747
2014-08-29 5:49 ` Rusi [this message]
2014-08-29 6:17 ` Guide for package use?(was A package in a league of its own: Helm) solidius4747
2014-08-29 13:36 ` A package in a league of its own: Helm Óscar Fuentes
[not found] ` <mailman.7830.1409319420.1147.help-gnu-emacs@gnu.org>
2014-08-29 14:03 ` solidius4747
2014-08-29 15:06 ` solidius4747
2014-08-29 16:48 ` Óscar Fuentes
[not found] ` <mailman.7852.1409330926.1147.help-gnu-emacs@gnu.org>
2014-08-29 17:08 ` solidius4747
2014-08-29 18:03 ` Óscar Fuentes
[not found] ` <mailman.7861.1409335444.1147.help-gnu-emacs@gnu.org>
2014-08-30 1:49 ` solidius4747
2014-08-30 3:33 ` Óscar Fuentes
[not found] ` <mailman.7892.1409369651.1147.help-gnu-emacs@gnu.org>
2014-08-30 3:55 ` solidius4747
2014-09-01 16:01 ` Phillip Lord
2014-09-01 16:49 ` York Zhao
2014-09-02 13:06 ` Phillip Lord
[not found] ` <mailman.8044.1409590146.1147.help-gnu-emacs@gnu.org>
2014-09-01 16:59 ` Tu, Do
2014-09-01 17:25 ` Nikolai Weibull
2014-09-01 17:28 ` Óscar Fuentes
2014-09-01 17:40 ` York Zhao
2014-09-01 20:37 ` Michael Heerdegen
2014-09-02 0:27 ` York Zhao
2014-09-02 1:40 ` Eric Abrahamsen
2014-09-02 1:56 ` York Zhao
2014-09-02 23:15 ` Tak Kunihiro
[not found] ` <mailman.8046.1409592357.1147.help-gnu-emacs@gnu.org>
2014-09-02 8:21 ` Tu, Do
2014-09-02 13:27 ` Phillip Lord
[not found] ` <mailman.8039.1409587302.1147.help-gnu-emacs@gnu.org>
2014-09-01 16:43 ` Tu, Do
2014-09-02 13:19 ` Phillip Lord
2014-09-02 14:13 ` York Zhao
2014-09-02 14:20 ` Phillip Lord
2014-09-02 17:03 ` York Zhao
2014-09-03 9:58 ` Phillip Lord
[not found] ` <mailman.8183.1409738348.1147.help-gnu-emacs@gnu.org>
2014-09-03 10:19 ` Tu, Do
[not found] ` <mailman.8134.1409677438.1147.help-gnu-emacs@gnu.org>
2014-09-02 17:11 ` Tu, Do
2014-09-02 17:32 ` York Zhao
2014-09-02 18:15 ` Tu
2014-09-03 0:35 ` York Zhao
[not found] ` <mailman.8166.1409704538.1147.help-gnu-emacs@gnu.org>
2014-09-03 3:50 ` Tu, Do
[not found] ` <mailman.8106.1409664004.1147.help-gnu-emacs@gnu.org>
2014-09-02 14:32 ` Tu, Do
2014-09-03 10:43 ` Phillip Lord
2014-08-31 9:09 ` Ernesto Durante
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=dcd41753-0892-4948-8c31-e7726d419e97@googlegroups.com \
--to=rustompmody@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).