From: covici@ccs.covici.com
To: Andrew Janke <andrew@apjanke.net>
Cc: Bart Schaefer <schaefer@brasslantern.com>, Zsh Users <zsh-users@zsh.org>
Subject: Re: problem with completion system
Date: Sat, 18 Jul 2015 14:25:55 -0400 [thread overview]
Message-ID: <26045.1437243955@ccs.covici.com> (raw)
In-Reply-To: <55AA957D.2@apjanke.net>
OK, thanks much. I did put anissue on there about something else and
have not heard back. I found those variables in the init.zsh, so maybe
that will help. I am also slowly making my way through the manual, so
maybe I will know something soon. Zsh has advantages, but it has quite
a learning curve. But then lots of things are like that.
Andrew Janke <andrew@apjanke.net> wrote:
> The main resource for Prezto support (as with Oh My Zsh) is its GitHub
> project and associated issue tracker
> (https://github.com/sorin-ionescu/prezto). Searching its issues
> (including the closed ones) or posting an issue of your own if you
> can't figure it out could get you help. They'll be more familiar with
> it than the main zsh mailing lists will.
>
> Prezto's completion-related stuff is set up in
> prezto/modules/completion/init.zsh. Browse through that to see what
> it's doing. It is commented. You probably care about the
> ALWAYS_TO_END, MENU_COMPLETE, and COMPLETE_IN_WORD
> options. https://github.com/sorin-ionescu/prezto/blob/6a812ed36bad9032df3645277793f5827dd64088/modules/completion/init.zsh#L25
>
> Prezto, OMZ, and Antigen can be good on-ramps to zsh, but like Bart
> says, they set and implement so many things that they diverge from
> default zsh, and you need to use them and their source code as your
> main reference and learning tool.
>
> Cheers,
> Andrew
>
>
> On 7/18/15 1:54 PM, covici@ccs.covici.com wrote:
> > I don't know of any mailing list for that -- maybe I will have to forget
> > about them and do my own -- I thought it would save me some time, but
> > maybe not.
> >
> > Bart Schaefer <schaefer@brasslantern.com> wrote:
> >
> >> On Jul 18, 8:05am, covici@ccs.covici.com wrote:
> >> }
> >> } hmmm, I am using zprezto
> >>
> >> In that case if there's a mailing list or other forum for prezto, I
> >> suggest you ask your question there. Plugin systems like oh-my-zsh
> >> and prezto can be very nice, but they reconfigure so many things that
> >> it's really not practical for us to try to debug them.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici
covici@ccs.covici.com
prev parent reply other threads:[~2015-07-18 18:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-18 7:01 covici
2015-07-18 10:16 ` Mikael Magnusson
2015-07-18 12:05 ` covici
2015-07-18 17:28 ` Bart Schaefer
2015-07-18 17:54 ` covici
2015-07-18 18:05 ` Andrew Janke
2015-07-18 18:25 ` covici [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=26045.1437243955@ccs.covici.com \
--to=covici@ccs.covici.com \
--cc=andrew@apjanke.net \
--cc=schaefer@brasslantern.com \
--cc=zsh-users@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).