zsh-users
 help / color / mirror / code / Atom feed
From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: question mark in filename.
Date: Sun, 10 Jan 2021 08:02:25 +0100	[thread overview]
Message-ID: <CAN=4vMpjAzui04sEP5SsXDfqnJjF8Jt0Oir0qUsWzXAojy3snQ@mail.gmail.com> (raw)
In-Reply-To: <d720a4ef-d2b6-51b4-d6a6-98b583338621@eastlink.ca>

On Sun, Jan 10, 2021 at 5:50 AM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> Not that there should ever be such a thing, but I was curious:  I throw
> strings around mostly successfully but not with the stupid question mark:
>
>
>     function test1 ()
>     {
>          input=( "$@" )         # 'input' is fine: "ls s,7*"
>          eval $input            # this works fine.
>          output=( $(eval ${()input}) )
>          print "$output"        # ... but 'output' looses the question
>     marks.
>     }
>
>     function test2 ()
>     {
>          string="ls s,7*"       # 'ls' finds: 's,7,big?improvements?in?code'
>          test1 $string
>     }
>
>     $ . test; test2
>     s,7,big?improvements?in?code
>     s,7,big improvements in code

My guess is that the name of this file contains something interesting
in place of question marks (ascii 63). Try this:

    ls s,7* | cat -v
    print -r -- s,7* | od -t x1 -An -v

Roman.


  parent reply	other threads:[~2021-01-10  7:03 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 [this message]
2021-01-10 15:03   ` Ray Andrews
2021-01-10 15:28     ` Roman Perepelitsa
2021-01-10 15:55       ` Ray Andrews
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='CAN=4vMpjAzui04sEP5SsXDfqnJjF8Jt0Oir0qUsWzXAojy3snQ@mail.gmail.com' \
    --to=roman.perepelitsa@gmail.com \
    --cc=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).