all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: LanX <lanx.perl@googlemail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: About Emacs Modernisation Project
Date: Tue, 1 Jun 2010 16:22:40 -0700 (PDT)	[thread overview]
Message-ID: <66c5242b-d254-4646-9537-6c669c6616bb@d12g2000vbr.googlegroups.com> (raw)
In-Reply-To: jwvocfuk065.fsf-monnier+gnu.emacs.help@gnu.org

> > I think Emacs Lisp actually
> > encourages the production of a lot of little, useful hacks.
>
> Indeed.  But lexical scoping and name spaces wouldn't make any
> difference in this respect.

But the lack of namespaces leads to very long names which IMHO
irritate newbies.

At least it did irritate me at the time to find out that I need to
type "M-x font-lock-fontify-buffer" to get highlighting, and it still
irritates others when I explain  to do so.

Snippets manipulating different aspects of font-lock would look less
intimidating, without the need to repeat "font-lock-" 20 times.

And something like customize-group NAME-SPACE wouldn't need to list
the prefix NAME-SPACE-... for each option.

IMHO the option to use shorter identifiers for functions and variables
would increase the acceptance of elisp and emacs!

You might think that it's only a matter of getting used to, but maybe
you should better ask the folks who turned away maybe thinking that a
system with >20 char identifiers is far too complicated...

When manipulating the DOM of a browser with JS I have standard
mechanisms to considerately shorten the path to a variable or
function.

Are there any in eLisp?


  reply	other threads:[~2010-06-01 23:22 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <143c6d28-4423-4e43-9fc5-c0fb3340043b@c11g2000vbe.googlegroups.com>
2010-05-31 15:44 ` About Emacs Modernisation Project Pascal J. Bourguignon
     [not found]   ` <0e994fe3-6dde-449f-879d-6701c7a195a9@e28g2000vbd.googlegroups.com>
2010-05-31 19:41     ` Alessandro Piras
     [not found]       ` <87iq63wsvt.fsf@kuiper.lan.informatimago.com>
2010-06-01  0:06         ` LanX
2010-06-01  8:44           ` Pascal J. Bourguignon
2010-06-01 11:19             ` LanX
2010-06-01 12:56               ` Pascal J. Bourguignon
2010-06-02  6:17         ` Xah Lee
     [not found]       ` <c41c63c0-b934-442d-8385-1abff6ab9b0b@s41g2000vba.googlegroups.com>
2010-06-01  0:40         ` Alessandro Piras
2010-06-02  6:07       ` Xah Lee
     [not found] ` <87ljazofkn.fsf@rapttech.com.au>
2010-05-31 23:33   ` LanX
2010-06-01 10:28     ` Helmut Eller
2010-06-01 11:27       ` LanX
2010-06-01 12:29         ` Helmut Eller
2010-06-01 12:55           ` LanX
2010-06-01 12:59             ` Pascal J. Bourguignon
2010-06-01 12:59           ` Pascal J. Bourguignon
2010-06-02 17:05       ` Xah Lee
2010-06-02 17:50         ` Helmut Eller
     [not found]     ` <87r5krh3e0.fsf@unm.edu>
2010-06-01  8:40       ` Pascal J. Bourguignon
2010-06-01 17:34         ` rustom
2010-06-02 12:47           ` B. T. Raven
2010-06-02 17:20             ` rustom
2010-06-01 19:50       ` Stefan Monnier
2010-06-01 23:22         ` LanX [this message]
     [not found]           ` <slrni0b8nm.9k6.bergv@u00.math.uiuc.edu>
2010-06-02 11:39             ` Pascal J. Bourguignon
     [not found]           ` <e73e123d-3f0c-4a6f-bbac-b91fb71bf07d@f14g2000vbn.googlegroups.com>
2010-06-03  9:26             ` Emulating namespaces Pascal J. Bourguignon
2010-06-03 15:33               ` LanX
2010-06-03 17:41                 ` Pascal J. Bourguignon
     [not found]         ` <87mxvegz12.fsf@unm.edu>
2010-06-01 23:36           ` About Emacs Modernisation Project Pascal J. Bourguignon
2010-06-02  5:58             ` Evans Winner
2010-06-04 18:33     ` Joseph Brenner
2010-06-05  2:55       ` Tim X

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=66c5242b-d254-4646-9537-6c669c6616bb@d12g2000vbr.googlegroups.com \
    --to=lanx.perl@googlemail.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.