I could understand it. That is the reason I said "But it's up to you.".
Jun ----- Original Message ----- > From: "Vít Ondruch" <vondr...@redhat.com> > To: ruby-sig@lists.fedoraproject.org > Sent: Monday, March 20, 2017 6:13:51 PM > Subject: Re: Ruby optparser bash completion support > > > > Dne 20.3.2017 v 17:20 Jun Aruga napsal(a): > > Hi, > > > >> Should we store the "rb_optparse.bash" somewhere? > > It does not matter for me. > > > > If we provide it, there is a sample in python3 package. > > > > http://pkgs.fedoraproject.org/cgit/rpms/python3.git/tree/python3.spec > > This was more rhetoric/abstrac question, because we don't need to use > the rb_optparse functionality directly. > > >> L1467 %doc Misc/README.valgrind Misc/valgrind-python.supp Misc/gdbinit > > "Misc" (camel case) is python's directory habit. we should use "misc" > > instead of that. > > > > The package name might be "ruby-misc" or "ruby-tools", or including > > "ruby-devel", and etc.. > > > > misc/ > > rb_optparse.bash > > rb_optparse.zsh > > *.el (emacs macro) > > > >> Should we try to enable the bash completion for every Ruby executable? > >> Should we have some macro for this? > > No, "rb_optparse.bash" are not installed when I installed Ruby from source > > with default configure option. > > That means that using the file is not common. > > Well, it is not common because it is not widely known. And we are > working on distribution, we know our platform and we have means to > provide better integration and user experience. > > Actually, now I realize that I was not precise enough saying "for every > Ruby executable" when I actually assumed executables provided by our > packages. But on the other hand, I would love to see this used for every > Ruby executable if possible. Why not (except from technical issues, > which can be resolved typically)? > > > Vít > > > > > But it's up to you. > > > > Jun Aruga > > > > ----- Original Message ----- > >> From: "Vít Ondruch" <vondr...@redhat.com> > >> To: "Ruby SIG mailing list" <ruby-sig@lists.fedoraproject.org> > >> Sent: Monday, March 20, 2017 3:39:00 PM > >> Subject: Ruby optparser bash completion support > >> > >> Hi all, > >> > >> For ages, there is Bash/Zsh completion support available for the default > >> OptParser [1]. That means quite some Ruby application could provide some > >> basic command completion out of the box. However, the setup is a bit > >> clumsy. The steps necessary to enable the command completion for single > >> executable are described her [2]. Any ideas, how we could benefit from > >> this feature? Should we store the "rb_optparse.bash" somewhere? Where to > >> load it and how to enable the completion for specific executables? > >> Should we try to enable the bash completion for every Ruby executable? > >> Should we have some macro for this? > >> > >> > >> Vít > >> > >> > >> > >> > >> [1] > >> https://github.com/ruby/ruby/commit/644f0445e86034dde399d6db8261c82cf34b8e07 > >> > >> [2] https://github.com/ruby/ruby/blob/trunk/misc/rb_optparse.bash > >> > >> _______________________________________________ > >> ruby-sig mailing list -- ruby-sig@lists.fedoraproject.org > >> To unsubscribe send an email to ruby-sig-le...@lists.fedoraproject.org > >> > > _______________________________________________ > > ruby-sig mailing list -- ruby-sig@lists.fedoraproject.org > > To unsubscribe send an email to ruby-sig-le...@lists.fedoraproject.org > > _______________________________________________ > ruby-sig mailing list -- ruby-sig@lists.fedoraproject.org > To unsubscribe send an email to ruby-sig-le...@lists.fedoraproject.org > _______________________________________________ ruby-sig mailing list -- ruby-sig@lists.fedoraproject.org To unsubscribe send an email to ruby-sig-le...@lists.fedoraproject.org
