From: Jim Newton <jimka.velizy@googlemail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: how to make next-error work on non-grep non-compilation
Date: Fri, 20 May 2011 07:06:27 -0700 (PDT) [thread overview]
Message-ID: <c3db91cb-522d-49b3-9a1b-339e3221b5b8@glegroupsg2000goo.googlegroups.com> (raw)
In-Reply-To: <jwvfwo9wnb9.fsf-monnier+gnu.emacs.help@gnu.org>
> Does its name have something specific to its format (e.g. it uses
> a particular extension)?
No the file has no particular extension, but i can give it whatever extension it needs if that makes the job easier.
> Do you also want it to be editable at the same time?
It should not be editable.
> Maybe you need to set compilation-error-regexp-alist.
what should I set it to? I'm trying to make the format of the file already compatible with grep. I'm assuming that only the grep match lines are important and not the header lines which show the grep command line.
> Calling `compilation-compat-parse-errors' is a bad idea: just remove the
> call, it should not make any difference.
okeydokey
> I'd recommend you try something simpler based around something like:
>
> (let ((buf (find-file-noselect file-name)))
> (grep-mode))
Well I would like the buffer to have a more generic name so that if i run my function many times, it reuses the same buffer, thus destroying its old content. So I'd rather not make the buffer simple a file-visiting buffer.
-jim
next prev parent reply other threads:[~2011-05-20 14:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 11:41 how to make next-error work on non-grep non-compilation jimka
2011-05-20 11:47 ` Jim Newton
2011-05-20 12:53 ` Stefan Monnier
2011-05-20 13:48 ` Jim Newton
2011-05-20 14:11 ` Stefan Monnier
2011-05-20 14:18 ` Jim Newton
2011-05-20 14:06 ` Jim Newton [this message]
2011-05-20 14:54 ` Jim Newton
2011-05-20 16:20 ` Stefan Monnier
2011-05-20 15:39 ` Ted Zlatanov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c3db91cb-522d-49b3-9a1b-339e3221b5b8@glegroupsg2000goo.googlegroups.com \
--to=jimka.velizy@googlemail.com \
--cc=gnu.emacs.help@googlegroups.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.