zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
	zsh-workers@math.gatech.edu
Subject: Re: fixsuffix() again
Date: Fri, 6 Nov 1998 00:57:29 -0800	[thread overview]
Message-ID: <981106005729.ZM936@candle.brasslantern.com> (raw)
In-Reply-To: <199811060816.JAA04521@beta.informatik.hu-berlin.de>

On Nov 6,  9:16am, Sven Wischnowsky wrote:
} Subject: Re:  fixsuffix() again
}
} Bart Schaefer wrote:
} > Sven, one of your patch hunks in zsh-workers/4510 removes a call to
} > fixsuffix() from the top of docompletion().  Is this intentional or not?
} 
} I have no idea where this fixsuffix() in docompletion() comes from

Looks like Zefram added it when he did the 3.1.5 release.  It's not in
any version I have in CVS until after I import the 3.1.5 code and merge.

} As I wrote in another message this may be a issue of personal
} taste. If we put a fixsuffix() there any suffix on the line that is
} autoremovable will become fixed when completion is tried in any way
} (listing matches, completion with no matches, ...).

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.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  reply	other threads:[~1998-11-06  9:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-06  8:16 Sven Wischnowsky
1998-11-06  8:57 ` Bart Schaefer [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-11-06  9:11 Sven Wischnowsky
1998-11-06 13:02 ` Peter Stephenson
1998-11-06 13:36   ` Sven Wischnowsky
1998-11-06 16:35     ` 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=981106005729.ZM936@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=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).