zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@math.gatech.edu
Subject: Re: fixsuffix() again
Date: Fri, 6 Nov 1998 14:36:25 +0100 (MET)	[thread overview]
Message-ID: <199811061336.OAA05917@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Peter Stephenson's message of Fri, 06 Nov 1998 14:02:32 +0100


Peter Stephenson wrote:

> 
> Sven Wischnowsky wrote:
> > > So you mean with that one call to fixsuffix() in docompletion() we can
> > > get rid of all the other calls to fixsuffix() scattered about in other
> > > places?  If so, then by golly I vote for putting that one back and
> > > nuking the others.
> > 
> > The one in deletecharorlist() will still be need since it is in the
> > branch where completion is noct called. So it would make two instead
> > of three calls in zle_tricky.c. The patch below does this, but note
> > that there is one ugliness:
> 
> I've found a more serious problem with this.
> 
> % export ZMLIB=$PWD               # some people probably have this set anyway
> % setopt noautomenu menucomplete noautolist
> % echo $Z<TAB>            -> $ZMLIST/
>          <TAB>            -> $ZSH_NAME
>          <TAB>            -> $ZSH_VERSION
>          <RET>            -> $ZSH_VERSIO
> 
> It seems to lose memory of the fact that the slash has already gone.

Ok, then there is another reason not to move the fixsuffix()
there (the problem Peter reported can be fixed by the fixsuffix() in
do_single()).


Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


         reply	other threads:[~1998-11-06 13:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-06  9:11 Sven Wischnowsky
1998-11-06 13:02 ` Peter Stephenson
1998-11-06 13:36   ` Sven Wischnowsky [this message]
1998-11-06 16:35     ` Bart Schaefer
  -- strict thread matches above, loose matches on Subject: below --
1998-11-06  8:16 Sven Wischnowsky
1998-11-06  8:57 ` Bart Schaefer
1998-11-06  7: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=199811061336.OAA05917@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --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).