From: Ted Zlatanov <tzz@lifelogs.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Run Shell Command on Buffer
Date: Thu, 25 Jan 2007 15:11:57 -0500 [thread overview]
Message-ID: <g691wlisw6q.fsf@dhcp-65-162.kendall.corp.akamai.com> (raw)
In-Reply-To: mailman.3575.1169739977.2155.help-gnu-emacs@gnu.org
On 25 Jan 2007, drew.adams@oracle.com wrote:
>>> It looks like `M-x occur' may be what you want.
>>
>> Yes, that is exactly it, thanks very much!
>
> If you like `occur', you might also be interested in this page:
> http://www.emacswiki.org/cgi-bin/wiki/OccurMode.
Also, the next-error/previous-error commands, which work under
grep/occur/compilation modes, are very useful. Try them. I bind mine
to F6/F7:
(global-set-key [f6] 'next-error)
(global-set-key [f7] 'previous-error)
They will jump to the next/previous point of interest out of all the
grep/occur/compilation points of interest related to the current
buffer.
Drew: can you update the wiki with this info, or I'll do it? Also,
can you check that your replace+.el (mentioned in the Emacs wiki)
works with next/previous error?
Ted
next parent reply other threads:[~2007-01-25 20:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3575.1169739977.2155.help-gnu-emacs@gnu.org>
2007-01-25 20:11 ` Ted Zlatanov [this message]
2007-01-25 21:04 ` Run Shell Command on Buffer Drew Adams
[not found] <mailman.3595.1169759151.2155.help-gnu-emacs@gnu.org>
2007-01-26 15:57 ` Ted Zlatanov
[not found] <mailman.3538.1169672554.2155.help-gnu-emacs@gnu.org>
2007-01-24 21:58 ` Marc Tfardy
2007-01-25 0:01 ` scame
2007-01-24 21:02 super-nub
2007-01-24 21:24 ` Peter Dyballa
2007-01-24 23:40 ` super-nub
2007-01-25 6:47 ` reader
2007-01-25 10:52 ` super-nub
2007-01-25 15:45 ` Drew Adams
[not found] ` <mailman.3545.1169683280.2155.help-gnu-emacs@gnu.org>
2007-01-25 2:32 ` Barry Margolin
2007-01-25 10:11 ` scame
2007-01-25 10:44 ` super-nub
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=g691wlisw6q.fsf@dhcp-65-162.kendall.corp.akamai.com \
--to=tzz@lifelogs.com \
--cc=help-gnu-emacs@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.
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).