M-x grep in buffer *grep* puts you at the end of the grep output

M-x grep in buffer *grep* puts you at the end of the grep output

[Drew Adams]

> From: Drew Adams Sent: Saturday, April 28, 2007 11:50 AM
> To: Emacs-Pretest-Bug
>
> > From: Drew Adams Sent: Monday, December 11, 2006 3:21 PM
> > Previously in Emacs 22, as well as in previous releases, , repeating
> > grep in the *grep* buffer would put you at the top of the buffer. This
> > was true at least as late as a build from 2006-07-19.
> >
> > Now, it puts you at the end of the buffer, so you must do M-< to get
> > back to the beginning. Quite annoying.
>
> This is still broken. Are there plans to fix this?

Still broken. Never heard anything back on this. I don't see
anything in NEWS saying that this change is by design. It is
an annoyance, IMO.

The first time you use `grep', there is no problem, but if you
repeat `grep' from the *grep* buffer, point ends up at the end
of the output.

FYI, I'm using Cygwin grep (but I don't imagine it makes a difference).

In GNU Emacs 22.1.1 (i386-mingw-nt5.1.2600)
 of 2007-06-02 on RELEASE
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4) --cflags -Ic:/gnuwin32/include'

Re: M-x grep in buffer *grep* puts you at the end of the grep output

[Richard Stallman]

Would you like to debug WHY it fails?

RE: M-x grep in buffer *grep* puts you at the end of the grep output

[Drew Adams]

> Would you like to debug WHY it fails?

Sorry, I really don't have the time now.

Re: M-x grep in buffer *grep* puts you at the end of the grep output

[Martin Fischer]

  >>>>> Drew Adams <drew.adams@oracle.com> writes:
  > Date: Mon, 23 Jul 2007 21:07:04 -0700
8<--------------------------------------------------------------------

  > FYI, I'm using Cygwin grep (but I don't imagine it makes a difference).

Same with GnuWin32 grep (GNU grep) 2.5.1

Martin
-- 
parozusa at web dot de

Re: M-x grep in buffer *grep* puts you at the end of the grep output

[Richard Stallman]

    > From: Drew Adams Sent: Monday, December 11, 2006 3:21 PM
    > Previously in Emacs 22, as well as in previous releases, , repeating
    > grep in the *grep* buffer would put you at the top of the buffer. This
    > was true at least as late as a build from 2006-07-19.
    > 
    > Now, it puts you at the end of the buffer, so you must do M-< to get
    > back to the beginning. Quite annoying.

I think I have fixed this.  Does it work properly now?

RE: M-x grep in buffer *grep* puts you at the end of the grep output

[Drew Adams]

>     > Previously in Emacs 22, as well as in previous releases, , repeating
>     > grep in the *grep* buffer would put you at the top of the
>     > buffer. This was true at least as late as a build from 2006-07-19.
>     >
>     > Now, it puts you at the end of the buffer, so you must do M-< to get
>     > back to the beginning. Quite annoying.
>
> I think I have fixed this.  Does it work properly now?

Sorry, I wanted to test this, but I ran into too much trouble. I downloaded
the latest grep.el, but it wouldn't load in Emacs 22.1 because of the
changed file-remote-p signature. I downloaded the latest files.el to get
file-remote-p, but files.el wouldn't load either because of
declare-function. I have no idea where declare-function is defined, and I
don't want to continue chasing this.

You probably fixed it fine. Sorry I couldn't be more help testing it.
Perhaps someone else can confirm the fix.

(If GNU posted Windows binaries of CVS Emacs, I might keep more up-to-date.)

Re: M-x grep in buffer *grep* puts you at the end of the grep output

[Eli Zaretskii]

> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Thu, 27 Dec 2007 09:24:01 -0800
> Cc: emacs-pretest-bug@gnu.org
> 
> Sorry, I wanted to test this, but I ran into too much trouble. I downloaded
> the latest grep.el, but it wouldn't load in Emacs 22.1 because of the
> changed file-remote-p signature. I downloaded the latest files.el to get
> file-remote-p, but files.el wouldn't load either because of
> declare-function. I have no idea where declare-function is defined, and I
> don't want to continue chasing this.
> 
> You probably fixed it fine. Sorry I couldn't be more help testing it.
> Perhaps someone else can confirm the fix.
> 
> (If GNU posted Windows binaries of CVS Emacs, I might keep more up-to-date.)

It's really not a big deal to have a working build environment on
Windows.  Lennart's site has all the instructions, and there are a few
people here to help if you run into trouble.

Re: M-x grep in buffer *grep* puts you at the end of the grep output

[Richard Stallman]

    (If GNU posted Windows binaries of CVS Emacs, I might keep more up-to-date.)

You should set up a machine to run GNU/Linux.
Not only will it be easier for you to build on,
but you will start getting used to free software
so that someday you can escape to the Free World.