All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add grep.fullName config variable
Date: Tue, 18 Mar 2014 11:39:23 -0700	[thread overview]
Message-ID: <xmqqzjkn8i78.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <mvmy507stf1.fsf@hawking.suse.de> (Andreas Schwab's message of "Tue, 18 Mar 2014 11:16:50 +0100")

Andreas Schwab <schwab@linux-m68k.org> writes:

> Yes, that would be required.  On the other hand, currently it is
> impossible to cut-n-paste a file name without --full-name, since the
> pager is always started in top-level.  Perhaps it is better to fix the
> latter?

So far we never cared where the pager runs, but as a principle, I
think it would be nice if we run it in the original subdirectory,
not at the top of the working tree (unless we have to bend backwards
to make the codepath involved too ugly, that is).

Don't we have the exact same issue for the editor, by the way?
Shouldn't we be running it in the original subdirectory as well?

  reply	other threads:[~2014-03-18 18:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-17 19:16 [PATCH] Add grep.fullName config variable Andreas Schwab
2014-03-17 22:21 ` Junio C Hamano
2014-03-18 10:16   ` Andreas Schwab
2014-03-18 18:39     ` Junio C Hamano [this message]
2014-03-18 19:51       ` Andreas Schwab
2014-03-18 20:16         ` Junio C Hamano
2014-03-18 20:01     ` Andreas Schwab
  -- strict thread matches above, loose matches on Subject: below --
2014-03-12  7:11 Andreas Schwab

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=xmqqzjkn8i78.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=schwab@linux-m68k.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 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.