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: Thu, 06 Jun 2019 17:15:00 -0000	[thread overview]
Message-ID: <f3fca58fb43d9d7a630a1c9dd29036e7@smtp-cloud7.xs4all.net> (raw)
In-Reply-To: <CADvWqDWTAxpC1LeBf9we4cVyiVm57xZdL7Uu4zQvs74W7sKWoQ@mail.gmail.com>

On Wed, 5 Jun 2019 21:26:06, Academy OfFetishes  wrote:
> Hello,

Hello to you.

> I tried to google for this but couldn't find anyone with the same problem.
> I'm using mintty 3.0.1 and cygwin 3.0.7(0.338/5/3).
> 
> On my previous computer, if I dragged a file from my explorer to the cygwin
> terminal, the cygwin terminal used to be populated with the full path to
> that file.  Now when I do this, the cygwin terminal isn't affected.

On your previous computer? So you are using a freshly installed, new computer?

What does "uname -a" tell you? (just for a start).

> How do I get it to work the way it used to?  I want dragging from my
> explorer to the terminal to expand the full path of the filename in my
> terminal.

I do not know ...

You are sitting behind YOUR computer ... Not me.

What did you try? Something that can give us (and you) a clue ...

What happens if you drag a file to Notepad? Does it insert the contents
of that file in the buffer of Notepad?

Maybe you have some ideas of your own ...

Chris tried to help ... but we really need more info.

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

  parent reply	other threads:[~2019-06-06 17:15 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 [this message]
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
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 ` 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
2019-06-06 17:51 ` Achim Gratz

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=f3fca58fb43d9d7a630a1c9dd29036e7@smtp-cloud7.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).