all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: reader@newsguy.com
To: help-gnu-emacs@gnu.org
Subject: Re: jump between if-fi
Date: Tue, 01 Jan 2008 09:39:41 -0600	[thread overview]
Message-ID: <87fxxhd076.fsf@newsguy.com> (raw)
In-Reply-To: 20080101141827.GA3830@muc.de

Alan Mackenzie <acm@muc.de> writes:

[...]

>> Yes that would be very nice but is also very unlikely.  My skill level
>> would have to be improved several hundred percentage points in a pretty
>> short while.
>
> Indeed.  Where's the problem with that?  The Emacs documentation
> (including that for Emac Lisp) is sensationally good, and there's as much
> help as you need on the net.  For functionality this useful, I'd happily
> help you by personal email, even several times a week.

time

And as you noted.. elisp isn't well suited for scripting so I'm
working on perl.

[...]

>> I guess not too many emacs developers really do much shell scripting.
>> Probably using a lot more high level scripting languages (perl, lisp,
>> python and etc).  I run into portability problems more with shell
>> scripts since something like perl is the same everywhere.
>
> I would think most Emacsers write shell scripts reasonably fluently.
> Lisp isn't really suited for the job, and p{erl,ython} seem over
> complicated.  In my humble opinion, of course.  ;-)

I'm sure they are fluent.  Way more than I am.

What I said was I doubt they use shell languages as much as someone
who isn't fluent in perl or python.  What I was getting at is there
may not be much of a perceived need for things that aid shell
scripting.  All the higher level stuff uses parens rather than if-fi.

I do agree though that hacking out something to make emacs able to
recognize shell constructs like it does with parens would be a great
learning tool and of some value to the emacs community.  God knows I
owe the community a huge debt for all the help over the years.

I may have to dig into it this new year.

  reply	other threads:[~2008-01-01 15:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-30 23:02 jump between if-fi reader
2007-12-30 23:23 ` Lennart Borgman (gmail)
2007-12-31  6:29   ` reader
2007-12-31  8:12     ` Thierry Volpiatto
2007-12-31 14:41       ` reader
2008-01-01 15:47   ` reader
     [not found]   ` <mailman.5533.1199082573.18990.help-gnu-emacs@gnu.org>
2008-01-09  5:40     ` Stefan Monnier
2007-12-31 16:24 ` Alan Mackenzie
2008-01-01  2:29   ` reader
2008-01-01 14:18     ` Alan Mackenzie
2008-01-01 15:39       ` reader [this message]
2008-01-01 15:53     ` Torturedly threaded .emacs portability. [Was: jump between if-fi] Alan Mackenzie
2008-01-01 15:53       ` reader
2008-01-02  5:00       ` Mike Mattie
2008-01-05 18:33     ` jump between if-fi reader
2008-01-09  9:43 ` Arnaldo Mandel
     [not found] <mailman.5524.1199055779.18990.help-gnu-emacs@gnu.org>
2008-01-01 18:12 ` Xah Lee
2008-01-01 19:12   ` Alan Mackenzie

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fxxhd076.fsf@newsguy.com \
    --to=reader@newsguy.com \
    --cc=help-gnu-emacs@gnu.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.