zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: saved from prince of eval
Date: Tue, 10 Nov 2015 20:18:13 -0800	[thread overview]
Message-ID: <151110201813.ZM2117@torch.brasslantern.com> (raw)
In-Reply-To: <564294D2.6050201@eastlink.ca>

On Nov 10,  5:07pm, Ray Andrews wrote:
}
} It's seems strange tho, how can a parameter be 
} set twice (or 16 times) to exactly the same value?

Obviously it can't.  You're either accidentally appending to something,
or setting the value of a new key in an associative array.

} Speaking of which, we have 'env' which only gives us the--don't know the 
} proper term--lowest level system stuff.

It's called "env" for "environment" -- it shows you the stuff that has
been "export"ed (or that was already in the environment before the
shell started).

} And we have 'set' which gives us 
} everything including the kitchen sink.

You probably want "typeset -p" followed by a list of the parameter
names you actually care about seeing.

} the output refuses to open in any of my editors if piped to a file, they 
} all think it's binary.

Probably because $IFS includes a NUL (zero) byte and bracketed_paste
contains a couple of ESC characters.

} Looking at it in hex, I see that it's a soup of 
} backslashes and single quotes. Why is that?

Because it's being output in the format that the shell would have to
parse in order to read it back in again.  However, the backslashes
are probably of your own making, from your attempts to use (e).  I've
got exactly two parameters that output with a backslash in the value:
SPROMPT and WORDCHARS.


  reply	other threads:[~2015-11-11  4:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-08 17:07 Ray Andrews
2015-11-08 19:57 ` Bart Schaefer
2015-11-08 22:04   ` Ray Andrews
2015-11-09  8:50     ` Ray Andrews
2015-11-09 18:41       ` Bart Schaefer
2015-11-10  0:48         ` Ray Andrews
2015-11-11  1:07         ` Ray Andrews
2015-11-11  4:18           ` Bart Schaefer [this message]
2015-11-11  5:31             ` 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=151110201813.ZM2117@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --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).