Re: add generated files to .gitignore

[Chet Ramey]

On 2/25/18 2:49 PM, don fong wrote:
> Chet, i'm not sure i understand your suggestion.
> 
>> You don't have to build in the source directory.
> 
> i don't see anything in the INSTALL or README files about building outside
> the source dir.
> according to INSTALL,

This is a standard feature of any autoconf-generated configure script, and
is not specific to bash. Make a directory, cd to it, run
"bash /path/to/srcdir/configure" and configure will make sure the right
paths end up in the generated Makefiles.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/

Re: add generated files to .gitignore

[don fong]

Chet, i'm not sure i understand your suggestion.

> You don't have to build in the source directory.

i don't see anything in the INSTALL or README files about building outside
the source dir.
according to INSTALL,

The simplest way to compile Bash is:
>   1. 'cd' to the directory containing the source code and type
>  './configure' to configure Bash for your system.


it sounds like you're suggesting to make a copy of the source directory?
(or if that's not what you mean, can you be more explicit?)

making a copy of the source directory has drawbacks.  i also don't see how
it solves the problem of "git status" being cluttered.  either the copy is
a git repo, in which case "git status" will still be cluttered with
generated files; or it's not a git repo in which case i won't be able to do
"git status" or "git diff" to create the patch.

either way, if i'm trying to create a patch, and i have to move my changed
files from the copy back to the original source dir, it'd be easy to
accidentally leave something out.

it seems to me that building in the source directory is the natural and
most convenient way to do things.  from what i've seen, it's also the way
that "most" other open source software works.  my proposed change to
.gitignore will facilitate that mode of operation.

what do you perceive as the drawback?






On Sat, Feb 24, 2018 at 3:29 PM, Chet Ramey  wrote:

> On 2/24/18 3:36 PM, don fong wrote:
> > Eric, thanks for the tip.
> >
> > my feeling is that regardless of whether these files are pushed, they
> > clutter up the "git status" listing after i've done a build.
>
> You don't have to build in the source directory.
>
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>  ``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/
>

How to apply Bash completion usefully and more practically

[Budi]

How to apply Bash completion in more useful way.
If TAB key is pressed Bash just show a list of corresponding command, I
thought it will scroll over all corresponding command on which the cursor
of shell prompt is active. (just like traditional Windows cmd prompt)
How to make it able to perform such ? Thanks so much in advance