[Buildroot] touch menuconfig

[Buildroot] touch menuconfig

[Ulf Samuelsson]

I find it quite useful to have an empty file "menuconfig" in the top directory,
so I can get command completion when doing

$ make menuconfig

Any objections to adding this?

Best Regards
Ulf Samuelsson

[Buildroot] touch menuconfig

[Frank Kujawski]

  I don't have an objection to the file and command completion, but I wonder
what could be put in the file?
  What hints could be placed in the file that would be of aid?  At first
thought it would be hints, but then that is what is in docs, so my next
thought is a link to a hint file in docs, perhaps docs/README.
  My 2c,
    Frank

> I find it quite useful to have an empty file "menuconfig" in the top
> directory,
> so I can get command completion when doing
>
> $ make menuconfig
>
> Any objections to adding this?
>
> Best Regards
> Ulf Samuelsson
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>

[Buildroot] touch menuconfig

[Ulf Samuelsson]

>> I find it quite useful to have an empty file "menuconfig" in the top
>> directory,
>> so I can get command completion when doing
>>
>> $ make menuconfig
>>
>> Any objections to adding this?
>>
>> Best Regards
>> Ulf Samuelsson
>>


>  I don't have an objection to the file and command completion, but I wonder
> what could be put in the file?
>  What hints could be placed in the file that would be of aid?  At first
> thought it would be hints, but then that is what is in docs, so my next
> thought is a link to a hint file in docs, perhaps docs/README.
>  My 2c,
>    Frank
> 


"make menuconfig" starts the configuration, but
linking it to docs/README obviously improves the usability.

Anyone else?

Best Regards
Ulf Samuelsson

[Buildroot] touch menuconfig

[Cristian Ionescu-Idbohrn]

On Wed, 1 Aug 2007, Ulf Samuelsson wrote:

> "make menuconfig" starts the configuration, but linking it to
> docs/README obviously improves the usability.

In that case it would be more intuitive to symlink:

  README -> docs/README

> Anyone else?

Yes. Please don't do confusing things like that and clutter the name
space more than necessary.

If it's command completion you're looking for write something about
that in the docs-directory.

Debian, for example, distributes /etc/bash_completion. And that's
215907 bytes completion worth :)
Similar for zsh. For example, the directory:

  /usr/share/zsh/4.3.2/functions/Completion/Unix

has a lot of those.


Cheers,

-- 
Cristian

[Buildroot] touch menuconfig

[Benjamin Tietz]

Just to have commandline-completion you dont have to put another silly
file in the directory confusing/annoying anyone.
See the section "Programmable Completion" in man 1 bash / your favorite
shell.

regards
Benjamin

On Wed, Aug 01, 2007 at 02:06:20AM -0500, Frank Kujawski wrote:
>   I don't have an objection to the file and command completion, but I wonder
> what could be put in the file?
>   What hints could be placed in the file that would be of aid?  At first
> thought it would be hints, but then that is what is in docs, so my next
> thought is a link to a hint file in docs, perhaps docs/README.
>   My 2c,
>     Frank
> 
> > I find it quite useful to have an empty file "menuconfig" in the top
> > directory,
> > so I can get command completion when doing
> >
> > $ make menuconfig
> >
> > Any objections to adding this?
> >
> > Best Regards
> > Ulf Samuelsson
> >
> >
> > _______________________________________________
> > buildroot mailing list
> > buildroot at uclibc.org
> > http://busybox.net/mailman/listinfo/buildroot
> >
> 
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
> 

[Buildroot] touch menuconfig

[Ulf Samuelsson]

ons 2007-08-01 klockan 09:35 +0200 skrev Benjamin Tietz:
> Just to have commandline-completion you dont have to put another silly
> file in the directory confusing/annoying anyone.
> See the section "Programmable Completion" in man 1 bash / your favorite
> shell.
> 
> regards
> Benjamin
> 

OK so you do:

complete -W menuconfig make

Thanks
Ulf

[Buildroot] touch menuconfig

[Yann E. MORIN]

All,
Ulf,

On Wednesday 01 August 2007 08:24, Ulf Samuelsson wrote:
> I find it quite useful to have an empty file "menuconfig" in the top directory,
> so I can get command completion when doing
> $ make menuconfig
> Any objections to adding this?

Yep. I'd prefer having a file somewhere in the tree (e.g. in docs/ or a new
tools/ directory) that contains some completion functions for somw shells
(at least bash and zsh come to mind) and that the users could source in theit
startup scripts.

Having a file which sole purpose is help completion would uselessly clutter
the directory, IMRHO.

