zsh-workers
 help / color / mirror / code / Atom feed
From: Mikael Puhakka <mr.progo@gmail.com>
To: zsh-workers@zsh.org
Subject: Two different zsh sessions handle $* differently
Date: Tue, 22 Aug 2017 20:22:52 +0300	[thread overview]
Message-ID: <CAD1ad9bLy7cV8JByJcLg91ms1Eu27VDVQa8RA9H2Yf-tuBp4hA@mail.gmail.com> (raw)

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.

This is what happens in a freshly launched session:

    (~) echo $ZSH_VERSION
    5.2

    (~) whence -f j
    j () {
        noglob journal.py "$*"
    }

    (~) j Test. ABC this is a test.
    argv ['/home/progo/pika/journal.py', 'Test. ABC this is a test.']


And this is what the faulty session does:


    (~) echo $ZSH_VERSION
    5.2

    (~) whence -f j
    j () {
        noglob journal.py "$*"
    }

    (~) j Test. ABC this is a test.
    argv ['/home/progo/pika/journal.py', 'Test.']


The python script is modified to be trivial:

    (~) head -n5 /home/progo/pika/journal.py
    #!/usr/bin/env python3

    import sys
    print ('argv', sys.argv)
    sys.exit (0)


The faulty session might be a longer running one, if there's a way to
find out zsh-uptime, let me know. But I have several terminals open with
at least as old zsh sessions running, they behave correctly.

Unless X crashes or there's a long electricity break, I'll have these
sessions open if anyone comes up with something I can run to help with
this issue.

BR,
-- Mikael


             reply	other threads:[~2017-08-22 17:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22 17:22 Mikael Puhakka [this message]
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
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=CAD1ad9bLy7cV8JByJcLg91ms1Eu27VDVQa8RA9H2Yf-tuBp4hA@mail.gmail.com \
    --to=mr.progo@gmail.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).