zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: globcomplete desctroys file completion
Date: Wed, 25 Feb 2009 17:30:59 -0800	[thread overview]
Message-ID: <090225173059.ZM21819@torch.brasslantern.com> (raw)
In-Reply-To: <20090225204844.08a39c17@pws-pc>

On Feb 25,  8:48pm, Peter Stephenson wrote:
} Subject: Re: globcomplete desctroys file completion
}
} Scratch that, it's simpler---we never want two -s's, we just want to
} ensure $ISUFFIX is there when needed.  This time I do have some evidence
} this is doing better things with GLOBCOMPLETE set than previously.

This is better, and in fact was something I was about to suggest, but
the cursor is still left in the wrong place when a component in the
middle of the path is ambiguous.

schaefer<505> print T/t/t<TAB>
schaefer<505> print Tmp/texlive/t

Cursor should be on the rightmost slash, because "texlive" could also
be completed to "texlive2008", but instead cursor is at the end.

Take a look at this:

schaefer<506> print T*/t*/t<TAB>
schaefer<506> print Tmp/texlive/texmf-local/
Completing default
texlive/      texlive/      texlive/      texlive2008/
texlive/      texlive/      texlive2008/  texlive2008/
texlive/      texlive/      texlive2008/  texlive2008/
texlive/      texlive/      texlive2008/  texlive2008/

(menu-select highlight is on the first "texlive/").  If I left-arrow
through the menu, I get e.g.

schaefer<506> print Tmp/texlive/texmf-config/

schaefer<506> print Tmp/texlive/texmf-var/

schaefer<506> print Tmp/texlive2008/texmf-dist/

This leads me to believe that really the second -s should have been
a -S (a suffix, not a hidden suffix) and the first -s in tmp4 was in
fact correct.   Making that change produces still better results:

schaefer<507> print T/t/t<TAB>
schaefer<507> print Tmp/texlive/t
Completing corrections
texlive/      texlive2008/
Completing original
T/t/t

However, that does not produce better cursor placement, so I remain
puzzled/unconvinced.

Also, any comment on the overlapping -W and -p values?  What exactly
does the doc mean when it says that they are used "together"?


  parent reply	other threads:[~2009-02-26  1:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-21 14:18 Jörg Sommer
2009-02-21 19:16 ` Bart Schaefer
2009-02-22  0:57   ` Bart Schaefer
2009-02-25 20:39     ` Peter Stephenson
2009-02-25 20:48       ` Peter Stephenson
2009-02-26  0:24         ` Jörg Sommer
2009-02-26  1:30         ` Bart Schaefer [this message]
2009-02-26  4:12           ` Bart Schaefer
2009-02-26 10:49             ` Peter Stephenson
2009-02-22 20:36   ` Jörg Sommer
2009-02-23  2:25     ` 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=090225173059.ZM21819@torch.brasslantern.com \
    --to=schaefer@brasslantern.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).