unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Kin Cho <kin@techie.com>
Subject: Re: Cool and Useful LISP for the .emacs file
Date: 07 Nov 2003 19:23:19 -0800	[thread overview]
Message-ID: <7ik76b4k7s.fsf@neoscale.com> (raw)
In-Reply-To: uk76bu8lb.fsf@coas.oregonstate.edu

"Jody M. Klymak" <jklymak@coas.oregonstate.edu> writes:

> My point was that the rut occupied by C, python, perl, etc is wide and
> shallow compared to the rather narrow and deep rut occupied by lisp.
> I'm not trying to say that lisp is a bad language, but, adapting to
> new habits takes time.  Having to jump ruts is an obstacle to those of
> us who do not choose to invest this time.
> 
> I wonder how many more developers there might be for emacs if it had a
> more accessible programming language.  And I wonder if being wedded to
> lisp will have an impact on emacs' future.  Certainly, for me, it
> makes casual dilettante hacking for my own uses difficult, whereas I
> can usually muddle by in a piece of perl code.  


> My point was that the rut occupied by C, python, perl, etc is wide and
> shallow compared to the rather narrow and deep rut occupied by lisp.
> I'm not trying to say that lisp is a bad language, but, adapting to
> new habits takes time.  Having to jump ruts is an obstacle to those of
> us who do not choose to invest this time.
> 
> I wonder how many more developers there might be for emacs if it had a
> more accessible programming language.  And I wonder if being wedded to
> lisp will have an impact on emacs' future.  Certainly, for me, it
> makes casual dilettante hacking for my own uses difficult, whereas I
> can usually muddle by in a piece of perl code.  

I used to carry around a collection of shell, sed, awk, and perl
scripts to do various text/file/directory processing, as well as
doing cvs/rcs stuff, running compilation and gdb etc...  Now I do
(almost) all these things in elisp.

Except for the limitation of 28 bit integers (which is about the
only time I need to drop to perl), elisp is much more powerful
and elegant.

Some of the things I wrote elisp to do include: run special
compilation commands depending on project directory, mount
loopback filesystem devices within dired, parse tcpdump output,
etc...

In short, elisp makes it possible for me to create my very own
(text-based) IDE.

> But perhaps your sentiments are correct - maybe the litmus test of
> having to learn lisp keeps out the riff-raff and leaves emacs to be
> developed by the dedicated "professional programmers."  Maybe that is
> why it has remained so successful and the quality of what is out
> there so high.  I'm just trying to point out the point of view from a
> longtime user in the trenches.  

I suspect many excellent elisp authors aren't "professional
programmers", but smart tinkerers.

-kin

  parent reply	other threads:[~2003-11-08  3:23 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3343.1068146343.21628.help-gnu-emacs@gnu.org>
2003-11-06 23:45 ` Cool and Useful LISP for the .emacs file Kevin Rodgers
2003-11-07  4:10 ` Bruce Ingalls
2003-11-07  9:08 ` roodwriter
2003-11-07 16:58   ` Kevin Rodgers
2003-11-07 18:35     ` roodwriter
2003-11-08 18:01   ` roodwriter
2003-11-11 10:48     ` Oliver Scholz
2003-11-07 11:27 ` Gareth Rees
2003-11-07 14:06   ` Adam Hardy
     [not found]   ` <mailman.3403.1068214062.21628.help-gnu-emacs@gnu.org>
2003-11-07 14:28     ` David Kastrup
2003-11-07 16:54   ` Dan Anderson
2003-11-07 17:19   ` Rob Thorpe
     [not found]   ` <mailman.0.1068227823.2005.help-gnu-emacs@gnu.org>
2003-11-07 17:45     ` Jody M. Klymak
2003-11-07 18:20       ` Kevin Rodgers
2003-11-07 19:37       ` Dan Anderson
     [not found]       ` <mailman.11.1068237562.2005.help-gnu-emacs@gnu.org>
2003-11-07 22:17         ` Jody M. Klymak
2003-11-08  1:22           ` Jesper Harder
2003-11-08  3:23           ` Kin Cho [this message]
2003-11-08 10:34             ` Artur Hefczyc
2003-11-08 13:20               ` Thien-Thi Nguyen
2003-11-08 20:06               ` David Kastrup
2003-11-08 21:45                 ` Artur Hefczyc
2003-11-08 22:02                   ` Artur Hefczyc
2003-11-09  3:20               ` Kin Cho
2003-11-12  5:15               ` David Masterson
2003-11-12  8:12                 ` Matthew Kennedy
2003-11-12 18:21                 ` Pascal Bourguignon
2003-11-13 19:54                   ` Artur Hefczyc
2003-11-23  8:08               ` Tim X
2003-11-08 23:15           ` Joe Fineman
2003-11-10 15:59           ` Stefan Monnier
2003-11-10 20:58             ` Thien-Thi Nguyen
2003-11-10 21:00             ` Burton Samograd
2003-11-11 10:34               ` Alan Mackenzie
2003-11-11 14:32                 ` Jesper Harder
2003-11-11 17:00                   ` Burton Samograd
2003-11-11 17:00                 ` Burton Samograd
2003-11-11 20:04                   ` Alan Mackenzie
2003-11-08 10:15         ` Oliver Scholz
2003-11-08 12:03           ` Orm Finnendahl
2003-11-08  1:28       ` Thien-Thi Nguyen
2003-11-08 14:09       ` Ole Laursen
2003-11-23  8:02       ` Tim X
2003-12-07 15:56       ` Kai Grossjohann
2003-11-07 18:09 ` Reiner Steib
2003-11-07 18:37   ` lawrence mitchell
2003-11-08 17:06     ` Reiner Steib
2003-11-07 23:41 ` Edward Dodge
2003-11-10 16:04   ` Stefan Monnier
2003-11-10 21:17     ` kgold
2003-11-11 10:43       ` Alan Mackenzie
2003-11-11 15:39         ` Eli Zaretskii
2003-11-11 15:52         ` Stefan Monnier
2003-11-11 17:35           ` Thien-Thi Nguyen
2003-11-12  7:25             ` Lars Brinkhoff
     [not found]             ` <mailman.197.1068625639.2005.help-gnu-emacs@gnu.org>
2003-11-12 10:22               ` Colin Marquardt
2003-11-12 11:15                 ` David Kastrup
2003-11-12 13:47                   ` Stefan Monnier
     [not found] <E1AIRNX-0002YI-H9@monty-python.gnu.org>
2003-11-08 22:01 ` Joe Corneli
     [not found] <E1AI57v-00032q-9p@monty-python.gnu.org>
2003-11-07 14:31 ` Joe Corneli
2003-11-06 19:18 Dan Anderson

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=7ik76b4k7s.fsf@neoscale.com \
    --to=kin@techie.com \
    /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).