From: jadamson@partners.org (Joel J. Adamson)
To: help-gnu-emacs@gnu.org
Subject: Re: newbie elisp help ??
Date: Thu, 16 Aug 2007 10:09:08 -0400 [thread overview]
Message-ID: <87y7gbh8qj.fsf@W0053328.mgh.harvard.edu> (raw)
In-Reply-To: mailman.4845.1187231410.32220.help-gnu-emacs@gnu.org
William Case <billlinux@rogers.com> writes:
> 4. I wanted to avoid the need for variable arguments, parameters
> and hooks by writing a simple set of functions where I could
> copy and manually substitute ';' and '#' for '/* */' commenting
> out symbols. Hooks, buffer/file names, etc. might come later.
I understand completely all your desires to learn: I'm doing the same
thing myself. To accomplish 4, I suggest checking out ESS, which is a
set of major modes for various statistical applications. It's mostly
aimed at R, however I use it for Stata; it has all the different
comment syntaxes worked out. I've only recently discovered the
sh-mode has the ability to stick in complete templates for whiles,
fors and conditionals --- it's pretty cool.
> 5. I did not ask for advice on the emacs mailing list lightly. I
> did my due diligence with manuals, info, wiki, archives, google
> and trial and error. I thought that after several hours of
> frustration it would be appropriate to ask for guidance.
>
> My understanding was that this emacs mailing list is for beginners and
> experienced people alike.
No problem: your post just reminded me of all the times I've thought
of doing similar things and discovered that (a) Emacs already does
what I want or (b) there's a much simpler way to do it that does not
involve any Lisp. This is somewhat of a shame, since I am always
trying to find a reason to learn more Lisp (right now I'm studying
Scheme more than Emacs Lisp). Unfortunately much of the time Emacs
already does what I want and I have no reason to learn:
DAMN YOU EMACS LISP DEVELOPERS AND YOUR EXCELLENT PRODUCTS AND
EXTENSIONS! YOU'RE RUINING IT FOR THE REST OF US!
Have a nice day,
Joel
--
Joel J. Adamson
Biostatistician
Pediatric Psychopharmacology Research Unit
Massachusetts General Hospital
Boston, MA 02114
(617) 643-1432
(303) 880-3109
"It can be interesting to study ancient philosophy, but more as a kind
of accident report than to teach you anything useful."
--Paul Graham
http://www.paulgraham.com/raq.html
next prev parent reply other threads:[~2007-08-16 14:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4824.1187198869.32220.help-gnu-emacs@gnu.org>
2007-08-15 18:02 ` newbie elisp help ?? Pascal Bourguignon
2007-08-15 19:04 ` William Case
2007-08-17 20:44 ` Thien-Thi Nguyen
2007-08-15 20:08 ` Joel J. Adamson
2007-08-16 2:30 ` William Case
[not found] ` <mailman.4845.1187231410.32220.help-gnu-emacs@gnu.org>
2007-08-16 14:09 ` Joel J. Adamson [this message]
2007-08-15 17:27 William Case
2007-08-15 17:48 ` Lennart Borgman (gmail)
2007-08-15 18:16 ` William Case
2007-08-15 18:24 ` Lennart Borgman (gmail)
[not found] ` <46C342F9.8070808@gmail.com>
2007-08-15 19:07 ` William Case
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=87y7gbh8qj.fsf@W0053328.mgh.harvard.edu \
--to=jadamson@partners.org \
--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.
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).