From: "Javier Oviedo" <email_joviedo@yahoo.com>
Subject: problem with grep and exec-path
Date: Tue, 15 Apr 2003 15:03:43 -0400 [thread overview]
Message-ID: <b7hkub$i2b$1@tilde.itg.ti.com> (raw)
Hello all:
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))
;;;
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.
Thanks in advance.
Javier.
next reply other threads:[~2003-04-15 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 19:03 Javier Oviedo [this message]
2003-04-15 21:12 ` problem with grep and exec-path Martin Stemplinger
2003-04-16 17:51 ` David Masterson
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='b7hkub$i2b$1@tilde.itg.ti.com' \
--to=email_joviedo@yahoo.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).