zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: question mark in filename.
Date: Sun, 10 Jan 2021 07:55:47 -0800	[thread overview]
Message-ID: <b8a7d8ff-e7ac-2961-3cbb-fb87dec3b69c@eastlink.ca> (raw)
In-Reply-To: <CAN=4vMrHD7gEZeMHrOjkkXSWEUcXRGY2z8X9c-VKFq8rYUdmFA@mail.gmail.com>

On 2021-01-10 7:28 a.m., Roman Perepelitsa wrote:
> It does that only when stdout is a tty. The output in this mode has
> been improved recently. Here's what I get:
>
>    % ls
>    's,7,big'$'\n''improvements'$'\n''in'$'\n''code'$'\n'
That's a whole lot more honest.  A linefeed is not a question mark. This 
can be put to bed now, but if I had one remaining question it is why (or 
how) I might have protected the rogue characters.  As I mentioned I 
tried ' ${(q)input} ' and variations because  that seems to swallow most 
things and I was suspicious.  Nevermind.
>    % ls | cat
>    s,7,big
>    improvements
>    in
>    code
Yeah, after I captured the output to a variable, that's exactly what it 
wanted to show and of course now I know that's exactly what it should 
show.  Linefeeds are linefeeds.

> That's just the output of `ls` when stdout is a tty.
Ok, so 'eval' is innocent of all this.  As usual the man page is less 
than helpful, they could mention all this and save us all the trouble.




  reply	other threads:[~2021-01-10 15:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-10  4:49 Ray Andrews
2021-01-10  5:39 ` Lawrence Velázquez
2021-01-10  5:46   ` Ray Andrews
2021-01-10  6:06     ` Lawrence Velázquez
2021-01-10  6:21       ` Ray Andrews
2021-01-10  7:02 ` Roman Perepelitsa
2021-01-10 15:03   ` Ray Andrews
2021-01-10 15:28     ` Roman Perepelitsa
2021-01-10 15:55       ` Ray Andrews [this message]
2021-01-10 16:32         ` Roman Perepelitsa
2021-01-10 20:57           ` Ray Andrews

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=b8a7d8ff-e7ac-2961-3cbb-fb87dec3b69c@eastlink.ca \
    --to=rayandrews@eastlink.ca \
    --cc=zsh-users@zsh.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).