From: Ken Raeburn <raeburn@raeburn.org>
To: Miles Bader <miles@gnu.org>
Cc: Emacs Dev <emacs-devel@gnu.org>
Subject: Re: Last call for lua-mode contributors
Date: Fri, 20 Jan 2012 02:12:05 -0500 [thread overview]
Message-ID: <73D59FE1-CE29-4A63-8597-94A661DFD757@raeburn.org> (raw)
In-Reply-To: <CADCnXoYCU=D55CPvnPFMEMf8UxXmWRWj1_C8PASo_ZGCciF3tg@mail.gmail.com>
On Jan 20, 2012, at 00:12, Miles Bader wrote:
> Emacs contains convenient commands to do exactly those things
> regardless of word-syntax: C-M-f (forward-sexp), C-M-k (kill-sexp)
> etc. Obviously these commands are even _more_ "reliable" in that
> sense because they work the same in _all_ programming modes, and don't
> depend on user-customization.
I actually use some of them frequently when dealing with parenthesized lists like argument lists… but I guess for some reason I don't think of them when I'm working with a single identifier or keyword. Without the parens or some opening delimiter, I guess it just doesn't say "s-expression" to me; time to do some retraining I guess….
It's not immediately obvious looking at the description of forward-sexp, though, that it's really suitable for other modes. For example, it refers to a "balanced expression (sexp)", which doesn't tell me very well what to expect if the cursor is pointing at "int" or "return" (which aren't expressions) or "sizeof x" (which is an expression only if you include both words). The help message says it comes out of lisp.el, which is not encouraging if I'm in C mode; I'd half expect it to assume Lisp comment syntax or not work with braces. (I'm not saying it doesn't work; I know it does. I'm saying the description could be improved. But not by me at this hour.)
And now that I'm taking a fresh look at the s-expression bindings I should be using more, I want eval-last-sexp in C mode to evaluate C expressions. :-)
> [There are actually modes which make word-commands respect
> "STuDlyCapS" though…]
If they're minor modes suitable for use in conjunction with programming modes, that might be suitable, yes.
>> I realize I'm much closer to the power-user end of the spectrum than
>> most typical users, but among those heavily using programming modes,
>> is this such a strange mind-set?
>
> Wellllllll.... it does seem like a "power-user," and especially a
> programmer, would be most likely to know about and use Emacs'
> programming-specialized movement commands ..... :]
*ahem* Yeah, I guess you got me there… I do use some of them, but after 20+ years I guess I've developed some habits that give me blind spots to some places where I should be using them. Okay, I'm convinced....
Ken
next prev parent reply other threads:[~2012-01-20 7:12 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 [this message]
2012-01-20 14:17 ` Stefan Monnier
2012-01-21 3:20 ` Miles Bader
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=73D59FE1-CE29-4A63-8597-94A661DFD757@raeburn.org \
--to=raeburn@raeburn.org \
--cc=emacs-devel@gnu.org \
--cc=miles@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 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).