Re: .bashrc is sourced even for non-interactive shells (when run from sshd)

2012-06-02 Thread Mikel Ward
On Sat, Jun 2, 2012 at 10:19 AM, Pierre Gaston wrote: > On Sat, Jun 2, 2012 at 8:15 PM, Mikel Ward wrote: >> bash sources .bashrc even for some non-interactive shells. ... > "Remote non login non interactive shells" > Bash has a special compile time option that will

Re: .bashrc is sourced even for non-interactive shells (when run from sshd)

2012-06-02 Thread Mikel Ward
or a network shell On Sat, Jun 2, 2012 at 10:15 AM, Mikel Ward wrote: > bash sources .bashrc even for some non-interactive shells. > > For example with > >    echo \$- is $- > > in ~/.bashrc, and shell set to /bin/bash (bash 4.2.28) > >    ssh -n -T localhost true > >

.bashrc is sourced even for non-interactive shells (when run from sshd)

2012-06-02 Thread Mikel Ward
bash sources .bashrc even for some non-interactive shells. For example with echo \$- is $- in ~/.bashrc, and shell set to /bin/bash (bash 4.2.28) ssh -n -T localhost true produces the output $- is hBc I assume this is caused by this code in shell.c if (run_by_ssh || isnetco

extglob not matching explicit leading dot

2012-05-14 Thread Mikel Ward
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-unknown-linux-gnu' -DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/local/share/l

Re: ${!vname} not documented

2009-10-05 Thread Mikel Ward
Mike Frysinger wrote: > Mikel Ward wrote: > > I was unfamiliar with ${!VAR}. As far as I can tell, it's not documented > > in the man page or the info pages. > > either your documentation is out of date (old bash install) or you just > missed > it. it's u

${!vname} not documented

2009-10-05 Thread Mikel Ward
Hi I came across a script that did $ VARIABLE1=value1 $ VARIABLE2=value2 $ for VAR in VARIABLE1 VARIABLE2 > do > echo ${VAR}=${!VAR} > done VARIABLE1=value1 VARIABLE2=value2 I was unfamiliar with ${!VAR}. As far as I can tell, it's not documented in the man page or the info pages. I assume it

Re: Ctrl+A with multi-line history

2008-09-07 Thread Mikel Ward
Hi Chet Thanks for your reply. Disabling cmdhist stores each line separately in the history, which I don't want. The documentation says C-a goes to the start of the line, not the start of the entry. Trivial or an RFE maybe, but I think it's a bug nonetheless. My ideal would be: At the end of a

Ctrl+A with multi-line history

2008-09-07 Thread Mikel Ward
When I enter a command over multiple lines, e.g. for f in *; do echo $f done Then I press to go back to that history entry, Ctrl+A takes me to the start of the entire multi-line command, rather than to the beginning of the "done" line, as I would expect. Settings: > shopt cmdhist cmdhist

prompt overwritten after tab completion - possibly fixed in readline 5.2

2008-08-19 Thread Mikel Ward
Hi On my newer systems (e.g. Red Hat Enterprise Linux 5.2), I had noticed a problem with tab completion. I can't reproduce it on my system which has readline-5.2-13 (versus readline-5.1-1.1), so I'm guessing it's fixed in readline-5.2, but the CHANGES list doesn't explicitly mention anything like

man page missing definition of jobspec

2008-02-03 Thread Mikel Ward
bg, fg, disown, jobs, kill, and notify take a "jobspec" as an argument. I couldn't find a definition of "jobspec" in the man page. (There is one in the info documentation.) This adds the definition just below the definition of the "jobs" builtin. There might be a better place for it, but it woul