unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Lua mailing list <lua-l@lists.lua.org>,
	immerrr again <immerrr+lua@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: Last call for lua-mode contributors
Date: Sat, 21 Jan 2012 12:20:30 +0900	[thread overview]
Message-ID: <87y5t1kagx.fsf@catnip.gol.com> (raw)
In-Reply-To: <jwvaa5io3yx.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 20 Jan 2012 09:17:09 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> [lua-mode redefines "_" as a word-component; it shouldn't, as it
>> really messes with users' instincts, and makes Emacs commands less
>> useful.  Historically this was often done by language-modes as an
>
> BTW, this reminds me: why do word-based movement commands even care
> about the syntax-table?  I understand that it's the way they're
> currently implemented, but AFAICT we don't actually want their behavior
> to depend on the major mode, do we?

Dunno, I suppose sometimes maybe it is reasonable to allow the details
to be tweaked; it's "consistency of feel" which is the goal, which may
not always entail literal consistency....

For instance:  is a single-quote part of a word?

In text-mode, it is, and that makes some sense, because single-quotes
are mostly followed by a single letter to form a contracted thingie.
Having word commands stop at the single-letter boundary in such cases
would be pretty annoying and not particularly useful, and generally
wouldn't feel "right" (even though there's a visual boundary).

However in some programming language mode that uses single-quotes like
Ada does, as an operator, you really want them to be punctuation,
because they are used to separate independent pieces that are thought of
as independent.

-Miles

-- 
Discriminate, v.i. To note the particulars in which one person or thing is,
if possible, more objectionable than another.



      reply	other threads:[~2012-01-21  3:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAERznn_UcioQzHojyW=JaDsSHkfihAP3b0YfcUz_NT2cLefTTg@mail.gmail.com>
     [not found] ` <CAERznn9+Y8OFPBNSDk=S_wRF+eP0u4_zfzUQjA9=Y=f=zf+MKw@mail.gmail.com>
2012-01-18  4:32   ` Last call for lua-mode contributors Miles Bader
2012-01-19 17:15     ` Ken Raeburn
2012-01-19 18:57       ` Underscores and word commands Stefan Monnier
2012-01-19 20:39         ` John Yates
2012-01-20 21:25           ` Stefan Monnier
2012-01-20  5:12       ` Last call for lua-mode contributors Miles Bader
2012-01-20  7:12         ` Ken Raeburn
2012-01-20 14:17     ` Stefan Monnier
2012-01-21  3:20       ` Miles Bader [this message]

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=87y5t1kagx.fsf@catnip.gol.com \
    --to=miles@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=immerrr+lua@gmail.com \
    --cc=lua-l@lists.lua.org \
    --cc=monnier@iro.umontreal.ca \
    /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 public inbox

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

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).