zsh-users
 help / color / mirror / code / Atom feed
From: Frank Terbeck <ft@bewatermyfriend.org>
To: Michel <michel.barret@gmail.com>
Cc: zsh-users@zsh.org
Subject: Re: Update size of term
Date: Thu, 16 May 2013 15:55:46 +0200	[thread overview]
Message-ID: <8738tnqba5.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <CADprNY=x9RERE3hA1XCSFyaJbpyETtAcn8C08e8wFdFp_M2+vA@mail.gmail.com> (Michel's message of "Thu, 16 May 2013 15:27:15 +0200")

Michel wrote:
> I have a little problems with using of zsh with ssh.
> I'm connect to a ssh server, when I connect to the login shell is bash.
> I run zsh (with the command zsh or with "exec zsh"), but when I resize my
> terminal zsh don't update the size. In bash (before running of zsh), the
> size is correctly updated.
>
> Do you have any track to resolve my problem?

Which version of zsh are you using? If it is a git-snapshot that is a
few weeks old, there might have been a bug that you are now seeing.

If you are using a git-snapshot, you can examine the value of
$ZSH_PATCHLEVEL. It has the following format:

<nearest-tag>-<number-of-commits-since-that-tag>-g<sha1-sum-of-commit>

"<nearest-tag>" should be a release tag, such as "zsh-5.0.2" and
"<number-of-commits-since-that-tag>" should be an integer.

The 85th commit since the 5.0.2 release should fix the bug I'm thinking
of. It has a sha1-sum of "2405b0a", thus $ZSH_PATCHLEVEL should look at
least like this:

  zsh-5.0.2-85-g2405b0a

Any integer larger than 85 should be okay, too. Any commit before
zsh-5.0.2 should be okay, as well.


Regards, Frank


  reply	other threads:[~2013-05-16 14:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16 13:27 Michel
2013-05-16 13:55 ` Frank Terbeck [this message]
2013-05-16 16:00   ` Michel
2013-05-16 19:18     ` Phil Pennock
2013-05-17 14:51     ` Bart Schaefer

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=8738tnqba5.fsf@ft.bewatermyfriend.org \
    --to=ft@bewatermyfriend.org \
    --cc=michel.barret@gmail.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).