Re: How to get shell source blocks to read my profile?

[Maxim Nikulin <manikulin@gmail.com>]

On 16/03/2021 20:21, George Mauer wrote:
> 
> I do still wonder what would be the disadvantage of just configuring it 
> to do --login by default and doing all configuration in profile scripts.

At the first glance it at least should not cause great trouble. Most 
shell stuff is written in fool-proof way to avoid loading interactive 
features in non-interactive shell or reinitialize login settings in 
nested shells. Local scripts could be written with less care.

I do not think you need completion functions or changing window title 
during execution of code snippets from emacs.

Self-contained org files have some value, you are trying to put some 
important settings outside. It might be reasonable for personal 
preferences as account names but hardly should be general practice.

On the other hand, I think, it is an equally valid question:
What is the profit?

For some reason your are avoiding over means to set environment 
variables. If you wish just exported environment variables, you could 
always create your own wrapper (untested)

#!/bin/bash

source ~/.config/wundershrc
exec "$0" "$@"

On 17/03/2021 03:32, Tim Cross wrote:
> It can sometimes help to remember what early Unix
> environments were like and what the resource constraints were to
> understand some of the design decisions. A time when memory and disk
> storage was extremely expensive and in short supply, where CPUs were
> slower and less capable than those commonly found in a modern washing
> machine.

Quite recent story is rewriting init scripts to be able to run them with 
dash instead of bash as /bin/sh. On the other hand unavailable features 
require more extensive usage of subprocesses like sed, awk, etc.