From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: shell-command causes problems with absolute/relative paths in TAGS
Date: Fri, 06 Jan 2012 20:46:53 +0200 [thread overview]
Message-ID: <83d3awoehu.fsf@gnu.org> (raw)
In-Reply-To: <96C2AF32F1EC4A1997BB692A003ED374@EUROPE.ROOT.PRI>
> From: "David Chappaz" <david.chappaz@free.fr>
> Date: Fri, 6 Jan 2012 16:03:47 -0000
>
>
> > > The variable name depends on which shell you use. By default, only
> > > explicit-bash-args and explicit-sh-args are defined in emacs.
> > > On windows, cmdproxy.exe is the default shell, hence the variable name.
> >
> > Well, I tried that on Windows with cmdproxy as the shell, and I still
> > don't see this variable.
>
> Ah well I haven't been accurate enough.
> It's for the user to create this variable if they want to. It will only be
> used if its name perfectly matches that of the shell.
> See details in section 7.10 of
> http://www.gnu.org/software/emacs/windows/Sub_002dprocesses.html
Never mind, that variable is not needed for reproducing the problem.
> Surely emacs must be passing slightly different arguments to ctags (perhaps
> slashes in a different orientation), before and after the first call to
> call-process-region ?
Probably some environment variable rather than command-line argument.
next prev parent reply other threads:[~2012-01-06 18:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 22:33 M-x mystery Silvio Levy
2012-01-02 23:25 ` Drew Adams
2012-01-04 16:05 ` shell-command causes problems with absolute/relative paths in TAGS David Chappaz
2012-01-04 16:15 ` Vladimir Murzin
2012-01-04 16:27 ` David Chappaz
2012-01-05 5:41 ` Bob Proulx
2012-01-05 12:20 ` David Chappaz
2012-01-05 16:53 ` Unknown
2012-01-05 22:20 ` Bob Proulx
2012-01-06 11:12 ` David Chappaz
2012-01-06 11:38 ` Eli Zaretskii
2012-01-06 13:04 ` David Chappaz
2012-01-06 15:42 ` Eli Zaretskii
2012-01-06 16:03 ` David Chappaz
2012-01-06 16:12 ` David Chappaz
2012-01-06 18:46 ` Eli Zaretskii [this message]
2012-01-06 11:25 ` Eli Zaretskii
2012-01-06 14:04 ` David Chappaz
2012-01-06 15:12 ` Eli Zaretskii
2012-01-06 15:52 ` Juanma Barranquero
2012-01-06 11:34 ` Eli Zaretskii
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=83d3awoehu.fsf@gnu.org \
--to=eliz@gnu.org \
--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).