zsh-workers
 help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh workers <zsh-workers@zsh.org>
Subject: Re: PATCH Re: squeeze-slashes false not working?
Date: Sun, 15 May 2011 11:48:59 +0200	[thread overview]
Message-ID: <BANLkTimts9FbKv9Et4kNfS544zfXCd-Gdw@mail.gmail.com> (raw)
In-Reply-To: <110514183909.ZM15134@torch.brasslantern.com>

On 15 May 2011 03:39, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On May 14,  8:31pm, Mikael Magnusson wrote:
> }
> } On 14 May 2011 07:58, Bart Schaefer <schaefer@brasslantern.com> wrote:
> } > On May 13, 10:07pm, Mikael Magnusson wrote:
> } > }
> } > } With the same and path-files off, it simply behaves as if I had ls
> } > } /<tab>, ie it completes components in / after the four slashes.
> } >
> } > You mean path-completion off, but yes.  In this case it *should* be
> } > happening this way because
>
> I accidentally left that sentence unfinished:
>
> ... because by definition path-completion false means not to try to
> do any completing between slashes (whether consecutive slashes or
> not) unless the cursor is placed there and complete-in-word is set.
> This is independent of the setting of squeeze-slashes.
>
> Given that, does this next thing you said --
>
> } So maybe the squeeze-slashes entry should mention something to the
> } effect that disabling it will only allow other options to do stuff,
> } but maybe nothing will. But in a less stupid way.
>
> -- still mean anything?

Yeah, I sort of guessed the part you left out. What I would want is
some sort of hint in the squeeze-slashes description that
path-completion also has to be on, and as it turns out, maybe it
should mention accept-exact-dirs too. Is the squeeze-slashes setting
needed at all though? It seems like changing it or path-completion has
exactly the same effect; does enabling squeeze-slashes change some
behaviour that disabling path-completion does not change?

-- 
Mikael Magnusson


  reply	other threads:[~2011-05-15  9:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-12 17:18 Mikael Magnusson
2011-05-13 18:17 ` Peter Stephenson
2011-05-13 18:23   ` Mikael Magnusson
2011-05-13 18:53     ` Peter Stephenson
2011-05-13 20:07       ` Mikael Magnusson
2011-05-14  5:58         ` PATCH " Bart Schaefer
2011-05-14 18:31           ` Mikael Magnusson
2011-05-14 18:45             ` Mikael Magnusson
2011-05-15  1:38               ` Bart Schaefer
2011-05-15 10:12                 ` Mikael Magnusson
2011-05-15 18:15                   ` Bart Schaefer
2011-05-15 18:20                     ` Mikael Magnusson
2011-05-15  1:39             ` Bart Schaefer
2011-05-15  9:48               ` Mikael Magnusson [this message]
2011-05-15 10:01                 ` Mikael Magnusson

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=BANLkTimts9FbKv9Et4kNfS544zfXCd-Gdw@mail.gmail.com \
    --to=mikachu@gmail.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \
    /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).