unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tim X <timx@spamto.devnul.com>
Subject: Re: Cool and Useful LISP for the .emacs file
Date: 23 Nov 2003 19:08:20 +1100	[thread overview]
Message-ID: <871xrztsln.fsf@tiger.rapttech.com.au> (raw)
In-Reply-To: 87oevn9mim.fsf@141-moc-9.acn.waw.pl

>>>>> "Artur" == Artur Hefczyc <DONTkobit@SPAMplusnet.MEpl> writes:

 Artur> Kin Cho <kin@techie.com> writes:
 >> 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.

 Artur> I like this idea! I would like to use elisp as scripting
 Artur> language also. However I would like to know if it is possible
 Artur> to use it that way. I mean, lets assume I create elisp script
 Artur> to update my Linux box system with new releases of some
 Artur> packages.

 Artur> Is it possible to run it from command line like all other
 Artur> scripts, bash, perl etc.?

 Artur> I mean file script starting from: #!/usr/bin/emacs

 Artur> Or any other elisp interpreter?

 Artur> Artur -- Artur Hefczyc, Open Source Developer:
 Artur> http://www.geotools.org/ http://generguide.sourceforge.net/
 Artur> http://wttools.sourceforge.net/
 Artur> http://maven-plugins.sourceforge.net/

For this sort of thing, I'd be tempted to just use lisp, not emacs
lisp. There are numerous lisp implementations which will allow you to
do this sort of thing. 

The thing about elisp is that its got lots of things which are useful
when dealing with text, buffers, displays characters etc. However, its
not as good as a general lisp if you want ot do more general stuff. 

Tim

-- 
Tim Cross
The e-mail address on this message is FALSE (obviously!). My real e-mail is
to a company in Australia called rapttech and my login is tcross - if you 
really need to send mail, you should be able to work it out!

  parent reply	other threads:[~2003-11-23  8:08 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
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 [this message]
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=871xrztsln.fsf@tiger.rapttech.com.au \
    --to=timx@spamto.devnul.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).