Greg Wooledge wrote:
> On Sun, Apr 07, 2013 at 01:13:09AM -0700, Linda Walsh wrote:
>>> getent passwd 'Domain Administrator'
>> Domain Administrator:x:500:18:Domain Admin accnt:/home/root:/bin/bash
>
> getent(1) is fine where it's available, but it's not a standard tool,
> so you can only use it
On Mon, Apr 08, 2013 at 10:32:40AM -0400, Chet Ramey wrote:
> One clarification: a variable is unset unless it has had a value assigned.
> There might be some placeholder there with some type information, but the
> variable is unset. There might be some inconsistencies in how bash treats
> such va
On 4/8/13 9:05 AM, Greg Wooledge wrote:
> If the upstream
> variable has a value assigned, then you can; but if it's empty, then you
> can't.
One clarification: a variable is unset unless it has had a value assigned.
There might be some placeholder there with some type information, but the
variabl
On Sun, Apr 07, 2013 at 01:13:09AM -0700, Linda Walsh wrote:
> > getent passwd 'Domain Administrator'
> Domain Administrator:x:500:18:Domain Admin accnt:/home/root:/bin/bash
getent(1) is fine where it's available, but it's not a standard tool,
so you can only use it on systems that have it.
If on
On Fri, Apr 05, 2013 at 09:15:10AM +0800, konsolebox wrote:
> The only thing left here is that we can't have error control like when we
> are to create generally shared library scripts e.g.:
>
> function lib_something {
> declare -n VAR=$1 &>/devnull || { # error message is not suppressed
>
On Thu, Apr 04, 2013 at 08:51:19PM -0500, Mara Kim wrote:
> The biggest benefit is that it is just plain easier than managing a
> directory of symbolic links on your own. I am extremely lazy.
>
> Here is an example use case. At the end of a work day, I like to bookmark
> the folder I am working in
