From: David <bouncingcats@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: Re: Git Gui - enhancement suggestion - Can a double click on the file name in the “unstaged” area move the item to “staged changes”
Date: Sun, 15 Sep 2019 02:07:02 +1000 [thread overview]
Message-ID: <CAMPXz=qWmHGpDrGVpg1gwEBQsg5pujY-Ghg8icyaPoiMNCXssg@mail.gmail.com> (raw)
In-Reply-To: <CAKPyHN0=AHzr1V35PDzsq02aeGK1e54CxTeunED_u6GRUygkuA@mail.gmail.com>
On Sat, 14 Sep 2019 at 06:51, Bert Wesarg <bert.wesarg@googlemail.com> wrote:
> On Fri, Sep 13, 2019 at 4:32 PM Pratyush Yadav <me@yadavpratyush.com> wrote:
> > On 13/09/19 12:24PM, Allan Ford wrote:
>
> I miss a general problem description: Whats wrong with the
> single-click on the icon to begin with?
No problem here, but see my other message for further thoughts.
> I consider adding a second way as not not acceptable. I also consider
> double-click on a file in a GUI an "open" action.
Yes!
In fact, I've often fantasized how useful it would be that if I double
clicked on that file name in the unstaged pane or the staged pane,
then that would open the file for editing in my preferred/configured editor.
Now for me *that* would be a very frequently used improvement!
I wonder what other readers think about this idea?
next prev parent reply other threads:[~2019-09-14 16:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 2:54 Git Gui - enhancement suggestion - Can a double click on the file name in the “unstaged” area move the item to “staged changes” Allan Ford
2019-09-13 14:32 ` Pratyush Yadav
2019-09-13 20:27 ` Bert Wesarg
2019-09-13 21:06 ` Pratyush Yadav
2019-09-14 16:07 ` David [this message]
2019-09-14 19:08 ` Pratyush Yadav
2019-09-15 3:41 ` David
2019-09-16 17:49 ` Pratyush Yadav
2019-09-13 21:53 ` Marc Branchaud
2019-09-14 15:57 ` David
2019-09-14 21:23 ` Pratyush Yadav
2019-09-15 3:42 ` David
2019-09-14 7:24 ` Johannes Sixt
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMPXz=qWmHGpDrGVpg1gwEBQsg5pujY-Ghg8icyaPoiMNCXssg@mail.gmail.com' \
--to=bouncingcats@gmail.com \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.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).