zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: Clinton Bunch <cdb_zsh@zentaur.org>
Cc: zsh-workers@zsh.org
Subject: Re: [RFC] adding zmktemp command
Date: Thu, 28 Mar 2019 16:36:19 +0100	[thread overview]
Message-ID: <71983-1553787379.577063@6_Yl.hHPA.g91O> (raw)
In-Reply-To: <c8ab4631-e66b-ffae-1db8-2a63e8fe2859@zentaur.org>

Clinton Bunch wrote:
> I'm thinking of adding a zmktemp command either in a new module (e.g. 

> The advantage I can see to being it's own module, is it could be 
> backported and separately packed for Long-Term Supported OS. (Mostly 
> thinking of Enterprise Linux distributions)

I doubt you'd be able to persuade such distributions to include even a
completely new and separate module.

> But it also seems like it would be a good fit into the zsh/files module 
> (mktemp and zf_mktemp instead of zmktemp)

zsh/files would mostly make sense for a mktemp builtin that closely
follows the interface of the normal mktemp Unix utility. If the focus is
to provide a consistent and convenient way to create temporary files,
then following mktemp is perhaps not the best choice. For security
reasons, an interface that returns a file handle is, I think, generally
preferred these days. Perhaps sysopen (in zsh/system) could accept a -t
option instead of a filename.

Oliver

  parent reply	other threads:[~2019-03-28 15:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20190327211847epcas2p395ce077891a4535f19e1e9605217df7c@epcas2p3.samsung.com>
2019-03-27 21:16 ` Clinton Bunch
2019-03-28  9:38   ` Daniel Shahaf
2019-03-28 15:00     ` Clinton Bunch
2019-03-28 21:13       ` Daniel Shahaf
2019-03-29 15:20         ` Clinton Bunch
2019-03-28 15:17   ` Peter Stephenson
2019-03-28 15:25     ` Clinton Bunch
2019-03-28 15:36   ` Oliver Kiddle [this message]
2019-03-28 15:40     ` Clinton Bunch
2019-03-28 20:26       ` Daniel Shahaf

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=71983-1553787379.577063@6_Yl.hHPA.g91O \
    --to=okiddle@yahoo.co.uk \
    --cc=cdb_zsh@zentaur.org \
    --cc=zsh-workers@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).