zsh-workers
 help / color / mirror / code / Atom feed
From: Clint Adams <clint@zsh.org>
To: zsh-workers@sunsite.dk
Subject: Re: Shebang diff
Date: Thu, 21 Feb 2008 21:53:52 -0500	[thread overview]
Message-ID: <20080222025352.GA4595@scowler.net> (raw)
In-Reply-To: <20080217162313.5c274cb8@pws-pc> <080216113822.ZM17179@torch.brasslantern.com>

On Sat, Feb 16, 2008 at 11:38:22AM -0800, Bart Schaefer wrote:
> Functions/Misc/sticky-note is explicitly designed to be runnable as a
> standalone script.  Removing the #! line was IMO wrong.

On Sun, Feb 17, 2008 at 04:23:13PM +0000, Peter Stephenson wrote:
> Actually, the same is true of calendar_add:  it's most useful when
> executed from an external programme that's managing called as a backend
> to processing calendars in mail.  However, Clint's point, which is
> reasonable, was that the files in question are being installed into the
> function area, not into the path.  If we wanted to make proper
> arrangements for them to be called directly, we should both install them
> into the path and make them executable at that point, rather than rely
> on them being executable from where they are.  So I think rather than
> changing the permissions again, if we're interested in doing something
> more with ambivalent scripts/functions it would be better to provide
> some utility to fix things. 

I didn't think this would be controversial, but

Index: Functions/Calendar/calendar_add
===================================================================
RCS file: /cvsroot/zsh/zsh/Functions/Calendar/calendar_add,v
retrieving revision 1.9
diff -u -r1.9 calendar_add
--- Functions/Calendar/calendar_add	19 Feb 2008 14:59:53 -0000	1.9
+++ Functions/Calendar/calendar_add	22 Feb 2008 02:49:33 -0000
@@ -1,3 +1,4 @@
+#!/bin/zsh
 # All arguments are joined with spaces and inserted into the calendar
 # file at the appropriate point.
 #
Index: Functions/Misc/sticky-note
===================================================================
RCS file: /cvsroot/zsh/zsh/Functions/Misc/sticky-note,v
retrieving revision 1.3
diff -u -r1.3 sticky-note
--- Functions/Misc/sticky-note	7 Feb 2008 02:11:00 -0000	1.3
+++ Functions/Misc/sticky-note	22 Feb 2008 02:49:33 -0000
@@ -1,3 +1,4 @@
+#!/bin/zsh -fi
 # A little zsh sticky-note ("post-it") application.  Sticky notes are
 # stored in the file named by the STICKYFILE variable (defaults to
 # $HOME/.zsticky).  The number of notes stored is STICKYSIZE (1000).


      parent reply	other threads:[~2008-02-22  2:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-16 19:38 Bart Schaefer
2008-02-17 16:23 ` Peter Stephenson
2008-02-18  1:50   ` Bart Schaefer
2008-02-22  2:54     ` Clint Adams
2008-02-22  4:01       ` Bart Schaefer
2008-02-22 15:56         ` Clint Adams
2008-02-22 17:20           ` Bart Schaefer
2008-02-23  4:31             ` Bart Schaefer
2008-02-23 17:35               ` Peter Stephenson
2008-02-22  2:53   ` Clint Adams [this message]

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=20080222025352.GA4595@scowler.net \
    --to=clint@zsh.org \
    --cc=zsh-workers@sunsite.dk \
    /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).