zsh-workers
 help / color / mirror / code / Atom feed
From: Tatsuo Furukawa <frkwtto@wnn.club.or.jp>
To: schaefer@brasslantern.com
Cc: zsh-workers@math.gatech.edu, olsenc@ichips.intel.com
Subject: Re: [3.0.5] patch for resize problem
Date: Wed, 28 Oct 1998 01:22:24 +0900	[thread overview]
Message-ID: <199810271622.BAA01468@pop1.ngy.3web.ne.jp> (raw)
In-Reply-To: <981024114334.ZM30186@candle.brasslantern.com> (schaefer@brasslantern.com)


Hi,

Bart> Unfortunately, what you did, except for irrelevant details in
Bart> params.c, is revert back to the 3.0.4 code.

Oh! Ouch!!

Bart> Although I don't entirely like the 3.0.5 behavior, *I've* never
Bart> had a problem with eval $(resize) setting LINES and COLUMNS
Bart> correctly (which was Clint's original complaint).

Yes, me too.  My (original, unpatched) zsh 3.0.5 does not have a
problem about "eval $(resize)".  Zsh always set correct LINES and
COLUMNS when I invoke eval $(resize).

But I hope I don't have to invoke "eval $(resize)".  I hope zsh always
set LINES and COLUMNS to right value automatically.

Because I use RPROMPT.  As you know, to use RPROMPT, I must always set
COLUMNS to right value.  To do this, I must invoke "eval $(resize)"
every time when I change the terminal size.  It makes me irritated.


Bart> If all you care about is having zsh believe SIGWINCH signals,
Bart> then a much simpler patch to 3.0.5, which doesn't back out the
Bart> other bug fixes, is:
    (snip)

Cool!  It works well!  Thank you Bart.  With this patch, I can say
Goodbye to "eval $(resize)".

--
Tatsuo Furukawa  (frkwtto@wnn.club.or.jp)


      reply	other threads:[~1998-10-27 16:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-24 10:52 Tatsuo Furukawa
1998-10-24 18:43 ` Bart Schaefer
1998-10-27 16:22   ` Tatsuo Furukawa [this message]

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=199810271622.BAA01468@pop1.ngy.3web.ne.jp \
    --to=frkwtto@wnn.club.or.jp \
    --cc=olsenc@ichips.intel.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@math.gatech.edu \
    /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).