From: Gary Johnson <garyjohn@spocom.com>
To: cygwin@cygwin.com
Subject: Re: Direct/efficient way to chop off trailing \n
Date: Wed, 01 Oct 2014 22:08:00 -0000 [thread overview]
Message-ID: <20141001220807.GC10508@phoenix> (raw)
In-Reply-To: <loom.20141001T235147-60@post.gmane.org>
On 2014-10-01, Paul.Domaskis wrote:
> Running bash in a Windows environment, I often find the need to
> generate a full Windows path to a file so that I can access the file
> from a Windows app.
>
> If I use
>
> cygpath -aw TheFile > /dev/clipboard
>
> I can paste into the Windows file-opener without browsing. Also, I
> don't need to mouse around to highlight the result of cygpath.
> However, the clipboard always contains an invisible carriage return,
> which I have to remove by pressing backspacing. This doesn't visibly
> change anything, but it does remove the trailing \n which chokes up
> Windows.
>
> Since I hate manually deleting stuff that I can't see, the most
> efficient way around this seems to be:
>
> cygpath -aw | tr -d '\n' > /dev/clipboard
>
> This is starting to get longer and longer. It is comprising the whole
> goal of getting a sequence of operations that is so brief that one
> does not sigh at having to do it countless times.
>
> Is there a more succinct way to get a clean path for a file from the
> bash shell into the Windows clipboard?
Define a function in your ~/.bashrc.
winclip()
{
cygpath -aw "$@" | tr -d '\n' > /dev/clipboard
}
Then just execute
winclip TheFile
Regards,
Gary
--
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
next prev parent reply other threads:[~2014-10-01 22:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 21:52 Paul.Domaskis
2014-10-01 22:08 ` Gary Johnson [this message]
2014-10-01 22:50 ` Jim Garrison
2014-10-01 22:54 ` Keith Christian
2014-10-01 22:56 ` Keith Christian
2014-10-01 23:06 ` Gary Johnson
2014-10-01 23:11 ` Paul.Domaskis
2014-10-01 23:35 ` Andrey Repin
2014-10-02 2:25 ` Eliot Moss
2014-10-02 2:33 ` Eric Blake
2014-10-02 13:13 ` Buchbinder, Barry (NIH/NIAID) [E]
2014-10-02 18:20 ` Paul.Domaskis
2014-10-02 23:24 ` Keith Christian
2014-10-03 5:05 ` Andrey Repin
2014-10-03 13:25 ` Paul.Domaskis
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=20141001220807.GC10508@phoenix \
--to=garyjohn@spocom.com \
--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).