- Last 7 days
-
-
Ausführliche Artikel der taz über das fossil fuel crime file, eine von Greenpeace erstellte Liste von Verbrechen und zivilrechtlichen Vergehen derFfossilindustrie. Sie dient als Basis für juristische Aktionen. https://taz.de/Fossilindustrie-vor-Gericht/!5936699/
Tags
- actor: Equinor
- actor: Lundin Energy
- actor: TotalEnergies
- NGO: Friends of the Earth
- actor: Statoil
- actor: ENI
- NGO: Milieudefensie
- mode: legal action
- expert: Channa Samkalden
- region: Niger delta
- project: Mining Impact
- actor: OMV
- NGO: Greenpeace
- actor: Shell
- project: EACOP
- expert: Donald Pöls
- project: East African Crude Oil Pipeline
- expert: Lisa Göldner
- actor: Glencore
Annotators
URL
-
- May 2023
-
-
www.theguardian.com www.theguardian.com
-
Eine neue, grundlegende Studie zu Klima-Reparationen ergibt, dass die größten Fosssilkonzerne jählich mindestens 209 Milliarden Dollar als Reparationen an von ihnen besonders geschädigte Communities zahlen müssen. Dabei sind Schäden wie der Verlust von Menschenleben und Zerstörung der Biodiversität nicht einberechnet. https://www.theguardian.com/environment/2023/may/19/fossil-fuel-firms-owe-climate-reparations-of-209bn-a-year-says-study
Studie: Time to pay the piper: Fossil fuel companies’ reparations for climate damages https://www.cell.com/one-earth/fulltext/S2590-3322(23)00198-7
Tags
- actor: TotalEnergies
- topic: climate finance
- actor: BP
- expert: Harjeet Singh
- institution: Climate Accountability Institute
- actor: Exxon
- expert: Margaretha Wewerinke-Singh
- expert: Richard Heede
- expert: Marco Grasso
- topic: loss and damage
- expert: Mohamed Adow
- actor: Shell
- climate reparations
- actor: Chevron
- actor: Aramco
- expert: Erika Lennon
- NGO: Power Shift Africa
- NGO: Climate Action Network
Annotators
URL
-
-
www.telegraph.co.uk www.telegraph.co.uk
-
Why the Church of England is taking on Shell
-
- Apr 2023
-
www.reuters.com www.reuters.com
-
Dutch government promises support to Shell to cut CO2 emissions
-
- Feb 2023
-
www.folia.nl www.folia.nl
-
tijdlijn
Tijdlijn Folia Fossiele industrie
-
-
www.folia.nl www.folia.nl
-
De UvA gaat voorlopig geen nieuwe onderzoekssamenwerkingen met Shell of soortgelijke bedrijven aan.
UvA gaat voorlopig geen nieuwe onderzoekssamenwerkingen met Shell of soorgelijke bedrijven aan.
-
-
www.clientearth.org www.clientearth.org
-
ClientEarth has today filed a world-first lawsuit against the Board of Directors of Shell plc for failing to manage the material and foreseeable risks posed to the company by climate change.
-
- Dec 2022
-
pythonspeed.com pythonspeed.com
-
For sufficiently simple cases, just running a few commands sequentially, with no subshells, conditional logic, or loops, set -euo pipefail is sufficient (and make sure you use shellcheck -o all).
Advice for when you can use shell scripts
Tags
Annotators
URL
-
-
www.zhihu.com www.zhihu.com
-
如何系统地学习Shell编程？
Tags
Annotators
URL
-
- Nov 2022
-
unix.stackexchange.com unix.stackexchange.com
-
Bash maintains an internal hash of previously found executables in your path. In this case, it has details that at one time there was an executable at /usr/bin/siege, and reuses that path to avoid having to search again. You need to tell bash to manually rehash the path for siege like so: hash siege You can also clear all hashed locations: hash -r
-
-
stackoverflow.com stackoverflow.com
-
Remember there are two kinds of variable. Internal Variables and Environment Variables. PATH should be an environment variable.
In my case, I was trying to debug
which asdfnot finding asdf, in a minimal shell.I had checked
bash-5.1$ echo $PATH|grep asdf /home/tyler/.asdf/binbut ```
The PATH environment variable
env | /bin/grep PATH
`` being empty was the key discovery here. Must have forgotten theexport`. -
All shells should tell you that your path is the same thing with BOTH of the two commands: # The PATH variable echo "$PATH" # The PATH environment variable env | /bin/grep PATH
-
-
www.derstandard.de www.derstandard.de
-
Auch der Standard weist in einem Halbzeitbericht zur COP27 darauf hin, wieviele Vertreter der Fossilindustrien an den Verhandlungen dürfen. Ein Hauptinteresse dabei ist es, durch Regeln zu verhindern, dass die selbst verursachten Emissionen wirksam reduziert werden müssen. Er verweist dabei auf Shells Einfluss bei der Formulierung des Aktikels 6 des Pariser Abkommens.
-
- Aug 2022
-
www.theguardian.com www.theguardian.com
-
“These ads are intended to create a clean warm glow about the companies concerned, giving them more social licence to operate,” said Doug Parr, chief scientist for Greenpeace UK
Die Ausgaben sprechen dafür, dass diese Art von Kommunikation sehr wirksam ist. Auch das schafft eine fundamentale Assymetrie zwischen der Fossilindustrie und ihren Gegnern.
-
-
stackoverflow.com stackoverflow.com
-
$0 would be OK in most cases, some exceptions are, for instance, when the script you're executing is aliased (through alias in .bash_profile). You should really use $BASH_SOURCE variable, instead of $0.
-
Using $0 does not work when the script is run using source script or . script; the name of the script is not available.
-
- Jul 2022
-
stackoverflow.com stackoverflow.com
-
Always use a while read construct: find . -name "*.txt" -print0 | while read -d $'\0' file do …code using "$file" done The loop will execute while the find command is executing. Plus, this command will work even if a file name is returned with whitespace in it. And, you won't overflow your command line buffer.
-
- Apr 2022
-
askubuntu.com askubuntu.com
-
You can close the single quotes before starting the double quotes and do the reverse at the end of that inner section to achieve what you want:
This is how to use variable in single quotes. It works well also for tcsh.
-
-
openwritings.net openwritings.net
-
mpv -playlist <(find "$PWD" -type f)
Tags
Annotators
URL
-
- Mar 2022
-
unix.stackexchange.com unix.stackexchange.com
-
Just let it expand inside an array declaration's right side: list=(../smth*/) # grab the list echo "${#list[@]}" # print array length echo "${list[@]}" # print array elements for file in "${list[@]}"; do echo "$file"; done # loop over the array
-
-
stackoverflow.com stackoverflow.com
-
The short answer is that you want an array: dirs=(/content/{dev01,dev01})
-
- Feb 2022
-
ghedamat.github.io ghedamat.github.io
- Sep 2021
-
github.com github.com
-
I think it's very confusing to overload common executables, such as yarn, in the /bin directory as I often put that bin directory first in my path. Thus, I'd unexpectedly get the bin/yarn rather than my system yarn, which I manage with yvm.
-
-
stackoverflow.com stackoverflow.com
-
One good use for /dev/tty is if you're trying to call an editor in a pipeline (e.g., with xargs). Since the standard input of xargs is some list of files rather than your terminal, just doing, e.g., | xargs emacs will screw up your terminal. Instead you can use | xargs sh -c 'emacs "$@" </dev/tty' emacs to connect the editor to your terminal even though the input of xargs is coming from elsewhere.
-
-
josephsdavid.github.io josephsdavid.github.io
Tags
Annotators
URL
-
- Jun 2021
-
docs.npmjs.com docs.npmjs.com
-
Please make sure that your file(s) referenced in bin starts with #!/usr/bin/env node, otherwise the scripts are started without the node executable!
-
-
mywiki.wooledge.org mywiki.wooledge.org
-
Since looping over the positional parameters is such a common thing to do in scripts, for arg defaults to for arg in "$@". The double-quoted "$@" is special magic that causes each parameter to be used as a single word (or a single loop iteration). It's what you should be using at least 99% of the time.
-
Bash (like all Bourne shells) has a special syntax for referring to the list of positional parameters one at a time, and $* isn't it. Neither is $@. Both of those expand to the list of words in your script's parameters, not to each parameter as a separate word.
-
-
superuser.com superuser.com
-
Instead of using a for loop, which will fail on spaces unless you redefine the IFS variable, I would recommend using a while loop combined with find.
-
-
stackoverflow.com stackoverflow.com
-
Different ways to prepend a line: (echo 'line to prepend';cat file)|sponge file sed -i '1iline to prepend' file # GNU sed -i '' $'1i\\\nline to prepend\n' file # BSD printf %s\\n 0a 'line to prepend' . w|ed -s file perl -pi -e 'print"line to prepend\n"if$.==1' file
-
-
stackoverflow.com stackoverflow.com
-
for cpp_file in *.cpp; do gcc -c $$cpp_file & done; wait This gives much finer control than make -j.
-
-
There is one very important reason for enabling job control to be useful inside scripts: the side-effect it has of placing background processes in their own process groups. This makes it much, much easier to send signels to them and their children with one simple command: kill -<signal> -$pgid. All other ways of dealing with signaling entire trees of processes either involve elaborate (sometimes even recursive) functions, which are often bugnests, or risk killing the parent in the process (no pun intended).
-
-
defragged.org defragged.org
-
askubuntu.com askubuntu.com
-
To avoid the problems with different versions of echo you may want to use printf instead. In contrast to echo printf always interprets \ sequences but doesn't automatically add a linefeed at the end so you have to append \n at the end if you want one.
-
-
-
medium.com medium.com
-
while (( "$#" )); do case "$1" in -a|--my-boolean-flag) MY_FLAG=0 shift ;; -b|--my-flag-with-argument) if [ -n "$2" ] && [ ${2:0:1} != "-" ]; then MY_FLAG_ARG=$2 shift 2 else echo "Error: Argument for $1 is missing" >&2 exit 1 fi ;; -*|--*=) # unsupported flags echo "Error: Unsupported flag $1" >&2 exit 1 ;; *) # preserve positional arguments PARAMS="$PARAMS $1" shift ;; esacdone# set positional arguments in their proper placeeval set -- "$PARAMS"
-
-
unix.stackexchange.com unix.stackexchange.com
-
As a general rule: You should quote everything (that may be quoted).
-
- May 2021
-
github.com github.com
-
For filter-branch, using pipelines like git ls-files | grep -v ... | xargs -r git rm might be a reasonable workaround but can get unwieldy and isn't as straightforward for users; plus those commands are often operating-system specific (can you spot the GNUism in the snippet I provided?)
-
-
github.com github.com
-
However, the place where pip places that package might not be in your $PATH (thus requiring you to manually update your $PATH afterwards), and on windows the pip install might not take care of python-specific issues for you (see "Notes for Windows Users", above). As such, installation via package managers is recommended instead.
-
-
linuxhint.com linuxhint.com
-
-
unix.stackexchange.com unix.stackexchange.com
-
the bullet-proof way to add a path (e.g., ~/opt/bin) to the PATH environment variable is PATH="${PATH:+${PATH}:}~/opt/bin"
-
-
toraritte.github.io toraritte.github.io
-
The command nix-shell will build the dependencies of the specified derivation, but not the derivation itself. It will then start an interactive shell in which all environment variables defined by the derivation path have been set to their corresponding values, and the script $stdenv/setup has been sourced. This is useful for reproducing the environment of a derivation for development.
QUESTION: What exactly does
nix-shellexecute from the Nix expression (i.e.,shell.nix,default.nix, etc.)?ANSWER: Based on my current understanding, the answer is everything. It calls
$stdenv/setup(see annotation below) to set up the most basic environment variables (TODO: expand on this), and "injects" the most common tools (e.g.,gcc,sed) into it.It also defines the phases (TODO: verify this) and builder functions, such as
genericBuilder. For example, the default builder is just two lines:source $stdenv/setup genericBuildTODO:
pkgs/stdenv/generic/builder.shis a mystery though.QUESTION: Once dropping into
nix-shell, how do I know what phases to execute by looking at adefault.nix? (E.g.,[..]freeswitch/default.nix)ANSWER: As far as I can tell, one can override the phases in their Nix build expression (to build the derivation, see at the bottom), but they won't get executed as only the
$stdenv/setup(see above) will get sourced, and no builders are called that, in return, invoke the phases (again, see above).So if one is using
nix-shellto create/hack on a package, the person has to manually invoke the builder or phases (TODO: still fuzzy on this subject)
to set up an environment, then one doesn't even have to worry about builders/phases because we just use
nix-shellto clear the environment and to inject tools that we need for a given task
QUESTION: When dropping into
nix-shell, is this Nix expression (i.e.,freeswitch/default.nix) executed? Or just parts of it?ANSWER: As stated above, all of the input Nix expression is evaluated, but no builders and build phases are called; although, nothing prevents one to override the phases, in case they are creating/hacking on a package.
QUESTION:
The command
nix-shellwill build the dependencies of the specified derivation, but not the derivation itself.What is the "derivation" here exactly? I know that it is a build expression, but does that mean the
default.nix(or other Nix expression)nix-shellis invoked with?<sup>This statement also seems like a contradiction with how `nix-shell` works (i.e., if one issues `nix-shell -p curl`, then `curl` will be available in that sub-shell), but `-p` acts like a shortcut to as if `curl` had been listed in `buildInputs` so this is not the case.</sup>
ANSWER: I have the feeling my confusion comes from the fact that the term "derivation" is used ambiguously in the manuals, sometimes to mean multiple things (see list below).
TODO: Substantiate this claim, and make sure that it not coming from my misunderstanding certain topics.
Nix build expression (such as
default.nix) whose output is going to become the store derivation itself (see last item at the bottom about the Nix manual's glossary definition)store derivation.
Had multiple cracks at unambiguously define what a derivation is, and here's a list of these:
What is the purpose of nix-instantiate? What is a store-derivation? (probably the best try yet)
What is a Nix expression in regard to Nix package management? (feels sloppier, but commenter mentions
ATerm, adding the possibility of making it very specific)Closure vs derivation in the Nix package manager (very short, and will have to be re-written, but adds closures to the mix)
There is now a glossary definition of a derivation in the Nix manual; see this annotation why I find it problematic
QUESTION: What is the difference between
nix-shell -pandnix-shellinvoked with a Nix expression ofmkShell(or other that achieves the similar effect)?QUESTION:
nix-shelldoes not create a sub-shell, so what does it do? (clarification: sonix-shellindeed does it; I confused it withnix shell)
-
- Apr 2021
-
stackoverflow.com stackoverflow.com
-
-
$ ./my_script Will end up in STDOUT(terminal) and /var/log/messages $ tail -n1 /var/log/messages Sep 23 15:54:03 wks056 my_script_tag[11644]: Will end up in STDOUT(terminal) and /var/log/messages
-
-
unix.stackexchange.com unix.stackexchange.com
-
exec &> >(tee -a "$log_file")
-
exec &> >(tee -a "$log_file") echo "This will be logged to the file and to the screen" $log_file will contain the output of the script and any subprocesses, and the output will also be printed to the screen.
-
-
unix.stackexchange.com unix.stackexchange.com
-
-
Write stderr and stdout to a file, display stderr on screen (on stdout) exec 2> >(tee -a -i "$HOME/somefile.log") exec >> "$HOME/somefile.log" Useful for crons, so you can receive errors (and only errors) by mail
-
I just wanted to point out that the syntax is not supported by the POSIX standard and thus won't universally work in /bin/sh scripts (many people erroneously use bash syntax in /bin/sh scripts)
-
exec > >(tee "$HOME/somefile.log") 2>&1
-
-
core.tcl-lang.org core.tcl-lang.org
-
#!/bin/sh # -*- tcl -*- # The next line is executed by /bin/sh, but not tcl \ exec tclsh "$0" ${1+"$@"}
-
-
expect.sourceforge.net expect.sourceforge.net
-
When you have a pipeline, unbuffer must be applied to each element except the last (since that doesn't have its output redirected). Example: unbuffer p1 | unbuffer p2 | unbuffer p3 | p4
-
-
en.wikipedia.org en.wikipedia.org
-
Operating systems implement a command-line interface in a shell for interactive access to operating system functions or services.
-
-
-
empty.sourceforge.net empty.sourceforge.net
-
empty is an utility that provides an interface to execute and/or interact with processes under pseudo-terminal sessions (PTYs). This tool is definitely useful in programming of shell scripts designed to communicate with interactive programs like telnet, ssh, ftp, etc.
-
can be easily invoked directly from shell prompt or script
Can't expect / unbuffer / etc. (whatever this is attempting to contrast itself with) be easily invoked directly from shell prompt or script too??
Okay, I guess you have to know more about how
expectis invoked to understand what they mean. One glance at the examples, comparing them, and all becomes clear:#!/bin/sh empty -f -i in -o out telnet foo.bar.com empty -w -i out -o in "ogin:" "luser\n"I didn't realize that expect required/expected (no pun intended) to be used in scripts with its own shebang line:
#!/usr/bin/expect spawn telnet foo.bar.com expect ogin {send luser\r}That does make it less easy/normal to use expect within a shell script.
I was coming to the expect project from/for the
unbuffercommand, which by contrast, is quite easy to include/use in a shell script -- almost the same asempty, in fact. (Seems like almost a mismatch to haveunbuffercommand inexpecttoolkit then. Or isexpectcommand the only odd one out in that toolkit?) -
does not use TCL, Perl, PHP, Python or anything else as an underlying language is written entirely in C has small and simple source code can easily be ported to almost all UNIX-like systems
-
-
stackoverflow.com stackoverflow.com
-
The quirky looking printf is necessary to correctly expand the script's arguments in $@ while protecting possibly quoted parts of the command (see example below).
-
-
serverfault.com serverfault.com
-
xargs -i sh -c 'test -f {} && echo {}'
-
-
unix.stackexchange.com unix.stackexchange.com
-
If a program receives file names as arguments, don't join them with spaces. Use "$@" to access them one by one.
-
- Mar 2021
-
askubuntu.com askubuntu.com
-
you can use "${@:1}" instead of shift, but that requires bash instead of sh in your #! shebang. IMHO your original shift approach is simpler and better
-
Given the deskopen script, you can use a reference to it as the shebang line in a .desktop file
-
- Feb 2021
-
unix.stackexchange.com unix.stackexchange.com
-
Now this probably won't make difference in the real world (e.g. because the exit codes are not portable and on top of that not always unambiguous as discussed in Default exit code when process is terminated?)
-
-
unix.stackexchange.com unix.stackexchange.com
-
non-interactive shells (actually when job control is not enabled)
-
In any case signal handling in shells is one of the least reliable and portable aspects. You'll find behaviours vary greatly between shells and often between different versions of a same shell. Be prepared for some serious hair pulling and head scratching if you're going to try to do anything non-trivial.
-
for sig in $(kill -l) ; do trap "echo parent:$sig" $sig done
-
-
unix.stackexchange.com unix.stackexchange.com
-
read -rep $'\nDo you wish to stop playing?(y/n)' yn
-
You also need job controlled -monitoring in your parent so it keep track of its children. wait, for example, only works at all with job control. -monitor mode is how shells interact with terminals.
-
-
unix.stackexchange.com unix.stackexchange.com
-
The parentheses always start a subshell. What's happening is that bash detects that sleep 5 is the last command executed by that subshell, so it calls exec instead of fork+exec. The sleep command replaces the subshell in the same process.
-
-
stackoverflow.com stackoverflow.com
-
if the process does not react on a normal kill, you may want to add an additional kill -9 a few seconds afterwards.
-
-
nixos.wiki nixos.wiki
-
example: get an environment which is used to build irssi (also see nix-shell) $ nix-build $NIXPKGS --run-env -A irssi example: get a persistent environment which is used to build irssi $ nix-build $NIXPKGS --run-env -A irssi --add-root
nix-build <path> --run-envhas been superseded bynix-shell. From Nix manual section C.12. Release 1.6 (2013-09-10):The command
nix-build --run-envhas been renamed tonix-shell.
-
-
toraritte.github.io toraritte.github.io
-
C.12. Release 1.6 (2013-09-10)In addition to the usual bug fixes, this release has several new features:The command nix-build --run-env has been renamed to nix-shell.
-
- Nov 2020
-
stackoverflow.com stackoverflow.com
-
Never use x && y || z when y can return a non-zero exit status.
-
-
stackoverflow.com stackoverflow.com
-
yell() { echo "$0: $*" >&2; } die() { yell "$*"; exit 111; } try() { "$@" || die "cannot $*"; }
-
If it's closing the "window" likely you're putting the exit # command inside a function, not a script. (In which case use return # instead.)
-
-
mywiki.wooledge.org mywiki.wooledge.org
-
Bash (like all Bourne shells) has a special syntax for referring to the list of positional parameters one at a time, and $* isn't it. Neither is $@. Both of those expand to the list of words in your script's parameters, not to each parameter as a separate word.
-
However, this construct is not completely equivalent to if ... fi in the general case.
The caveat/mistake here is if you treat it / think that it is equivalent to if a then b else c. That is not the case if b has any chance of failing.
-
-
-
-
The potential problem: if second_task fails, third_task will not run, and execution will continue to the next line of code - next_task, in this example. This may be exactly the behavior you want. Alternatively, you may be intending that if second_task fails, the script should immediately exit with its error code. In this case, the best choice is to use a block - i.e., curly braces: first_task && { second_task third_task } next_task Because we are using the -e option, if second_task fails, the script immediately exits.
-
When people write COND && COMMAND, typically they mean "if COND succeeds (or is boolean true), then execute COMMAND. Regardless, proceed to the next line of the script." It's a very convenient shorthand for a full "if/then/fi" clause.
-
-
stackoverflow.com stackoverflow.com
-
[[ -z "$a" || -z "$b" ]] && usage
-
-
blog.csdn.net blog.csdn.net
-
zip -r myfile.zip ./filename
把filename 压缩成 myfile.zip
unzip -d /home/file myfile.zip
把myfile.zip 压缩到 home/file 目录下
zip -d myfile.zip smart.txt
删除 myfile.zip 中的 smart.txt
zip -m myfile.zip add.txt
往 myfile.zip 中加 add.txt
Tags
Annotators
URL
-
-
github.com github.com
-
It starts truncating it's output (shortening strings with ...) once you pipe it's output into grep. That is quite unacceptable. When I am checking if something is inhibited in a script, I should have all possible information available and not have to consider if a string will get truncated when being piped into a tool, that is perfectly readable on a wide terminal.
-
- Oct 2020
-
unix.stackexchange.com unix.stackexchange.com
-
An even more general version that allows using find options:
"find up" command
-
readlink is not part of the standard. A portable script could be implemented with only POSIX shell features.
-
-
stackoverflow.com stackoverflow.com
-
the following seems to do it without the bashism
-
-
www.shellscript.sh www.shellscript.sh
-
Variables - Part 1
变量第一部分
-
-
www.shellscript.sh www.shellscript.sh
-
*
* 应该表示当前文件夹内的文件， 类似于 ls
-
begins with a special symbol: #. This marks the line as a comment
以#开头的代码表示这行代码被注释掉了，这点跟 Python 一致。
-
-
www.shellscript.sh www.shellscript.sh
-
Philosophy
shell 编程的哲学
-
-
www.shellscript.sh www.shellscript.sh
-
Note that to make a file executable, you must set the eXecutable bit, and for a shell script, the Readable bit must also be set:
这句话没懂
-
Shell Scripting Tutorial
shell 编程教程
-
- Aug 2020
-
www.howtogeek.com www.howtogeek.com
-
You can also nest brace expansion lists in the mkdir command. For example, in the articles subdirectory under the htg directory, we want to create two subdirectories called new and rewritten. So, we type the following command at the prompt and press Enter. mkdir -p htg/{articles/{new,rewrites},images,notes,done}
-
- Jul 2020
-
adoptingerlang.org adoptingerlang.org
-
The most commonly supported tool for this is kerl. Kerl is a wrapper around downloading, compiling, and loading various Erlang/OTP versions on a single system, and will abstract away most annoying operations.
Or use the Nix package manager's
nix-shell.
Tags
Annotators
URL
-
- Jun 2020
-
stackoverflow.com stackoverflow.com
-
{ read foo ; read filesystem size using avail prct mountpoint ; } < <(df -k /)
-
- May 2020
-
stackoverflow.com stackoverflow.com
-
I have used this bash one-liner before set -- "${@:1:$(($#-1))}" It sets the argument list to the current argument list, less the last argument.
Analogue of
shiftbuilt-in. Too bad there isn't just apopbuilt-in.
-
-
thoughtbot.com thoughtbot.com
- Apr 2020
-
github.com github.com
-
Invert the exit code of a process. Make 0 into 1 and everything else into a 0. An alternative to ! some-command syntax present in some shells.
Tags
Annotators
URL
-
-
stackabuse.com stackabuse.com
-
-
www.cyberciti.biz www.cyberciti.biz
-
Apple replaced Bourne Again SHell with Z shell for licensing reasons
-
-
stackoverflow.com stackoverflow.com
-
And I continue to tell people: Friends don't let friends write bash script.
-
-
riptutorial.com riptutorial.com
-
www.linuxjournal.com www.linuxjournal.com
-
docs.python.org docs.python.org
-
# Add auto-completion and a stored history file of commands to your Python # interactive interpreter. Requires Python 2.0+, readline. Autocomplete is # bound to the Esc key by default (you can change it - see readline docs). # # Store the file in ~/.pystartup, and set an environment variable to point # to it: "export PYTHONSTARTUP=~/.pystartup" in bash. import atexit import os import readline import rlcompleter historyPath = os.path.expanduser("~/.pyhistory") def save_history(historyPath=historyPath): import readline readline.write_history_file(historyPath) if os.path.exists(historyPath): readline.read_history_file(historyPath) atexit.register(save_history) del os, atexit, readline, rlcompleter, save_history, historyPath
Enable history and sane keys in python shell
-
- Feb 2020
-
github.com github.com
-
github.com github.com
-
github.com github.com
-
leimao.github.io leimao.github.io
Tags
Annotators
URL
-
- Jan 2020
-
wilsonmar.github.io wilsonmar.github.io
-
ps f
this doesn't run on my system. However
ps -fseems to list processes started in the terminal andps -eflists all (?) processes
Tags
Annotators
URL
-
-
www.linuxjournal.com www.linuxjournal.com
-
fishshell.com fishshell.com
-
- Dec 2019
-
-
\curl
What is the leading \ for? Is that the same as prefixing it with
commandto ensure no aliases are used?Found answer here: https://hyp.is/1lBLAiHEEeqP7Sd3rqQLxg/rvm.io/rvm/install
-
-
-
Point to be noted is, there is a backslash before curl. This prevents misbehaving if you have aliased it with configuration in your ~/.curlrc file.
-
-
security.stackexchange.com security.stackexchange.com
-
As for exec, I am just using it because it makes sense to run the final command in the same process, replacing the wrapper script instead of spawning a new process. It's not strictly necessary.
-
-
stackoverflow.com stackoverflow.com
-
For those (like me) wondering why is the space needed, man bash has this to say about it: > Note that a negative offset must be separated from the colon by at least one space to avoid being confused with the :- expansion.
-
-
unix.stackexchange.com unix.stackexchange.com
-
Do not start ssh-agent from .bashrc or .zshrc, since these files are executed by each new interactive shell. The place to start ssh-agent is in a session startup file such as .profile or .xsession.
-
- Nov 2019
-
devhints.io devhints.io
- Sep 2019