Introduction to Programming in Emacs Lisp

Introduction to Programming in Emacs Lisp

[Robert J. Chassell]

I updated the Introduction to Programming in Emacs Lisp again -- and
have little left to do.  (I have a few items left that Stuart
D. Herring recommended.)  The update includes the Texinfo source in
lispintro/emacs-lisp-intro.texi and the Info files in info/eintr*

Please look at a copy.  Thanks!

-- 
    Robert J. Chassell                          GnuPG Key ID: 004B4AC8
    bob@rattlesnake.com                         bob@gnu.org
    http://www.rattlesnake.com                  http://www.teak.cc

Re: Introduction to Programming in Emacs Lisp

[Eli Zaretskii]

> Date: Tue, 31 Oct 2006 18:10:55 +0000 (UTC)
> From: "Robert J. Chassell" <bob@rattlesnake.com>
> 
> I updated the Introduction to Programming in Emacs Lisp again -- and
> have little left to do.  (I have a few items left that Stuart
> D. Herring recommended.)  The update includes the Texinfo source in
> lispintro/emacs-lisp-intro.texi and the Info files in info/eintr*

Thanks, but why on Earth did you commit the Info files in info/ ?  We
don't keep Info files in the CVS repository; the onloy exception is
info/dir.  Please "cvs remove" info/eintr and info/eintr-1.

Re: Introduction to Programming in Emacs Lisp

[Juri Linkov]

> I updated the Introduction to Programming in Emacs Lisp again -- and
> have little left to do.  (I have a few items left that Stuart
> D. Herring recommended.)  The update includes the Texinfo source in
> lispintro/emacs-lisp-intro.texi and the Info files in info/eintr*
>
> Please look at a copy.  Thanks!

I fixed some unbalanced quotes in this manual.  I found them after
converting the manual to the XML format, where the result was an
incorrect XML file.

-- 
Juri Linkov
http://www.jurta.org/emacs/

Re: Introduction to Programming in Emacs Lisp

[Robert J. Chassell]

    I fixed some unbalanced quotes in this manual.  I found them after
    converting the manual to the XML format, where the result was an
    incorrect XML file.

Thank you.  I did not see most of the problems.  Are there others?
What about content?  Of your four changes, three look good.  I
reverted rotate-yank-pointer, the change to which another poster also
noted was in error.

-- 
    Robert J. Chassell                          GnuPG Key ID: 004B4AC8
    bob@rattlesnake.com                         bob@gnu.org
    http://www.rattlesnake.com                  http://www.teak.cc

Introduction to Programming in Emacs Lisp

[T. V. Raman]

For your next revision, it would be nice to add a short section
on advice.

>>>>> "Robert" == Robert J Chassell <bob@rattlesnake.com> writes:
    Robert> I updated the Introduction to Programming in Emacs
    Robert> Lisp again -- and have little left to do.  (I have a
    Robert> few items left that Stuart D. Herring recommended.)
    Robert> The update includes the Texinfo source in
    Robert> lispintro/emacs-lisp-intro.texi and the Info files in
    Robert> info/eintr*
    Robert> 
    Robert> Please look at a copy.  Thanks!
    Robert> 
    Robert> -- Robert J. Chassell GnuPG Key ID: 004B4AC8
    Robert> bob@rattlesnake.com bob@gnu.org
    Robert> http://www.rattlesnake.com http://www.teak.cc
    Robert> 
    Robert> 
    Robert> _______________________________________________
    Robert> Emacs-devel mailing list Emacs-devel@gnu.org
    Robert> http://lists.gnu.org/mailman/listinfo/emacs-devel

-- 
Best Regards,
--raman

      
Email:  raman@users.sf.net
WWW:    http://emacspeak.sf.net/raman/
AIM:    emacspeak       GTalk: tv.raman.tv@gmail.com
PGP:    http://emacspeak.sf.net/raman/raman-almaden.asc
Google: tv+raman 
IRC:    irc://irc.freenode.net/#emacs

Re: Introduction to Programming in Emacs Lisp

[Robert J. Chassell]

    For your next revision, it would be nice to add a short section
    on advice.

No.  When readers make worth while additions they should go into the
GNU Emacs sources.

Only great programmers can start a new thread, as you did.  Most
programmers are not great, nor are the expressions they write.

As     (elisp)Advising Functions     says

    Advising a function can cause confusion in debugging
    ... if you have the possibility ... run a hook ...

    ... a file in Emacs should not put advice on a function ...

Over the next decade or two, I expect that more and more otherwise
sighted people will want to listen to their email and the like.  They
will be using mobile telephones or driving their cars.  (Certainly,
the rest of us do not want a car driver to look at a computer screen;
we want him to keep his eyes on the road!)  

Over time, a large number of people will see themselves as
`situationally blind' and see that a solution is to listen.  Text to
speech synthesizers were developed for the permanently blind but they
work as well for the situationally blind.

It makes sense that `all core Emacs functionality ... speak
intelligently' as you wrote in `emacspeak/lisp/emacspeak-advice.el'.
After all, speech is another output format.  And while the interface
is somewhat like an Emacs for the sighted, but without a windowing
system, it is also truly different, as you say.

I wish Emacspeak were within the GNU Emacs sources.  Then sighted
developers would remember it as they do the current output formats,
the virtual consoles without different textual faces and the windowing
systems with.  Moreover, even the sighted who do not know about
Emacspeak could learn of it and find it installed.

It could be called inside Emacs as a speech mode, as an emacspeak
mode, or called outside Emacs, that is to say, started, as a program.

But I doubt it is possible to incorporate Emacspeak into GNU Emacs.
For one, GNU Emacs is not released frequently, so for most people
Emacspeak would not get updated.  My brother-in-law, for example, is
using GNU Emacs 21, which was released in 2001.  (It would make sense
to release more frequently a program named Emacspeak that has the
appropriate GNU Emacs in it ...)

Also, I fear too many functions were written with advice and won't be
changed.  

In addition, you may not have kept proper legal papers for Emacspeak.
I don't know.  Without them, it would be easy for enemies of free
software to threaten obvious costs and thereby hinder distribution
among corporations in countries with strong court systems.  GNU Emacs
and RMS are sufficiently visible that this could happen.  Other
distributions are less visible, so no one cares -- a case of "security
through obscurity" succeeding with humans.  A lack of proper legal
papers might prevent re-written Emacspeak files from entering GNU
Emacs sources.

So, I suspect this is an example of the good, Emacspeak and GNU Emacs
being separate, being an enemy of the better, namely Emacspeak being
incorporated formally into GNU Emacs.

-- 
    Robert J. Chassell                          GnuPG Key ID: 004B4AC8
    bob@rattlesnake.com                         bob@gnu.org
    http://www.rattlesnake.com                  http://www.teak.cc