it is not political, nor is it related to bash at all
-mike
signature.asc
Description: Digital signature
On Mon, Aug 17, 2015 at 5:54 AM, Linda Walsh wrote:
> From the manpage I wouldn't have guess it changed
> paths to absolute -- but would expand variables and wildcards
> in the path.
>
> It doesn't seem to make alot of sense when there are other
> ways to go from rel->abs, but not so many that ju
bash-4.3/lib/readline/complete.c:2193: warning: Using 'getpwent' in
statically linked applications requires at runtime the shared libraries
from the glibc version used for linking
Other syms: getpwnam, setpwent, endpwent.
Is providing a static lib that reads the local machine's /etc/passwd
f
From the manpage I wouldn't have guess it changed
paths to absolute -- but would expand variables and wildcards
in the path.
It doesn't seem to make alot of sense when there are other
ways to go from rel->abs, but not so many that just expand
vars or aliases on a dir.
Does anyone know why pa
The commands work fine, and one understands pretty easily while playing
with them how the stack works.
There are just ambiguities in the manual.
Check the pushd builtin command documentation.
"
`pushd'
pushd [-n] [+N | -N | DIR]
Save the current directory on the top of the direct
Andreas Schwab wrote:
Linda Walsh writes:
in bash 4.3.39,
if I type a command, (like "."(source)) and a relative path
like : ../conf,
it expands the relative pathname to absolute pathnames.
Worksforme. Make sure to run complete -r first.
---
You didn't say what version of bash you were u
On 8/14/15 6:08 AM, Tim Nielens wrote:
> Bash Version: 4.3
> Patch Level: 39
> Release Status: release
>
> Description:
> There is a ambiguity about the directory stack in the manual: 6.8.1
> Directory Stack Builtins
>
> It's difficult to understand if the current directory is part of the stack
