zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Eric De Mund <ead@ixian.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: jumping ampersands?
Date: Sat, 16 Jul 2005 15:09:28 +0000	[thread overview]
Message-ID: <1050716150928.ZM30937@candle.brasslantern.com> (raw)
In-Reply-To: <17113.6118.560033.793675@bear.he.net>

On Jul 16,  7:21am, Eric De Mund wrote:
} Subject: Re: jumping ampersands?
}
} Bart Schaefer <schaefer@brasslantern.com>:
} ] the auto-removal of the previously auto-added trailing space.
} 
} Is this behavior option-settable?

Unfortunately, it's not settable in a way that you'd find useful.

You can turn off auto-removal, but that turns off auto-removal of all
suffixes (including most notably slashes after directory names), not
just spaces and not exclusively before semicolon/ampersand/bar, and
you *can't* turn off the auto-addition of the space.

The completion system supports using a shell function to decide what
to remove, but its name must be explicitly passed to the compadd
builtin; one function can't be applied generically to all completions.

} It represents an aesthetic that I just don't share; I strongly prefer
} a space character between commands and any following &'s, &&'s, and
} ||'s.

I share your sentiment.  The only thing I can immediately suggest is
that you train your fingers to type the space even if completion has
already added one.  Typing the space will cause the auto-added space
to be removed and replaced by the one you type, so the net effect is
invisible except that auto-removal will not thereafter occur.


      reply	other threads:[~2005-07-16 15:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-15 11:23 Eric De Mund
2005-07-15 14:54 ` Bart Schaefer
2005-07-16 14:21   ` Eric De Mund
2005-07-16 15:09     ` 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=1050716150928.ZM30937@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=ead@ixian.com \
    --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).