git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Koppe <andy.koppe@gmail.com>
To: "Rudisill, Steven L. (Booz Allen Hamilton)" <Steven.Rudisill@va.gov>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: mintty bug in current git bash (Git-2.42.0.2-64-bit.exe)
Date: Fri, 3 Nov 2023 14:58:25 +0000	[thread overview]
Message-ID: <CAHWeT-Z--gefA561v8i3Ff4EmfJbMasG3WPTHs7_YwCo0H03BA@mail.gmail.com> (raw)
In-Reply-To: <SJ0PR09MB99693718DDA17BC15532A3099CA5A@SJ0PR09MB9969.namprd09.prod.outlook.com>

On Fri, 3 Nov 2023 at 14:11, Rudisill, Steven L. (Booz Allen Hamilton) wrote:
> Mintty has a bug - when double-clicking on text, the preceding '~' or '.' is not selected.
> https://github.com/mintty/mintty/issues/1237
>
> This really slows down interacting in git bash because this is a very frequent console interaction:
> Double-clicking to select a path (which copies it to the paste buffer since the text is highlighted), then easily paste to manipulate text.
> The pasted text is omitting the preceding '~' or '.' character.
>
> Please release a new git bash version that uses the updated mintty with the fix for this bug. The issue link above indicates that this is a bug and has been fixed.

This is fixed in mintty 3.6.5, which is part of the Git for Windows
2.43.0 release candidate announced earlier today:

https://lore.kernel.org/git/20231103085526.3655-1-johannes.schindelin@gmx.de

Regards,
Andy

      reply	other threads:[~2023-11-03 14:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <SJ0PR09MB99699E1D1F577734F535CB1D9CA6A@SJ0PR09MB9969.namprd09.prod.outlook.com>
2023-11-03 14:10 ` mintty bug in current git bash (Git-2.42.0.2-64-bit.exe) Rudisill, Steven L. (Booz Allen Hamilton)
2023-11-03 14:58   ` Andy Koppe [this message]

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=CAHWeT-Z--gefA561v8i3Ff4EmfJbMasG3WPTHs7_YwCo0H03BA@mail.gmail.com \
    --to=andy.koppe@gmail.com \
    --cc=Steven.Rudisill@va.gov \
    --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.
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).