unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: trentbuck@gmail.com (Trent W. Buck)
Cc: 18805@debbugs.gnu.org
Subject: bug#18805: 24.3; tramp adds /dev/null, breaks M-x grep
Date: Sun, 09 Nov 2014 11:58:27 +0100	[thread overview]
Message-ID: <87oasghc8c.fsf@gmx.de> (raw)
In-Reply-To: <87d29j6xkb.fsf@gmail.com> (Trent W. Buck's message of "Thu, 23 Oct 2014 18:43:16 +1100")

trentbuck@gmail.com (Trent W. Buck) writes:

> I routinely do M-x grep, but don't always run grep itself.
> For example, I might type in
>     find /usr/share/emacs/24.3/lisp/ -name \*.el.gz -exec zgrep -nH -e /dev/null {} +
> like I did to investigate this issue.
>
> The problem I'm having is when *in tramp* I do
>     M-x grep RET git grep -nH foo
> tramp helpfully appends " /dev/null" to the command, breaking it:
>     fatal: '/dev/null' is outside repository
>
> If I change it to
>     M-x grep RET git grep -nH foo #
> then I get the behaviour I want.
>
> This issue *DOES NOT* occur in local directories, only over tramp.

But this is neither a bug of Tramp nor of the grep command. The error
message "fatal: '/dev/null' is outside repository" comes from git.

As you have said the other message, /dev/null is added due to the
setting of grep-use-null-device. This is computed according to the needs
of grep, and not of git.

So I wouldn't regard this as an error.

Best regards, Michael.





  parent reply	other threads:[~2014-11-09 10:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-23  7:43 bug#18805: 24.3; tramp adds /dev/null, breaks M-x grep Trent W. Buck
     [not found] ` <handler.18805.B.14140502429734.ack@debbugs.gnu.org>
2014-10-23  8:05   ` Trent W. Buck
2014-11-09 10:58 ` Michael Albinus [this message]
2014-11-09 11:36   ` Michael Albinus

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=87oasghc8c.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=18805@debbugs.gnu.org \
    --cc=trentbuck@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).