public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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 23:06:00 -0000	[thread overview]
Message-ID: <20141001230637.GD10508@phoenix> (raw)
In-Reply-To: <542C854D.3050001@jhmg.net>

On 2014-10-01, Jim Garrison wrote:
> On 10/1/2014 2:52 PM, 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.
> [snip]
> >... but it does remove the trailing \n which chokes up
> > Windows.
> 
> Sounds like cygpath needs a "-n" option which eliminates the
> trailing newline.

The trouble with that is that the "problem" is common to (almost?)
all Unix commands, not just cygpath.  That is, they all send their
output to stdout as lines of text, each line terminated by a
newline, as it should be.  You can send the output of any command to
/dev/clipboard and it will be terminated by a newline.  If that's
not desired, then one needs to take extra steps in the pipeline,
which is what tr is for.

Another solution would be to wrap the redirection to /dev/clipboard
in a function or script that takes your "-n" option and pipe the
output of cygpath or whatever command to that wrapper.

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

  parent reply	other threads:[~2014-10-01 23:06 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 [this message]
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=20141001230637.GD10508@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).