zsh-workers
 help / color / mirror / code / Atom feed
From: Wayne Davison <wayned@users.sourceforge.net>
To: <zsh-workers@sunsite.dk>
Subject: Re: Another keep-prefix problem
Date: Thu, 26 Apr 2001 16:38:50 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.30.0104261631150.22890-100000@phong.blorf.net> (raw)
In-Reply-To: <1010426171819.ZM17731@candle.brasslantern.com>

On Thu, 26 Apr 2001, Bart Schaefer wrote:
>      something like `~foo' or `$foo', but not if it is `~foo/' or
>      `$foo/bar', unless that suffix itself contains characters eligible
>                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>      for expansion.  The default for this style is `true'.

Which is what I'm advocating changing.  Don't require the variable to
be at the start of the word, just look if there are suffix char(s)
between the variable and the cursor, and only expand the variable if
the cursor is right next to the variable.  This is how the old
expander works.

> Which means, I think, that you would like the default setting of suffix
> to be false rather than true, and the default setting of keep-prefix to
> be true rather than "changed".

No, setting suffix to false would make it expand variables even when
suffix chars are present, and that's different than the default with
the old expander, so I'd leave suffix set to true by default.  I
wouldn't mind having keep-prefix set to true by default, but I think
that's a separate issue from making "suffix true" work the same as the
old expansion code.

..wayne..


  reply	other threads:[~2001-04-26 23:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-26 14:27 Oliver Kiddle
2001-04-26 15:43 ` Wayne Davison
2001-04-26 17:18   ` Bart Schaefer
2001-04-26 23:38     ` Wayne Davison [this message]
2001-04-27  9:03 ` Sven Wischnowsky
  -- strict thread matches above, loose matches on Subject: below --
2001-04-24  0:46 Wayne Davison
2001-04-24 16:50 ` Bart Schaefer
2001-04-24 19:18   ` Wayne Davison
2001-04-25 13:25     ` Sven Wischnowsky
2001-04-26  4:33       ` 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=Pine.LNX.4.30.0104261631150.22890-100000@phong.blorf.net \
    --to=wayned@users.sourceforge.net \
    --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).