There are new options in Bash 4: checkjobs and autocd.
However, I did not find documentation for them at
man bash
I run unsuccessfully
{checkjobs,autocd}
I found the following in release notes
There is a new `checkjobs` option that causes the shell to check for and
report any running or stopped jobs at exit
and
There is a new `autocd` option that, when enabled, causes bash to attempt
to `cd` to a directory name that is supplied as the first word of a
simple command.
How can you use autocd and checkjobs?
autocd and checkjobs are not commands, but rather, they are options.
They can be set by using the shopt built-in.
Example:
shopt -s autocd
and
shopt -s checkjobs
or
shopt -s autocd checkjobs
to set both.
Related
I'm trying to save the current status of shopt globstar to a variable so I can change it if needed then set it back as to not leave the user's environment altered.
I have tried storing the command output multiple ways such as var=$(command) and var=`command` but when I test with
echo $var it always reads the state as "off" even though it's not.
gstar=$( shopt globstar )
echo "$gstar"
I'm hoping to use echo to test the current state against manually running shopt globstar but they do not match.
This basic variable store is working fine with whoami command.
Are you running your script directly (./script.sh) or sourcing it (. script.sh or source script.sh)?
If you're running it directly it'll have its own environment and you don't have to worry about preserving the user's settings. Scripts get a copy of the user's environment and changes only affect the copy, not the original. Just set the option however you like at the top of your script.
#!/bin/bash
shopt -s globstar
foo **/bar
If it's being sourced it's a lot easier to just wrap the relevant parts of the script in a subshell so they run in an isolated environment.
(
shopt -s globstar
foo **/bar
)
baz
I suspect it's case 1 since you say it always starts out off.
To save the shopt value:
if shopt -q globstar
then
# the option is enabled
saved_globstar=-s
else
# the option is disabled
saved_globstar=-u
fi
Now you can change your globstar value. If you later want to restore it to the previous state, do a
shopt $saved_globstar globstar
I'm currently confused why shell globbing in terminal works with negation but shows an error when running in bash.
Take the commands executed in the terminal below, which shows all js files within the ./HTML directory except for js files that ends with .bundle.js.
$ shopt -s globstar
$ ls ./HTML/**/!(*.bundle).js
The command above works perfectly, now let's put it in a bash file
list-js.sh
#!/usr/bin/env bash
shopt -s globstar
ls ./HTML/**/!(*.bundle).js
Executing it in a terminal:
$ bash list-js.sh
list-js.sh: line 4: syntax error near unexpected token `('
list-js.sh: line 4: `ls ./HTML/**/!(*.bundle).js'
As you can see, it shows a syntax error.
globstar only enables the ** pattern. The extglob option allows !(...). Somewhere in your interactive shell, that has already been enabled (perhaps in your .bashrc, perhaps you typed shopt -s extglob earlier). However, it needs to be enabled explicitly in your script, since such settings are not inherited from the shell that starts the script.
#!/usr/bin/env bash
shopt -s globstar extglob
ls ./HTML/**/!(*.bundle).js
(As an aside, ** without globstar does not cause a syntax error because it is treated simply as two adjacent *s, the second one being redundant.)
Its been 15 years since I used Unix ksh shell, bash now. It's coming back to me but I spent a lot of time trying to get the basic interactive shell to not only like my scripts and syntax, I read man pages on setting up .bashrc and such but nothing.
example: I could not source anything till i took out all the "." chars in function names and file names, still could not get the functions and vars to load from a sourced script back to the caller... and then finally.... discovered the problem was using " 2>&1 $LOGFILE" on my calls when sourceing. go figure. days wasted.
I now have bash kinda working enough to try to install image magick 6.8.8 but its not working either. I followed the instructions for installing, expanded the tar ball, set the env var, added to path before all others. like the source issue i had the shell finds the IM commands, in the right folder and runs them, they just dont do anything. all i get is a CR/LF when entering any IM exe.
Thats why i am asking now, seems like some flag I am not setting..
do I need to register the dlls? why are they .exe files?
What am I forgetting to do?
Also do you have any good default settings or tips on setting up bash shell to work with and debug lots of bash
GNU bash, version 4.3.42(4)-release (x86_64-unknown-cygwin)
cygwin64 on Windows7."
ImageMagick-6.8.8
here is the relevant part of the env...
$ ls -l convert.exe compare.exe
-rwxr-xr-x 1 Administrators None 74892 Jan 27 2014 compare.exe
-rwxr-xr-x 1 Administrators None 74316 Jan 27 2014 convert.exe
$ which convert
/home/ripple/ImageMagick-6.8.8/bin/convert
ripple#prp-lap-tos ~
$ convert.exe -version
convert.exe -version
ripple#prp-lap-tos ~
========================================
============================
$ **env**
HOMEPATH=\Users\ripple
ProgramW6432=C:\Program Files
HOSTNAME=prp-lap-tos
SHELL=/bin/bash
TERM=xterm
PROCESSOR_IDENTIFIER=AMD64 Family 15 Model 104 Stepping 2, AuthenticAMD
PROFILEREAD=true oRIGINAL_PATH=/cygdrive/c/bin:/cygdrive/c/Windows/system32:/cygdrive/c/Windows
USER=ripple
!::=::\
LD_LIBRARY_PATH=/home/ripple/ImageMagick-6.8.8/lib
USERNAME=ripple
PROCESSOR_LEVEL=15
PATH=/home/ripple/bin:/home/ripple/ImageMagick6.8.8/bin:/usr/local/bin:/usr/bin:/cygdrive/c/bin:/cygdrive/c/Windows/system32:/cygdrive/c/Windows
PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\
FP_NO_HOST_CHECK=NO
PWD=/home/ripple/ImageMagick-6.8.8/bin
LANG=en_US.UTF-8
TZ=America/Denver
PS1=\[\e]0;\w\a\]\n\[\e[32m\]\u#\h \[\e[33m\]\w\[\e[0m\]\n\$
MAGICK_HOME=/home/ripple/ImageMagick-6.8.8
PROCESSOR_ARCHITECTURE=AMD64
EXECIGNORE=*.dll
SHLVL=1
HOME=/home/ripple
INFOPATH=/usr/local/info:/usr/share/info:/usr/info
_=/usr/bin/env
==================================
from .**bashrc**
export MAGICK_HOME="$HOME/ImageMagick-6.8.8"
export PATH="$MAGICK_HOME"/bin:$PATH
LD_LIBRARY_PATH="${LD_LIBRARY_PATH:+$LD_LIBRARY_PATH:}"$MAGICK_HOME/lib
export LD_LIBRARY_PATH
==================================================
$ **shopt**
autocd off
cdable_vars on
cdspell on
checkhash on
checkjobs off
checkwinsize on
cmdhist on
compat31 off
compat32 off
compat40 off
compat41 off
compat42 off
completion_strip_exe off
complete_fullquote on
direxpand off
dirspell off
dotglob off
execfail off
expand_aliases on
extdebug off
extglob on
extquote on
failglob off
force_fignore on
globstar off
globasciiranges off
gnu_errfmt off
histappend on
histreedit on
histverify on
hostcomplete on
huponexit off
interactive_comments on
lastpipe off
lithist off
login_shell on
mailwarn off
no_empty_cmd_completion on
nocaseglob on
nocasematch off
nullglob off
progcomp on
promptvars on
restricted_shell off
shift_verbose off
sourcepath on
xpg_echo off
scripts
!#/bin/bash -x
which does not seem to work right either, its not echoing like I thought.
been playing with these commands too.
#set +n
#set +C
#set -o posix
#set -euo pipefail
thanks,
Ripple Ratt
Phat Ratt Photography
If the goal is to install imagemagick on Windows, consider the chocolatey package manager.
ImageMagick 6.9.3.7 is available, so after installing chocolatey, one would run:
choco install imagemagick
I cannot figure it out, i understand shopt -s cdspell but cannot find out what shopt -s dirspell does.
The Bash Reference Guide says:
dirspell
If set, Bash attempts spelling correction on directory names during word completion if the directory name initially supplied does not exist.
I tried several times on several directories but that is not the behavior.
I'm using bash 4.2.10(2) on i386-apple-darwin10.7.0
From the change-log
x. There is a new shell option: `dirspell'. When enabled, the filename
completion code performs spelling correction on directory names during
completion.
Let's try:
$ ls
spam/
$ cat spam/test
hello world
without dirspell
$ cat span/test [tab]
# nothing happens
with dirspell
$ shopt -s dirspell
$ cat span/test [tab]
#line is replaced by
$ cat /home/user/tmp/shopt/spam/test
If you set the shell options direxpand and dirspell, then the tab-completion does work.
I put the following unsuccessfully to my .bashrc
shopt -s globstar
I am trying to test the command in action by
ls **/*.c
and by comparing it to
ls */*/*.c
How can you enable globstar in Bash 4?
Hmm. shopt -s globstar should work.
To debug, make sure you are running Bash 4:
$SHELL --version
Then check the setting of globstar:
shopt globstar
If it is unset, try setting it manually:
shopt -s globstar
Now see if that works. If it does, you might want to look into why your .bashrc isn't working. Did you remember to restart you shell after editing your .bashrc, or load it with . .bashrc?