zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: two mysteries
Date: Wed, 4 Nov 2015 12:35:46 -0800	[thread overview]
Message-ID: <151104123546.ZM20556@torch.brasslantern.com> (raw)
In-Reply-To: <563A4A75.1020009@eastlink.ca>

On Nov 4, 10:12am, Ray Andrews wrote:
}
}      START_IDX=1+((idx-1)/page_hight)*page_hight
} 
} ... it will work fine for days, then one Tuesday 'START_IDX' starts 
} throwing 'divide by zero' errors

This would be because page_hight (sic) is zero, not because the type
of START_IDX has changed.

}      START_IDX=$(( 1+((idx-1)/page_hight)*page_hight ))
} 
} ... fixes it

I suspect not really.  Something else changed so that the "page" is
no longer empty, or whatever.

} playing with associative arrays, yesterday I had to single quote:
} 
}       varis 'array[value]' line456 5
} 
} ... but only with arrays--scalars were fine--or I got a message to the 
} effect that 'no values were matched'.

Without the quotes, array[value] is being treated as a file glob, and is
looking for a file named one of arrayv, arraya, arrayl, arrayu, arraye.
The "no matches found" error is because none of those files exists.

} In the same vein, if one of these 'zcurses' functions crashes, what the 
} docs say about the terminal being in a unstable state sure is true. 
} Things look fine, but, for example, history recall goes screwy.

"stty sane" will often fix you up in this situation.  It might also work
to use "ttyctl -f" in your startup file (i.e., before any zcurses stuff
is run) but I'm not sure that handles the case where a zsh builtin has
itself messed up the terminal state.


  reply	other threads:[~2015-11-04 20:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-04 18:12 Ray Andrews
2015-11-04 20:35 ` Bart Schaefer [this message]
2015-11-05  0:38   ` Ray Andrews
2015-11-06 18:44     ` Bart Schaefer
2015-11-06 22:22       ` Ray Andrews
2015-11-07  9:55         ` Bart Schaefer
2015-11-07 15:19           ` Ray Andrews
2015-11-07 17:19             ` Bart Schaefer
2015-11-07 18:37               ` 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=151104123546.ZM20556@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).