unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs Mini Manual (PART 3) - CUSTOMIZING AND EXTENDING EMACS
Date: Tue, 08 Jul 2014 01:12:10 +0200	[thread overview]
Message-ID: <87egxwg3w5.fsf@debian.uxu> (raw)
In-Reply-To: 5eaf0440-3124-4d89-bd20-ddada9a3db12@googlegroups.com

solidius4747@gmail.com writes:

> I wrote part 3:
> http://tuhdo.github.io/emacs-tutor3.html
>
> It includes popular packages that people are
> using. If you are new to Emacs, it would be useful.

I wouldn't call that tutorial "mini"!

It is clear you put a very big effort into this. You
should get a medal, or some part of the gold stashed in
IET, the International Emacs Treasury (if there is
one).

But, this makes me think, did you experience any
shortcomings or "gaps" in the official Emacs manual?
Perhaps you could integrate your project with it,
somehow. If not, the official Emacs people should put a
link to your project from the official site, at least,
if they didn't already.

Feedback on the material itself: the part on MELPA,
what I can see it misses one essential part, namely how
to *submit* code: both how that is done in practice,
and guidelines on the Elisp itself (or references, if
you don't feel like writing this all over).

Keep it up!

-- 
underground experts united


  parent reply	other threads:[~2014-07-07 23:12 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01  4:41 Emacs Mini Manual (PART 3) - CUSTOMIZING AND EXTENDING EMACS solidius4747
2014-07-01  7:44 ` James Freer
     [not found] ` <mailman.4638.1404200703.1147.help-gnu-emacs@gnu.org>
2014-07-01 14:16   ` Emanuel Berg
2014-07-01 14:38     ` James Freer
     [not found]     ` <mailman.4649.1404225527.1147.help-gnu-emacs@gnu.org>
2014-07-08  8:36       ` solidius4747
2014-07-08 15:09         ` Emanuel Berg
2014-07-08 16:18           ` Drew Adams
2014-07-08 16:45           ` solidius4747
2014-07-08 21:36             ` Emanuel Berg
2014-07-09  2:41               ` solidius4747
2014-07-09  8:52                 ` Robert Thorpe
2014-07-09 17:11                 ` Emanuel Berg
2014-08-25 14:05             ` Jude DaShiell
2014-07-08 18:56           ` Robert Thorpe
     [not found]           ` <mailman.5091.1404836351.1147.help-gnu-emacs@gnu.org>
2014-07-08 21:21             ` Emanuel Berg
2014-07-09  8:44               ` Robert Thorpe
2014-07-10  2:11               ` Bob Proulx
     [not found]               ` <mailman.5163.1404958319.1147.help-gnu-emacs@gnu.org>
2014-07-10 22:16                 ` Emanuel Berg
2014-07-12 14:52                   ` Javier
2014-07-12 19:49                     ` Emanuel Berg
2014-07-12 23:30                       ` Javier
2014-07-13 16:52                         ` Emanuel Berg
2014-07-13  1:40                     ` Robert Thorpe
2014-07-07 23:12 ` Emanuel Berg [this message]
2014-07-08  8:37   ` solidius4747
2014-07-08 15:15     ` Emanuel Berg
2014-07-08 16:48       ` solidius4747
2014-07-08 21:43         ` Emanuel Berg
     [not found] <mailman.5117.1404898261.1147.help-gnu-emacs@gnu.org>
2014-07-09 16:55 ` Emanuel Berg
2014-07-11 11:51   ` Robert Thorpe
     [not found] <mailman.5279.1405079523.1147.help-gnu-emacs@gnu.org>
2014-07-11 12:07 ` Emanuel Berg

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=87egxwg3w5.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --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).