public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: Dragging from explorer to cygwin terminal is not putting the path into the terminal
Date: Fri, 07 Jun 2019 08:31:00 -0000	[thread overview]
Message-ID: <fe26d935ff31ee1dd5a1003b5e4530fd@smtp-cloud9.xs4all.net> (raw)
In-Reply-To: <c2313d0c-e8ab-86a9-c68c-40a2e6c78a24@towo.net>

On Fri, 7 Jun 2019 09:41:45, Thomas Wolff wrote:

> Am 07.06.2019 um 01:04 schrieb Houder:
[snip]

> > I cannot say anything sensible about the 2 scripts you have executed. Sorry.
> >
> > But I am afraid, that you may have to start from scratch again (reinstalling
> > W10) in order to find out under what circumstances the MinTTY feature starts
> > to fail. Yes, that would be a huge disappointment to you, I understand.
> Don't shoot with canons on sparrows (German proverb)!

Ah, you mean overkill ...

 - shoot sparrows w/ cannons
 - shoot gnats w/ cannons (Dutch proverb, even stronger :-)
 - crack nuts w/ sledgehammers (English proverb)

> I can confirm that I observed the issue, occasionally, under yet unclear 
> conditions. It even stopped to work once in a terminal session where it 
> initially worked. So no relation to Windows stuff to be assumed.
> It would be helpful to find a pattern that raises the issue. It would 
> also be helpful to check whether it occurs with mintty 3.0.0, as there 
> were some minor clipboard modifications in 3.0.1.

Again "Ah", you have the advantage of "Inside Information"; I did not.

Henri


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2019-06-07  8:31 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-06  4:26 Academy OfFetishes
2019-06-06 15:52 ` Chris Wagner
2019-06-06 16:08   ` Academy OfFetishes
2019-06-06 16:21     ` Academy OfFetishes
2019-06-06 17:15 ` Houder
2019-06-06 17:57   ` Academy OfFetishes
2019-06-06 19:56     ` Houder
2019-06-06 22:27       ` Academy OfFetishes
2019-06-06 22:34         ` Academy OfFetishes
2019-06-06 22:57           ` Brian Inglis
2019-06-06 23:04         ` Houder
2019-06-07  7:41           ` Thomas Wolff
2019-06-07  8:31             ` Houder [this message]
2019-06-07 17:33             ` Academy OfFetishes
2019-06-08  0:41               ` Doug Henderson
2019-06-08  0:53                 ` Academy OfFetishes
2019-06-08  7:10                   ` Thomas Wolff
2019-06-08 13:12                     ` Brian Inglis
2019-06-09 13:05                       ` Thomas Wolff
2019-06-09 13:20                         ` Jose Isaias Cabrera
2019-06-07  5:41         ` Achim Gratz
2019-06-07  5:46           ` Academy OfFetishes
2019-06-06 17:51 ` Achim Gratz
2019-06-06 17:51 ` Brian Inglis
2019-06-06 18:01   ` Academy OfFetishes
2019-06-06 21:59     ` Brian Inglis
2019-06-06 22:23       ` Academy OfFetishes
2019-06-06 23:03         ` Brian Inglis
2019-06-07  3:37         ` Brian Inglis
2019-06-07  4:04           ` Academy OfFetishes
2019-06-07  4:46             ` Brian Inglis
2019-06-07  5:20               ` Academy OfFetishes

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=fe26d935ff31ee1dd5a1003b5e4530fd@smtp-cloud9.xs4all.net \
    --to=houder@xs4all.nl \
    --cc=cygwin@cygwin.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.
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).