From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Alex Riesen <alexander.riesen@cetitec.com>
Cc: git@vger.kernel.org, Pat Thoyts <patthoyts@users.sourceforge.net>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 1/2] Support for $FILENAMES in tool definitions
Date: Mon, 27 Jun 2016 17:49:30 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1606271748250.12947@virtualbox> (raw)
In-Reply-To: <20160627132137.GC4194@pflmari>
Hi Alex,
On Mon, 27 Jun 2016, Alex Riesen wrote:
> This adds a FILENAMES environment variable, which contains the repository
> pathnames of all selected files the list.
> The variable contains the names separated by spaces.
>
> Similar to the FILENAME it is broken yet, if the names contain spaces.
>
> Note that the file marked and diffed immediately after starting the GUI up,
> is not actually selected. One must click on it once to really select it.
>
> Signed-off-by: Alex Riesen <alexander.riesen@cetitec.com>
Maybe prefix the subject with `git-gui: ` to indicate that this is for the
git-gui.git repository?
Also, please muster some patience, Pat seems to be super busy these days.
Ciao,
Dscho
next prev parent reply other threads:[~2016-06-27 15:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 13:21 [PATCH 1/2] Support for $FILENAMES in tool definitions Alex Riesen
2016-06-27 13:23 ` [PATCH 2/2] Ensure the file in the diff pane is always in the list of selected files Alex Riesen
2016-06-27 17:32 ` Jakub Narębski
2016-06-28 8:03 ` Alex Riesen
2016-06-27 15:49 ` Johannes Schindelin [this message]
2016-06-28 8:04 ` [PATCH 1/2] Support for $FILENAMES in tool definitions Alex Riesen
2016-06-27 17:28 ` Jakub Narębski
2016-06-27 17:53 ` Junio C Hamano
2016-06-27 18:09 ` Jakub Narębski
2016-06-28 8:54 ` Alex Riesen
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=alpine.DEB.2.20.1606271748250.12947@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=alexander.riesen@cetitec.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=patthoyts@users.sourceforge.net \
/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 NNTP newsgroup(s).