Posted by jpluimers on 2020/06/09
The PlasticSCM GUI does not allow you to edit the paths of Workspaces (you can either rename a workspace or delete edit; no other editing options are available).
Luckily you can do this by hand editing the configuration files in %LocalAppData%\plastic4, though this is largely undocumented
Some of those configuration files are explained in [WayBack] Configuration files – Installation and configuration – Plastic SCM Community, but plastic.workspaces is not, so here are the steps:
Posted in Development, PlasticSCM, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2020/06/09
I’ve added this to my ~/.bashrc to stuff installed by pip install --user is accessible from interactive shells:
# set PATH so it includes user's private python "pip --user" bin if it exists
if [ -d "$HOME/.local/bin" ] ; then
PATH="$PATH:$HOME/.local/bin"
fi
The addition is at the end of the path. It is a choice: it means machine installs take prevalence over user installs. That’s usually what I want. For more considerations (including non-interactive shells), see [WayBack] bash – How to correctly add a path to PATH? – Unix & Linux Stack Exchange.
The --user installs do not affect the full system, nor other users.
Further reading:
--user installs in site.USER_BASE which luckily is the same for Python 3 and Python 2: [WayBack] Python 3 site.USER_BASE, [WayBack] Python 2 site.USER_BASEvenv, virtualenv, easy_install, easy_build, pip install --user and such as even this SO question has inconclusive answers: [WayBack] What’s the proper way to install pip, virtualenv, and distribute for Python? – Stack Overflow–jeroen
Posted in Development, Python, Scripting, Software Development | Leave a Comment »
Posted by jpluimers on 2020/06/09
This is part of a bash alias where I had to use quadruple backslash in order to escape it for sed:
# The sed with quad //// is to prevent 'unterminated substitute in regular expression':
alias x='... | sed "s/=.*/ \\\\/"'
This is needed because bash will escape \\\\ into \\ which sed then escapes to \.
The easiest way to find this is to replace the sed with echo to see the expansion.
References:
–jeroen
Posted in *nix, *nix-tools, bash, bash, Development, Power User, Scripting, sed, Software Development | 2 Comments »
The Wiert Corner - irregular stream of stuff 