Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Comments on Replacing the shebang in a script

Parent

Replacing the shebang in a script

+5
−0

In a Bash script and/or at the command line, given that $file is the path to an executable text file with a shebang, and $env is a valid shebang, I want to replace the existing shebang in the file with the new one. Is there a standard or well-known way?

I thought of echoing the new shebang and then tailing the rest of the file, but this requires explicitly making a temporary file and replacing the original with it (and possibly fixing mode/owner).

I also thought of using sed, but I can't quite figure it out given that shebangs generally contain multiple forward slashes which interfere with the regex syntax. It also seems like overkill since only the first line needs to be considered for replacement.

History

1 comment thread

What's the use case? (1 comment)
Post
+5
−0

Sed has more commands than just s! You can replace the first line of the input with a new value using the c command, without having to write any regular expressions.

sed "1c\\$env" "$file"
History

1 comment thread

portability (1 comment)
portability
jhnc‭ wrote 7 months ago

note that the portable way of writing this requires a literal newline after the backslash. the version here will generate an error with BSD versions of sed and perhaps others (macOS?)