zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
	zsh-workers@sunsite.auc.dk
Subject: Re: blah*[TAB] (difference between 3.1.6 and 3.1.9)
Date: Wed, 7 Jun 2000 14:42:08 +0000	[thread overview]
Message-ID: <1000607144208.ZM8052@candle.brasslantern.com> (raw)
In-Reply-To: <200006070649.IAA11929@beta.informatik.hu-berlin.de>

On Jun 7,  8:49am, Sven Wischnowsky wrote:
} Subject: Re: blah*[TAB] (difference between 3.1.6 and 3.1.9)
}
} I wrote:
} 
} > Bart Schaefer wrote:
} > 
} > > Something's definitely gone wrong with expand-or-complete.  This was not
} > > intentional.
} > 
} > Ahem. Changed in 9777 in reply to 9756 (guess the author).
} > 
} > 9777 commented out some stuff in doexpansion(). Change it back?
} 
} I want to get that from my todo-list. Should we change it back? Bart
} (9765 was from you)?

Sorry, I couldn't make up my mind yesterday.

In 9777 you wrote:
> About the space: this was obviously intentional, too. I've just
> changed the test in doexpansion() so we can go back easily if suddenly 
> we decide the old behaviour was better. But what I would really like
> to have is a better test: when do we want the space and when not.

I think it should add the space only when the expansion results in more
than one word being inserted.  The reasoning is that it probably doesn't
make sense to continue completing only the last of several words that
were generated from the same pattern, but if only one word resulted then
it might reasonably be a prefix of a longer completion.

The potential issue I see with this is that what a lot of people want is
really expand-AND-complete (not "or"), which makes them think a space
should be appended if the result is an existing plain file, or something
like that.  In fact, I used to be one of them; for a long time I had
"setopt recexact" just so that two tabs would expand and then insert a
space rather than expand and then produce a listing (when one file name
is a prefix of another).  I've since come to the conclusion that recexact
is almost always more trouble than it is worth.  However, that doesn't
help resolve this ... perhaps another style?

-- 
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-07 14:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-07  6:49 Sven Wischnowsky
2000-06-07 14:42 ` 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=1000607144208.ZM8052@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=wischnow@informatik.hu-berlin.de \
    --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).