I once had make-completion working in bash: it would scan the makefile in some
manner and suggest matching options, files or rules depending on the pre-
existing command line (was that in a Mandriva?). I'll try to dig that up and
come back to you later this evening (GMT+2).

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +0/33 662376056 | Software  Designer | \ / CAMPAIGN     |   ^                |
| --==< ?_? >==-- ?------------.-------:  X  AGAINST      |  /e\  There is no  |
| http://ymorin.is-a-geek.org/ | (*_*) | / \ HTML MAIL    |  """  conspiracy.  |
?------------------------------?-------?------------------?--------------------?

[Buildroot] touch menuconfig

[Yann E. MORIN]

All,
Ulf,

On Wednesday 01 August 2007 19:39, Yann E. MORIN wrote:
> On Wednesday 01 August 2007 08:24, Ulf Samuelsson wrote:
> > I find it quite useful to have an empty file "menuconfig" in the top directory,
> > so I can get command completion when doing
> > $ make menuconfig
> > Any objections to adding this?
> I once had make-completion working in bash: it would scan the makefile in some
> manner and suggest matching options, files or rules depending on the pre-
> existing command line (was that in a Mandriva?). I'll try to dig that up and
> come back to you later this evening (GMT+2).

OK, it's still present in the bash-completion package of Mandriva 2007.0.
Debian has it as well. Both have good make completion.

So I don't see any reason to provide it by ourselves. But we can still point
to completion somewhere in docs/

I will try to submit a patch to document completion after dinner.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +0/33 662376056 | Software  Designer | \ / CAMPAIGN     |   ^                |
| --==< ?_? >==-- ?------------.-------:  X  AGAINST      |  /e\  There is no  |
| http://ymorin.is-a-geek.org/ | (*_*) | / \ HTML MAIL    |  """  conspiracy.  |
?------------------------------?-------?------------------?--------------------?

[Buildroot] touch menuconfig

[Ulf Samuelsson]

ons 2007-08-01 klockan 20:27 +0200 skrev Yann E. MORIN:
> All,
> Ulf,
> 
> On Wednesday 01 August 2007 19:39, Yann E. MORIN wrote:
> > On Wednesday 01 August 2007 08:24, Ulf Samuelsson wrote:
> > > I find it quite useful to have an empty file "menuconfig" in the top directory,
> > > so I can get command completion when doing
> > > $ make menuconfig
> > > Any objections to adding this?
> > I once had make-completion working in bash: it would scan the makefile in some
> > manner and suggest matching options, files or rules depending on the pre-
> > existing command line (was that in a Mandriva?). I'll try to dig that up and
> > come back to you later this evening (GMT+2).
> 
> OK, it's still present in the bash-completion package of Mandriva 2007.0.
> Debian has it as well. Both have good make completion.
> 
> So I don't see any reason to provide it by ourselves. But we can still point
> to completion somewhere in docs/
> 
> I will try to submit a patch to document completion after dinner.
> 

complete -W menuconfig make 

works for me and the rest is not so common that it
is a pain to write it out, but if it is easy to install,
why not!



> Regards,
> Yann E. MORIN.
> 

[Buildroot] touch menuconfig

[Yann E. MORIN]

Ulf,
All,

On Wednesday 01 August 2007 21:45, Ulf Samuelsson wrote:
> ons 2007-08-01 klockan 20:27 +0200 skrev Yann E. MORIN:
> > So I don't see any reason to provide it by ourselves. But we can still point
> > to completion somewhere in docs/
> complete -W menuconfig make 
> works for me and the rest is not so common that it
> is a pain to write it out, but if it is easy to install,
> why not!

OK, here is a updated docs/buildroot.html.
Do as you want, apply it, or toss it. :-)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +0/33 662376056 | Software  Designer | \ / CAMPAIGN     |   ^                |
| --==< ?_? >==-- ?------------.-------:  X  AGAINST      |  /e\  There is no  |
| http://ymorin.is-a-geek.org/ | (*_*) | / \ HTML MAIL    |  """  conspiracy.  |
?------------------------------?-------?------------------?--------------------?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: buildroot.completion-doc.patch
Type: text/x-diff
Size: 1472 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20070801/2c166fd1/attachment-0001.bin 

[Buildroot] touch menuconfig

[Bernhard Fischer]

On Wed, Aug 01, 2007 at 08:24:32AM +0200, Ulf Samuelsson wrote:
>I find it quite useful to have an empty file "menuconfig" in the top directory,
>so I can get command completion when doing
>
>$ make menuconfig
>
>Any objections to adding this?

Yes, i object to this. Fix your shell instead (or use zsh).