From: Bart Schaefer <schaefer@brasslantern.com>
To: zeurkous@volny.cz
Cc: "Lawrence Velázquez" <larryv@zsh.org>,
"Ray Andrews" <rayandrews@eastlink.ca>,
"Zsh Users" <zsh-users@zsh.org>
Subject: Re: Best practices for managing aliases in ohmyzsh?
Date: Wed, 1 Sep 2021 14:19:41 -0700 [thread overview]
Message-ID: <CAH+w=7bREyKBdnSojK2yrUG1yaAOEYvwWgYsssoTw9a+JkcduQ@mail.gmail.com> (raw)
In-Reply-To: <20210901231117.2EFB4C2C@volny.cz>
On Wed, Sep 1, 2021 at 2:11 PM <zeurkous@volny.cz> wrote:
>
> Haai,
>
> "Lawrence Velázquez" <larryv@zsh.org> wrote:
> > Similarly, I don't think you should include a shebang in a file
> > that is not meant to be executed by a separate interpreter because
> > that is the whole point of shebangs. Including one sends a strong
> > signal that that file is supposed to be executed.
>
> It's magic that allows file(1) et al. to make a proper identification.
Also used by smart editors to initialize syntax coloring.
The ONLY trustworthy signal that a file is supposed to be executed
should be that it's execute permission bit is set.
next prev parent reply other threads:[~2021-09-01 21:20 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 18:13 Steve Dondley
2021-08-30 22:27 ` Ray Andrews
2021-08-30 23:22 ` Steve Dondley
2021-08-30 23:34 ` Ray Andrews
2021-08-31 1:44 ` Steve Dondley
2021-08-31 0:14 ` Lawrence Velázquez
2021-08-31 1:29 ` Steve Dondley
2021-08-31 8:26 ` Roman Perepelitsa
2021-08-31 15:51 ` Steve Dondley
2021-08-31 17:57 ` Roman Perepelitsa
2021-08-31 18:54 ` Bart Schaefer
2021-08-31 21:22 ` Steve Dondley
2021-08-31 21:36 ` Roman Perepelitsa
2021-08-31 21:43 ` Steve Dondley
2021-08-31 21:44 ` Roman Perepelitsa
2021-09-01 0:12 ` Ray Andrews
2021-09-01 0:28 ` Bart Schaefer
2021-09-01 2:33 ` Ray Andrews
2021-09-01 3:01 ` Bart Schaefer
2021-09-01 14:20 ` Daniel Shahaf
2021-09-01 15:58 ` Ray Andrews
2021-09-01 18:22 ` Lawrence Velázquez
2021-09-01 19:11 ` Ray Andrews
2021-09-01 19:16 ` Bart Schaefer
2021-09-01 19:56 ` Ray Andrews
2021-09-01 20:03 ` Bart Schaefer
2021-09-01 20:52 ` Steve Dondley
2021-09-01 21:06 ` Ray Andrews
2021-09-01 22:06 ` Steve Dondley
2021-09-01 20:53 ` Lawrence Velázquez
2021-09-01 21:11 ` zeurkous
2021-09-01 21:19 ` Bart Schaefer [this message]
2021-09-01 21:29 ` Lawrence Velázquez
2021-09-01 21:23 ` Ray Andrews
2021-09-01 21:05 ` Ray Andrews
2021-09-01 3:19 ` Steve Dondley
2021-09-01 3:30 ` Bart Schaefer
2021-09-01 3:27 ` Lawrence Velázquez
2021-09-01 16:20 ` Ray Andrews
2021-09-01 18:34 ` Lawrence Velázquez
2021-09-01 19:19 ` Ray Andrews
2021-08-31 8:06 ` Anssi Saari
2021-08-31 15:45 ` Steve Dondley
2021-08-31 16:24 ` zzapper
2021-08-31 16:47 ` Steve Dondley
2021-08-31 17:20 ` Steve Dondley
2021-08-31 17:26 ` Bart Schaefer
2021-08-31 17:40 ` Steve Dondley
2021-08-31 17:47 ` Steve Dondley
2021-08-31 18:31 ` Ray Andrews
2021-08-31 18:59 ` Lawrence Velázquez
2021-09-01 6:40 ` Michael Klemm
2021-09-01 22:13 ` Steve Dondley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH+w=7bREyKBdnSojK2yrUG1yaAOEYvwWgYsssoTw9a+JkcduQ@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=larryv@zsh.org \
--cc=rayandrews@eastlink.ca \
--cc=zeurkous@volny.cz \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).