From: Barry Margolin <barmar@alum.mit.edu>
Subject: Re: Problem With Emacs Lisp Mode
Date: Sun, 26 Jun 2005 22:46:59 -0400 [thread overview]
Message-ID: <barmar-273336.22465926062005@comcast.dca.giganews.com> (raw)
In-Reply-To: 877jgh5nzu.fsf@narke.yellow.line
In article <877jgh5nzu.fsf@narke.yellow.line>,
Steven Woody <narkewoody@gmail.com> wrote:
> everyone knows that a Ctrl-e will move the cursor to the end of current
> statement, but in Emacs Lisp mode, it seems no the true to me. Created a .el
> file and typed in something like below,
>
> (setq a 1)
> (setq b 2)
>
> then, i put the cursor on the begin of the first sentence, the do a Ctrl-e,
> the cursor will unexpectedly go to the end of the second sentence! has anyone
> encountered this kind of problem? i like to share your solution. thanks!
Control-e normally goes to the end of the current *line*. Are you
talking about Meta-e? Sentences end with a ".", "!", or "?" character
followed by whitespace, with an optional close quote or close
parenthesis after the punctuation. Your example doesn't have any of
these, so it goes to the end of the paragraph.
Most of the commands that deal with Lisp expressions are Meta-Control.
E.g. M-C-e will go to the end of the current function definition.
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
next prev parent reply other threads:[~2005-06-27 2:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-26 11:57 Problem With Emacs Lisp Mode Steven Woody
2005-06-27 2:46 ` Barry Margolin [this message]
2005-06-27 4:20 ` narke
2005-06-27 4:58 ` Barry Margolin
2005-06-27 6:19 ` narke
2005-06-27 13:34 ` Miles Bader
[not found] ` <mailman.1324.1119880749.2857.help-gnu-emacs@gnu.org>
2005-07-01 3:48 ` Steven Woody
2005-07-02 1:09 ` Miles Bader
2005-07-02 17:40 ` Stefan Monnier
2005-07-04 19:11 ` Steven Woody
2005-06-28 7:16 ` Stefan Monnier
2005-07-04 12:46 ` David Combs
2005-07-05 4:18 ` Stefan Monnier
2005-07-05 9:09 ` N. Raghavendra
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=barmar-273336.22465926062005@comcast.dca.giganews.com \
--to=barmar@alum.mit.edu \
/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).