From: vb <help-gnu-emacs@vsbe.com>
Cc: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: current directory
Date: Mon, 23 Oct 2006 13:59:02 -0700 [thread overview]
Message-ID: <200610231359.03037.help-gnu-emacs@vsbe.com> (raw)
In-Reply-To: <ehj8u1$ocf$1@sea.gmane.org>
Kevin,
thank you for the hint on Crisp emulation - I tried it before, and it did not
work quite as expected - I just tried it again, and it still doesn't - say
the numeric keypad asterisk which is an 'undo' key in Crisp doesn't work this
way. Window navigation (Shift->arrow key) doesn't work either, but I am sure
it all is fixable. A bigger issue is that a big macro library can not be
reused between Crisp and Emacs (not that I think this is even feasible to
expect between any two editors).
On Monday 23 October 2006 13:32, Kevin Rodgers wrote:
>
> > You
> > can write macros in object oriented c-like language, not in this
>
> weird lisp
>
> > which is a remnant of computing stone age (I know, I know that it is
>
> still
>
> > used to teach students).
>
> Good grief.
Yeah, well, I was half kidding. My daughter graduated from UCB CS program
recently - I watched her learn and use schema - she sure would be quite
comfortable with Emacs macro extensions.
But believe me, not all (and I would bet not even a majority) of Emacs users
came through a CS program teaching schema - for all of us it is so weird to
adjust to Lisp after some most popular in the industry programming languages
(be it C/C++ or Java or Perl/PHP - whatever people use to earn living these
days) so many don't even try.
I understand it's too late to expect Emacs to switch to another scripting
language, but I sure think the need to use lisp is a deficiency.
cheers,
/vb
next prev parent reply other threads:[~2006-10-23 20:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.83.1161235004.2130.help-gnu-emacs@gnu.org>
2006-10-19 16:01 ` current directory Fang lun gang
2006-10-19 16:52 ` vb
2006-10-20 6:22 ` Eli Zaretskii
[not found] ` <mailman.100.1161276782.2130.help-gnu-emacs@gnu.org>
2006-10-19 19:22 ` rgb
2006-10-19 21:00 ` vb
2006-10-21 18:38 ` don provan
2006-10-23 17:24 ` vb
2006-10-23 19:17 ` John Sullivan
2006-10-23 19:57 ` Eli Zaretskii
2006-10-23 20:36 ` vb
2006-10-23 21:47 ` Dieter Wilhelm
2006-10-24 4:26 ` Eli Zaretskii
2006-10-24 5:24 ` Dieter Wilhelm
[not found] ` <mailman.178.1161635783.27805.help-gnu-emacs@gnu.org>
2006-10-23 21:52 ` Maarten Bergvelt
2006-10-23 20:32 ` Kevin Rodgers
2006-10-23 20:59 ` vb [this message]
[not found] ` <mailman.166.1161624291.27805.help-gnu-emacs@gnu.org>
2006-10-23 17:48 ` David Kastrup
2006-10-23 20:03 ` Eli Zaretskii
2006-10-23 18:33 ` Colin S. Miller
2006-10-23 18:58 ` vb
[not found] ` <mailman.169.1161629903.27805.help-gnu-emacs@gnu.org>
2006-10-23 19:46 ` Peter Boettcher
[not found] <mailman.74.1161208352.2130.help-gnu-emacs@gnu.org>
2006-10-20 16:46 ` Sam Peterson
2006-10-19 5:16 help-gnu-emacs
2006-10-20 5:49 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2006-10-18 21:52 help-gnu-emacs
2006-10-18 22:32 ` Peter Dyballa
2006-10-18 23:12 ` vb
2006-10-19 4:25 ` Eli Zaretskii
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=200610231359.03037.help-gnu-emacs@vsbe.com \
--to=help-gnu-emacs@vsbe.com \
--cc=ihs_4664@yahoo.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).