zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: (one-liner) adjustwinsize doesn't update prompt string
Date: Tue, 09 Aug 2005 11:05:45 +0100	[thread overview]
Message-ID: <200508091005.j79A5kY6025245@news01.csr.com> (raw)
In-Reply-To: <200508081258.38014.dan.zsh@bullok.com>

Dan Bullok wrote:
> I kept at this, and have made some progress  I'm able to completely work 
> around this problem by creating a new function in Src/Zle/zle_main.c  called 
> zle_resetprompt.  This does the same thing that resetprompt does, only it can
> be called from call the zle reset-prompt from outside of zle (i.e. in ).  
> Then you don't have to call trashzle, which seems to be the cause of the 
> extra newlines.  Instead, you call zle_resetprompt after calling zrefresh 
> (before might work, too, but I didn't try it).

Seems to work, so I checked this on both branches (code is a little
different on main).  I'm not convinced we need both the zrefresh()
before and the redisplay() after the prompt expansion (even though the
logic depends on zleactive), but it's small enough that I haven't played
around with it.

> > By the way, our mail scanning software (blackspider) decided there was a
> > virus (huntsman) in your script attachment.  It's presumably wrong, but
> > anyway the attachment got blocked.
> 
> Hmmm.  Everything looks okay here.  Mail was sent from a hardened Linux box 
> that gets regular inspections by rkhunter and chkrootkit.  It also seems to 
> have gone through the mailing list intact, because I got a copy (and it's the
> same one I sent).  I think your virus scanner's probably overcautious (which 
> isn't necessarily a bad thing).

Yes, I think so, too.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

**********************************************************************


      reply	other threads:[~2005-08-09 10:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-06 17:20 Dan Bullok
2005-08-08 10:32 ` Peter Stephenson
2005-08-08 17:58   ` Dan Bullok
2005-08-09 10:05     ` Peter Stephenson [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=200508091005.j79A5kY6025245@news01.csr.com \
    --to=pws@csr.com \
    --cc=zsh-workers@sunsite.dk \
    /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).