Skip to content
#

shell-scripts

A shell is a text-based terminal, used for manipulating programs and files. Shell scripts typically manage program execution.

Here are 809 public repositories matching this topic...

Open

TODO

8
dylanaraps
dylanaraps commented Jun 14, 2018
  • Dynamic variable naming.
  • Internal variables.
  • Turn the non-functions into functions.
    • This is so tests can be written.
    • It also shows a working use case for the task.
  • Add a CONTRIBUTING.md.
  • Look into side effects of using shopt and set.
  • /dev/tcp
  • Convert to pdf
    • Add a cover.
    • Add references.
  • Write some
ssbarnea
ssbarnea commented Mar 24, 2017

I am wondering if autoenv could not be used in complex CI environments where we have multiple steps and where we need to save/restore status between different steps.

We are currently doing appending variables inside some env_jenkins.properties files and on some some steps (builders) and on others we do source env_jenkins.properties in order to load them.

If autoenv would work also for

sumbach
sumbach commented Jan 31, 2016

I think it would be valuable to explicitly talk about whitespace requirements in [ ] and [[ ]] conditionals--this tripped me up when learning Bash and I know it's a pain point for a lot of developers.

The way I like to think about it is that [ and [[ are commands/builtins (like echo, etc), as opposed to being part of Bash syntax. For this reason, the command name and each of its argumen

headius
headius commented Aug 18, 2019

When a compiled script is run from $PATH it appears to be unable to locate its own file path.

An example with the JRuby bash launcher:

[] ~/projects/jruby $ bin/jruby.bash -e 'puts ENV_JAVA["jruby.home"]'
/Users/headius/projects/jruby

[] ~/projects/jruby $ jruby.bash -e 'puts ENV_JAVA["jruby.home"]'
/Users/headius/projects/jruby

[] ~/projects/jruby $ shc -f bin/jruby.bash -o bin
edannenberg
edannenberg commented Feb 13, 2017

Currently ARG_OPTIONAL_BOOLEAN is displayed like so:

$ ./foo.sh --help
foo!
Usage: ./foo.sh [--(no-)no-deps]
-n,--no-deps,--no-no-deps: some description

With many of those the negating (no-) text adds a lot of visual noise and can be borderline silly as in the above case. I would imagine that most people have no use for an option flag that equals the application's default va

treinen
treinen commented Mar 25, 2019

Morbig fails with "Failure: Unsupported expansion in here document delimiter" on the following
script

cat << $x
kgjlkfdjgkdflkg
$x

bash accepts it both with with and without --posix, and dash gives an error.

I think that the behaviour of bash is correct since nothing in the standard says that the delimiter word may not contain variables, subshells, or globs. However these

Created by Glenda Schroeder

Released 1965

Wikipedia
Wikipedia

Related Topics

bash
You can’t perform that action at this time.