zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: zsh-workers@zsh.org
Subject: Re: zle messes up 'words' variable?
Date: Mon, 02 May 2011 18:42:35 -0700	[thread overview]
Message-ID: <110502184235.ZM14465@torch.brasslantern.com> (raw)
In-Reply-To: <BANLkTin1YcDOSGb+9FGYVgoC4cwN37_dnA@mail.gmail.com>

On May 2,  9:11pm, Felipe Contreras wrote:
}
} On Fri, Apr 29, 2011 at 6:31 AM, Bart Schaefer
} <schaefer@brasslantern.com> wrote:
} > Your example in workers/29086 explicitly loads and runs bashcompinit.
} > What am I missing?
} 
} What is 'workers/29086'?

Sorry, I'm writing in zsh-workers subscriber-speke.  Every message sent
to the zsh-workers (or zsh-users) list is tagged with an "X-Seq:" header
containing a number.  The archive server at zsh.org is able to look up
messages by sequence number.  So we shorthand "go to the zsh.org archive
and put 29086 into the workers lookup field" as "workers/29086".
 
} I am using bashcompinit, but the issue appears without it.

Without bashcompinit, there is by definition not an issue.  Or, if you
prefer, you should have expected this issue to appear, because words is
documented as a special variable in completion function context.

If what you want to discuss is ways to fix bashcompinit so that the
functions in bash completion work as expected, that's one thing.  If
what you're asking is for the special-ness of "words" to be undone
for completion in general, that's so unlikely to happen as to not be
worth continuing.


  reply	other threads:[~2011-05-03  1:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27  8:26 Felipe Contreras
2011-04-27  9:02 ` Jérémie Roquet
2011-04-27  9:11   ` Felipe Contreras
2011-04-27  9:51     ` Felipe Contreras
2011-04-27 15:06 ` Bart Schaefer
2011-04-28 20:19 ` Felipe Contreras
2011-04-29  3:31   ` Bart Schaefer
2011-05-02 18:11     ` Felipe Contreras
2011-05-03  1:42       ` Bart Schaefer [this message]
2011-05-03  8:05         ` Felipe Contreras
2011-05-03 14:39           ` Bart Schaefer
2011-05-03 15:04             ` Bart Schaefer
2011-05-03 17:41               ` Felipe Contreras
2011-05-04  0:39                 ` Bart Schaefer
2011-05-05 14:39                   ` Felipe Contreras
2011-05-05 16:24                     ` Bart Schaefer
2011-05-05 16:40                       ` Felipe Contreras
2011-05-05 19:38                         ` Bart Schaefer
2011-05-05 20:14                           ` Felipe Contreras
2011-05-05 21:12                             ` Nikolai Weibull
2011-05-03 17:36             ` Felipe Contreras
2011-05-04  0:56               ` Bart Schaefer
2011-05-05 14:48                 ` Felipe Contreras
2011-05-05 15:50                   ` Bart Schaefer
2011-05-05 15:55                     ` Felipe Contreras

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=110502184235.ZM14465@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=felipe.contreras@gmail.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).