From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: solidius4747@gmail.com Newsgroups: gmane.emacs.help Subject: Re: Emacs Mini Manual (PART 3) - CUSTOMIZING AND EXTENDING EMACS Date: Tue, 8 Jul 2014 01:36:20 -0700 (PDT) Message-ID: <619ae998-2ce5-428d-bec7-a654427b81d0@googlegroups.com> References: <5eaf0440-3124-4d89-bd20-ddada9a3db12@googlegroups.com> <87r425qi4t.fsf@debian.uxu> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1404808845 22554 80.91.229.3 (8 Jul 2014 08:40:45 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 8 Jul 2014 08:40:45 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Jul 08 10:40:40 2014 Return-path: Envelope-to: geh-help-gnu-emacs@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 1X4Qx5-0006F8-Ba for geh-help-gnu-emacs@m.gmane.org; Tue, 08 Jul 2014 10:40:39 +0200 Original-Received: from localhost ([::1]:54515 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X4Qwx-0004KV-M6 for geh-help-gnu-emacs@m.gmane.org; Tue, 08 Jul 2014 04:40:31 -0400 X-Received: by 10.236.86.178 with SMTP id w38mr7890871yhe.13.1404808581693; Tue, 08 Jul 2014 01:36:21 -0700 (PDT) X-Received: by 10.50.221.39 with SMTP id qb7mr48071igc.0.1404808581198; Tue, 08 Jul 2014 01:36:21 -0700 (PDT) Original-Path: usenet.stanford.edu!w8no6827979qac.0!news-out.google.com!gf2ni0igb.0!nntp.google.com!uq10no74780igb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=14.161.32.83; posting-account=c2AWuQoAAACA36o69JJJEmXY5MOg4YNp Original-NNTP-Posting-Host: 14.161.32.83 User-Agent: G2/1.0 Injection-Date: Tue, 08 Jul 2014 08:36:21 +0000 Original-Xref: usenet.stanford.edu gnu.emacs.help:206307 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:98577 Archived-At: V=C3=A0o 21:38:24 UTC+7 Th=E1=BB=A9 ba, ng=C3=A0y 01 th=C3=A1ng b=E1=BA=A3y= n=C4=83m 2014, jessejazza =C4=91=C3=A3 vi=E1=BA=BFt: > On Tue, 1 Jul 2014, Emanuel Berg wrote: >=20 >=20 >=20 > > James Freer writes: >=20 > > >=20 > >> I'm very grateful for the time you have spent >=20 > >> although now after a couple of weeks I have learnt >=20 > >> enough to be happy with. I've found using emacs-nox >=20 > >> and forgetting about the gui is worthwhile and taking >=20 > >> time to learn from the cheatsheet. It would be nice >=20 > >> to have the 'mini manual' in pdf then one could print >=20 > >> it out and read on the train (or similar times when >=20 > >> one is away from the PC). >=20 > > >=20 > > Do my ears deceive me?! Finally a guy with class! >=20 > > F*ing right! >=20 > > >=20 > > I haven't seen the particular document, though. I will >=20 > > read it tonight and probably get back to the OP with >=20 > > some comments. >=20 > > >=20 > > If you don't like to just print and read the HTML, you >=20 > > can use several tools to get it to PDF. You can use >=20 > > html2ps, and then ps2pdf - html2ps is in the repos, >=20 > > ps2pdf is part of ghostscript, which is likewise in the >=20 > > repos. (There are other ways to do this as well.) >=20 >=20 >=20 > html2ps >=20 > I'll have to look up >=20 >=20 >=20 > I knew about ps2pdf and pdf2ps as I use it to send faxes. (yes fax still = has=20 >=20 > a use). Or maybe I need to look at other methods. >=20 >=20 >=20 > When I 'read on a train' - in truth I really meant that I like the pdf to= print=20 >=20 > out, bind, and then use like a book for bedtime reading. keen beginner eh= . >=20 >=20 >=20 > james I'm glad that you like my tutorial. I'm working on how to generate a pdf do= cument with org-mode. Not sure how many pages my "mini manual" actually con= sumes. I didn't intend it to be a book in the first place. V=C3=A0o 06:12:10 UTC+7 Th=E1=BB=A9 ba, ng=C3=A0y 08 th=C3=A1ng b=E1=BA=A3y= n=C4=83m 2014, Emanuel Berg =C4=91=C3=A3 vi=E1=BA=BFt: > solidius4747@gmail.com writes: >=20 >=20 >=20 > > I wrote part 3: >=20 > > http://tuhdo.github.io/emacs-tutor3.html >=20 > > >=20 > > It includes popular packages that people are >=20 > > using. If you are new to Emacs, it would be useful. >=20 >=20 >=20 > I wouldn't call that tutorial "mini"! >=20 >=20 >=20 > It is clear you put a very big effort into this. You >=20 > should get a medal, or some part of the gold stashed in >=20 > IET, the International Emacs Treasury (if there is >=20 > one). >=20 >=20 >=20 > But, this makes me think, did you experience any >=20 > shortcomings or "gaps" in the official Emacs manual? >=20 > Perhaps you could integrate your project with it, >=20 > somehow. If not, the official Emacs people should put a >=20 > link to your project from the official site, at least, >=20 > if they didn't already. >=20 >=20 >=20 > Feedback on the material itself: the part on MELPA, >=20 > what I can see it misses one essential part, namely how >=20 > to *submit* code: both how that is done in practice, >=20 > and guidelines on the Elisp itself (or references, if >=20 > you don't feel like writing this all over). >=20 >=20 >=20 > Keep it up! >=20 >=20 >=20 > --=20 >=20 > underground experts united Thanks!=20 As I stated in Part 1 in "Why I wrote this guide" section, it is because I = feel the Emacs manual is designed to be more like a reference material than= a beginner material. It also does not mention about popular 3rd party pack= ages, and popular package archives like MELPA. Where should new users to Em= acs find this information? They will have to waste time to rediscover packa= ges that people used long ago. I want to get productive with Emacs as fast = as possible. Telling people to read the whole Emacs Lisp manual before able= to customizing/extending Emacs is likely to push them away from Emacs. As for submitting code to MELPA, I don't think it's necessary to include in= the guide, because clearly the targeted audience is beginners who just sta= rt their journey with customizing/extending Emacs. It's unlikely they will = roll a package on their own after finishing the guide anyway.