Syeed Ali via plug on 30 May 2023 17:39:10 -0700
|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
Re: [PLUG] zsh: command not found:
|
- From: Syeed Ali via plug <plug@lists.phillylinux.org>
- To: plug@lists.phillylinux.org
- Subject: Re: [PLUG] zsh: command not found:
- Date: Tue, 30 May 2023 17:38:50 -0700
- Arc-authentication-results: i=1; rspamd-d7bbc7d84-hdz2x; auth=pass smtp.auth=21tnwsjmfw smtp.mailfrom=syeedali@syeedali.com
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1685493543; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=RhvrmczPzE5BfmPt9je+wa8UytlMzAVq0NMC7+HMsZ0=; b=dI3HBZuIwlE0k1DJpDstneeZBtZ2ffFx+sXr42Z4Z/tlbhDouO8weMEzsxMmueB5G2kVeC xzd565rRZbLI0xU4noZ+R8DYVc8hTciPeSYRZNkDKFJevWLwQJRPbFgvPlSDmJgiDnSiAE L08xB2NymjRQYvmzTbbVBh1I9QUUJrFBagoqCs5+/4VjYBafWDrZFfoEGRlUvGLZQSUuyx UMVL+qmPMVBIeYqxW9lDhH3gWrosYW36LtDT975cppSVyTBK8Zoa7xHoaEpRGbEZa3khgl Ur/0UCz3tcmkv3khNSFsd9i88vmEHtfZs0lOQ3ErzuTzSBs5EZ3ubsSFDvsPmg==
- Arc-seal: i=1; s=arc-2022; d=mailchannels.net; t=1685493543; a=rsa-sha256; cv=none; b=XjJZCkFM6HKlWRToMp/U1dwB7keQIaHUT00rpMgEZfbJm4qvvTCTyxgFTiz8a+1MtAcKyX Jh03y4Y97TY1OaitLmXBnmQoh0CEKE/yAFlU58uSnPzpwEGAHlD1ZhSB2+LnWSPH38eTg/ Hu3m160sKkgD/sksuYAXpdhY5l/DJ24uymWaUgzXy7MnR2HIEF0Q4JZciKn7fJBRy8OyZk +KhSGcHHVF+tHKS7pT8m6GmnBZaxcRnYKB3/hDLUym/6badDNLQf+Msbjij9i5gxNpOd4R n4OQgGk6mJnw+0x5E9eg0vr+a7maSFued/0sJuLqql4G7bHLeyTNjCcY5PKkGQ==
- Reply-to: plug@lists.phillylinux.org, Syeed Ali <SyeedAli>
- Sender: "plug" <plug-bounces@lists.phillylinux.org>
On Tue, 30 May 2023 18:49:18 -0400
Ronald P Guilmet via plug <plug@lists.phillylinux.org> wrote:
I learned about the "hash" command, maybe that's the solution? I read:
hash -r will reload your shell hash-table for the executable within
your $PATH
> 3. The file is a bash script with the proper shebang path to
> /bin/bash, and the bash location is verified by 'which bash'.
This doesn't solve your problem, but it's a good practice for your
shebang to be something like:
#!/usr/bin/env bash
(also maybe try plain sh)
___________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug