zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Re: _expand doesn't do brace expansion?
Date: Fri, 16 Jun 2000 17:37:42 +0000	[thread overview]
Message-ID: <1000616173742.ZM4489@candle.brasslantern.com> (raw)
In-Reply-To: <200006160750.JAA12736@beta.informatik.hu-berlin.de>

On Jun 16,  9:50am, Sven Wischnowsky wrote:
} Subject: PATCH: Re: _expand doesn't do brace expansion?
}
} About the `a{b,c}<TAB>': of course this discussion now got me thinking 
} about it again, but this is horrible. There are a few things that I
} never changed in all my work on the completion code from 2.4.xxx
} on. One of them is that the completion code only ever has to work on
} one string. Trying to implement the above would change that and
} currently I don't even know where to place the loop over the possible
} prefixes/suffixes.

My inclination would be not to change the C code for this, but instead
to make the shell code expand the braces, generate completions for each
resulting string separately, and then mash them back together somehow.

Of course the "mash them back together" is the hard part, but if you
don't try to compute intersections it's just chopping off each of the
different prefixes and sticking on the original (with unexpanded braces)
from the line.

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

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


      reply	other threads:[~2000-06-16 17:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-16  7:50 Sven Wischnowsky
2000-06-16 17:37 ` Bart Schaefer [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=1000616173742.ZM4489@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=zsh-workers@sunsite.auc.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).