From: Paul.Domaskis <Paul.Domaskis@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Direct/efficient way to chop off trailing \n
Date: Wed, 01 Oct 2014 23:11:00 -0000 [thread overview]
Message-ID: <loom.20141002T011040-272@post.gmane.org> (raw)
In-Reply-To: <loom.20141001T235147-60@post.gmane.org>
On 2014-10-01, Paul.Domaskis wrote:
> cygpath -aw foo | tr -d '\n' > /dev/clipboard
Gary Johnson wrote:
> Define a function in your ~/.bashrc.
>
> winclip()
> {
> cygpath -aw "$ <at> " | tr -d '\n' > /dev/clipboard
> }
>
> Then just execute
>
> winclip TheFile
Jim Garrison wrote:
> Sounds like cygpath needs a "-n" option which eliminates the
> trailing newline.
Eliot Moss wrote:
> echo -n $(cygpath -aw foo) > /dev/clipboard?
Gary, I was hoping for a magic bullet code idiom so that I don't have
to haul around a growing .alias.bash file. But I think your solution
might be the only one that significantly cuts down on the typing.
Jim, I think you're right. cygpath could benefit a lot from a -n
switch to suppress the new line. From google, however, it's actually
just li'l olde me that would benefit as no one else seems to have the
want for it. So I can see why such a switch has never been developed.
It's probably only needed for cygwin users, as it is the *unixy crowd
that uses both Windows & *nix at the same time.
Eliot, your solution takes 2 characters less than mine. If I want to
live without spaces aroud the "$(" and the ")". Which I suppose I
could do, for 2 characters..... I'm a bit enamoured of the linear
simplicity of my original pipeline, though. Appreciate the other
perspective, though.
Thank you all.
--
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 23:11 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
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 [this message]
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=loom.20141002T011040-272@post.gmane.org \
--to=paul.domaskis@gmail.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).