[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


From: solidius4747
Date: Tue, 8 Jul 2014 19:41:57 -0700 (PDT)
User-agent: G2/1.0

Vào 04:36:55 UTC+7 Thứ tư, ngày 09 tháng bảy năm 2014, Emanuel Berg đã viết:

> It depends what packages and what users, and what they
> do.

Well I was wrong. The Emacs manual does not cover those packages. Over 600 
pages dedicate to Emacs alone.

> I think that is very unlikely for the majority of Emacs
> users. But it is not a bad idea to do - on the
> contrary...

Yes I know since the official manuals are huge. But if they have smaller and 
simpler books (i.e. how to books), they will usually read cover by cover. And 
when I say reading the whole book, I mean they actually spend time playing with 
Emacs, but use the book as the primary learning source most of the time, 
similar to someone leare a new programming language with a book.

> Screencast = screenshot or dump? If so, that's
> great. Those are very informative for the trained eye
> and there is no coincidence that computer magazines are
> always littered with those. In the accursed computer
> science world, they don't do that a lot (at all) but
> there is actually no one stopping you, so just do it
> where it helps. One thing with the computer magazines
> though, they tend to include very small screenshots,
> often you cannot see. I think screenshots should be
> half a page or at least one fourth a page to be truly
> telling. Often it doesn't help to litter them with
> arrows and boxes. It is better to add this in the
> description beneath the image, with "down left" (etc.)
> instead of arrows and the like.

Screencast is a recording of screen using video or image like GIF. I used GIF 
for demonstrating what Emacs looks like when it has 3rd party packages and 
properly configured. For example, I showed users  that Emacs is also capable of 
context-sensitive completion for C/C++, GUD GDB provides an easy to use and 
interactive user interface, with colors, Magit...
> Yeah, I suppose it isn't wrong to think up some logical
> order but in reality I don't think it works that way
> most of the time. I don't think people start reading
> one thing, completes it, then the next thing at a
> somewhat higher level, until they master it. They read
> some, experiment some, use the help some, Google some,
> ...

Yes, that's why I wrote this tutorial. I want users to collect experience here 
and there from various sources. That's why I wrote part 3, a collection of 
useful and popular packages, with useful configurations, to prevent users from 
rediscover from somewhere. In part 1, I provided exercises in most sections for 
users to practice. The exercises are common use cases for Emacs features, i.e. 
why should we save window configurations in register and how to use it 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]