Problem With Emacs Lisp Mode

Problem With Emacs Lisp Mode

[Steven Woody]

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!


-
narke

Re: Problem With Emacs Lisp Mode

[Barry Margolin]

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 ***

Re: Problem With Emacs Lisp Mode

[narke]

Barry Margolin wrote:
> 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.

no. i did mean Ctrol-e and what i expected is go to the end of current
line. in my example, the Ctrol-e always moves cursor to end of the next
line. but if i split a statement into more than one lines, such as
(setq a
      1)
Ctrol-e will work normally. i do not know why.


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

for this case, the M-C-e in my system always goes to the begining of
the next line which immediately below the ending line of the function!

>
> --
> Barry Margolin, barmar@alum.mit.edu
> Arlington, MA
> *** PLEASE post questions in newsgroups, not directly to me ***

Re: Problem With Emacs Lisp Mode

[Barry Margolin]

In article <1119846018.854668.134710@g49g2000cwa.googlegroups.com>,
 "narke" <narkewoody@gmail.com> wrote:

> Barry Margolin wrote:
> > 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.
> 
> no. i did mean Ctrol-e and what i expected is go to the end of current
> line. in my example, the Ctrol-e always moves cursor to end of the next
> line. but if i split a statement into more than one lines, such as
> (setq a
>       1)
> Ctrol-e will work normally. i do not know why.

Sounds like you have some non-standard key bindings.  What does C-h c 
C-e show?  For me it says end-of-line.

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***

Re: Problem With Emacs Lisp Mode

[narke]

Barry Margolin wrote:
> In article <1119846018.854668.134710@g49g2000cwa.googlegroups.com>,
>  "narke" <narkewoody@gmail.com> wrote:
>
> > Barry Margolin wrote:
> > > 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.
> >
> > no. i did mean Ctrol-e and what i expected is go to the end of current
> > line. in my example, the Ctrol-e always moves cursor to end of the next
> > line. but if i split a statement into more than one lines, such as
> > (setq a
> >       1)
> > Ctrol-e will work normally. i do not know why.
>
> Sounds like you have some non-standard key bindings.  What does C-h c
> C-e show?  For me it says end-of-line.

it says, C-e runs the command move-end-of-line

>
> --
> Barry Margolin, barmar@alum.mit.edu
> Arlington, MA
> *** PLEASE post questions in newsgroups, not directly to me ***

Re: Problem With Emacs Lisp Mode

[Miles Bader]

"narke" <narkewoody@gmail.com> writes:
> it says, C-e runs the command move-end-of-line

It sounds like you're running CVS Emacs.

There have been a few bizarre bugs recently that made line movement
commands do funny things; I don't know if they've been fixed, though.

-Miles
-- 
We are all lying in the gutter, but some of us are looking at the stars.
-Oscar Wilde

Re: Problem With Emacs Lisp Mode

[Stefan Monnier]

> 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!

You're running Emacs-CVS, i.e. unreleased software with weird bugs.
As explained in the file INSTALL.CVS, report problems via
M-x report-emacs-bug to emacs-pretest-bug@gnu.org.


        Stefan

Re: Problem With Emacs Lisp Mode

[Steven Woody]

Miles Bader <miles@gnu.org> writes:

> "narke" <narkewoody@gmail.com> writes:
>> it says, C-e runs the command move-end-of-line
>
> It sounds like you're running CVS Emacs.
>

sure! if this is really a bug, can i be noticed when it is fixed?

Re: Problem With Emacs Lisp Mode

[Miles Bader]

Steven Woody <anti-spam.narkewoody@gmail.com.dont-post-to> writes:
> sure! if this is really a bug, can i be noticed when it is fixed?

The bugs I noticed before (which resembled your bug, though I'm not sure
they're actually the same ones) seem to have been fixed in CVS.

-Miles
-- 
自らを空にして、心を開く時、道は開かれる

Re: Problem With Emacs Lisp Mode

[Stefan Monnier]

>>> it says, C-e runs the command move-end-of-line
>> It sounds like you're running CVS Emacs.
> sure! if this is really a bug, can i be noticed when it is fixed?

Only if you report it with M-x report-emacs-bug


        Stefan

Re: Problem With Emacs Lisp Mode

[David Combs]

In article <87k6kf7y0z.fsf-monnier+gnu.emacs.help@gnu.org>,
Stefan Monnier  <monnier@iro.umontreal.ca> wrote:
...
>
>You're running Emacs-CVS, i.e. unreleased software with weird bugs.
>As explained in the file INSTALL.CVS, report problems via
>M-x report-emacs-bug to emacs-pretest-bug@gnu.org.

So, just how do I run M-x report-emacs-bug and have
it (as implied, automatically!) redirect to emacs-pretest-bug@gnu.org.

Probable answer?:  Not automatic -- you edit-in that to-addr
*by hand*?

Thanks,

David

Re: Problem With Emacs Lisp Mode

[Steven Woody]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>>> it says, C-e runs the command move-end-of-line
>>> It sounds like you're running CVS Emacs.
>> sure! if this is really a bug, can i be noticed when it is fixed?
>
> Only if you report it with M-x report-emacs-bug
>
>
>         Stefan

i reported that and go back to the lastest stable release, now everything seems
well.

-
narke

Re: Problem With Emacs Lisp Mode

[Stefan Monnier]

>> You're running Emacs-CVS, i.e. unreleased software with weird bugs.
>> As explained in the file INSTALL.CVS, report problems via
>> M-x report-emacs-bug to emacs-pretest-bug@gnu.org.

> So, just how do I run M-x report-emacs-bug and have
> it (as implied, automatically!) redirect to emacs-pretest-bug@gnu.org.

> Probable answer?:  Not automatic -- you edit-in that to-addr
> *by hand*?

Try it,


        Stefan

Re: Problem With Emacs Lisp Mode

[N. Raghavendra]

dkcombs@panix.com (David Combs) writes:

> In article <87k6kf7y0z.fsf-monnier+gnu.emacs.help@gnu.org>,
> Stefan Monnier  <monnier@iro.umontreal.ca> wrote:
> ...
> >
> >You're running Emacs-CVS, i.e. unreleased software with weird bugs.
> >As explained in the file INSTALL.CVS, report problems via
> >M-x report-emacs-bug to emacs-pretest-bug@gnu.org.
> 
> So, just how do I run M-x report-emacs-bug and have
> it (as implied, automatically!) redirect to emacs-pretest-bug@gnu.org.
> 
> Probable answer?:  Not automatic -- you edit-in that to-addr
> *by hand*?

See the definition of `report-emacs-bug'.  If your Emacs version
contains four numbers, then the bug message is sent to
`report-emacs-bug-pretest-address', whose value is
"emacs-pretest-bug@gnu.org".

Raghavendra.

-- 
N. Raghavendra <raghu@mri.ernet.in> | See mail headers for contact
Harish-Chandra Research Institute   | and OpenPGP details.