zsh-workers
 help / color / mirror / code / Atom feed
From: Yuri D'Elia <wavexx@thregr.org>
To: zsh-workers@zsh.org
Subject: Re: Changing subword-range according to current completion context
Date: Fri, 03 Nov 2017 15:57:33 +0100	[thread overview]
Message-ID: <87h8ubbeaq.fsf@wavexx.thregr.org> (raw)
In-Reply-To: <20171103122349.4bf81a1c@pwslap01u.europe.root.pri>

On Fri, Nov 03 2017, Peter Stephenson wrote:
>> I'd like to fine-tune the way words are interpreted according to the
>> completion context which was used to expand the word, not to the zle
>> context.
>> 
>> Is it saved anywhere? Is it possible to correlate the two?
>
> Hmm, I'm not sure that completion even has a generic notion of
> words as such.  Each completion just parses the command line, generally
> (but not necessarily) starting with a single command line word as
> entered so far --- in this case parsed according to shell rules by
> the lexical analyser, this is hard-wired because it's extremely
> complicated --- and then takes it from there. I can't think of a point
> where it matches neatly onto a single interface that tells you the bits
> of what you're looking at.

Isn't the state of each word, once expanded, saved somewhere?
_complete_debug doesn't show anything interested.

By reading the manual, I'm not completely sure about the relationship
between match-words-by-style and match-word-context.

> Did you have an example?

Just to reiterate, imagine expanding a path. But the expansion needs to
be altered for some reason. I often kill the last path component.

If the context of the completer was saved, I could say that *only*
expanded paths get splitted by '/', and not other arguments.

I'm not sure it would be "terrific" in practical terms, as for this kind
of interaction you need to play around and see if it's worth the
tweaking.


  reply	other threads:[~2017-11-03 14:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20171103121014epcas2p1342033fa4eb58a6d7f61400c619d0b52@epcas2p1.samsung.com>
2017-11-03 11:52 ` Yuri D'Elia
2017-11-03 12:23   ` Peter Stephenson
2017-11-03 14:57     ` Yuri D'Elia [this message]
2017-11-04  1:22       ` Bart Schaefer
2017-11-04 10:41         ` Yuri D'Elia

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=87h8ubbeaq.fsf@wavexx.thregr.org \
    --to=wavexx@thregr.org \
    --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).