From: Mikael Puhakka <mr.progo@gmail.com>
To: Eitan Adler <lists@eitanadler.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Two different zsh sessions handle $* differently
Date: Tue, 22 Aug 2017 22:04:14 +0300 [thread overview]
Message-ID: <CAD1ad9ZjUeKomMFykg7w6RZmbOgWVQ=Lm=+GgG2wUCTo2r-EBA@mail.gmail.com> (raw)
In-Reply-To: <CAF6rxgneDifwUJKQAXZuwG6zhOtGTzFiARDh+HyJtr=7wFvzpw@mail.gmail.com>
They are the same in both:
posixargzero -> off
autolist -> on
printexitvalue -> off
kshzerosubscript -> off
histreduceblanks -> off
chaselinks -> off
extendedglob -> off
localloops -> off
histnostore -> off
automenu -> on
globcomplete -> off
unset -> on
listpacked -> off
promptsubst -> on
shwordsplit -> off
pathdirs -> off
kshtypeset -> off
listtypes -> on
warncreateglobal -> off
promptbang -> off
dotglob -> off
braceexpand -> on
listbeep -> on
correctall -> off
privileged -> off
numericglobsort -> off
histverify -> off
trackall -> on
histsubstpattern -> off
globstarshort -> off
cbases -> off
rcquotes -> off
posixaliases -> off
histfindnodups -> on
bashautolist -> off
sharehistory -> off
overstrike -> off
kshautoload -> off
incappendhistory -> on
appendcreate -> off
promptcr -> on
mailwarn -> off
pushdignoredups -> off
interactive -> on
ignoreeof -> off
globsubst -> off
rematchpcre -> off
monitor -> on
histsavebycopy -> on
histbeep -> on
debugbeforecmd -> on
magicequalsubst -> off
rmstarsilent -> off
posixjobs -> off
hashcmds -> on
posixtraps -> off
extendedhistory -> off
notify -> on
kshoptionprint -> off
histexpiredupsfirst -> off
glob -> on
posixcd -> off
braceccl -> off
badpattern -> on
longlistjobs -> off
banghist -> on
dvorak -> off
alwaystoend -> off
hashall -> on
globalexport -> on
ksharrays -> off
correct -> off
autonamedirs -> off
histexpand -> on
typesetsilent -> off
rmstarwait -> off
histnofunctions -> off
autoparamslash -> on
trapsasync -> off
sunkeyboardhack -> off
promptsp -> on
histsavenodups -> off
autocd -> off
allexport -> off
posixidentifiers -> off
cshjunkiehistory -> off
autopushd -> off
completeinword -> off
completealiases -> off
aliases -> on
autocontinue -> off
appendhistory -> on
singlelinezle -> off
hashlistall -> on
ignoreclosebraces -> off
recexact -> off
localoptions -> off
interactivecomments -> off
errexit -> off
cshjunkiequotes -> off
markdirs -> off
hashdirs -> on
cdablevars -> off
rcexpandparam -> off
vi -> off
printeightbit -> off
multifuncdef -> on
xtrace -> off
login -> off
cshjunkieloops -> off
histappend -> on
histignorespace -> off
evallineno -> on
shfileexpansion -> off
rcs -> on
functionargzero -> on
errreturn -> off
combiningchars -> off
histignoredups -> on
histfcntllock -> off
beep -> on
autoremoveslash -> on
hup -> on
globdots -> off
autoparamkeys -> on
shnullcmd -> off
multibyte -> on
zle -> on
promptpercent -> on
flowcontrol -> on
continueonerror -> off
incappendhistorytime -> off
autoresume -> off
globassign -> off
caseglob -> on
shortloops -> on
bsdecho -> off
cprecedences -> off
log -> on
transientrprompt -> off
verbose -> off
localpatterns -> off
ignorebraces -> off
pipefail -> off
equals -> on
menucomplete -> off
cshnullglob -> off
casematch -> on
promptvars -> on
histallowclobber -> off
bareglobqual -> on
shinstdin -> on
restricted -> off
pushdminus -> off
nullglob -> off
chasedots -> off
mailwarning -> off
listambiguous -> on
cshnullcmd -> off
bashrematch -> off
octalzeroes -> off
forcefloat -> off
exec -> on
multios -> on
emacs -> off
nomatch -> on
pathscript -> off
localtraps -> off
stdin -> on
onecmd -> off
kshglob -> off
clobber -> on
posixbuiltins -> off
alwayslastprompt -> on
pushdtohome -> off
histignorealldups -> off
hashexecutablesonly -> off
pushdsilent -> off
shoptionletters -> off
physical -> off
sourcetrace -> off
histlexwords -> off
bgnice -> on
globalrcs -> on
posixstrings -> off
checkjobs -> on
shglob -> off
singlecommand -> off
listrowsfirst -> off
BR,
-- Mikael
On 8/22/17, Eitan Adler <lists@eitanadler.com> wrote:
> On 22 August 2017 at 13:22, Mikael Puhakka <mr.progo@gmail.com> wrote:
>> Hi zsh-workers,
>>
>> Recently I noticed that my journal script has started to lose data. Then
>> I noticed that this is somehow in how zsh handles my little helper
>> function. This peculiarly affects one zsh session and not many others
>> that I can see.
>
> for key val in ${(kv)options}; do echo "$key -> $val"; done
> in each shell please
>
>
> --
> Eitan Adler
>
next prev parent reply other threads:[~2017-08-22 19:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 17:22 Mikael Puhakka
2017-08-22 18:40 ` Eitan Adler
2017-08-22 19:04 ` Daniel Shahaf
2017-08-22 19:19 ` Eitan Adler
2017-08-22 19:04 ` Mikael Puhakka [this message]
2017-08-23 19:17 ` Phil Pennock
2017-08-24 6:05 ` Mikael Puhakka
2017-08-24 8:48 ` Daniel Shahaf
2017-08-24 9:07 ` Mikael Puhakka
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='CAD1ad9ZjUeKomMFykg7w6RZmbOgWVQ=Lm=+GgG2wUCTo2r-EBA@mail.gmail.com' \
--to=mr.progo@gmail.com \
--cc=lists@eitanadler.com \
--cc=zsh-workers@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).