From: David Masterson <David.Masterson@synopsys.com>
Subject: Re: problem with grep and exec-path
Date: 16 Apr 2003 10:51:32 -0700 [thread overview]
Message-ID: <uhe8yjpp7.fsf@synopsys.com> (raw)
In-Reply-To: b7hkub$i2b$1@tilde.itg.ti.com
>>>>> Javier Oviedo writes:
> I am using emacs 21.2 WINXP.
> I add the following line to my .emacs file in order to include the
> execution path for grep:
> ;;; Set exec paths.
> (setq exec-path (cons "T:/gen/gnu/99-11-01/cygwin-b20/H-i586-cygwin32/bin"
> exec-path))
> ;;;
Although this form is probably the simpler and, therefore, more
portable form, I prefer to use:
(add-to-list 'exec-path
"T:/gen/gnu/99-11-01/cygwin-b20/H-i586-cygwin32/bin")
> I evalutate this line and see that indeed the path was modified
> correctly. I still get errors when using grep.
> If I, however, move grep.exe under the emacs-21.2\bin driectory,
> everything seems to work.
> Does anyone have any ideas on this path issue? I'd prefer to not
> have a copy sitting in emacs-21.2\bin.
Hmmm. I believe that M-x grep uses essentially the same mechanism as
M-x shell. Therefore, after setting up exec-path, try M-x shell to
get to a shell buffer and then check the PATH of that shell from the
command line. Perhaps there is something in your setup that is
resetting the PATH in a new shell.
Another option is to try setting "grep-command" to be the full path of
your grep command. You may also want to adjust your find-grep-command
variable as well.
--
David Masterson David DOT Masterson AT synopsys DOT com
Sr. R&D Engineer Synopsys, Inc.
Software Engineering Sunnyvale, CA
prev parent reply other threads:[~2003-04-16 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 19:03 problem with grep and exec-path Javier Oviedo
2003-04-15 21:12 ` Martin Stemplinger
2003-04-16 17:51 ` David Masterson [this message]
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=uhe8yjpp7.fsf@synopsys.com \
--to=david.masterson@synopsys.com \
/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).